Editing sensors and rules
-
@user2684
During the change of all topics of the sensors and their names it occurred that after renaming some sensors couldn't be edited the normal way. I solved it by deleting those sensors via the advanced editor and create them via the normal procedure. Thereafter they could be edited the normal way.Now I tried to clone a rule. After cloning it could not be edited. So I did the trick which worked for sensors and deleted the rule via the advanced editor. I created a rule from scratch and guess what... it was not editable. Also I could not run it manually. No reaction at all.
Logs showed nothing unusual.
-
@user2684
Stopped and started eGeoffrey. Cleaned history.
Did not change anything.
I can not edit the new rule.
-
@user2684
I cloned an example rule again and now I can edit it.
Every now and then eGeoffrey is a weird guy.
-
When I clone the high humidity rule and give it the name "Test" everything is ok. I can edit it.
When I clone again and call it "Local humidity" I can not edit it.What's in a name?
-
The answer to that question is a "space".
Do not use any space in a name but apply an underscore instead.
-
Yeah, spaces could be problematic for identifiers, you should see some errors showing up in the logs. But validation should be up to the gui... https://github.com/egeoffrey/egeoffrey-gui/issues/75
closed Check allowed characters for identifiers #75
-
-
@eporocrail any warning/error either in the browser console log or in eGeoffrey logs? If not, anything related to the configuration change showing up in eGeoffrey logs upon your action? Thanks
-
No log entry. This one I deleted via advanced editor.
But two days ago something very weird happened. The main examples popped-up again.
I was not able to delete them. I checked the .env file. Was OK.I used the advanced editor. I could not delete the stuff.
TZ=Europe/Amsterdam EGEOFFREY_CONFIG_ACCEPT_DEFAULTS=0
The last one is the error message after deleting with advanced manager
-
Clearing browser history does not solve the problem.
-
@user2684
Solved the issue by activating creation of examples (.env file setting), stop and start. All examples were there. Then deleted all examples and modified .env again.
-
Kind of a weird behaviour, I'm happy you solved the issue but cannot really imagine what caused it or went wrong...anyhow, let me know if this will happen again
