ZHA error after update 2022.04 #69494
Comments
|
Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as it has been labeled with an integration ( zha documentation |
|
I also had problem with Zigbee using ZHA and Conbee. |
|
Remove /config/deps/lib/ |
|
I do not see a /config/deps/lib/ folder and I am having the same issue after 2022.04. |
|
After deleting this folder it works. |
is the folder somewhere vs code can't see? |
|
No. in the same folder where you have configuration.yaml there is a folder named deps |
|
that's so weird could not find it with either vs code or file editor but I did find and delete it in the terminal and now I'm good :) thanks @vdlr26 for asking the question and @Adminiuga for the answer. |
|
deleting /config/deps/lib/ worked for me. all my aqara sensors needed to have their button pressed a few times to get them reconnected as well, while other stuff connected just fine. havent had to touch each aqara sensor in a few months worth of updates now. |
|
My folder /config/deps is empty and ZHA is not working after update to 2022.04. All entities are flagt as unavailable and the log is full of errors. When reverting back to 2022.3.8 ZHA is working instantly without any problems :-/ |
|
I am not seeing the folder either. My network works, but is just very slow to respond. I will let it run for a few hours, to see if there is any improvement before I revert to 2022.3.8. |
|
Can only see folder using terminal, strange. [core-ssh deps] pwd This is before upgrade still version 2022.3.8 when should the folder bee there and when should it be deleted? /Kent |
|
I could only see the deps directory (within /config) which when removed didn't have any positive effect - when I restarted the container the directory was recreated. For now I've reverted to 2022.3.8. |
|
Hi, I had similar issue with custom quirk for "Aqara H1 Wireless Remote Double Rocker (Version WRS-R02)" and I got it working by simply changing "manufacturer_attributes" to "attributes" in "AqaraRemoteManuSpecificCluster" class and adding "zhaquirks" before ".xiaomi" in |
|
i also have lots of problems with ZHA and conbee 2 after update to 2022.4 but dont see any related errors in the log. but ikea tradfri 5 button remotes only react to the middle button. zigbee lights go on some times some times not. motion sensors seem to work but door sensors not. i posted my log file i tried to find anything related but didt see any ZHA/zigpy related errors. but maybe i overlooked. i switched back to 2022.3.8 no issues there for me with ZHA. |
|
I have the same issue since updating to 2022.4, ZHA won’t load. I deleted the deps/lib folder mentioned in a previous comment, but it still won’t load, errors as below. 2022-04-07 10:21:39 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry socket://192.168.1.78:8888 for zha |
|
Also got this error however ZHA was running normally. Could see responses when listening to zha_event in dev tools but those same responses weren't triggering automations for some reason. I see no deps/lib folder when checking either. Have reverted to 2022.3.8 for now as well. |
|
Unfortunately, for some reason I can’t restore my backup either! |
|
Since 2022.4.0 update ZHA stops working in my HA. First I got this error about a quirk: Then I remove the quirk and ZHA is still not working. I got those errors: Have reverted to 2022.3.8 for now as well. |
|
Had similar ZHA weirdness upgrading to 2022.4.0. Downgrading to 2022.4.0b4 fixed it as I was on the dev channel before. Maybe that helps narrow down suspects. |
|
As 2022.4.1 is already on it's way and the ZHA issue is not listed in the fixes what's the best way to get attention to this issue? |
|
I've got the same problems and I managed to fix it by updating the ZHA quirks to the latest version. (In my case from 0.0.64 to 0.0.69) Steps I took: Press Save and then Start Latest quirks: Edit: I forgot to mention I rebooted the host system afterwards. I don't know if it makes any difference. |
|
Wife is home soon, I'll restore version 2022.3.8 and await for the developers to sort it out. 😆 |
|
I just got killed by my wife yesterday evening. So it won't hurt anymore today 😆 |
This also fixed my issues after updating to 2022.4. Posted instructions on the 2022.4 blog |
I also tried this after i updated to 2022.4 but no big improvement noticeable |
Will do, though I can't promise I experienced the same issues as you guys. My issues were mostly related to a very sluggish and unresponsive network. |
|
I updated to 2022.4.1 but my problems still exist. Most devices are offline/not available. After a while some of them are available and network is very unresponsive or not working at all :-/ |
Thanks for the update. MEans for now better stay on 2022.3.8 |
That is disheartening. Do you get any error messages, that we can relay to the ZHA team? |
Sure. Logfile is full of messages that have not been there in 2022.3.x. It's really a mess :-( |
|
Hi @dmulcahey and @Adminiuga have you had a look at this comment thread yet? |
|
after update to 2022.4.1 i still have issues with zigbee lights from IKEA and Lidl. some ikea lights restored after identify press but some wont or only go one but not off or vice versa. doorsensors don't work. motion sensors do. i only see this warning in the log but that kind of warning i have had always but sinds 2022.4 the zigbee network is becoming unusable moving back to 2022.3.8 fixes everything for me. but yea thats not really a solution. |
|
anyone who has used local quirks or the custom deps add-on is kind of on their own. There is absolutely nothing we can do to correct local modifications you have made. If you have messages in the logs like this: If there are other issues please open unique issues and do not combine them all into one report please. Threads like this with several conflated things are not easy to follow / address. |
Can you help me understand the impact of using custom quirks with ZHA? Eg. I had a custom quick for a Wyze lock that I no longer use. Since the Wyze is no longer paired, I saw no impact on Wyze. What I did see what Hue motion sensors fail to report or re-pair until I downgraded. After removing the custom Wyze folder and cache, the upgrade to 2022.4.1 was successful for all ZHA devices. I know this story has no logs, but if there is general advise for deploying custom quirks with ZHA I am open to better understanding. |
when you use custom local files they aren't updated when we make core changes to ZHA. In this release we had some significant changes to the type system and how we define commands and attributes. We did our best to make sure everything was working (we missed a couple smallish things). Anyone who has custom quirks / custom dependencies would have to ensure they made the same changes. Honestly we probably should have stuck something in the release notes but this situation isn't one we thought about ahead of time. |
|
I am also seeing issues with devices being unavailable and unresponsiveness. My logs are flooded with these messages:
There are no other changes to the system between everything working prior to updating and now. |
|
@dmulcahey I started having issues (unavailable, unresponsive Zigbee devices) after updating to 2022.4. As recommended above, I installed 0.0.69 quirk over 2022.4 but it did not help. I updated to 2022.4.1 and I am still having the same issues. I deleted the folders in deps that was created when 0.069 was installed and rebooted the host. I am still having issues. The logs show errors and something about a state.BUSY. As you mentioned above, I have seen something similar in previous upgrades but I was able to recover without repairing all my 90 devices. I only did a few, but in this case I tried doing so with one, and it won't even find it. When I press the button on the light switch I see errors etc flash but the logs move too fast. EDIT: @dmulcahey - From what you say it sounds like the deConz radio (Conbee II) has caused issues before. What is the BEST Zigbee 3.0 coordinator? If I have to pair everything back up, or run into this again, I would rather just buy the BEST possible zigbee controller now. |
Can't comment on whether it is "the best", but I've been using the Gocontrol Hubz-1 dongle for over a year and works flawlessly with ZHA and Zwave.js (has both protocols on it a single stick) https://www.amazon.com/GoControl-CECOMINOD016164-HUSBZB-1-USB-Hub/dp/B01GJ826F8 another option (without zwave) that I've heard good things about is the sonoff dongle https://www.amazon.com/SONOFF-Gateway-Universal-Assistant-Wireless/dp/B09KXTCMSC/ref=pd_lpo_3?pd_rd_i=B09KXTCMSC&psc=1 |
|
@dmulcahey |
The best is subjective, for all of them YMMV. For conbee, physically re-plug it, restart HA let it sit for a while, then just restart HA without touching ConBee |
|
@Adminiuga I liked the Sonoff Zigbee 3.0 controller recommended by @smarthomelawyer so I purchased a kit with 2 of them (one for testing). Hopefully it is fully supported by ZHA / HA and gets occasional firmware updates when needed. I don't like vendors that stop updating their hardware soon after releasing it. I am not looking forward to moving all the devices (~90) over. Is there a good way to limit the effort needed? Even just the renaming of entities is a pain. |
|
Deleting config/deps/lib together with changing zha-quirks to latest version did the trick for me |
|
How can I tell what version of quirks I am using? I deleted the libs folder for 0.0.69 that got created when I tried that fix, downgraded back to 2022.4 and back up to 2022.4.1 hoping it would ensure I was on 0.0.71. Could I possibly still be on the old version? My ZHA network is basically dead. |
This happens to lots of conbee users. Try letting the system sit for like an hour after a restart. |
|
the issues you have with data transmission have absolutely nada to do with quirks. The conbee is stating it can't send messages to the network because it is busy. Try shutting everything down, unplug / replug the stick, start everything back up and let it sit for an hour or so. |
|
I am closing this issue as several things are conflated here: conbee general issues, folks that mucked w/ dependencies etc. If you still have issues please open a new issue (do NOT piggy back off another issue unless your problem is the same as what is in an existing issue). You can link to this one if you would like. |
|
fixed, I'm on 2022.4.1 not working, disconnected the usb adapter and reconnected, then started OK |
I powered down the house, thus all mains Zigbee devices multiple times with no change. I unplugged the ConBee II multiple times, changed port, rebooted the PC running proxmox with HA VM and no change. I took the nuclear approach of removing the ZHA integration and adding it back hoping it would somehow spare my entity names but I lost them all (90 devices!). Tomorrow I am receiving 2 x Sonoff Zigbee 3.0 Dongle Plus and will start the laborious job of moving to that coordinator. My Conbee II is likely fine but from what I have read the Sonoff one is better, so this is a good time to make the switch... @dmulcahey You are the expert here... I doubt anyone was intentionally piggy backing the original issue (title is so broad my issues were indeed related to 2022.4 update, however I had NO idea whether they were the same as the issue posted by OP.). I am now understanding that my issues are caused by unruly devices that for whatever reason have opted to no longer communicate with the controller... a mutiny of sorts. I've had a Samjin Outlet (Smartthings Outlet) and a Jasco Light Switch cause trouble before (network issues vanished after resetting them) so I am not surprised. I just wonder why it tends to happen after updates or when house power is off for a while. Fingers crossed that moving to Sonoff Zigbee 3.0 Dongle Plus is a good move... EDIT: I let my mesh rest for many hours, even overnight, but issues never went away. |
@dmulcahey It’s all well and good saying we are on our own, but I’ve been forced into this situation to get my curtain motors working. I raised a support request back in February but it would appear this hasn’t been looked at, at least it hasn’t even been commented on! zigpy/zha-device-handlers#1399 What else are we supposed to do? It would also make life much easier if there was some documentation on custom quirks, at least I haven’t found any explanation. Rummaging through various threads I managed to get the custom quirk working back in Feb so I could use my curtains, this update broke that. I have managed to get them working again by downloading the latest 0.0.71 quirks and editing those to create a new custom ts601 file. This has sorted out my issues once again with a custom quirk but it would be nice if standard support for the device was sorted out so we don’t have to resort to custom quirks and end up "on our own" again in a future release. If it helps others I’ve created a text file in my custom quirks folder with some notes for next time as follows:- When adding a custom quirk, you also want to update the information here: (This maps the open, close, stop to the correct buttons) (For some other device, TUYA_COVER_INVERTED_BY_DEFAULT also needs to be updated Note: |
|
If you have it working open a pull request and it will make it into an official release |
Sorry, I have no idea how to create a pull request for this. |
|
I had the same issue: Lots of devices that didn't work anymore and a very slow response. After I restarted HA, I've noticed my ZHA integration wouldn't start. Somehow the Conbee stick was pointed to the "Nue" folder in the zhaquirks path. I haven't investigated it, but I've removed the Nue folder, restarted HA again and now everything is working like it did before. |
and others
The problem
After update to 2022.04 ZHA state is: "Failed to set up"
Log deatil:
Logger: homeassistant.config_entries
Source: deps/lib/python3.9/site-packages/zhaquirks/centralite/init.py:11
First occurred: 23:39:14 (1 occurrences)
Last logged: 23:39:14
Error setting up entry socket://192.168.1.128:8888 for zha
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/init.py", line 99, in async_setup_entry
setup_quirks(config)
File "/config/deps/lib/python3.9/site-packages/zhaquirks/init.py", line 394, in setup
importlib.import_module(modname)
File "/usr/local/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/config/deps/lib/python3.9/site-packages/zhaquirks/centralite/init.py", line 11, in
class CentraLiteAccelCluster(CustomCluster):
File "/usr/local/lib/python3.9/site-packages/zigpy/zcl/init.py", line 91, in init_subclass
raise TypeError(
TypeError:
manufacturer_attributesis deprecated. Copy the parent class'sattributesdictionary and update it with your manufacturer-specificattributes. Make sure to specify that it is manufacturer-specific through the appropriate constructor or tuple!What version of Home Assistant Core has the issue?
2022.04
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 Zigbee Home Automation
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
The problem is with Sonoff Zigbee Bridge with Tasmota 11.0.0 (192.168.1.128)
The text was updated successfully, but these errors were encountered: