Some screenshots of the system as it is now: On this part of the page one can select a sensor and change the values of the aspects. "kies sensor" is used to select a sensor. "bevestig bericht" transmits an acknowledgement. On receipt the changes are performed. "opvragen data" facilitates querying a sensor. under "data" the value of all aspects are displayed. "reset module" enforces resetting the aspects to their default values. "totaal" designates the buttons to change settings of all sensors together

@eporocrail correct, I wanted to be sure users have maximum flexibility in manipulating their data. So yes, you can do something like the followin: BOOL_TO_UPDOWN: echo 'print "up" if "%value%"=="1" else "down"' | python Of course this can become a bit complex for more sophisticated requirements.

IMHO the use of SSO is being sure that when I log out I have logged out for everything. The same for logging in.

Got it! https://github.com/egeoffrey/docs.egeoffrey.com/issues/7 user2684 created this issue in egeoffrey/docs.egeoffrey.com open Add backup/restore procedure description #7

Thanks! https://github.com/egeoffrey/egeoffrey-gui/issues/62 user2684 created this issue in egeoffrey/egeoffrey-gui open Input widget with 2 decimals support #62

@user2684 Thanks for the info. I will do some further experiments when all aspects of my control page are working (almost there).

@user2684 I think I had a glitch somewhere. It is OK now. So forget about this one.

Try adding in the .env file the following and restart eGeoffrey (https://developer.egeoffrey.com/learn/components/controller/#advanced-settings EGEOFFREY_CONFIG_ACCEPT_DEFAULTS=0 Remember this will be overwritten if setup is run again. Once restarted you can delete the examples and they will never show up again. Better examples management is definitely something to be reviewed (https://github.com/egeoffrey/egeoffrey-controller/issues/19) user2684 created this issue in egeoffrey/egeoffrey-controller open Better way to manage examples #19

@eporocrail You're right, documentation is lacking here (https://github.com/egeoffrey/docs.egeoffrey.com/issues/6). The button widget does not link with any sensor but uses the same format as the "Actions" you have in the rules in which you can: Set value to a sensor (SET sensor_id value). If the sensor is an actuator of course this will be also sent along Run a rule (RUN rule_id) Poll a sensor configured in pull mode (POLL sensor_id) user2684 created this issue in egeoffrey/docs.egeoffrey.com open Detailed explanation of every UI widget #6

@user2684 Thanks for the update. Works for me.

@user2684 I think the point in time approaches where I have to spend some time to get familiar with the advanced editor.

@eporocrail said in Google Assistant Integration: Yes, I would like to participate. Thanks! It will still take a while since there are things to do in the backend and the integration has to go eventually through Google before being published but I will let you know once ready. Thanks!

@eporocrail said in My general sensor system: When looking into another problem I discovered that I had introduced the leading "/" myself, while there is no real need to do it. So just forget this issue. Well, there was an issue indeed with the MySensors module actually and even if not completely related this has helped me in identifying it. So was useful anyhow

@user2684 I expanded the documentation a little. I aim for simplicity as far as possible: Module control One software package Sensor always active, interrupt driven. Switch interrupt driven. Switched port activated by MQTT message from eGeoffrey. Ad sensor sub-PCB for sensor activity. Ad switch for switch control of system activation. Ad accessories to module for external alert. Sensor and switch do not require system configuration. They are interrupt driven. External accessories do not require system configuration because they are activated via MQTT by eGeoffrey. To address an individual module the ID of that module is required. This ID is part of the topic for activating that module. The option will be implemented.

@user2684 It is a tough job to prevent the user from making all possible mistakes. But I get to like your system more and more as I get to know it better. You do a formidable job creating eGeoffrey.

Ok, good! Next time it will happen give an eye at the logs to ensure there is no errors, the configuration files are correctly saved and the configuration reloaded, something like egeoffrey-controller_1 | [2020-07-01 09:38:24][controller/config] INFO: Saved configuration file gui/users (v1) egeoffrey-controller_1 | [2020-07-01 09:38:29][controller/config] INFO: Configuration successfully published

@eporocrail perfect, got it and tracked with https://github.com/egeoffrey/egeoffrey-gui/issues/48 user2684 created this issue in egeoffrey/egeoffrey-gui open Streamline page management capabilities #48