No unfortunately 
It ended up for me with removing all zigbee devices and re-pairing/adding them again.
Apparently zigbee coordinator (conbee) was working fine all this time.
Thanks, I just moved/re-paired everything over to Zigbee2MQTT. I’ve lost too much trust in the current ZHA solution…
1 Like
Sharing in case it’s of value to anyone as I had this error today.
I’ve recently moved my environment of Zigbee over from ST to HA. I discovered my Zigbee devices having this issue tonight. At first it was one SONOFF switch, then bulbs failed after. It was after I had been updating flows in Node-Red.
What was interesting in my case is one or two bulbs were responding still. Like many above, I power cycled the HA Pi many times with no luck. The log book was showing some activity on motion sensors but not all.
Curious about the random working lights and sensors, I checked the config of my Conbee II - I noticed that settings were blank. I hit Update Config and refreshed and notice a random set of settings appeared. I reset them all back to black and null where possible and smashed update config a few more times for good measure. The status on dashboard cycled on and off repeatedly and then settled. I then manually power cycled the devices at the power switch and everything has now once again returned to normal.
In sum, I wonder if it is config corruption that is repaired by overwriting settings and then rebooting devices that have been hung by receiving corrupt commands.
Side note : I do have a Zigbee IKEA repeater which was rebooted also during this troubleshooting. No changes to HA build or core.
Running 2022.8.8 I’ve same issue today. I use a sonoff bridge with Tasmota Firmware 12.0.2.4.
Same issue here, everything working fine, now on vacation my zigbee network is dead with the same error messages in the log, tried everything what I could, like removing devices (doenst work), delete integration and re-add (doesnt work) power off HA completely for more then 30 minutes (doesnt work), re-seed the Conbee II USB stick (doesnt work). no clue what to do.
If I google this error there are so many people which seem to suffer from this issue but there is no clear solution, apart from start from scratch, which doesnt seem like a good solution at all…
After upgrading to 2022.8.8 I got this problem also. I’m almost sure that this is independent from the upgrade process, et least from the corresponding versions as seems the problem can appear in very different situations. But in the process there could be some data corruption or so.
I’m not so happy, as have no time to debug now while my whole Zigbee network is dead, but luckily I have just very little number of Zigbee devices.
Although I know that bugs could be everywhere (especially as I’m something like ‘developer’), but such generic problems could be very sensitive in a living smart home sstem:(
I’m using 2022.8 too with a Raspbee on a pi3 and since a few days 1 Ikea bulb has this problem, the other zigbee devices (wired and wireless) are working fine.
If I go back to my “old” system, deconz, everything works fine. So it has to be a bug in HA, right?
I’m not a programmer or debugger, but if I can help, let me know.
Sucks when they’re built into the wall, like hue wall switch modules. Ridiculous.
1 Like
Sadly I’m also having these issues with the async failed error. I’m running HA 2022.9.2 on a Raspberry Pie 4 2GB. I also have a combee II stick running the latest firmware. I have it plugged into a USB2 port on an extender.
I also have 12 devices on my HA and a few days ago it was one of my innr plugs wasn’t responding correctly and bow today all my Zigbee devices with no/off functionality are not working correctly. When I click a device to toggle, HA seems to think about it but then fails. I have to click the devices approximately 5+ times before they will respond. They are also failing when trying to reconfigure.
It’s super frustrating and unsure whether to just tey Zigbee2MQTT
1 Like
same here with 2022.9.4, been having this issue since I first updated to 9.0 where my zigbee connection is unstable and i would have to restart HA and pray that it works again… This time with not so much luck though.
Same problem here. Using the fitst gen raspbee. Seems the problem mainly occurs with Conbees/RaspBees. Since the first gen rasbee get’s no software support anymore I will upgrade to the sonoff zigbee stick and will drop ZHA for Z2M. :\
//EDIT So I switched to z2m without any issue.
Had the same problem a few months back after a core update, did a complete restore to get everything back up and running. Yesterday I decided to update to the latest version (Release 2022.10.1) and had the same problem. Before deciding to restore back to an older version I just clicked on ‘update configuration’ without changing anything and all devices came back online (plugged & battery powered). (thanks @davidorsel @ge33ek !)
Still might convert everything over to Zigbee2MQTT to avoid this in the future.
With everyone above, so had it with zigbee functionality on HA. Have about 20 sonoff devices and everything just randomly goes off and stops responding. Then when troubleshooting, the logs don’t even tell you what devices the errors are pointing to. It’s all cryptic.
Did you follow a guide on how to switch?
Hmm not really. First I copied all my entity ids of my zigbee devices but the most are still in my head. 
Then I disabled and deleted zha, restart ha, install z2m (there are many yt videos out there). Now I repaired my devices and named it like the old entity ids.
When I switched the dongle the devices were still available.
I did allmost the same. I installed z2m and at home I put a conbee II on a cable, I used raspbee II before.
At the summer cottage I also switched after verifying that it was stable, but there I still have the raspbee II. And it works like charm! I don’t want any problems now, as the zigbee network has grown, 50+ devices at each place!
The z2m also supports the Sunricher green devices, so I have neat wall switches everywhere 
. And I don’t need to change batteries 
I cannot say it followed on from an update (currently 2023.6.3) but a few hours ago, out of the blue, noticed all my automations not firing. Checked the logs and find:
Logger: homeassistant.components.zha.core.cluster_handlers
Source: components/zha/core/cluster_handlers/__init__.py:506
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 00:19:57 (89 occurrences)
Last logged: 00:20:43
[0x8D2C:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>')]
[0x8D2C:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>')]
[0x5D36:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_NO_ROUTE: 205>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_NO_ROUTE: 205>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_NO_ROUTE: 205>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_NO_ROUTE: 205>')]
[0x8D2C:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>')]
[0x1D02:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>')]
On checking the network see all zigbee devices offline, although integrations e.g. Overkiz work fine. Then noticed this error:
Your network is using the insecure Zigbee2MQTT network key!
which is odd because, although it’s installed, I have not yet had time to edumacate myself in the use of Z2M. Its not actually configured.
Multiple reboots later, thought I would try a restore to 2023.6.2. All devices still offline. Presume something up with that network key, which has poisoned the network and now must re-pair all devices.
Kind of blows a hole in my confidence in HA as a home automation solution for anyone without a fairly deep tech knowledge e.g. the boss who up to now was impressed with how stable and convenient it all is, what with over 55 devices now deployed. I don’t see that anyone has ever had a satisfactory explanation for it, so I thought I would post my experience here in case it helps anyone in the future.
kr
g
Some new people arrived in the block of flats I live in. Is it possible they have a zigbee network and somehow cross-contaminated mine, cf this post Secure your Zigbee network | Zigbee2MQTT
I don’t feel its the sort of thing I can approach new neighbours with. But I am now a couple hours in to resuscitating my network and I gotta say its not a good experience. Not got to the switch behind the pendant lamp yet, because I cannot get the candeo with its built-in dimmer zigbee until the morning
. Fingers crossed
to paraphrase Alan Sugar, this is an absolute bloody nightmare
I saw this happen today. It didn’t break the all zha lights, but anything that was used from an automation was broken for all usage. The only thing that changed today was an update to ZHA toolkit. A restart didn’t fix it, but an update to Adaptive Lighting + a full reboot of the HAOS server fixed it all.