ZHA - weLink CK-BL702-SWP-01(7020) switches restart every 8 - 9 minutes

[eepyaich]

The problem

I have just got 4 new Woolley smart plugs, which appear in ZHA as weLink CK-BL702-SWP-01(7020) devices. They've connected into the network fine and I can control them OK. However, every 8 or 9 minutes, they "reboot". By this, if they are switched on they switch off and then revert to their start-up behaviour. Looking at the ZHA logs, at the point this happens, I see the following warnings and debug info:

2023-10-28 10:22:48.343 WARNING (MainThread) [zigpy.zcl] [0xD864:1:0xfc11] Unknown cluster command 1 b'\x04 \x01\x00'
2023-10-28 10:22:48.343 DEBUG (MainThread) [zigpy.zcl] [0xD864:1:0xfc11] Received command 0x01 (TSN 6): b'\x04 \x01\x00'
2023-10-28 10:22:48.343 DEBUG (MainThread) [zigpy.zcl] [0xD864:1:0xfc11] No explicit handler for cluster command 0x01: b'\x04 \x01\x00'

I can't tell whether this cluster command is received after the reboot (i.e. is an effect) or is a trigger.

What I can say is that if I power down HA, then the switches don't restart, so HA does seem to be key in the issue.

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

Zigbee Home Automation

Diagnostics information

home-assistant_zha_2023-10-28T09-22-52.888Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

In the attached diags, I was specifically monitoring device D864.  I noticed the behaviour at 1013 on 28th October so turned on debug diagnostics in ZHA.  I then saw the behaviour again at 1022 and turned off debug shortly after.  The unknown cluster command that relates to this "incident" is at line 16661.

2023-10-28 10:22:48.343 WARNING (MainThread) [zigpy.zcl] [0xD864:1:0xfc11] Unknown cluster command 1 b'\x04 \x01\x00'
2023-10-28 10:22:48.343 DEBUG (MainThread) [zigpy.zcl] [0xD864:1:0xfc11] Received command 0x01 (TSN 6): b'\x04 \x01\x00'
2023-10-28 10:22:48.343 DEBUG (MainThread) [zigpy.zcl] [0xD864:1:0xfc11] No explicit handler for cluster command 0x01: b'\x04 \x01\x00'

Note - earlier in the file, you can see the same unknown cluster messages from the other 3 similar switches I have.

Additional information

• I'm using SkyConnect as my Zigbee coordinator.
• Other Zigbee switches don't exhibit this problem (for example, I've an Ikea switch which is fine).
• These switches allegedly might have power monitoring (i.e. it was mentioned in the Amazon listing and some folks in the zigbee2mqtt team mentioned this - [New device support]: CK-BL702-SWP-01(7020) Koenkk/zigbee2mqtt#19334.
• Based on that last link, I get the impression these are pretty new switches as well.

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[TheJulianJES]

Please take a backup and update to the latest Home Assistant Core 2023.11 beta.

The issue should be fixed there. (Referenced issue: #101291)

[eepyaich]

@TheJulianJES - thanks so much! That appears to have done the trick (i.e. I'm now 30 minutes post-upgrade and no rebooting switches). Much appreciated the quick response!

[relexx]

@eepyaich
Just to check: Your problem regarding reboots have been resolved, right? (Then maybe close this issue)
What about the power monitoring? Still not working, right?

[eepyaich]

Sorry - my bad. Yes, the reboot issue has been solved. Thanks again!

No - power monitoring is not available, but I can raise a separate issue about that.