zigpy errors - Githubissues

boatmon0 commented 11 months ago

The problem

Cannot add new zigbee devices. Some zigbee devices are not connected. Worked well for a while. Added some devices mostly motion sensors and I cannot add any more devices. I have about 27 devices, and 125 entities on the zigbee network.

What version of Home Assistant Core has the issue?

core-2023.10.1

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

zigphy

Link to integration documentation on our website

/config/integrations/integration/zha

Diagnostics information

This is a repeating pattern.

023-10-06 18:38:21.017 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x728F), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=255, source_route=None, extended_timeout=False, tsn=27, profile_id=260, cluster_id=6, data=Serialized[b'\x08\x94\n\x00\x00\x10\x01'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=255, rssi=-71) 2023-10-06 18:38:21.019 DEBUG (MainThread) [zigpy.zcl] [0x728F:1:0x0006] Received ZCL frame: b'\x08\x94\n\x00\x00\x10\x01' 2023-10-06 18:38:21.020 DEBUG (MainThread) [zigpy.zcl] [0x728F: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=0, reserved=0, is_cluster=False, is_general=True), tsn=148, command_id=10, direction=<Direction.Client_to_Server: 1>) 2023-10-06 18:38:21.024 DEBUG (MainThread) [zigpy.zcl] [0x728F:1:0x0006] Decoded ZCL frame: OnOff:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.true: 1>))]) 2023-10-06 18:38:21.026 DEBUG (MainThread) [zigpy.zcl] [0x728F:1:0x0006] Received command 0x0A (TSN 148): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.true: 1>))]) 2023-10-06 18:38:21.027 DEBUG (MainThread) [zigpy.zcl] [0x728F:1:0x0006] Attribute report received: on_off=<Bool.true: 1> 2023-10-06 18:38:21.031 DEBUG (MainThread) [zigpy.zcl] [0x728F:1:0x0006] Sending reply header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, direction=<Direction.Client_to_Server: 1>, disable_default_response=1, reserved=0, is_cluster=False, is_general=True), tsn=148, command_id=<GeneralCommand.Default_Response: 11>, direction=<Direction.Client_to_Server: 1>) 2023-10-06 18:38:21.032 DEBUG (MainThread) [zigpy.zcl] [0x728F:1:0x0006] Sending reply: Default_Response(command_id=10,

Example YAML snippet

No response

Anything in the logs that might be useful for us?

[<EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5>, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_UNKNOWN|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 264>, groupId=0, sequence=210), 255, 0, 0x0000, 255, 255, b'\x98\xfe\x00']
2023-10-06 18:37:43.123 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5>, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_UNKNOWN|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 264>, groupId=0, sequence=210), 255, 0, 0x0000, 255, 255, b'\x98\xfe\x00']
2023-10-06 18:37:43.123 DEBUG (MainThread) [bellows.zigbee.application] Ignoring message type: <EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5>
2023-10-06 18:37:43.127 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'5152a18a5452b27e'
2023-10-06 18:37:43.127 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'8610be7e'
2023-10-06 18:37:43.131 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received permitJoining: [<EmberStatus.SUCCESS: 0>]
2023-10-06 18:37:43.773 DEBUG (MainThread) [bellows.ezsp.protocol] Send command nop: ()
2023-10-06 18:37:43.776 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'165321adeef07e'
2023-10-06 18:37:43.784 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'6253a1ad7dec7e'
2023-10-06 18:37:43.785 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'87009f7e'
2023-10-06 18:37:43.787 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received nop: []
2023-10-06 18:37:44.016 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'7253b19750d6eab259a24a25aa5d93499c9cbeabed4af37e'
2023-10-06 18:37:44.016 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'8070787e'
2023-10-06 18:37:44.020 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received messageSentHandler: [<EmberOutgoingMessageType.OUTGOING_MULTICAST_WITH_ALIAS: 4>, 65532, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_UNKNOWN|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 264>, groupId=0, sequence=210), 153, <EmberStatus.SUCCESS: 0>, b'']
2023-10-06 18:37:44.021 DEBUG (MainThread) [bellows.zigbee.application] Received messageSentHandler frame with [<EmberOutgoingMessageType.OUTGOING_MULTICAST_WITH_ALIAS: 4>, 65532, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_UNKNOWN|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 264>, groupId=0, sequence=210), 153, <EmberStatus.SUCCESS: 0>, b'']
2023-10-06 18:37:44.022 DEBUG (MainThread) [bellows.zigbee.application] Unexpected message send notification tag: 153
2023-10-06 18:37:46.289 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x5CA1](3328-G): Device seen - marking the device available and resetting counter
2023-10-06 18:37:46.290 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x5CA1](3328-G): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:37:50.340 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xD96B](RH3040): Device seen - marking the device available and resetting counter
2023-10-06 18:37:50.340 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xD96B](RH3040): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:37:50.430 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x2F77](TS0011): Device seen - marking the device available and resetting counter
2023-10-06 18:37:50.431 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x2F77](TS0011): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:37:51.658 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xD9AD](MS01): Device seen - marking the device available and resetting counter
2023-10-06 18:37:51.659 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xD9AD](MS01): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:37:52.363 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xEC81](DG15S): Device seen - marking the device available and resetting counter
2023-10-06 18:37:52.364 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xEC81](DG15S): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:37:52.392 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x14AF](MS01): Device seen - marking the device available and resetting counter
2023-10-06 18:37:52.392 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x14AF](MS01): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:37:53.790 DEBUG (MainThread) [bellows.ezsp.protocol] Send command nop: ()
2023-10-06 18:37:53.792 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'205021adbcd07e'
2023-10-06 18:37:53.797 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'0350a1ad0bda7e'
2023-10-06 18:37:53.797 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'8160597e'
2023-10-06 18:37:53.799 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received nop: []
2023-10-06 18:38:03.378 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x4F4B](Zen-01): Device seen - marking the device available and resetting counter
2023-10-06 18:38:03.378 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x4F4B](Zen-01): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:38:03.800 DEBUG (MainThread) [bellows.ezsp.protocol] Send command nop: ()
2023-10-06 18:38:03.803 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'315121ade6f37e'
2023-10-06 18:38:03.808 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'1451a1ad76607e'
2023-10-06 18:38:03.808 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'82503a7e'
2023-10-06 18:38:03.811 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received nop: []
2023-10-06 18:38:06.406 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x2753](TS0011): Device seen - marking the device available and resetting counter
2023-10-06 18:38:06.406 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x2753](TS0011): Update device availability -  device available: True - new availability: True - changed: False
2023-10-06 18:38:06.664 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x862E](TS0201): last_seen is 2480150.742149353 seconds ago and ping attempts have been exhausted, marking the device unavailable
2023-10-06 18:38:06.665 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x862E](TS0201): Update device availability -  device available: False - new availability: False - changed: False
2023-10-06 18:38:13.814 DEBUG (MainThread) [bellows.ezsp.protocol] Send command nop: ()
2023-10-06 18:38:13.817 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'425621adbaca7e'
2023-10-06 18:38:13.822 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'2556a1ada9ad7e'
2023-10-06 18:38:13.822 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'83401b7e'
2023-10-06 18:38:13.824 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received nop: []
2023-10-06 18:38:14.315 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x7F25](PGC314): Device seen - marking the device available and resetting counter

Additional information

If you see something that I should be pursuing please let me know. I've been hung up on this error for several weeks. I have ordered a sonoff usb stick and plan to re-do all of my devices hoping that might fix the problem.

home-assistant[bot] commented 11 months ago

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 commented 11 months ago

What 27 devices do you have? Are any of them bulbs, outlets, or things that are mains-powered? Please upload diagnostic info for the ZHA integration as well.

boatmon0 commented 11 months ago

13 Of the devices are mains powered. Light switches, outlets, thermostat. Most of the others are motion detectors or temp/humidity sensors. /config_entry-zha-f7696a5d5c4a2bd990c907ae204740c5.json.2.txt) e204740c5.json(2).txt](https://github.com/home-assistant/core/files/12875886/config_entry-zha-f7696a5d5c4a2bd990c907ae204740c5.json.2.txt)

Hedda commented 11 months ago

FYI, if already ruled out low-battery being root cause then be aware the two most commonly reported issues/symptoms are caused by EMF/EMI/RMI interference and a lack of enough Zigbee Router devices or root causes can be a combination of those two:

https://www.home-assistant.io/integrations/zha#zigbee-interference-avoidance-and-network-rangecoverage-optimization

https://www.home-assistant.io/integrations/zha#defining-zigbee-channel-to-use

https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties

https://www.home-assistant.io/integrations/zha#using-router-devices-to-add-more-devices

https://www.home-assistant.io/integrations/zha#zigbee-network-visualization-in-zha-ui

PS: There are more detailed tips and discussions related to these two Zigbee issues in this community forum thread:

https://www.home-assistant.io/integrations/zha#zigbee-network-visualization-in-zha-ui

boatmon0 commented 11 months ago

I am all working now! Seems like the latest update fixed all of my zigbee problems.

boatmon0 commented 11 months ago

All good for me.