To be sure: Manually you mean that you manually switch the domoticz device On/Off and the scripts are run by Domoticz?
--> Yes
Do you see in the domoticz log file that the script is executed? Also with the timer activation? Like below
2021-04-30 18:44:01.743 Status: Executing script: /home/udoox86/domoticz/scripts/nefit-openhaard-uit.sh
Here are the log when I manually switch the domoticz device, device is On initially:
It seems that EventSystem is initialized/updated only on startup and not after a timer modification.
Then a timer modification is not taken into account while EventSystem is not restarted.
What do you think ?
Raspberry Pi Model B Rev 2, running Raspbian Buster
Domoticz Version: 2021.1 release (build 13191)
Build Hash: 8547c5b7e
Compile Date: 2021-04-17 17:29:11
dzVents Version: 3.1.7
Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
This looks indeed an issue. I believe that every night at 24.00 hrs the event system is reset.
I did a test too for checking your issue and for me the timer was triggered just after the change so your conclusion is not always true. But I also noticed that only the off action was triggered and not the Off.
But perhaps someone will react that has more knowledge about the event system and timer functions.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
waltervl wrote: ↑Friday 30 April 2021 21:24
But perhaps someone will react that has more knowledge about the event system and timer functions.
@waltervl @melbourne,
from your profiles it looks like you are on different builds.
The issue is not so much on the eventsystem itself but an added or updated timer will only become active after a reset of all device statuses...
or after some minutes. So if I add a timer for 22:14 at 22:13:02 it will not be picked up the next minute but a timer for 22:14 entered at 22:11:30 will be picked up at 22:14.
You can force a reset of all device statuses in many ways. An easy way is to add or delete a char from the description in the device edit window.
Thanks Waaren and Waltervl for your test and informations.
@Waaren
The issue is not so much on the eventsystem itself but an added or updated timer will only become active after a reset of all device statuses...
or after some minutes. So if I add a timer for 22:14 at 22:13:02 it will not be picked up the next minute but a timer for 22:14 entered at 22:11:30 will be picked up at 22:14.
You can force a reset of all device statuses in many ways. An easy way is to add or delete a char from the description in the device edit window.
I agree with your tests.
I expected an "Event reset" after switch timer update/modification and not only after modification in the device edit window.
-> Maybe an evolution request to trig an "Event reset" after switch timer update/modification and/or that will be take into account after some minutes ?
