search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.87k stars 30.95k forks source link

Zigbee Door Sensor Fails to Join Network, Stuck in Configuration Stage After Resetting and Re-joining with ZHA #125291

Open luobenwang opened 2 months ago

luobenwang commented 2 months ago

The problem

I am trying to add a Zigbee door sensor to my Home Assistant (HA) system and have encountered some issues. Here is the problem and the steps I have taken:

Problem Description:

My Zigbee door sensor failed to join the network on the initial attempt, specifically during the configuration of the child device stage. I attempted to reset the device locally to leave the network and observed that the child device successfully sent a leave packet. Afterwards, I used Zigbee Home Automation (ZHA) to re-join the network, which resulted in a new short address 0xBEC5, but the joining process is stuck in the configuration stage. Packet sniffing revealed that ZHA keeps trying to send read/write attribute packets to the previous short address: 0x790A, with a very large number of packets. It is not sending any packets to the new short address 0xBEC5. Questions:

Has any developer encountered a similar situation before? Could this be a bug in ZHA? If so, how should I report this issue? If not, are there any recommended solutions or further debugging steps? [zha_join.log](https://github.com/user-attachments/files/16883274/zha_join.log) Join_ZHA_config_fail.zip

Thank you for your help and suggestions!

What version of Home Assistant Core has the issue?

2024.8.3

What was the last working version of Home Assistant Core?

20240809.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

zigbee packet and ZHA debug log

Additional information

No response

luobenwang commented 2 months ago

Here’s a rundown of what I’ve got going on:

1.Interference Check: I’ve confirmed that my door sensor is free from EMI/RFI/EMF interference, as it’s operating within a close 1-meter proximity to the Zigbee coordinator. 2.Pairing Strategy: To ensure a smooth pairing process with ZHA, I’ve set my device to remain active for a full 70 seconds after the initial pairing. This should provide ZHA with sufficient time to read the device’s attributes and complete the configuration.

home-assistant[bot] commented 1 month ago

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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

zha documentation zha source (message by IssueLinks)