Zigbee smart plugs turning off on their own randomly - Not Tuya TS001F Issue #101291

Technoholic84 · 2023-10-02T19:14:44Z

The problem

Since upgrading to 2023.9.3, all my zigbee smart plugs have been turning themselves off randomly, but usually all within a few minutes of each other. All it shows in the logbook is this:

It does not show that it has been triggered by an automation or a manual button press, because it hasn't, it just turns off. This is with a Sonoff Dongle-P. I thought this was because I had migrated to a new machine but it seems that the actual problem is due to 2023.9.3 because when reverting to a backup of 2023.8.4, the problem is no longer there.

There was zero problems before I migrated, and the old machine was also running 2023.8.4. Since upgrading the old machine to 2023.9.3 and putting that back into use, the problem also occurs on that machine too, so it definitely seems to be something in 2023.9.3

What version of Home Assistant Core has the issue?

core-2023.9.3

What was the last working version of Home Assistant Core?

core-2023.8.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zigbee ZHA

Link to integration documentation on our website

No response

Diagnostics information

config_entry-zha-18c9e8603b58b3ffb5155c5df3d49529.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

kevinklinkmuller · 2023-10-03T22:45:15Z

Same exact issue since the new update. All zigbee plugs (in my case Woolley) turn off every 1.2 hours. All of them in roughly the same time.
activity shows just “turned off” and that’s it.

Technoholic84 · 2023-10-03T22:58:46Z

Mine are Woolley too! I wonder what the issue is in the latest release. I’ve just reverted back to 2023.8.4 again and it’s gone away

Technoholic84 · 2023-10-04T19:49:20Z

Problem still exists in 2023.10, having to roll back to 2023.8.4 again

kevinklinkmuller · 2023-10-04T20:27:56Z

Same, roll back solved it

TheJulianJES · 2023-10-05T15:55:55Z

Please upload the device diagnostic information for the affected plugs.

Technoholic84 · 2023-10-05T16:00:20Z

Please upload the device diagnostic information for the affected plugs.

Not sure exactly how to get that, I'm a fairly new user but also, given that I've downgraded to 2023.8.4 where it's working, I guess the diagnostics will not be useful?

Technoholic84 · 2023-10-10T08:40:54Z

Please upload the device diagnostic information for the affected plugs.

@TheJulianJES

Hi, is there anything that we can do to get this investigated? I am stuck on an older version now, not a big problem at the moment but as things change more, it would be good to be able to upgrade

home-assistant · 2023-10-11T14:37:41Z

Hey there @dmulcahey, @Adminiuga, @puddly, 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)}}

puddly · 2023-10-11T14:40:26Z

@Technoholic84 without diagnostic info there's no way to tell what device you're using. Can you upload it the same way you did for the whole integration?

Technoholic84 · 2023-10-11T14:42:13Z

zha-18c9e8603b58b3ffb5155c5df3d49529-Sonoff SA-030-1-f12d3f0f6f6db027e1ba2d3e4f1e8314.json-2.txt

Technoholic84 · 2023-10-11T14:42:20Z

Hopefully that works

TheJulianJES · 2023-10-11T18:58:50Z

So are only those "Sonoff SA-030-1" plugs affected or also plugs from other manufacturers?

It seems like Sonoff did wonders with their Zigbee implementation and Z2M needs to work around multiple issues:

skip sending default response (and relevant zigbee-herdsman code for sending default response)
ignore messages with same TSN, code here

I don't think these issues should cause the plug to randomly turn off though? (unless it maybe crashes and then turns off?)
(And I'm also not sure if both fixes are actually needed for that plug. It seems like they were added without explanation in a PR)

Technoholic84 · 2023-10-11T19:02:00Z

Yes only those plugs and they are branded as “Woolley” over here but yes it’s only those. I don’t know if that would cause them to randomly turn off, I’m not using z2m. The only thing I can do to stop it is to downgrade to 2023.8.4, the moment I move back to 2023.9.3 it starts happening again

TheJulianJES · 2023-10-11T19:06:15Z

I just wanted to check Z2M implementation to see if they had fixed some issue regarding this. It doesn't look like there's anything that would affect the plug turning off randomly though.

Did you try updating to HA 2023.10.x to see if the issue is maybe resolved there?
Also, you're running a ZBDongle-E with the stock firmware, right? The firmware should be fine, but you could also try updating the EZSP version of it: https://darkxst.github.io/silabs-firmware-builder/ (<- haven't tested this, but should be fine)

Also, you could try the following: turn on both plugs, unplug the Zigbee coordinator, see if the plugs still turn off.
(Obviously, your Zigbee network wouldn't work for the time your stick is unplugged)

Lastly, debug logs (can be turned on using integration page) for when the plugs turn off could help too.

Technoholic84 · 2023-10-11T19:13:44Z

Yes 2023.10.1 does the same thing. It’s a Dongle -E yes with the firmware that came with it.

I’ll need to upstage the software again and then try those tests as there’s no point doing it now. Let me try that and see what happens. I’ll reply when I have some information.

Technoholic84 · 2023-10-11T19:59:58Z

I upgraded to 10.1 just after my last message. About 20 mins later and they turned off again. Debug logs to follow shortly…

Technoholic84 · 2023-10-11T20:03:12Z

config_entry-zha-18c9e8603b58b3ffb5155c5df3d49529.json-3.txt

here you go.

puddly · 2023-10-11T20:38:31Z

@Technoholic84 Debug logging is accessible from the integration's menu. Enable it, reproduce the problem, and then disable it:

Technoholic84 · 2023-10-11T20:40:52Z

Yes that’s what I did, and attached the logs above

puddly · 2023-10-11T20:46:14Z

You attached the diagnostics information for the config entry, which doesn't include any logs:

Debug logging is enabled with the option I have highlighted in the previous comment.

Technoholic84 · 2023-10-11T20:47:17Z

I have debug logging enabled but which file do I need to upload? The main home assistant log?

Technoholic84 · 2023-10-11T20:50:30Z

home-assistant_2023-10-11T20-47-45.750Z.log

Is this the right log? The time of the event was about 20:57

puddly · 2023-10-11T21:14:02Z

Interesting. The plug seems to crash/reboot after trying to ask for an OTA update.

This log looks like it's from 2023.10.x. Could you generate a similar debug log with 2023.9.3? If it doesn't do the same thing, just leave debug logging running for a few hours and ZIP up the resulting log file

Here's only the relevant info, with a few annotations:

# The plug periodically reports that it is on
2023-10-11 20:28:37.893 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=105), 132, -67, 0xb9e9, 255, 255, b'\x18\x06\n\x00\x00\x10\x01']
2023-10-11 20:28:37.893 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=105), 132, -67, 0xb9e9, 255, 255, b'\x18\x06\n\x00\x00\x10\x01']
2023-10-11 20:28:37.894 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xB9E9), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=105, profile_id=260, cluster_id=6, data=Serialized[b'\x18\x06\n\x00\x00\x10\x01'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=132, rssi=-67)
2023-10-11 20:28:37.894 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Received ZCL frame: b'\x18\x06\n\x00\x00\x10\x01'
2023-10-11 20:28:37.895 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=0, direction=<Direction.Client_to_Server: 1>, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=6, command_id=10, *direction=<Direction.Client_to_Server: 1>)
2023-10-11 20:28:37.896 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Decoded ZCL frame: OnOff:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.true: 1>))])
2023-10-11 20:28:37.896 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Received command 0x0A (TSN 6): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.true: 1>))])
2023-10-11 20:28:37.897 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Attribute report received: on_off=<Bool.true: 1>

# Exactly 15 minutes later, it again reports that it is still on
2023-10-11 20:43:37.907 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=106), 148, -63, 0xb9e9, 255, 255, b'\x18\x07\n\x00\x00\x10\x01']
2023-10-11 20:43:37.907 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=106), 148, -63, 0xb9e9, 255, 255, b'\x18\x07\n\x00\x00\x10\x01']
2023-10-11 20:43:37.908 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xB9E9), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=106, profile_id=260, cluster_id=6, data=Serialized[b'\x18\x07\n\x00\x00\x10\x01'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=148, rssi=-63)
2023-10-11 20:43:37.908 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Received ZCL frame: b'\x18\x07\n\x00\x00\x10\x01'
2023-10-11 20:43:37.909 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=0, direction=<Direction.Client_to_Server: 1>, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=7, command_id=10, *direction=<Direction.Client_to_Server: 1>)
2023-10-11 20:43:37.910 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Decoded ZCL frame: OnOff:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.true: 1>))])
2023-10-11 20:43:37.910 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Received command 0x0A (TSN 7): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.true: 1>))])
2023-10-11 20:43:37.911 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Attribute report received: on_off=<Bool.true: 1>

# Plug sends an active endpoint request to the coordinator??
2023-10-11 20:57:46.876 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=0, clusterId=5, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=107), 144, -64, 0xb9e9, 255, 255, b'\x1d\x00\x00']
2023-10-11 20:57:46.877 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=0, clusterId=5, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=107), 144, -64, 0xb9e9, 255, 255, b'\x1d\x00\x00']
2023-10-11 20:57:46.877 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xB9E9), src_ep=0, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=0, source_route=None, extended_timeout=False, tsn=107, profile_id=0, cluster_id=5, data=Serialized[b'\x1d\x00\x00'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=144, rssi=-64)
2023-10-11 20:57:46.878 DEBUG (MainThread) [zigpy.zdo] [0xb9e9:zdo] ZDO request ZDOCmd.Active_EP_req: [0x0000]
2023-10-11 20:57:46.878 DEBUG (MainThread) [zigpy.zdo] [0xb9e9:zdo] No handler for ZDO request:ZDOCmd.Active_EP_req([0x0000])

# Then tries to perform an OTA update
2023-10-11 20:57:54.758 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=25, sourceEndpoint=1, destinationEndpoint=255, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=58), 144, -64, 0xb9e9, 255, 255, b'\x01\x01\x01\x00\x86\x12\x00\x00\x01\x00\x00\x00']
2023-10-11 20:57:54.758 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=25, sourceEndpoint=1, destinationEndpoint=255, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=58), 144, -64, 0xb9e9, 255, 255, b'\x01\x01\x01\x00\x86\x12\x00\x00\x01\x00\x00\x00']
2023-10-11 20:57:54.758 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xB9E9), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=255, source_route=None, extended_timeout=False, tsn=58, profile_id=260, cluster_id=25, data=Serialized[b'\x01\x01\x01\x00\x86\x12\x00\x00\x01\x00\x00\x00'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=144, rssi=-64)
2023-10-11 20:57:54.759 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] Received ZCL frame: b'\x01\x01\x01\x00\x86\x12\x00\x00\x01\x00\x00\x00'
2023-10-11 20:57:54.760 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.CLUSTER_COMMAND: 1>, is_manufacturer_specific=0, direction=<Direction.Server_to_Client: 0>, disable_default_response=0, reserved=0, *is_cluster=True, *is_general=False), tsn=1, command_id=1, *direction=<Direction.Server_to_Client: 0>)
2023-10-11 20:57:54.761 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] Decoded ZCL frame: Ota:QueryNextImageCommand(field_control=<FieldControl: 0>, manufacturer_code=4742, image_type=0, current_file_version=1)
2023-10-11 20:57:54.761 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] Received command 0x01 (TSN 1): QueryNextImageCommand(field_control=<FieldControl: 0>, manufacturer_code=4742, image_type=0, current_file_version=1)
2023-10-11 20:57:54.762 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] OTA query_next_image handler for 'Sonoff SA-030-1': field_control=0, manufacturer_id=4742, image_type=0, current_file_version=1, hardware_version=None, model='SA-030-1'

# There's no available image for the plug so we tell the plug there is no image
2023-10-11 20:57:54.762 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] No OTA image is available
2023-10-11 20:57:54.763 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] Sending reply header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.CLUSTER_COMMAND: 1>, is_manufacturer_specific=False, direction=<Direction.Client_to_Server: 1>, disable_default_response=1, reserved=0, *is_cluster=True, *is_general=False), tsn=1, command_id=2, *direction=<Direction.Client_to_Server: 1>)
2023-10-11 20:57:54.764 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0019] Sending reply: query_next_image_response(status=<Status.NO_IMAGE_AVAILABLE: 152>, manufacturer_code=None, image_type=None, file_version=None, image_size=None)
2023-10-11 20:57:54.764 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xB9E9), dst_ep=1, source_route=None, extended_timeout=False, tsn=1, profile_id=260, cluster_id=25, data=Serialized[b'\x19\x01\x02\x98'], tx_options=<TransmitOptions.ACK: 1>, radius=0, non_member_radius=0, lqi=None, rssi=None)
2023-10-11 20:57:54.765 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendUnicast: (<EmberOutgoingMessageType.OUTGOING_DIRECT: 0>, 0xb9e9, EmberApsFrame(profileId=260, clusterId=25, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=1), 29, b'\x19\x01\x02\x98')

# The plug instantly shuts off??
2023-10-11 20:57:54.770 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=59), 144, -64, 0xb9e9, 255, 255, b'\x18\x02\n\x00\x00\x10\x00']
2023-10-11 20:57:54.770 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=59), 144, -64, 0xb9e9, 255, 255, b'\x18\x02\n\x00\x00\x10\x00']
2023-10-11 20:57:54.771 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xB9E9), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=59, profile_id=260, cluster_id=6, data=Serialized[b'\x18\x02\n\x00\x00\x10\x00'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=144, rssi=-64)
2023-10-11 20:57:54.771 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Received ZCL frame: b'\x18\x02\n\x00\x00\x10\x00'
2023-10-11 20:57:54.772 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=0, direction=<Direction.Client_to_Server: 1>, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=2, command_id=10, *direction=<Direction.Client_to_Server: 1>)
2023-10-11 20:57:54.773 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Decoded ZCL frame: OnOff:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.false: 0>))])
2023-10-11 20:57:54.773 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Received command 0x0A (TSN 2): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.false: 0>))])
2023-10-11 20:57:54.773 DEBUG (MainThread) [zigpy.zcl] [0xB9E9:1:0x0006] Attribute report received: on_off=<Bool.false: 0>

Technoholic84 · 2023-10-11T21:18:34Z

Ok thank you for analysing that. I don’t have a 9.3 backup I don’t think so I need to restore the 8.4, then upgrade to 9.3 and then enable debug logging at that time. It’s nighttime here now so the lights will be off soon anyway so I will get this done and then upload a log asap.

Thanks again

Technoholic84 · 2023-10-12T10:39:32Z

Hi again,

So I upgraded to 9.3 yesterday, and this morning turned the lights on, as predicted, switched off not long after. Here's the (big) log, and the turn off happened at 09:16 approx.

home-assistant_2023-10-12T10-37-33.699Z.log.zip

Technoholic84 · 2023-10-12T14:59:23Z

Sorry I just realised I maybe misread your request. Did you want a log from a version where the problem DOES NOT happen?
If so I need to do that on 8.4

Technoholic84 · 2023-10-19T14:26:24Z

Hi there, is there any update on this at all?

Technoholic84 · 2023-10-20T07:13:43Z

Hi @puddly i see this issue is closed now. Which is good, but Can someone explain how it was fixed and what the problem was? Thanks!

crameth · 2023-10-20T18:19:37Z

Had the same issue. Mine was about every 6-7 minutes on... you guessed it, Woolley smart plugs.

Using the dev release for HA Docker fixed the issue for me (2023.11.0). Prior to this I was using stable (2023.10.3), which I think was already identified as a problematic version on this thread.

Hope this helps.

EDIT: Thanks for bringing this up @Technoholic84, was crawling the internet in search of a solution and almost demanded a refund for the "faulty" plugs.

Technoholic84 · 2023-10-20T18:59:15Z

Had the same issue. Mine was about every 6-7 minutes on... you guessed it, Woolley smart plugs.

Using the dev release for HA Docker fixed the issue for me (2023.11.0). Prior to this I was using stable (2023.10.3), which I think was already identified as a problematic version on this thread.

Hope this helps.

EDIT: Thanks for bringing this up @Technoholic84, was crawling the internet in search of a solution and almost demanded a refund for the "faulty" plugs.

Thanks for sharing, I will try upgrading to the dev release later, see if that helps. I dont seem to be able to find a 10.4 beta which would be preferable but glad your issue is fixed, let's hope it does it for me too!

crameth · 2023-10-20T19:10:54Z

Sorry, I jumped the gun. My plugs are still turning themselves off with the latest version :/

I might want to downgrade if that's the case, see if it fixes the issue.

Technoholic84 · 2023-10-20T21:02:49Z

Yep I upgraded to 11.0 and it still happened. It looks like the fix, if it works, was put into 10.4 but I can’t find a way to install that

joostlek · 2023-10-20T21:05:03Z

10.4 will be released tomorrow

Technoholic84 · 2023-10-20T21:06:00Z

Ah that’s great. I assume this fix is in that version?

joostlek · 2023-10-20T21:07:15Z

The PR that closed this issue is in there. But this PR is also in 2023.11, so if you have issues on dev, it most likely won't be fixed by the next release

Technoholic84 · 2023-10-20T21:08:53Z

Oh that’s a shame. Yes it’s not working in 2023.11, turns off as it always has.

joostlek · 2023-10-20T21:10:20Z

I'll reopen the issue then

Technoholic84 · 2023-10-20T21:11:17Z

Thank you very much

puddly · 2023-10-20T21:15:57Z

I'll order a few of these plugs to test, as I'm out of ideas otherwise. Hopefully the US version has the same problem.

zwack-am · 2023-10-21T01:31:15Z

It does... at least these ones that I bought from Amazon randomly turn themselves off. CMARS Smart Plug, ZigBee Switch Mini Smart Outlet Works with ST, Alexa, Echo (4th gen) Echo Plus (2nd) Google Home, Works as a Range Extender, Hub Required （2 Pack） https://a.co/d/0sS1oAO

…

On October 20, 2023 2:16:08 PM PDT, puddly ***@***.***> wrote: I'll order a few of these plugs to test, as I'm out of ideas otherwise. Hopefully the US version has the same problem. -- Reply to this email directly or view it on GitHub: #101291 (comment) You are receiving this because you commented. Message ID: ***@***.***>

Technoholic84 · 2023-10-21T22:39:52Z

I don’t want to say it’s 100% confirmed yet but I did install 10.4 today and the plugs have been on for longer than I would expect before normally having this issue. @joostlek are you sure the PR related to this was in the 11.0 dev release? Because 10.4 so far is looking promising…

joostlek · 2023-10-21T23:16:55Z

Dev is always the latest. But it could be that your system didn't fully install the right dependencies, but I'm not sure about that

Technoholic84 · 2023-10-21T23:19:37Z

Well I’ll test again tomorrow but after installing 10.4 I had those plugs on for 3 hours and they didn’t turn off. I would have expected them to turn off at least once, maybe twice in that time. So let me see how it goes tomorrow and I’ll report back and maybe send some debug logs

byannnn · 2023-10-22T05:44:17Z

I downgraded to 8.4 and everything is working fine, but I'm keen to test out 10.4 too. Will update later tonight and report back if it fixes the problem.

puddly · 2023-10-22T13:59:03Z

2023.10.5 reverts this change due to a bug with some coordinators so I recommend skipping it if you're testing this change out: https://github.com/home-assistant/core/releases/tag/2023.10.5

It will again be in the 2023.11.0 beta scheduled for next week.

Technoholic84 · 2023-10-22T14:08:29Z

So will this fix be back in a future release or will it be removed from future releases too?

Technoholic84 · 2023-10-22T15:19:13Z

The plugs have been on for 8 hours and they haven’t turned off, so I think that is fixed, but if the fix is going to be removed then I’ll have to stay on 10.4

Technoholic84 · 2023-10-24T17:43:43Z

Can someone confirm which version will bring back this fix?

puddly · 2023-10-24T19:57:06Z

It will again be in the 2023.11.0 beta scheduled for tomorrow.

joostlek added the integration: zha label Oct 11, 2023

home-assistant bot assigned dmulcahey, Adminiuga and puddly Oct 11, 2023

puddly mentioned this issue Oct 19, 2023

Bump ZHA dependencies #102358

Merged

20 tasks

frenck closed this as completed in #102358 Oct 20, 2023

joostlek reopened this Oct 20, 2023

puddly mentioned this issue Oct 25, 2023

Bump ZHA radio dependencies #102750

Merged

20 tasks

puddly closed this as completed in #102750 Oct 25, 2023

TheJulianJES mentioned this issue Oct 28, 2023

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

Closed

github-actions bot locked and limited conversation to collaborators Nov 24, 2023

Zigbee smart plugs turning off on their own randomly - Not Tuya TS001F Issue #101291

Zigbee smart plugs turning off on their own randomly - Not Tuya TS001F Issue #101291

Comments

Technoholic84 commented Oct 2, 2023

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

kevinklinkmuller commented Oct 3, 2023

Technoholic84 commented Oct 3, 2023

Technoholic84 commented Oct 4, 2023

kevinklinkmuller commented Oct 4, 2023

TheJulianJES commented Oct 5, 2023

Technoholic84 commented Oct 5, 2023

Technoholic84 commented Oct 10, 2023

home-assistant bot commented Oct 11, 2023

puddly commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

TheJulianJES commented Oct 11, 2023 • edited Loading

Technoholic84 commented Oct 11, 2023

TheJulianJES commented Oct 11, 2023 • edited Loading

Technoholic84 commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

puddly commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

puddly commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

puddly commented Oct 11, 2023

Technoholic84 commented Oct 11, 2023

Technoholic84 commented Oct 12, 2023

Technoholic84 commented Oct 12, 2023

Technoholic84 commented Oct 19, 2023

Technoholic84 commented Oct 20, 2023

crameth commented Oct 20, 2023 • edited Loading

Technoholic84 commented Oct 20, 2023

crameth commented Oct 20, 2023

Technoholic84 commented Oct 20, 2023

joostlek commented Oct 20, 2023

Technoholic84 commented Oct 20, 2023

joostlek commented Oct 20, 2023 • edited Loading

Technoholic84 commented Oct 20, 2023

joostlek commented Oct 20, 2023

Technoholic84 commented Oct 20, 2023

puddly commented Oct 20, 2023

zwack-am commented Oct 21, 2023 via email

Technoholic84 commented Oct 21, 2023

joostlek commented Oct 21, 2023

Technoholic84 commented Oct 21, 2023

byannnn commented Oct 22, 2023

puddly commented Oct 22, 2023 • edited Loading

Technoholic84 commented Oct 22, 2023

Technoholic84 commented Oct 22, 2023

Technoholic84 commented Oct 24, 2023

puddly commented Oct 24, 2023

TheJulianJES commented Oct 11, 2023 •

edited

Loading

TheJulianJES commented Oct 11, 2023 •

edited

Loading

crameth commented Oct 20, 2023 •

edited

Loading

joostlek commented Oct 20, 2023 •

edited

Loading

puddly commented Oct 22, 2023 •

edited

Loading