ZHA won't bind any new Zigbee Devices anymore #131068
Comments
|
Can you upload diagnostics JSON for the ZHA integration as well? 
|
|
Something seems to be seriously wrong. That doesn't work. I get the message 'web site not available' (in german). |
|
After reloading ZHA I could dowload the file... |
|
I have the same issue, here is my diagnostics file also, maybe it helps? |
|
Same issues here! 80% of ZigBee devices no longer work after the update. Really annoying! Did they forget to unit test? |
|
@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. |
|
Hey there @dmulcahey, @Adminiuga, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
|
I've found an odd work-around also, repeated it many times and it's worked. 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". 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. |
|
I can not confirm andyb2000's work-around. Not working here.... |
|
@andyb2000 what specific coordinator are you using? Please upload a ZHA debug log of your device joining procedures. |
|
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'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. 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 (3).json config_entry-zha-f10e4645291bce79d4581e458a2da891 (2).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! |
|
Same here, have 1 Zigbee device that is no longer connected and am unable to repair or re-pair it.
|
|
hello, i have same issue with my ZHA integration : devices no longer connected, impossible to pair. Sometimes device is paired but it is impossible to do some action (switch, identifier button). |
|
Also having this issue. Unable to pair any of my SONOFF zbmini or NSPanel devices although sometimes they will get to the "interview" stage. |
|
Try reverting to 2014.11.0. that did the trick for me. Curious to see if it works on more systems |
|
I also cannot add new devices. Next to that, the controller lost connection to devices that act as a signal repeater. When trying to add a device using the controller (Conbee II), it just keeps on searching. When trying to add a device using a signal repeater (for example IKEA Trådfri), it also keeps on searching, and I see this log message (likely because the signal repeaters lost their connection): Couldn't open '[insert mac here]' for joining: Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>. I feel like this happened after I updated Home Assistant from 2024.11.1 to 2024.11.3. |
|
Move your Conbee away from USB 3.0 devices, SSDs, WiFi routers, and other 2.4GHz interference sources. |
It used to work fine for years, and only after the update things didn't work correctly anymore. Also, devices that are directly linked to the controller still work fine. It just doesn't find new devices and connections to repeaters do not work, no matter how close I place them to the controller. The controller is connected using a usb 2.0 extension cable. MAC_CHANNEL_ACCESS_FAILURE is not logged when trying to add a device directly from the controller. |
|
My apologies, even though the setup never changed and worked fine for so long, switching around devices on the usb ports helped to fix it. 😖 Should've tried it sooner, sorry about that. |
|
Got some new Tuya Zugbee plugs today and tried to bind them. That seemed to work right away. But even though paired seemed to be successful, the devices are not available. I have atteched the log. home-assistant_zha_2024-11-28T20-48-01.072Z.log.zip Interesting: The Tuya plug succeeds in binding (still not working afterwards) and the IKEA plug will only get to "starting interview", not any further. Hope this helps... |
|
I am encountering the same issue with Sonoff temperature and humidity probes SNZ-02P type. The workaround posted by andyb2000 worked for me |
|
Hello All, I have the same issue that only sonoff devices showed as offline whereas Aqara are all online. No way to repair the SONOFF devices via the coordinator which is Home Assistant Yellow. What I found out is that if I try to add the devices via some of the routers (Ikea and Aqara outlet) it works immediately. However I can add aqara devices via the Yellow coordinator. |
|
Exactly the same here, devices that has been paired in ZHA and using Sonoff Zigbee 3.0 dongle Plus for months and maybe a year mostly still works. If i delete it and trying to repair a device, ZHA discovering it fast but after it says complete all the entities for the device is unavailable. The same device(s) is pairing and working find with Deconz using a Conbee if compatible. Edit: Seems like HA/ZHA does not sendt data back to the device that telling the device/confirming that "hello i got you" because the device continues to be in pairing mode until timeout. Frustrating! |
|
Not much happening here right now. Has anybody come up with a workaround or a fix? |
Revert to a previous version and wait for good and decent unit testing is in place? |
|
not a fix but I've go try ZHA up and running again with all my devices online. I had to do two things, not sure which one resolved the issue unfortunately deleted the database Yes this meant reconnecting all my devices, not too bad in my case (11 devices) but can imagine some have huge networks! I guess this at least proves ZHA is functional but something has changed in the 2024.11 updates it seems. |
|
Resolution for me was to take the SonOff dongle offline, and reflash it to the latest software, and then add back every device in the network. it's been stable since and working actually better than before. The last software for ZHA is dated July 2024. If your Sonoff software is older than that, this could be the only route back to a working system.
|
|
I am wondering if somebody from Nabucasa is working on the issue ? My
understanding is that the problem started sometime in June
this year but I discovered it only one month ago. As we install a new
version of HA, we all check that the system is working
like before : paired device remain paired. But we don't test that pairing a
new device has an issue (I don't).
For now my paired devices mainly Sonoff temperature sensors and my Sonoff
dongle stay paired but my fear is that a new version
(2014.12.4) may destroy the pairing as I know that reverting to 12.3 will
not allow to pair the device back.
Does somebody now what was the last version that allowed the pairing ?
csierra67
.
Le ven. 13 déc. 2024 à 13:57, SmOeL-swdev ***@***.***> a
écrit :
… Not much happening here right now. Has anybody come up with a workaround
or a fix?
I really don't want to move to Z2M but this has been broken for over a
month now....
Revert to a previous version and wait for good and decent unit testing is
in place?
—
Reply to this email directly, view it on GitHub
<#131068 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6MSPJFK32E5PXH6G6UMCZT2FLKSVAVCNFSM6AAAAABSFI4J5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRGQYDQMJQGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Ladies and Gentlemen, I have just updated the firmware of my Sonoff Dongle using this: https://vandalen.dev/post/how-to-update-sonoff-zigbee-3-0-zbdongle-p-usb-firmware-using-a-mac/ After that, ZHA started normally. All previoously working devices were up an running. I could now successfully bind the IKEA Tradfri Outlet and the Snonoff ZBMINIL2 that I could not get to bind earlier. This might have solved the problem. |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
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
The text was updated successfully, but these errors were encountered: