ZHA won't bind any new Zigbee Devices anymore

[hbothmer]

The problem

When I try to bind a new Zigbee device via ZHA, the process stops at the blue Configuring dialogue. Tried different deviced from Ikea, Sonoff and Tuya. Some Devices have lost their connection though they still are show as online in the graphical network diagram. Switching one of them produces a time out.

What version of Home Assistant Core has the issue?

core-24.11.2

What was the last working version of Home Assistant Core?

core-24.10.?

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

home-assistant_zha_2024-11-20T19-01-56.082Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[puddly]

Can you upload diagnostics JSON for the ZHA integration as well?

[hbothmer]

Something seems to be seriously wrong. That doesn't work. I get the message 'web site not available' (in german).

[hbothmer]

After reloading ZHA I could dowload the file...

config_entry-zha-24d0729b542e0b9eb999a66c04c8cd5c.json

[myromeo]

I have the same issue, here is my diagnostics file also, maybe it helps?

config_entry-zha-01J3TC6PJ5CF8AC0DG2R1QEBAE.json

[SmOeL-swdev]

Same issues here! 80% of ZigBee devices no longer work after the update. Really annoying! Did they forget to unit test?

[puddly]

@SmOeL-swdev Enable ZHA debug logging, reload the integration, and download the debug log after letting the integration run for 10 minutes. In those 10 minutes, try to control some devices to fill the log with something useful.

[home-assistant]

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

[andyb2000]

I've found an odd work-around also, repeated it many times and it's worked.
This is a combination of trying to pair (or re-pair after battery replacement) eWelink and Sonoff devices.

Set ZHA into pairing mode. Do the pin/reset on ONE zigbee device (I use a sacrificial sensor!). It shows up and gets stuck on either "Starting Interview" or "Configuring".
THEN start the device you actually want pairing (pin/reset) and it seems to pair straight away.

I've repeated this about 5 times now and it worked each time. The sacrificial sensor never pairs but the subsequent devices do.

I'll put ZHA into debug and get some logs.

[hbothmer]

I can not confirm andyb2000's work-around. Not working here....

[puddly]

@andyb2000 what specific coordinator are you using? Please upload a ZHA debug log of your device joining procedures.

[SmOeL-swdev]

For me the solution was to revert back to core v2024.11.0. no need to reconfigure anything. Everything works again as before (no pairing required).
I don't have saved a log file, sorry.

[L81ker]

I've had the same. Still having the same. Dropped all the IKEA devices that were working, and I cant get those added back at all. Some devices are 'embedded' in ceiling lamps, so they can stay offline till this is resolved.

Here's the network map with partial recovery but even those devices have dropped again. Log files from 2 days of trying resets, reloads, delete and add back, the above workaround would work for one device and drop the next.
So frustrating, has been working 100% reliable till now. Even restoring previous back up hasn't helped so far.

I'd like guidance on how to resolve this once the fix is known. I really hppe it's not a 'delete all and start over' situation!

[config_entry-zha-f10e4645291
[config_entry-zha-f10e4645291bce79d4581e458a2da891.json](https://github.com/user-attachments/files/17882363/config_entry-zh

config_entry-zha-f10e4645291bce79d4581e458a2da891 (3).json
a-f10e4645291bce79d4581e458a2da891.json)
bce79d45

config_entry-zha-f10e4645291bce79d4581e458a2da891 (2).json
81e458a2da891 (1).json](https://github.com/user-attachments/files/17882360/config_entry-zha-f10e4645291bce79d4581e458a2da891.1.json)

[SmOeL-swdev]

I've had the same. Still having the same. Dropped all the IKEA devices that were working, and I cant get those added back at all. Some devices are 'embedded' in ceiling lamps, so they can stay offline till this is resolved.

Here's the network map with partial recovery but even those devices have dropped again. Log files from 2 days of trying resets, reloads, delete and add back, the above workaround would work for one device and drop the next.
So frustrating, has been working 100% reliable till now. Even restoring previous back up hasn't helped so far.

I'd like guidance on how to resolve this once the fix is known. I really hppe it's not a 'delete all and start over' situation!

[config_entry-zha-f10e4645291
[config_entry-zha-f10e4645291bce79d4581e458a2da891.json](https://github.com/user-attachments/files/17882363/config_entry-zh

config_entry-zha-f10e4645291bce79d4581e458a2da891 (3).json
a-f10e4645291bce79d4581e458a2da891.json)
bce79d45

config_entry-zha-f10e4645291bce79d4581e458a2da891 (2).json
81e458a2da891 (1).json](https://github.com/user-attachments/files/17882360/config_entry-zha-f10e4645291bce79d4581e458a2da891.1.json)

I hope that the latest core update solves your problem (2024.11.3). I had to revert to 2024.11.0 without rebinding (everything works as before)

Good luck!

[L81ker]

I've had the same. Still having the same. Dropped all the IKEA devices that were working, and I cant get those added back at all. Some devices are 'embedded' in ceiling lamps, so they can stay offline till this is resolved.
Here's the network map with partial recovery but even those devices have dropped again. Log files from 2 days of trying resets, reloads, delete and add back, the above workaround would work for one device and drop the next.
So frustrating, has been working 100% reliable till now. Even restoring previous back up hasn't helped so far.
I'd like guidance on how to resolve this once the fix is known. I really hppe it's not a 'delete all and start over' situation!

[config_entry-zha-f10e4645291
[config_entry-zha-f10e4645291bce79d4581e458a2da891.json](https://github.com/user-attachments/files/17882363/config_entry-zh
config_entry-zha-f10e4645291bce79d4581e458a2da891 (3).json
a-f10e4645291bce79d4581e458a2da891.json)
bce79d45
config_entry-zha-f10e4645291bce79d4581e458a2da891 (2).json
81e458a2da891 (1).json](https://github.com/user-attachments/files/17882360/config_entry-zha-f10e4645291bce79d4581e458a2da891.1.json)

I hope that the latest core update solves your problem (2024.11.3). I had to revert to 2024.11.0 without rebinding (everything works as before)

Good luck!

I might have to resort to that. I spent last sunday building the Google AI to get the creative notifications for movement on the cameras, and that's all working brilliantly..... Rolling back to 11.0 will mean a different set of work!