ZHA & Home Assistant Version 2022.3.1 no longer works #67780
Comments
|
Enable debug logging for zha (check integration documentation) and submit logs. Replug phisically the stick What kind of radio? |
|
The problem occurred only after a reset (off and on again) because HA crashed in version 2022.3.1. Since then I have reset several times via the UI and also turned the server completely off and on again. even unplugging the USB stick (CC 2531) did nothing. And again, up to version 2022.3.0/2022.3.1 it ran since montanen without problems.
|
|
Hey there @dmulcahey, mind taking a look at this issue as it has been labeled with an integration ( zha documentation |
|
|
My ZHA works (sonoff 3.0 usb). I have used all the betas as well as the point updates. Maybe something got hosed on the reset? Can you go back to the February version and see if it works? If it does make sure you turn on the debug logs and try the update again. Hopefully if it fails you will get enough information for someone to help. |
|
Version 2022.2.9 works. But other people have already reported that. After my experience with HA, I can only say that starting backups and updates from the web UI is, unfortunately, absolutely unreliable. Often the tasks abort. This was also not a problem about a year ago. |
|
I have the same problem. ZHA is working for a few hours and then he loose the communication and I must shut down my raspberry. |
|
There were no zha changes in znp library since previous version. |
|
I removed the "Zigbee Home Automation" and tried to reinstall. I can select the port where the Texas Inst. stick is connected or it is displayed in the selection. After some time it asks which protocol to use. If I select there the "Texas CC2531...", I get shortly after the error message that the port is not accessible. No matter if I backup from version 2022.2.9, 2022.3.0, 2022.3.1 or 2022.3.2 ZHA absolutely does not work anymore. |
|
Same issue when I updated Home Assistant to version 2022.3.2 Edit: i just waited a few hours doing anything and it seems to work fine now. My suggestion is to wait and see. Hope you have the same luck. |
|
I don't know what happened, but something was really screwed up. This is also proven by the large number of bug/problem reports. HA is unfortunately no longer usable for me at the moment. |
|
I'm facing the same issue after the update. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
I'm also facing this issue reported I try to reboot the hots, enable and disable the ZHA integration without success, also all the search of new device never find any device also the reconfigure devices always finish with errors HA Version 2022.3.3 |
After remove the stick and restar the hots The devices still unavailable and when I try to search for a new device the device appear but again finished with erros no device added successfully.... Log : [0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_rsp: [<Status.SUCCESS: 0>]
|
|
removed - determined my issue was unrelated |
|
I have a similar issue after upgrading to 2022.3.3 with my ZB-GW04 SiliconLabs EFR32MG21A020F768IM32 USB 3.0 stick. It sees all my devices and displays their current states, but I cannot change them (i.e. an OFF outlet stays OFF, an ON outlet stays ON). MQTT and ESP32 devices work just fine. |
|
Same issue here. Using a Conbee2 zigbee stick. Unable to change device status or read a sensor. |
|
Same with a zigate `Logger: homeassistant.config_entries Error setting up entry USB-Serial Controller, s/n: n/a - Prolific Technology Inc. for zha The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
Zigate error looks like the port is not working anymore. If this is HAssOS, then make sure the boot configuration to expose the port is still in place. |
|
Yes it's HassOS. |
I was able to solve it by plugging the conbee stick to an other port on the PI |
|
Even with a downgrade I could not get ZigBee to work with the CC2531 USB stick. Even after deleting the ZigBee integration and reinstalling, HA could not access the port or the CC2531 stick. The only thing that worked was updating to version 2022.3.3 and using a new Sonoff Universal Zigbee 3.0 USB dongle. However, ALL ZigBee devices had to be re-paired, which changed the entity IDs. Absolute chaos! In the process I found that the backups of HA are absolutely unusable because no add-ons are taken over and also the settings and certificates of Let's Encrypt are not copied. |
Same for me, thanks ! |
|
I had also tried unplugging the stick or pressing the rest button of the stick (CC2531) before. Both of these did not help either! :-( |
|
I had the same issue with HA docker 2022.3.4 and Conbee II, tried the following things:
None of those approaches work. I finally resolved the issue by use the switch on the wall to turn lights off/on, then ZHA started working again. |
|
The symptom the the network not working i was having the alpha testing tasmota and the system was resetting the network key security counter on restart. So very likely is the counter running away or are being retested in the coordinator and and the network is not in sync and think its one replay attack and dont like talking with the coordinator. |
|
|
|
|
|
Same error here, with Tasmota flashed Sonoff Zigbee bridge. Logger: homeassistant.components.websocket_api.http.connection Logger: homeassistant.components.zha.core.gateway Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
I cant saying anything of the ZiGate then its looks being command from the coordinator that making strange things. @esackbauer the last message is the important: TimeoutError. |
|
@MattWestb I can reach it with web interface. |
|
For Zigate pleas look on zigpy/zigpy-zigate#118 |
|
Any pointers on how to roll back zigpy (and only zigpy) in HA? |
|
Updated to HA 7.5 + Core 2022.3.5, removed USB ZigBee stick and deleted original integration. Rebooted, added ZHA integration anew. Ask for the port (USB was one of the choices so I selected it). Seemed to have worked, but the old device registries are still there and the topology shows EVERYTHING off line, even the coordinator. Log: Logger: homeassistant.components.zha.core.channels.base [0x438C:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x438c:1:0x0006]: Message send failure'), DeliveryError('[0x438c:1:0x0006]: Message send failure'), DeliveryError('[0x438c:1:0x0006]: Message send failure'), DeliveryError('[0x438c:1:0x0006]: Message send failure')] |
|
removed - determined my issue was unrelated |
|
After downgrade the core to 2022.2.3, ZHA/Zigbee works fine. ha core update --version 2022.2.3 EDIT: Fixed only for me - but I didn't know why it works for me since downgrade. |
|
Reverting to core 2022.2.3 didn't fix mine. Lesson learned: once this is working again, I'm buying a SECOND Pi and use one to shake down upgrades before I commit. |
|
I can recommend nanopi neo that is working great with armbian and is not so expensive for one test setup or using docker in windows and one network connected coordinator (both not supported as supervised but first is working and the last is not supporting comports so well). |
|
Add me on the list... And reverting to 2022.2.x doesn't fix anything. |
|
removed - determined my issue was unrelated |
|
Using a spare SD card, I installed HASSIO 7.3 (from https://github.com/home-assistant/operating-system/releases/download/7.3/haos_rpi4-64-7.3.img.xz) from scratch. HA Core was automatically upgraded to 2022.3.5 but not the Supervisor. I downgraded Core to 2022.2.9, plugged in my ZigBee controller stick, added the ZHA integration -- and it was able to pair with one of my device. Only problem now is that I don't have an old backup and this version of HA (understandably) refuses to upload a 2022.3.5 backup. I guess it is going to be a race between having ZHA fixed in 7.5, and me figuring out a way to bounce all my YAML files from my 7.5 SSD to my 7.3 SDcard... |
|
Core: core-2022.3.5 Worked until i rebooted today, maybe an update was installed (conbee works on my mac). With a conbee II i get these messages (hot plug after boot) Host Supervisor logfile |
|
Very strange ... moving the conbee in the HA Blue USB ports made a connection possible ... seems to me, that the connection is wonky ... |
That is the system issue, not zha problem. |
|
Blue USB = USB 3 that can delivering more power to the device. |
|
I’m using the preconfigured „HA Blue Device (https://www.home-assistant.io/blue/)“ it’s like the usb ports allow to much movement of the conbee II so that touching it can break the connection, strange. So my problem is not related to the issue, agree. |
|
It was starting to smell like an electrical problem: I was using the SDcard I used before switching to a SSD drive to figure out which exact HASSIO upgrade caused ZHA to break, and I took it up all the way to 7.5/2022.3.5 and it worked! After backing everything up from my SSD drive to my SDcard (which can now upload and restore the backup without problems since they are both at the same versions), I re-installed 7.5/2022.3.5 on the SSD from scratch and before loading any integrations, I plugged my ZigBee controller, added ZHA and tried to pair a new device: it didn't work. My setup:
I then tried plugging the ZigBee controller into a powered USB hub and leaving the SSD directly connected to the RPi. Still not working. So not a pure power problem, but definitely something related to the combination of the SSD and ZigBee controller being present at the same time. Update: I'm now back to using my old SDcard running 7.5/2022.3.5 and everything is still working perfectly. I re-paired all of my ZigBee devices last night and this morning without any issues. Looks like I'll be buying a few high-quality SDcards as backups and relegate the SSD drive as a backup system for my laptop :-/ |
|
Has anyone came up to any conclusion? Just installed 2022.2.9 and 2022.3.x and zha is absolutely broken :( |
|
Yeah, your issue is absolutely unrelated, but the error gives you some hints: RuntimeError: zigpy requires SQLite 3.24.0 or newer. If your distribution does not provide a more recent release, install pysqlite3 with Use HassOS. |
You are absolutely right, after I've updated SQLite the problem went away. Appologies |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
There are several unrelated issues and several corrected issues listed in this report. For anyone still experiencing issues please open a new issue (you can link to this one if you want). Please do not add replies to the new issues if your log messages / errors are not the same. |
and others
The problem
Since version 2022.3.1 the following problem:
What version of Home Assistant Core has the issue?
2022.3.1
What was the last working version of Home Assistant Core?
2022.3.2
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
No response
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: