Scheduled "turn group off" is reverted a couple seconds later

[jo-me]

Describe the bug

I have a dead simple schedule for christmas lights that is not working correctly.

Involved is only one Blitzwolf smart plug (BW-SHP13) which I added to a group as the only item. The schedule e.g. says activate scene "turned on" at 07:00 and "turn group off" at 09:00.

At 7:00, the plug is turned on fine and at 9:00 it is switched off. However, a couple seconds later (5-15s) it is automatically turned back on and I cannot figure out why.

If I turn off the group manually, it will stay off until the next scheduled activation.

Since it is a new plug that I have not used before there is also no other automation that could involve it.

Please advise. Thanks

Steps to reproduce the behavior

Happens every time the "turn group off" action is executed.

Expected behavior

Group should remain off

Screenshots

I've tracked the state in home assistant to better illustrate this:

Logs of this time period are below.

Environment

• Host system: Ubuntu 18.04
• Running method: Marthoc Docker container
• Firmware version: 26400500
• deCONZ version: 2.12.06 / 19.8.2021
• Device: ConBee I
• Do you use an USB extension cable: yes
• Is there any other USB or serial devices connected to the host system? Zwave stick

deCONZ Logs

20:55:52:606 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:55:53:614 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:00:230 schedule 16: Lichter wieder aus trigger, 20:56:00:231 schedule 16 body: {"bri":0,"on":false,"transitiontime":0}, 20:56:01:601 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:02:610 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:04:066 ZCL attribute report 0x00158D00034448B6 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:06:595 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:07:603 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:08:323 Device TTL 5880 s flags: 0x7, 20:56:08:612 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:14:598 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:15:606 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:18:135 ZCL attribute report 0x00158D0003280EEA for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:18:600 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:19:608 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 , 20:56:21:400 Bind response success for 0x60a423fffeff4792 ep: 0x01 cluster: 0x0B04, 20:56:21:855 Websocket disconnected 192.168.178.5:61747, state: 0, close-code: 1001, reason: , 20:56:22:601 ZCL attribute report 0x00158D0001FE558C for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode:

Additional context

[Mimiix]

Hi,

As this seems to be a bug within Phoscon and not deCONZ, i'm moving this to the phoscon repository. I am currently not sure if they log bugs there or on the Forums.

Kind regards,

[stale[bot]]

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[stale[bot]]

As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again.