Zigbee ZHA async_initialize: all attempts have failed #89172
Comments
|
Hey there @dmulcahey, @Adminiuga, @puddly, 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 decided to try and rebuild my zigbee network from scratch, moving to channel 25 which looks maybe less congested after viewing 2.4GHz wifi . After adding several devices I had no errors, but at 20 devices I now see this error again: On a positive note, devices seem to be working and not showing as unavailable. Similar to before, this error comes up when Home Assistant has restarted. Is there any way to use the information in the error to identify the devices involved? |
|
In square brackets, the 1st hex number is the nwk address of the device |
Thanks @Adminiuga, do you know if there is a way to view detailed device information (including nwk address) for all devices? I see this information on each separate device page if I click Zigbee Info, but I'm hoping there is a more accessible list. |
|
I've found I can add nwk info to the zha-network-card https://github.com/dmulcahey/zha-network-card :) |
|
I got the same issue with the HA Yellow board It was working pretty well for 1 month and this issue just appeared. If you have an idea to locate the root cause |
|
Looks the same as me, but was on older OS: https://github.com/home-assistant/core/issues/88806 |
|
Since moving to channel 25 (away from 15) and restarting my network from scratch, things have improved. I have lots of zigbee router devices in my network, but it's difficult to interpret the "health" of the network in the visualization tab or to get insight into why the |
|
My problem seems to be solved by some config edit. |
|
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. |
|
i have the same problem. I switched from Sonoff ZB Bridge zu Skyconnect The new device are visible and can be conneced. But the connection is not stable (online/offline every 10 sec.) Logfile: System: |
|
I am having a similar issue as well. I was using a Nortek Zigbee/Zwave stick and noticed since 6/10/23 many zigbee devices not responding to automations or manual toggling. Sometimes it would respond to on/off on a 5-10 second delay, sometimes the devices wouldn't respond to any toggle. System: To eliminate my build/config, or physical hardware, I purchased a Sonoff 3.0 Zigbee device and built a new HA VM from scratch. The only configuration I made on the new build was add the ZHA integration and configure with the Sonoff 3.0 (Nortek is unplugged). I scanned and paired a few zigbee devices and am experiencing the same issue. This is a completely new build, all up to date. System: I have attached my log file with ZHA debugging turned on. Please let me know if there is anything I can help provide for further diagnosis. |
|
Recently, after each reboot, I get the below warnings in the HA log file. However, all my Zigbee devices appear to be working okay. Did something change in the Zigbee integration to cause this? I haven't changed anything on my zigbee network... these warnings just started to appear one day after I upgraded Home Assistant... I just can't remember which version caused this. |
|
now I have changed from Skyconnect-Stick to SONOFF Zigbee 3.0 USB Dongle Plus. |
|
Still the same problem here with sky connect, the devices worked well but now the mesh begins to get unreliable and slow. `Logger: homeassistant.components.zha.core.cluster_handlers [0x49F8:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')] |
My experience is that is takes a few days before the mash network has arranged itself. Just wait a day and you should see a change in LQI and RSSI. Sometimes better or worse. |
|
The network was reliable for 2 months. Now it began to get unreliable. |
|
OK, today, the Sonoff USB dongle arrives. |
|
I have the same experience. I used Raspberry Pi 4 and Raspbee II, and I never had any issues. Then I switched (changed the radio) to Skyconnect, and since then, there is no day with reliable network (almost 3 months of frustration). In the log, I constantly see "all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')" I also bought Sonoff dongle and flashed the repeater firmware, but nothing improved (except much better LQI). I have around 50 Zigbee devices, half of which are routers. It seems to me that Skyconnect is also a problem. |
Hi, Sometimes I get errors from my Aqara illumination sensor, but it works with no problems.
|
|
Have the same with con bee2 stick, at certain point all zig bee device start to be super laggy, full restart of HA make it better for some time, but i keep seeing these messages in the logs after every reboot |
|
After years of stable use, today I switched from a Conbee2 stick to SkyConnect. Everything seemed to be working fine for a few hours, but now everything started failing with similar issues as described above. Reboot does not fix it. |
|
@jinovak |
|
I have the con bee2, has been solid for the last 2 plus years, not all of a sudden, the network very unreliable. i have just ordered the sonoff e stick. fingers crossed. update: Sonoff Zigbee 3.0 e arrived and once migrated everything came back up with he exception of one led controller. I tried setting it to pair but is will connect and then go back into pairing mode |
|
Try out 2023.8.2, there was a bugfix in this release that may improve connectivity in poor environmental conditions. |
I have it already and it did not help. |
|
Same here. .2 didn't solve my issues. Although it does allow me to disable and re-enable automations that are stuck without freezing up the UI. |
|
Hi, I had the same problems you are reporting here with a Sonoff Zigbee Dongle E (chip EFR32MG21). Some devices would simply fail respond with the DELIVERY_FAILED error and after some trials they would magically wake. I tried all firmware versions for this Dongle, from 6 to 7.3. The issue never went away. Then I went back to my trusty Sonoff Zigbee Dongle P (chip CC2652) with KoenKK firmware. Everything went perfectly well. No device lags or failures. Note that the network configuration never changed (channel, IEEE, keys, etc...) Today I received my Skyconnect (chip EFR32MG21) and immediately upgraded to the latest official firmware (7.2). The excitement of the new device went away as soon as I started to have the same problems I had with the Dongle E. Back to Dongle P and my network is perfect! Conclusion: The problem is with the EFR32MG21 based devices. I feel that this chipset/firmware is very "impatient" and does not wait enough for the responses from mesh. |
|
Same issue here. |
|
@Grey-Sheep just an FYI, this doesn't seem to be related to Skyconnect. I have this same problem with a completely different ZHA dongle: HUSBZB-1 (with ZHA and Zwave radios). The common denominator is Home Assistant. Also, I don't use Home Assistant Yellow. I use Home Assistant VMWare VM. Whatever this issue is, I didn't have this issue 4 months ago. |
|
@danpeig @matthewhadley don't think the issue is specific to EFR32MG21. I use the popular dual radio HUSBZB-1 USB dongle with a |
|
Since changing my zigbee channel #89172 (comment) my network has been stable. This is probably a separate matter, but I will mention here that I have recently been having issues with ZHA not being able to initialize on Homeassistant (re)start, with these kind of errors: When this happens the network is totally unresponsive (it didn't start) and I have to reload the integration to fix. It seems similar to #99750 and I'm hoping it's resolved by #99764 |
I have made the same switch and can report the same issue. One would assume that SkyConnect should be the dongle that has the best support for Home Assistant, but after migrating to SkyConnect I started seeing the 102 errors (delivery failed). |
|
I can say that there have been no such problems with the Sonoff Dongle P for two months. |
|
Upgrading to 2023.9.2 did not fix the error preventing ZHA from starting :( I was on the multipan protocol for SkyConnect to support both zigbee and thread. I've decided to go back to using it exclusively for Zigbee. Since doing that Zigbee starts ok on homeassistant start, but the I cannot tell if it's related, but the supervisor logs also show these errors during startup: |
|
Exactly the same problem: |
|
Same problem here. Moved to ZHA few months ago when started to use skyconnect (RaspPi4). At first everything worked perfectly but this week started to get EmberStatus.DELIVERY_FAILED: 102. Reloading Zha "fixes" the problem for short periods but then same errors come back again. |
|
I have HA installed on an Intel NUC, use ZHA via SkyConnect and since a while exactly the same problem - the SkyConnect is connected to a USB 2.0 port with a 1m extension cable, any USB 3.0 interference sources are not in range. Every few days the same error pattern - <EmberStatus.DELIVERY_FAILED: 102> |
ZigBee Dongle P is rock stable! |
|
Tested with Skyconnect and Sonoff zdongle-E: Same errors with both, <EmberStatus.DELIVERY_FAILED: 102> etc. Then migrated radio to old Sonoff dongle (Texas_Instruments_TI_CC2531) and everything works problem free. |
|
I had the same issye with async_initalize issues for some devices in the network. Rebooting and shutting down did not solve the issue for me. I disabled the support for Multiprotocol (Thread) in my SkyConnect since no devices use Thread in my installation and immediatly all devices started communicating again. |
|
this problem just started to plague me today. I haven't been able to get any deterministic causes. I do not have SkyConnect. I am currently in the process of updating from 2023.10.3 to 10.5, crossing my fingers that this will work. I am using a Sonoff 3.0 dongle. I even went to the step of moving my 2.4ghz wifi to channel 11 just in case that was the problem |
|
In trying to track it down, I started with a clean install of HA, and have been slowly moving across the Zigbee devices one at a time. I'm using the SkyConnect Dongle. |
|
I only have 36 devices which is the sad thing. I have several routers (wired outlets for zigbee) Edit: I got a 1 meter USB extension cable and moved the Sonoff 3 USB dongle and that hasn't made any difference Edit 2: I moved my Zigbee channel to 11... based on this website that should mean I am not overlapping
Still having the same problem. I have dropped 5 zigbee devices from my network and still cannot communicate with most of them |
|
I have 107 devices now , no problems with Sonoff dongle P, channel 25 |
|
I'm using a ZigStar UZG-01 LAN Zigbee coordinator, which uses the same chip as the Sonoff-P dongle (CC2652P). I'm having the following error, constantly: |
Had the same problem, in my case it was a zigbee device that wasn't de-registered properly |
|
Same erratic issue here with SkyConnect (was sometimes the case before with POP) and please note that I moved all wifi chan to the end and change Zigbee Channel from 25 to 20. I'll also add that I completely reinstalled a fresh HA on HAOS only 3 weeks ago and I also get a 2m wire to isolate the Skyconnect key from USB or anything else... |
|
Same problem with conbee II. I have try almost everything. The last month is really unstable and unreliable |
|
Its looks that it is not problem of Skyconnect or chip used in Skyconnect. I bought Sonoff 3.0 dongle P in August (#89172 (comment)) and migrate to this dongle. It was little bit better, but network was not stable. |
|
I have a very similar experience as jinovak. After constant problems with ZHA+Skyconnect for almost a year, I migrated everything to Z2M+Skyconnect a few weeks ago. Everything runs rock-solid since I made the leap. |
|
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. |
issue-triage-workflows
bot
closed this as not planned
and others
The problem
Recently my zigbee network has become unreliable. Sensors will become unavailable and there are a number of errors in the logs.
This happened recently, after switching to SKyConnect: #87813 (comment)
I thought it was resolved, but the issue came back. I have been trying to follow the guidelines at https://community.home-assistant.io/t/guide-for-zigbee-interference-avoidance-and-network-range-coverage-optimization/515752 - the skyconnect is attached to a long usb 2.0 extension.
I am wondering if there's a way to completely restart my zigbee network from scratch - would that be just a matter of removing all current devices?
Here are the errors in the log:
What version of Home Assistant Core has the issue?
core-2023.3.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
ZHA
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
config_entry-zha-0dedda09ac60fefd7e29f0f87d9f0cd9.json.txt
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: