After the upgrade to v3.0.3, the Schedules (in Automation menu) seem to trigger differently. I have a DummyDevice that is associated (Association app) to a CodeDevice which sends a HTTP request to trigger a wifi plug. When the DummyDevice is triggered by a Schedule the log looks like:
Code: Select all
[2020-02-03 07:12:00.150] [I] [core] --- DummyDevice_100 performCommand processing: {"0":"off"}
[2020-02-03 07:12:00.159] [I] [core] Notification: device-info (device-OnOff): {"dev":"Plug_dd","l":"off","location":""}
[2020-02-03 07:12:00.162] [I] [core] --- Code_Device_switchBinary_99 performCommand processing: {"0":"off"}
[2020-02-03 07:12:00.450] [I] [core] Notification: device-info (device-OnOff): {"dev":"Nedis Plug","l":"off","location":""}
[2020-02-03 07:12:00.607] [I] [core] [BaseModule-92] Set lastLevel to off for DummyDevice_100 (was on)
[2020-02-03 07:12:00.753] [I] [core] [BaseModule-92] Set lastLevel to off for Code_Device_switchBinary_99 (was on)
But when I trigger the DummyDevice e.g. clicking in the Smart Home UI it works fine and the log shows:
Code: Select all
[2020-02-03 19:11:38.187] [I] [core] --- DummyDevice_100 performCommand processing: {"0":"off","1":{}}
[2020-02-03 19:11:38.225] [I] [core] Notification: device-info (device-OnOff): {"dev":"Plug_dd","l":"off","location":""}
[2020-02-03 19:11:38.228] [I] [core] --- Code_Device_switchBinary_99 performCommand processing: {"0":"off"}
[2020-02-03 19:11:38.403] [I] [core] Notification: device-info (device-OnOff): {"dev":"Nedis Plug","l":"off","location":""}
[2020-02-03 19:11:38.557] [I] [core] [BaseModule-92] Set lastLevel to off for DummyDevice_100 (was on)
[2020-02-03 19:11:38.703] [I] [core] [BaseModule-92] Set lastLevel to off for Code_Device_switchBinary_99 (was on)
I guess the behaviour should not be different in the two scenarios above?