core: Zigbee ZHA async_initialize: all attempts have failed
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: https://github.com/home-assistant/core/issues/87813#issue-1578791007
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:
Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 4:15:10 PM (30 occurrences)
Last logged: 4:15:18 PM
[0x360E:1:0x0006]: 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>')]
[0x97B1:1:0x0006]: 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>')]
[0xD782:1:0x0406]: 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>')]
[0x6697:1:0x0006]: 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>')]
[0x6697:1:0x0702]: 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>')]
Logger: zigpy.application
Source: runner.py:179
First occurred: 4:15:27 PM (4 occurrences)
Last logged: 4:20:08 PM
Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x8394)
Received relays from an unknown device: 0xb6ff
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
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 2
- Comments: 53 (2 by maintainers)
I’ve found I can add nwk info to the zha-network-card https://github.com/dmulcahey/zha-network-card 😃
Its looks that it is not problem of Skyconnect or chip used in Skyconnect. I bought Sonoff 3.0 dongle P in August (https://github.com/home-assistant/core/issues/89172#issuecomment-1641796691) and migrate to this dongle. It was little bit better, but network was not stable. Last chance to stable network was to migrate from ZHA to Z2M. After 8 months of problems (starts with some ZHA update in spring) with daily unstable network i decided to move to Z2M (11/2023). I did not change any hardware or position of hardware. Everything works like a charm. There is no non responding device for whole 2 months from migration. I am using Skyconnect (much more better signal range/pairing speed than Sonoff 3.0 dongle P) without any issues.
In square brackets, the 1st hex number is the nwk address of the device
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. The fact is Zigbee integration seems to be overloaded and could not reach the light switchs or get Zlinky data. The workaround is a zigbee integration restart but ofter directly HA restart and everything get back for a while
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…
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.
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.
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.
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: HA VM running on Unraid (qcow2 file) Home Assistant 2023.6.2 Supervisor 2023.06.2 Operating System 10.2 Frontend 20230608.0 - latest
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: HA VM running on Unraid (NEW qcow2 file) Home Assistant 2023.6.2 Supervisor 2023.06.2 Operating System 10.3 Frontend 20230608.0 - latest
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.
home-assistant_zha_2023-06-16T16-39-15.907Z.log
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
async_initialize: all attempts have failedwarnings happen (they still happen and they’re for mains powered devices). It’s unclear if these are warnings that need action to be taken - they only seem to come up when home assistant restarts and the devices otherwise operate normally as best I can tell.