@user2684 It is not trivial. Through a sensor alerts are arriving. Sometimes such an alert is false. An alert is converted into an alarm when the period between alerts is larger than 2 seconds and smaller than 9 seconds. When an alert arrives the timestamp is stored. When the following alert arrives it's timestamp needs to be compared with the stored one. At the same time it tries to store it's timestamp. Storing the timestamp only when there is a delta of 1 between the stored one and the new one does not work. Any suggestions? Using COUNT is even more complex, because of the already addressed COUNT issue.

@user2684 Setting to "0" is seen as a trigger and the counter is increased by 1.

@user2684 The timeline widget is displaying quite nice. The only point is that retrieving of historical data does not work at all in my case. Even going back 1 day is not working. The fields "From" and "To" do not accept any change. They revert back to the default. The other selections are greyed out, but that might be caused by lack of data or missing data of an intermediate period. Your action please.

@user2684 Just put the name of the page in the mentioned field, save. Start your browser, CLEAR HISTORY. Now it works. Guest gets the page presented which is set-up.

@user2684 Yes, that works.

@user2684 I see what you mean. In the mean time I took a look at other comparable software. All do the same. So, one has to be aware what the target display will be for the system and design the GUI for that display.

Understood! Yes, noticed something similar as well

The idea is you add a list of placeholders and for each one of those the rule will run independently replacing the %i% with the placeholder. If e.g. you have two sensors you want to apply the same logic to, you add sensor1 and sensor2 to the macro page and use %i% wherever you would have used the sensor. %ph% is not a valid placeholder that's why it is not working, you need to use %i%

@eporocrail said in Feed/Notifiction/Log: My problem was that I did not recollect that I had to set the severity of a rule to "NONE" to get rid of pop-ups. "none" and "debug" severity really deserve a better naming and explanation, point taken. Thanks!

@user2684 What I am aiming for is that when a sensor message arrives the time of arrival is displayed with a widget. I would like to use this facility to do several power supply tests. As long as power supply is OK the time display is kept up to date. As soon as the power supply is not there any more, the time of the last message is preserved. This way I do have a way to see how long a certain battery type is able to power a certain module with a certain load.

Ok, let me keep track with https://github.com/egeoffrey/egeoffrey-gui/issues/77 and I'll give it a in depth look during the weekend. Thanks! user2684 created this issue in egeoffrey/egeoffrey-gui open Delete page not working #77

@user2684 I never observed this.

@user2684 Yes that is the reason. First I will explore the raspi track. If that succeeds it is fine with me. Otherwise I have to revert to the laptop. What I am aiming for is a as minimalistic set-up as possible. On a Raspi eGeoffrey with a hotspot. The sensor/actuator modules on ESP8266 in a Esp8266MQTT mesh network. It should be possible to get it working. Until now at some point in time it is not possible to get access with a browser via the hotspot after logging in into the hotspot. This issue I have to explore to find out what causes this. If it turns that there is no other way than accessing eGeoffrey via a browser on the machine running the hotspot and eGeoffrey then I will switch to the laptop track.

@user2684 That could be the reason why it started working later on.

@eporocrail said in Conflict eGeoffrey with hotspot on Raspi: Do not back-up from a different system. Just start from scratch. Shouldn't be the case...wonder if there is already an eGeoffrey running after installation while you try to start the one you have just restored...

ok so the issue was with the delete action from the gui. I'd be interested when deleting what showed up in the logs, if a delete successful or an error but nevermind for now, if will happen again then could be something to look at. Thanks

@eporocrail said in Problem with a rule: The data format in the sensor is set to integer. Looks like you are trying to save into the sensor "clck/slr/sec" which is of type int the string "second" how can I copy the content of a widget into an other sensor which is used as location to store that value? Isn't the input widget doing this job?

@user2684 OK

@eporocrail said in Create a weather station: https://pypi.org/project/buienradar/ Sure let me have a look and I'll let you know. I've also linked this fantastic guide from https://docs.egeoffrey.com/howto/

Also the eGeoffrey Android app (https://play.google.com/store/apps/details?id=com.egeoffrey.app) has been just updated with the latest GUI changes listed above.