Automations Unable to get ZHA Device.

[spartandrew18]

The problem

Whenever I restart HA or reboot HA I receive an error message stating that HA is unable to get ZHA devices for certain automations. The devices work normally and are paired with ZHA. This error is relatively new from the 2023.3.x if I recall. Sometimes restarting/rebooting allows the devices to properly load with the automation, but its usually more error prone than normal.

I have the Home Assistant Yellow with the Multi Protocol Addon installed.

What version of Home Assistant Core has the issue?

2023.3.5

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

Zigbee Home Automation (ZHA)

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?

home-assistant_2023-03-20T03-05-56.246Z.log

Additional information

(https://github.com/home-assistant/core/issues/89701)](#89701)

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, 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!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[MattWestb]

I have the same problem with one RCP test on armbian32.
Most time its taking to long for ZHA getting contact with the EZSP handle from the addon and oft is Zigbeed restarting and making it taking more treys getting it working OK.
The test install is having one IKEA new motion sensor with Dirigera updated 24.5 firmware and 2 Symfonisk gen 2 with original and updated firmware and is having 13 and 17 DA for testing plus my main thread network with 4 active devices.
Then ZHA is loading OK from start but the automatons not its can partly helping reloading the automatons but its looks like the DA is then not working OK and need one clean ZHA start.

My experience of the last updates is 1/3 times the automatons is loading OK and most of the time is ZHA stating OK after some treys but very rear ZHA is not starting and blocking HA stating OK (it can being im wrong and its not happening in HS 2023.3.X).

[mikebumpus]

Having same issue with Home Assistant 2023.3.5 running on ESXi. Manual actions to zigbee devices seem to work fine, and triggers from zigbee remotes are showing up in HA logs. Thought it may be a problem in my VM with USB passthrough from the host, but looks like others are seeing similar results on different hardware.

[0xE220:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
8:28:32 AM – (WARNING) Zigbee Home Automation - message first occurred at 8:26:08 AM and shows up 11 times
Unable to remove unknown dispatcher <bound method GroupProbe._reprobe_group of <homeassistant.components.zha.core.discovery.GroupProbe object at 0x7f0c1432ee30>>
8:28:21 AM – (WARNING) helpers/dispatcher.py

[MattWestb]

@mikebumpus Your system cant communicating with the device 0xE220 but its looks that the coordinator is online and can communicating with the network.
If having one USB-dongle coordinator make sure using one extension cable for it and keep it away from radio interference sources and also look if you is having WiFi overlapping with your Zigbee network.

Also look what device the 0xE220 is and if its having some problems that can making it being off line.

[issue-triage-workflows]

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.

[alexvaltchev]

Did anyone find a fix for it? Is this a bug? I have just opened this issue - #96332 but I am not sure if this is the same or similar problem? Please help!