core: ZHA error after update 2022.04

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 “<frozen importlib._bootstrap>”, line 1030, in _gcd_import File “<frozen importlib._bootstrap>”, line 1007, in _find_and_load File “<frozen importlib._bootstrap>”, line 986, in _find_and_load_unlocked File “<frozen importlib._bootstrap>”, line 680, in _load_unlocked File “<frozen importlib._bootstrap_external>”, line 850, in exec_module File “<frozen importlib._bootstrap>”, line 228, in _call_with_frames_removed File “/config/deps/lib/python3.9/site-packages/zhaquirks/centralite/init.py”, line 11, in <module> class CentraLiteAccelCluster(CustomCluster): File “/usr/local/lib/python3.9/site-packages/zigpy/zcl/init.py”, line 91, in init_subclass raise TypeError( TypeError: manufacturer_attributes is deprecated. Copy the parent class’s attributes dictionary and update it with your manufacturer-specific attributes. 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)

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 63 (16 by maintainers)

Most upvoted comments

Remove /config/deps/lib/

Adminiuga on Apr 6, 2022

I just got killed by my wife yesterday evening. So it won’t hurt anymore today 😆

itn3rd77 on Apr 7, 2022

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 😕

itn3rd77 on Apr 8, 2022

Some various ZHA fixes released with 2022.4.1, including a bump of quirks.

I will test it tomorrow: https://www.home-assistant.io/blog/2022/04/06/release-20224/#release-202241---april-7

bjornsivertsen on Apr 8, 2022

I also had problem with Zigbee using ZHA and Conbee. After update to 2022.4 lost some actions and everything was working strange but not totally gone. After restore to 2022.3.8 all was fine again. Lights and remotes are IKEA using “Awesome HA Blueprints”. /Kent

KentGitIvar on Apr 6, 2022

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.

@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!

https://github.com/zigpy/zha-device-handlers/issues/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:

 "_TZE200_3i3exuay": {0x0000: 0x0000, 0x0001: 0x0002, 0x0002: 0x0001},

(This maps the open, close, stop to the correct buttons)

(For some other device, TUYA_COVER_INVERTED_BY_DEFAULT also needs to be updated (This is needed for my curtain motor)

Note: Also edit the ts0601_cover.py file and change the following line (13): from zhaquirks.tuya import ( to from . import (

rjbungay on Apr 9, 2022

Deleting config/deps/lib together with changing zha-quirks to latest version did the trick for me

snorbik on Apr 9, 2022

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.

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.

dmulcahey on Apr 8, 2022

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: Settings > Addons > Custom deps deployment Configuration:
pypi:
  - zha-quirks==0.0.69
apk: []
Press Save and then Start Latest quirks: https://pypi.org/project/zha-quirks/
This also fixed my issues after updating to 2022.4. Posted instructions on the 2022.4 blog

I forgot to mention I rebooted the host system afterwards. I don’t know if it makes any difference.

iotkb on Apr 7, 2022

Wife is home soon, I’ll restore version 2022.3.8 and await for the developers to sort it out. 😆

bjornsivertsen on Apr 7, 2022

Unfortunately, for some reason I can’t restore my backup either!

rjbungay on Apr 7, 2022

@pbvdven See this issue https://github.com/home-assistant/core/issues/69375

TheZoker on Apr 7, 2022

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 from .xiaomi import ( LUMI, BasicCluster, XiaomiAqaraE1Cluster, XiaomiCustomDevice, ) Both changes were made in my “aqara_h1_remote.py” file in /config/custom_zha_quirks/ Hope this will help some of you.

Chrups23 on Apr 7, 2022

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.

2022-04-07 08:01:24 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x8353:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x8353:11:0x0006]: Message send failure'), DeliveryError('[0x8353:11:0x0006]: Message send failure'), DeliveryError('[0x8353:11:0x0006]: Message send failure'), DeliveryError('[0x8353:11:0x0006]: Message send failure')]
2022-04-07 08:01:25 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x1756:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x1756:11:0x0008]: Message send failure'), DeliveryError('[0x1756:11:0x0008]: Message send failure'), DeliveryError('[0x1756:11:0x0008]: Message send failure'), DeliveryError('[0x1756:11:0x0008]: Message send failure')]
2022-04-07 08:01:25 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x8353:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x8353:11:0x0008]: Message send failure'), DeliveryError('[0x8353:11:0x0008]: Message send failure'), DeliveryError('[0x8353:11:0x0008]: Message send failure'), DeliveryError('[0x8353:11:0x0008]: Message send failure')]
2022-04-07 08:01:25 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x1756:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x1756:11:0x0006]: Message send failure'), DeliveryError('[0x1756:11:0x0006]: Message send failure'), DeliveryError('[0x1756:11:0x0006]: Message send failure'), DeliveryError('[0x1756:11:0x0006]: Message send failure')]
2022-04-07 08:01:25 ERROR (MainThread) [homeassistant.components.sensor] Platform zha does not generate unique IDs. ID bc:33:ac:ff:fe:27:bf:a5-1-1 already exists - ignoring sensor.ikea_tradfri_a5bf27fe_battery_power
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:00:ff:64:c4-11 already exists - ignoring light.philips_lct001_c464ff00_level_light_color_on_off
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:00:fd:19:57-11 already exists - ignoring light.philips_lct001_5719fd00_level_light_color_on_off
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c1:c5:19-11 already exists - ignoring light.philips_ltw013_19c5c104
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c1:cb:2a-11 already exists - ignoring light.philips_ltw013_2acbc104
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c1:cb:94-11 already exists - ignoring light.philips_ltw013_94cbc104
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:02:f0:48:90-11 already exists - ignoring light.philips_ltw013_9048f002
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c1:d2:6a-11 already exists - ignoring light.philips_ltw013_6ad2c104
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:0b:28:1e:20-11 already exists - ignoring light.signify_netherlands_b_v_lwe004_201e280b_level_on_off
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:0b:27:18:5a-11 already exists - ignoring light.signify_netherlands_b_v_lwe004_5a18270b_level_on_off
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID light_zha_group_0x0002 already exists - ignoring light.zha_bathroom_ceiling
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID light_zha_group_0x0003 already exists - ignoring light.zha_kitchen_spots
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID light_zha_group_0x0004 already exists - ignoring light.zha_coffee_lounge
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID light_zha_group_0x0005 already exists - ignoring light.zha_livingroom_couch
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID light_zha_group_0x0006 already exists - ignoring light.zha_corridor
2022-04-07 08:01:26 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID light_zha_group_0x0007 already exists - ignoring light.zha_kitchen_cabinet
2022-04-07 08:01:31 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xD197:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0xd197:11:0x0300]: Message send failure'), DeliveryError('[0xd197:11:0x0300]: Message send failure'), DeliveryError('[0xd197:11:0x0300]: Message send failure'), DeliveryError('[0xd197:11:0x0300]: Message send failure')]
2022-04-07 08:01:32 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 58:8e:81:ff:fe:93:5b:c8-1 already exists - ignoring light.ikea_tradfri_driver_c85b93fe
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c2:dd:05-11 already exists - ignoring light.philips_ltw013_05ddc204
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:03:ae:6a:9a-11 already exists - ignoring light.philips_ltw013_9a6aae03_level_light_color_on_off
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c1:d3:29-11 already exists - ignoring light.philips_ltw013_29d3c104_level_light_color_on_off
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:c1:d2:8b-11 already exists - ignoring light.philips_ltw013_8bd2c104_level_light_color_on_off
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:00:ff:65:09-11 already exists - ignoring light.philips_lct001_0965ff00_level_light_color_on_off
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:03:ae:1e:08-11 already exists - ignoring light.philips_ltw013_081eae03_level_light_color_on_off
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:03:ae:1e:05-11 already exists - ignoring light.philips_ltw013_051eae03_level_light_color_on_off
2022-04-07 08:01:35 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:15:8d:00:04:76:c3:90-1 already exists - ignoring light.neuhaus_lighting_90c37604
2022-04-07 08:01:36 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xD197:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xd197:11:0x0006]: Message send failure'), DeliveryError('[0xd197:11:0x0006]: Message send failure'), DeliveryError('[0xd197:11:0x0006]: Message send failure'), DeliveryError('[0xd197:11:0x0006]: Message send failure')]
2022-04-07 08:01:44 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 58:8e:81:ff:fe:97:be:47-1 already exists - ignoring light.ikea_tradfri_driver_47be97fe
2022-04-07 08:01:47 ERROR (Thread-9) [pychromecast.socket_client] [KD-55XE8096(192.168.100.52):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.100.52', 8009)), retrying in 5.0s
2022-04-07 08:01:52 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xD197:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0xd197:11:0x0008]: Message send failure'), DeliveryError('[0xd197:11:0x0008]: Message send failure'), DeliveryError('[0xd197:11:0x0008]: Message send failure'), DeliveryError('[0xd197:11:0x0008]: Message send failure')]
2022-04-07 08:01:55 ERROR (MainThread) [homeassistant.components.light] Platform zha does not generate unique IDs. ID 00:17:88:01:04:47:12:42-11 already exists - ignoring light.philips_ltw013_42124704
2022-04-07 08:02:06 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x8187:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x8187:11:0x0300]: Message send failure'), DeliveryError('[0x8187:11:0x0300]: Message send failure'), DeliveryError('[0x8187:11:0x0300]: Message send failure'), DeliveryError('[0x8187:11:0x0300]: Message send failure')]
2022-04-07 08:02:41 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x8187:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x8187:11:0x0006]: Message send failure'), DeliveryError('[0x8187:11:0x0006]: Message send failure'), DeliveryError('[0x8187:11:0x0006]: Message send failure'), DeliveryError('[0x8187:11:0x0006]: Message send failure')]
2022-04-07 08:02:51 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x8187:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x8187:11:0x0008]: Message send failure'), DeliveryError('[0x8187:11:0x0008]: Message send failure'), DeliveryError('[0x8187:11:0x0008]: Message send failure'), DeliveryError('[0x8187:11:0x0008]: Message send failure')]
2022-04-07 08:02:55 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xAB02:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0xab02:11:0x0300]: Message send failure'), DeliveryError('[0xab02:11:0x0300]: Message send failure'), DeliveryError('[0xab02:11:0x0300]: Message send failure'), DeliveryError('[0xab02:11:0x0300]: Message send failure')]

When reverting back to 2022.3.8 ZHA is working instantly without any problems 😕

itn3rd77 on Apr 7, 2022

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.

seastonestu on Apr 6, 2022