search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.11k stars 29.79k forks source link

ZHA all attempts have failed after core-2022.2.5 Update #66291

Closed wurschtsemml closed 1 year ago

wurschtsemml commented 2 years ago

The problem

After updating the HA core to version 2022.2.5 and rebooting the system, the ZHA Integration could not control any devices. I tried several reboots and reconfiguration on just one device or all together, but nothing will solve this problem. My devices are from Ikea, Osram and Lidl.

HA is running on a Raspberry Pi 4 with a Sonoff Zigbee 3 Stick. The solution was stabil until this update was installed.

What version of Home Assistant Core has the issue?

core-2022.2.5

What was the last working version of Home Assistant Core?

core-2022.2.4

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?

Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:428
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 22:24:19 (10 occurrences)
Last logged: 22:36:41

[0x9128:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x4809:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x4809:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x497B:3:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x4809:1:0x1000]: Couldn't get list of groups: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

zha documentation zha source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @dmulcahey, @adminiuga, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

Adminiuga commented 2 years ago

there were no changes in ZHA between .4 and .5 Physically unplug adapter, then plug again and try again,

RoldyBuffalo commented 2 years ago

The problem

After updating the HA core to version 2022.2.5 and rebooting the system, the ZHA Integration could not control any devices. I tried several reboots and reconfiguration on just one device or all together, but nothing will solve this problem. My devices are from Ikea, Osram and Lidl.

HA is running on a Raspberry Pi 4 with a Sonoff Zigbee 3 Stick. The solution was stabil until this update was installed.

What version of Home Assistant Core has the issue?

core-2022.2.5

What was the last working version of Home Assistant Core?

core-2022.2.4

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?

Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:428
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 22:24:19 (10 occurrences)
Last logged: 22:36:41

[0x9128:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x4809:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x4809:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x497B:3:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
[0x4809:1:0x1000]: Couldn't get list of groups: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

Additional information

No response

Same problem as OP. Tried all available troubleshooting techniques so don't ask. Resorting to buying a different coordinator fixed it. Went with USB instead of GPIO because for whatever reason GPIO is all jacked up in this release of HA.

jimoverly commented 2 years ago

Same issue.. numerous reboots, full power off, unplug re-plug.. regardless of the claim nothing changed, something changed

Adminiuga commented 2 years ago

"same issue" as in it happened after upgrading from 2022.2.4 to 2022.2.5?

What radio? What environment?

jimoverly commented 2 years ago

identical setup and versions.. so I moved to 2022.2.6 from 2022.2.5 and no change. Attempted a downgrade as well with no change in behavior. So I suspect it botched something with the zigbee network. After reading that a zigbee repair is initiated after a 30 min power off, I unplugged it for 35 minutes and MOST devices are now active. It did not repair all devices, I still have about half in an unavailable state. I will try it again and leave it off longer

The startup logs still show

2022-02-12 09:15:03 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x3307:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x3307:1:0x0300]: Message send failure'), DeliveryError('[0x3307:1:0x0300]: Message send failure'), DeliveryError('[0x3307:1:0x0300]: Message send failure'), DeliveryError('[0x3307:1:0x0300]: Message send failure')] 2022-02-12 09:15:04 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x3307:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x3307:1:0x0008]: Message send failure'), DeliveryError('[0x3307:1:0x0008]: Message send failure'), DeliveryError('[0x3307:1:0x0008]: Message send failure'), DeliveryError('[0x3307:1:0x0008]: Message send failure')] 2022-02-12 09:15:23 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x3307:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x3307:1:0x0006]: Message send failure'), DeliveryError('[0x3307:1:0x0006]: Message send failure'), DeliveryError('[0x3307:1:0x0006]: Message send failure'), DeliveryError('[0x3307:1:0x0006]: Message send failure')]

puddly commented 2 years ago

regardless of the claim nothing changed, something changed

There were no changes related to ZHA, its dependencies, or HA Core between 2022.2.4 and 2022.2.5. Read through the full diff, it's tiny: https://github.com/home-assistant/core/compare/2022.2.4...2022.2.5

The only thing that happened was a HA Core reboot. The Zigbee adapter will be reset when that happens, so it will take a few minutes for routes to be re-built by the coordinator.

jimoverly commented 2 years ago

I had left the unit on for 12 hours after the upgrade and it never rebuilt routes. I did multiple reboots with several hours in between with no change. It wasn't until I powered off completely, let it sit for 30+ minutes did some units reconnect. None of my Osram bulbs or Ikea devices reconnected despite repeating the process and allowing hours to lapse between attempts. I had to remove and reconnect every bulb and my Ikea repeaters. This is the first upgrade I have had anything like this occur.

Exact same setup as the original poster and exact same brand of devices refused to re-establish connection. I am back and fully functional at this point.

puddly commented 2 years ago

@jimoverly the original issue contains DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), which means the reporter is using a CC2531 or a CC2652. Your debug log contains DeliveryError('[0x3307:1:0x0300]: Message send failure').

What hardware are you using? A Conbee?

Martin781 commented 2 years ago

I have the same issue. I'm using the Conbee2 as coordinator. I have two Xiaomi Power Plugs (lumi.plug.mmeu01 https://zigbee.blakadder.com/Xiaomi_ZNCZ04LM.html These two that drops out from the network. I can only get them back if I bring them right next to the coordinator and even after I do that sometimes it looses them instantly sometimes after a couple of hours later. One of these is right next to the coordinator about 50 cm but still cant connect only if I put it to directly to the coordinator. Before the update I had no problems whit these at all. I installed HA 2022.2 6 yesterday (from 2021.12.10) along with Home Assistant OS 7.4 (from 7.2 I think) on a Pi3b.

Logger: homeassistant.components.zha.core.channels.base

Source: components/zha/core/channels/base.py:428

Integration: Zigbee Home Automation (documentation, issues) First occurred: 23:00:03 (4 occurrences) Last logged: 23:01:24

[0xFCDF:1:0x0002]: async_initialize: all attempts have failed: [DeliveryError('[0xfcdf:1:0x0002]: Message send failure'), DeliveryError('[0xfcdf:1:0x0002]: Message send failure'), DeliveryError('[0xfcdf:1:0x0002]: Message send failure'), DeliveryError('[0xfcdf:1:0x0002]: Message send failure')] [0xFCDF:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xfcdf:1:0x0006]: Message send failure'), DeliveryError('[0xfcdf:1:0x0006]: Message send failure'), DeliveryError('[0xfcdf:1:0x0006]: Message send failure'), DeliveryError('[0xfcdf:1:0x0006]: Message send failure')]'

mitsmits commented 2 years ago

I'm also having this issue. Im now on core-2022.2.6 and Home Assistant OS 7.4

The event log keeps saying

[0xDA5B:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0xda5b:1:0x0008]: Message send failure'), DeliveryError('[0xda5b:1:0x0008]: Message send failure'), DeliveryError('[0xda5b:1:0x0008]: Message send failure'), DeliveryError('[0xda5b:1:0x0008]: Message send failure')]

natemacinnes commented 2 years ago

I'm also experiencing similar symptoms and the same errors since updating.

All of my zigbee devices went dark after having been stable since first setting them up. Using Conbee II: After repairing my bulbs, go, led strip, and light bars. They were all back briefly, then after a few minutes all but the led strip were unavailable. This was reproduced multiple times after repairing the unavailable devices.

All devices are located within 10ft of the Conbee II (on a USB extension, tested with and without) except for the LED strip and the light bars. They are approx. 20ft. No other network changes, or neighbours within 2.4ghz range.

Logs:

Logger: homeassistant.components.zha.core.channels.base Source: components/zha/core/channels/base.py:428 Integration: Zigbee Home Automation (documentation, issues) First occurred: 10:15:33 AM (5 occurrences) Last logged: 10:16:15 AM

[0x205E:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x205e:11:0x0008]: Message send failure'), DeliveryError('[0x205e:11:0x0008]: Message send failure'), DeliveryError('[0x205e:11:0x0008]: Message send failure'), DeliveryError('[0x205e:11:0x0008]: Message send failure')]
[0xE824:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0xe824:11:0x0008]: Message send failure'), DeliveryError('[0xe824:11:0x0008]: Message send failure'), DeliveryError('[0xe824:11:0x0008]: Message send failure'), DeliveryError('[0xe824:11:0x0008]: Message send failure')]
[0x205E:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x205e:11:0x0300]: Message send failure'), DeliveryError('[0x205e:11:0x0300]: Message send failure'), DeliveryError('[0x205e:11:0x0300]: Message send failure'), DeliveryError('[0x205e:11:0x0300]: Message send failure')]
[0xE824:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xe824:11:0x0006]: Message send failure'), DeliveryError('[0xe824:11:0x0006]: Message send failure'), DeliveryError('[0xe824:11:0x0006]: Message send failure'), DeliveryError('[0xe824:11:0x0006]: Message send failure')]
[0x205E:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x205e:11:0x0006]: Message send failure'), DeliveryError('[0x205e:11:0x0006]: Message send failure'), DeliveryError('[0x205e:11:0x0006]: Message send failure'), DeliveryError('[0x205e:11:0x0006]: Message send failure')]
ZzetT commented 2 years ago

Same here:

2022-02-14 20:17:20 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xB416:11: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>')]
2022-02-14 20:20:40 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE3E6:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
2022-02-14 20:20:40 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE3E6:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
2022-02-14 20:20:40 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE3E6:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]

Very strange. If I look at a Philips Hue Plug (model LOM001) it becomes unavailable every ~2 hours and stay available for 2 hours and so on: zhaPhilippsLOM001Unavailable

From the backups I can see that I updated on February 11, 2022, 10:19 AM and this is exactly the time where this strange off-unavailable-off behavior started. I think I have to switch back to a previous version.

DarioB92 commented 2 years ago

This week I received a usb CC2652P dongle and switched to it. I had same issue even on 2021.x.x ha version. However we are both on pi4 and CC2652P

lebeno commented 2 years ago

I have the same problem with a CC2531 (0451:16a8). reverted to snapshot of older version core 2021.12.1 and OS 7.0 but still not working.

burkemw3 commented 2 years ago

Same behavior for me (very stable ConBee II based ZHA network, did upgrades* yesterday, now no zigbee network and same errors).

*I am running HASS via official docker container on ubuntu 20.04 host. I think I was running hass 2021.11, ran apt-get update && apt-get upgrade on ubuntu host, rebooted ubuntu host, saw now ZHA network, upgraded HASS container to 2022.02, saw this error, then started searching. Relevant apt log entries are: https://gist.github.com/burkemw3/3344acdc1dc6441595a9f75560ed560b. The upgrade error on the first entry was likely due to running out of space on /boot, which lead to the forced removal of a kernel, and then the upgrade succeeded. I haven't tried rolling back packages yet. I did try using 5.13.0-27-generic kernel (instead of 5.13.0-28-generic), and still saw this error.

ZzetT commented 2 years ago

Same here:

2022-02-14 20:17:20 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xB416:11: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>')]
2022-02-14 20:20:40 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE3E6:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
2022-02-14 20:20:40 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE3E6:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]
2022-02-14 20:20:40 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE3E6:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>'), DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')]

Very strange. If I look at a Philips Hue Plug (model LOM001) it becomes unavailable every ~2 hours and stay available for 2 hours and so on: zhaPhilippsLOM001Unavailable

From the backups I can see that I updated on February 11, 2022, 10:19 AM and this is exactly the time where this strange off-unavailable-off behavior started. I think I have to switch back to a previous version.

I switched back to 2022.2.3 and didn't see that error anymore. Then I upgraded to 2022.2.7 and it's also looking fine for ~10 hours. So I can't say exactly what the reason was (either a restart fixed it or the latest version). I'll give an update if I see any changes. I'm running a SONOFF Zigbee 3.0 USB Dongle attached to a RPi4 and OS 6.6.

CaliLuke commented 2 years ago

Seeing the same here too. I'm downgrading to 2022.2.3 to see if that does the trick.

Sjorsa commented 2 years ago

I get Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator with a TI CC2531. It started on 2022.2.1, and its still so on 2022.2.8. Edit: also on 2021.12.10, somethings properly messed up, I can't use anything in my Zigbee network anymore. Also, it didn't break immediatly upon updating to 2022.2.1 for me. I have been on that version for like a week or so, and today it broke. I think it broke after I restarted HA, but I also restarted yesterday which didn't break it. Really weird.

I am actually surprised by the relatively low activity on this thread, so I assume this is not happening to everyone using ZHA. (which probably makes it even harder to solve :(

Full error:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 530, in _skip_bootloader
    result = await responses.get()
  File "/usr/local/lib/python3.9/asyncio/queues.py", line 166, in get
    await getter
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 152, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 69, in new
    await app.startup(auto_form)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 152, in startup
    return await self._startup(
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 165, in _startup
    await znp.connect()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 572, in connect
    self.capabilities = (await self._skip_bootloader()).Capabilities
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 530, in _skip_bootloader
    result = await responses.get()
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 129, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 212, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

And also this one:

Logger: zigpy.application
Source: /usr/local/lib/python3.9/site-packages/zigpy/application.py:73
First occurred: 20:32:31 (1 occurrences)
Last logged: 20:32:31

Couldn't start application
eth481642 commented 2 years ago

I can confirm this issue. Since today I started to get "DeliveryError('Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>')" in my log without any reason. I didn't update HA to 2022 yet and still using 2021.12.10. I didn't change anything in my setup. Some of my ZigBee devices working normally(mostly ZigBee 2.0), but my ZigBee 3.0 power strip works with failures - sometimes it reacts on my commands, but most of the time - it didn't

eth481642 commented 2 years ago

After about 10 hours it started to work normally as before. Looks like ZigBee network got disorganized for some reason and after some time it reorganized itself. The most strange thing in this situation is it happened with many people in approximately same time

MattWestb commented 2 years ago

Is some other integration rising the minimal version of some dependency that is being used in ZHA or Zigpy libs and is implanting / correcting some bug and making problems ??

Have looking thru release notes 2022.2.1 - 5 but cant finding any in the change log = not sad its being done under the hood and we is not knowing it.

Adminiuga commented 2 years ago

There have been no changes to zha since 2022.2 Common factor between those reports, there are coming from TI chipset users and ConBee users.

MattWestb commented 2 years ago

I agree but what if some integration have changing the dependency of pyserial-asyncio that is used of many integrations ?

Adminiuga commented 2 years ago

Yeah, but t the problem is not with the serial communication? Unless it does not detect the serial disconnect anymore? And most reports are still from TI users. Report from ConBee users come with every release and have to do with host reboot after the upgrade, as conbee users report these kind of issues for every release

Sjorsa commented 2 years ago

I fixed it by replugging the CC2531. The green light wasn't on and when I replugged it was. Weird thing is I have even rebooted the host machine but that wasn't enough. I hope this won't happen regularly since my server is in the attic :P

catatonico2 commented 2 years ago

If I restart home assistant, lost conection with conbee, unplugging and plugging it works in all cases, but we can't be doing it on every reboot.

burkemw3 commented 2 years ago

After the dismissal in #66291#issuecomment-1046009191, I took more drastic actions. I re-paired all my devices :( and my stuff started working again

mkintzel commented 2 years ago

Thank you to the developers working on this problem!!!! Its been a couple weeks since the last developer update; can you update us on the progress? @burkemw3 - you mention "repaired" all of your devices; does this mean removing them all from the environment and adding back in; will that get around the issue? Thanks

burkemw3 commented 2 years ago

@mkintzel One by one, I placed my devices into pairing mode (usually holding a button on the device for 5-10 seconds), then in ZHA I went to 'Add Device' and waited for it to show up. This did not create new devices in HA and existing automations with these devices continued to work once they were back online.

catatonico2 commented 2 years ago

It seems that everything is back to normal. The only thing is that in the network map there are many connections in red. Screenshot_2022-03-04-19-44-20-739_io homeassistant companion android

SmartKobol commented 2 years ago

Dear Guys! I have the same annoying failure since couple of days. The latest version of HA and Sonoff zigbee devices, coordinator and bridge (R3) message attached. Any reasonable and prompt solution? ZHA failures

sderungs commented 2 years ago

I have the same error when trying to reach (reconfigure device) my Philips Hue Smart Plug: 2022-04-09 16:06:38 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x561E:11:0x1000]: Couldn't get list of groups: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

It worked for a couple of hours but then suddenly stopped working. Now in the meantime I upgraded from core 2022.3.* to 2022.4.0 in the hopes that it would solve the issue...

I'm using sonoff zigbee 3.0 usb dongle. My environment: Home Assistant OS 7.6, supervisor-2022.03.5, core-2022.4.0

ChrisHaPunkt commented 2 years ago

https://github.com/home-assistant/core/issues/69877

tola2000 commented 2 years ago

Whet setting a cluster value I get an error reported above:

2022-05-13 14:29:52 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=zha, service=set_zigbee_cluster_attribute, service_data=ieee=00:15:8d:00:07:25:b6:7d, endpoint_id=1, cluster_id=0, cluster_type=in, attribute=65293, value=1, manufacturer=4447> 2022-05-13 14:29:57 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x5AE1: failed to set attribute: value: True attribute: 65293 cluster_id: 0 endpoint_id: 1 Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

I'm using sonoff zigbee 3.0 usb dongle. My environment: Version | core-2022.2.5

dmulcahey commented 2 years ago

Whet setting a cluster value I get an error reported above:

2022-05-13 14:29:52 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=zha, service=set_zigbee_cluster_attribute, service_data=ieee=00:15:8d:00:07:25:b6:7d, endpoint_id=1, cluster_id=0, cluster_type=in, attribute=65293, value=1, manufacturer=4447> 2022-05-13 14:29:57 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x5AE1: failed to set attribute: value: True attribute: 65293 cluster_id: 0 endpoint_id: 1 Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

I'm using sonoff zigbee 3.0 usb dongle. My environment: Version | core-2022.2.5

If you are trying to issue a command to a battery powered device you need to wake it up

tola2000 commented 2 years ago

If you are trying to issue a command to a battery powered device you need to wake it up

I tried many different sequences. What is the right sequence for a aquare xiaomi vibration sensor? Just push the button on the device shortly ( and release ) and within the second push set?

Both sequences fail ( first short press on device and then SET and the reverse )

Thanks for the tip but same error

tola2000 commented 2 years ago

Same error for reading a cluster value:

2022-05-13 15:06:22 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.average_day_temperature_entertainmentroom, old_state=<state sensor.average_day_temperature_entertainmentroom=22.65; state_class=measurement, start=2022-05-12T15:05:52+02:00, end=2022-05-13T15:05:52+02:00, sources=['sensor.average_temperature_entertainmentroom'], count_sources=1, available_sources=1, count=289, max_value=24.07, min_value=21.8, unit_of_measurement=°C, device_class=temperature, friendly_name=average_day_temperature_entertainmentroom @ 2022-05-13T14:00:51.974218+02:00>, new_state=<state sensor.average_day_temperature_entertainmentroom=22.65; state_class=measurement, start=2022-05-12T15:06:22+02:00, end=2022-05-13T15:06:22+02:00, sources=['sensor.average_temperature_entertainmentroom'], count_sources=1, available_sources=1, count=287, max_value=24.07, min_value=21.8, unit_of_measurement=°C, device_class=temperature, friendly_name=average_day_temperature_entertainmentroom @ 2022-05-13T14:00:51.974218+02:00>> 2022-05-13 15:06:27 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.indoor_temperature, old_state=<state sensor.indoor_temperature=26.8; state_class=measurement, value=26.8, minValue=0.0, maxValue=90.0, unitOfMeasure=C, writeable=0, unit_of_measurement=°C, device_class=temperature @ 2022-05-13T15:05:27.457720+02:00>, new_state=<state sensor.indoor_temperature=26.9; state_class=measurement, value=26.9, minValue=0.0, maxValue=90.0, unitOfMeasure=C, writeable=0, unit_of_measurement=°C, device_class=temperature @ 2022-05-13T15:06:27.460098+02:00>> 2022-05-13 15:06:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139794710015808] Error handling message: Unknown error Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response await func(hass, connection, msg) File "/usr/src/homeassistant/homeassistant/components/zha/api.py", line 679, in websocket_read_zigbee_cluster_attributes success, failure = await cluster.read_attributes( File "/usr/local/lib/python3.9/site-packages/zigpy/zcl/init.py", line 297, in read_attributes result = await self.read_attributes_raw(to_read, manufacturer=manufacturer) File "/usr/local/lib/python3.9/site-packages/zigpy/quirks/init.py", line 210, in read_attributes_raw return await super().read_attributes_raw( File "/usr/local/lib/python3.9/site-packages/zigpy/device.py", line 265, in request result, msg = await self._application.request( File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 439, in request return await self._send_request( File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 1528, in _send_request raise DeliveryError( zigpy.exceptions.DeliveryError: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

ChrisHaPunkt commented 2 years ago

`Logger: homeassistant.components.zha.core.channels.base Source: components/zha/core/channels/base.py:474 Integration: Zigbee Home Automation (documentation, issues) First occurred: 19:07:48 (59 occurrences) Last logged: 19:17:12

[0x0957:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x0957:1:0x0006]: Message send failure'), DeliveryError('[0x0957:1:0x0006]: Message send failure'), DeliveryError('[0x0957:1:0x0006]: Message send failure'), DeliveryError('[0x0957:1:0x0006]: Message send failure')] [0xE8B0:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('[0xe8b0:1:0x0b04]: Message send failure'), DeliveryError('[0xe8b0:1:0x0b04]: Message send failure'), DeliveryError('[0xe8b0:1:0x0b04]: Message send failure'), DeliveryError('[0xe8b0:1:0x0b04]: Message send failure')] [0xD9CD:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('[0xd9cd:1:0x0b04]: Message send failure'), DeliveryError('[0xd9cd:1:0x0b04]: Message send failure'), DeliveryError('[0xd9cd:1:0x0b04]: Message send failure'), DeliveryError('[0xd9cd:1:0x0b04]: Message send failure')] [0xD9CD:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('[0xd9cd:1:0x0702]: Message send failure'), DeliveryError('[0xd9cd:1:0x0702]: Message send failure'), DeliveryError('[0xd9cd:1:0x0702]: Message send failure'), DeliveryError('[0xd9cd:1:0x0702]: Message send failure')] [0xD9CD:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xd9cd:1:0x0006]: Message send failure'), DeliveryError('[0xd9cd:1:0x0006]: Message send failure'), DeliveryError('[0xd9cd:1:0x0006]: Message send failure'), DeliveryError('[0xd9cd:1:0x0006]: Message send failure')]`

longunmin commented 2 years ago

Any update on this? Seems like a widespread issue (I am experiencing it too). My network has been down for days and I have tried the 35 minutes unplug trick as well

DunklerPhoenix commented 2 years ago

Someone mentioned it earlier. Just add/readd an device which act as zigbee repeater. After you did this the network comes back step by step.

puddly commented 2 years ago

@longunmin What coordinator are you using?

For the most part, network connectivity isn't something ZHA or any of the radio libraries have any control over.

longunmin commented 2 years ago

@puddly I am using the Sonoff Zigbee Bridge with Tasmota. It's strange, the battery devices came back, but all the mains powered I've had to manually reincluded

Duraines commented 2 years ago

Same issue here, has this been patched?

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

MartinPham commented 1 year ago

still not working

puddly commented 1 year ago

@MartinPham This issue from February is likely not relevant to your problem other you seeing a similar error message: this isn't really a problem with ZHA, the error is just notifying you of a device being unreachable.

If you have a specific problem, open a new issue and post detailed ZHA debug logs.