thanks for the quick reply and the clear explanation.

In DzVents time triggered script, immediately after switchOn a device, the active status is still false. switchEventTestSwich.switchOn() if switchEventTestSwich.active then ... never getting here else ... end On next run of the script, the active status is correct. Am I missing something ? I have ...

I have enabled more debugging.
For me, the log does not show anything of importance.
I do notice, that with all the logging, the expected dzVent happens with much less time lag, which is strange.
I turned-off logging yesterday, and a dzVent came in about 5 hours later again....

I turned on debug and logging to a file. I see differences with respect to time after restart. Shortly after restart the trigger fires as expected (within one second), look at 103/GeoIPThuis/On 2021-05-30 22:56:11.402 Status: User: Admin (IP: 192.168.180.30) initiated a switch command (103 ...

Maybe I cheered a bit too early. It appears that after some time, the event processing gets delayed. The delay seems to increase with time, until it seems that at some point in time, nothing seems happens anymore or it is untracable what is (not) happening. Restarting domoticz solves this, however ...

I found some time to try your last remark.

Updating to the latest version by commandline helped.

The event is now triggered when I hit the switch with id 113.
It looks like I can get on now with my script.

thanks a bunch

Really appreciate your help.

I figured to do an update earlier, but when I hit the 'check for update' I get 'No Update Available !...'

I have attached the generated file.
After activating the debug, I hit the switch 'eventTestSwich'from off to on to off to on to off.
I peeked in the file, but dunno what to look for.
Hope this helps

http://pi:8080/json.htm?type=hardware { "result" : [ { "Address" : "", "DataTimeout" : 0, "Enabled" : "true", "Extra" : "", "Mode1" : 0, "Mode2" : 0, "Mode3" : 0, "Mode4" : 0, "Mode5" : 0, "Mode6" : 0, "Name" : "slimmeMeter", "Password" : "", "Port" : 0, "SerialPort" : "/dev/ttyUSB1", "Type" : 4 ...

http://pi:8080/json.htm?type=devices&rid=113 { "ActTime" : 1618431602, "AstrTwilightEnd" : "22:42", "AstrTwilightStart" : "04:29", "CivTwilightEnd" : "21:07", "CivTwilightStart" : "06:04", "DayLength" : "13:52", "NautTwilightEnd" : "21:52", "NautTwilightStart" : "05:19", "ServerTime" : "2021-04-14 ...

Are device 103 and 100 set to active? (Are the arrows on devices tab blue?)

Yes they are blue

As mentioned earlier, typos on the idx, should have been 113 and 110, scripts are fine.
Both are blue, only 110 appears in the log (due to wildcard)

How can I debug this ?

The dummy (problem) switch has Idx 113.

I mistakenly mentioned 103, should have been 113.
Sorry about the confusion.

The wildcard '*'' results in the logging of one device with id 110 in the log. When I flip the switch device 103, the event is not triggered. Device 103 and 100 are of exactly the same type 'type Light/Switch, Switch, On/Off' I read in some old posts that there might be a conflict with other scripts ...

I cannot get an dzVents script to be triggered. I want to handle status change of a dummy switch. This is my script: -- eventTestSwich.lua return { on = { devices = { 113 } }, logging = { level = domoticz.LOG_INFO, marker = "I am eventTestSwich script....." }, execute = function(domoticz, device ...