This is a good alternative, SLAVA UKRAJINI!
https://www.ebay.com/itm/165178757770
ZHA also completely stopped working for me yesterday after upgrading to the latest HA version. All devices are coupled and I can see them in the topology view but I can not do any actions. E.g. let my covers down or pair new devices.
Same here - no updates, no restarts, yet my devices stopped responding after weeks of solid performance. ZHA visualization looks fine. After restarting and a hard reboot didn’t work, I updated to latest HA Core and OS. No relief. Super frustrating.
Anyone had any luck with this? I just updated to 2022.3.8 and all of my zha devices just stopped working. Same async error, they still show up in the visualization, but none of them respond, even after a full hard reboot. Anyone find anything?
Turns out my problem was due to my HUSZBZ being plugged into a USB 3.0 slot. I moved it to a 2.0 slot and everything returned. Just in case someone comes across this later!
Tip is to see/follow https://github.com/home-assistant/home-assistant.io/pull/18864
https://github.com/home-assistant/home-assistant.io/commit/970295a277e8f01d3ee39eeeaacf453625b988d3
and also
I am having these messages appear in my logs since updating to 2022.4.0. My network follows most of the best practices listed in @Hedda 's reply. Around 40 devices with ample amounts of routers for my ~900 sqft apartment.
Out of the blue the messages started to appear in my logs, continually spamming them. None of my Zigbee devices are available during this time, although 50-70% of them will start to come online over the next half hour, and then stop short of having my entire network back online.
Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:457
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 6:44:02 PM (13 occurrences)
Last logged: 6:47:46 PM
[0x03AC:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x03ac:1:0x0300]: Message send failure'), DeliveryError('[0x03ac:1:0x0300]: Message send failure'), DeliveryError('[0x03ac:1:0x0300]: Message send failure'), DeliveryError('[0x03ac:1:0x0300]: Message send failure')]
[0x9117:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x9117:1:0x0006]: Message send failure'), DeliveryError('[0x9117:1:0x0006]: Message send failure'), DeliveryError('[0x9117:1:0x0006]: Message send failure'), DeliveryError('[0x9117:1:0x0006]: Message send failure')]
[0x03AC:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x03ac:1:0x0006]: Message send failure'), DeliveryError('[0x03ac:1:0x0006]: Message send failure'), DeliveryError('[0x03ac:1:0x0006]: Message send failure'), DeliveryError('[0x03ac:1:0x0006]: Message send failure')]
[0x9117:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('[0x9117:1:0x0702]: Message send failure'), DeliveryError('[0x9117:1:0x0702]: Message send failure'), DeliveryError('[0x9117:1:0x0702]: Message send failure'), DeliveryError('[0x9117:1:0x0702]: Message send failure')]
[0x03AC:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('[0x03ac:1:0x0702]: Message send failure'), DeliveryError('[0x03ac:1:0x0702]: Message send failure'), DeliveryError('[0x03ac:1:0x0702]: Message send failure'), DeliveryError('[0x03ac:1:0x0702]: Message send failure')]
I have attempted to upgrade to 2022.4.1 without success. I have attempted to delete my “deps” folder. I have attempted rolling back to my full backups from weeks ago where there were no issues. I attempted to switch my ConBee 2 from USB 2.0 to USB 3.0 and back again. No luck.
When attempting to troubleshoot this, I have noticed that the Studio Code Server add-on as well as the Samba fileshare I had set up thru an additional add-on were not functional at this time.
Activating extension 'esbenp.prettier-vscode' failed: ENOENT: no such file or directory, uv_cwd.
This is a serious breaking issue for me that I can’t seem to resolve, and it appears as though I am far from being alone with ZHA issues recently. But this seems way deeper than that. Is there any suggestions to getting my HomeAssistant back to where it needs to be? Has anyone else been able to get this fixed?
FYI, release notes did not mention it but there was a huge update/change to ZHA dependencies (zigpy and zha-quirks/ zha-device-handlers Zigbee libraries) for Home Assistant 2022.4.x so I would just wait.
zigpy was updated to the very latest Zigbee Cluster Library specification, which should greatly improve interoperability in the long run, meaning that newer devices will need fewer quirks. But that was a large change so there is no real surprise that things broke.
Tip is not upgrade to the first revisions of any new releases if you want to avoid breakage for stability.
Regardless, did you update the firmware on Zigbee Coordinator dongle to the very latest version?
If computer only has USB 3.0 ports then the recommendation is to get a powered USB 2.0 hub for it.
https://www.google.com/search?q=powered+USB+2.0+hub
https://www.amazon.com/s?k=powered+USB+2.0+hub
Example:
https://www.amazon.com/AmazonBasics-Port-USB-Power-Adapter/dp/B00DQFGJR4/
Thank you for your thoughtful reply, boss.
Release notes not mentioning massive dependency updates doesn’t seem too helpful in HA’s quest to become mass-market adoptable. I generally agree with your sentiment of not updating to newest releases for compatibility, the fact that I can’t get my HA instance revived with backups is frustrating for me. I take frequent backups, validate them as working, and store on multiple remote locations following best practices to allow me to upgrade my Home Assistant version (working in information security has pounded into my head that you must keep everything up to date). However, none of my backups will roll-back the damage that this update has done to my network.
I did a clean install onto Home Assistant OS 8.0 RC1 yesterday and right out of the box, everything seemed to work fine. Then, I uploaded a full backup of my system from a 2022.3.6 release and was met without a working install yet again.
This morning I spent some time clearing out my Zigbee.db and ZHA.config files, then deleted/reinstalled ZHA. After adding about 6 devices (1/8th of my overall Zigbee network) I attempted to reboot and instantly my issues came right back. At this point, it seems like my best bet is to literally sit with a non-functioning Zigbee network in hopes that a dev fixes this… or completely start from ground zero on my Home Assistant install ie. reconfiguring remote access, mobile app companions, all my dashboards, node-red and HA automation flows, etc etc etc.
I have the same issue. After upgrading to 2022.4.x I regularly loose devices after a couple of hours until the whole zigbee network is dead. The only option to keep my Home Assistant instance working is to downgrade to 2022.3.5. With that my zigbee network seems stable.
I use a ConBee II USB stick with ZHA integration.
1 Like
That is not the same issue/symptoms. Symptom here is only some specific devices is not recognized.
The issue introduced in 2022.4 causes some ZHA Device Handlers (quirks) to not work properly or be presented differently, so symtom is that they do not work at all, not that they work for a while and then stop working after some time.
Your symptom sounds like signal interference or memory leak in Zigbee Coordinator or device firmware.
Suggest that update ConBee II firmware and connect it via a long USB extension cable to get it away and connect to a USB 2.0 port (and not a USB 3.0 port as they are well known to cause interference).
Read all tips regarding interfernce → https://github.com/home-assistant/home-assistant.io/pull/18864 → https://github.com/home-assistant/home-assistant.io/commit/970295a277e8f01d3ee39eeeaacf453625b988d3
Also follow best practices → https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties
An issue I found on github regarding this.
Regarding empty ‘config’ directory. The ssh add-on also showed no files, i.e. no ‘configuration.yaml’
I had to go to the add-on and disable “Protection mode”, then it was back…
+1 Right in the same boat with you. I read some other posts that said rolling back to 3.8 worked for them but I didn’t have such luck. fingers crossed that some dev is working on this as we speak
I experienced the same issue after upgrading from 2022.3.8 to 2022.4.1
I’m running HassOs on Pi4, ZHA with a Conbee2. On latest firmware and an extension cable. The zigbee network really became unreliability. Devices intermittently don’t respond, or not available.
1 Like
Following this thread
I haven’t even upgraded. It worked yesterday. Today zha (Conbee II) is not working. Just stopped working. I did a complete restore from when it used to work, and some devices are back, but not all of them. I just ordered a Sonoff Zigbee 3 dongle.
Same here. I haven’t updated HA when ZHA stopped working properly. Really strange. Wondering what could have been the cause.
I was using the HUSBZB-1 and replaced it with the Sonoff dongle but hat didn’t help.
I then upgraded the firmware to the latest version and things seemed to have gotten much better, but still not as well how things worked before the problem started (one leak sensor not updating its state).