[0x4AD5:1:0x0702]: async_initialize: all attempts have failed:

[matthewhadley]

The problem

I am running ZHA using the SkyConnect device on firmware version 7.2.1.0.144

I experimented with enabling multi-protocol thread support, but believe the warnings below existed before then. I have also flashed back to the ZHA only firmware (as I was unable to get ZHA working at the same time). What would be the source of these warnings and how can I resolve them?

Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486 
Integration: Zigbee Home Automation (documentation, issues) 
First occurred: 5:41:04 PM (92 occurrences) 
Last logged: 5:49:31 PM

[0x4AD5:1:0x0702]: 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>')]
[0x4AD5: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>')]
[0xF7AD:1:0x0702]: 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>')]
[0xFE48:1:0x0702]: 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>'), TimeoutError()]
[0xFE48: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>'), TimeoutError(), TimeoutError()]

I also have a warning about protocol version:

Logger: bellows.ezsp
Source: components/zha/core/gateway.py:174 
First occurred: 5:40:56 PM (3 occurrences) 
Last logged: 5:49:11 PM

Protocol version 10 is not supported, using version 9 instead

What version of Home Assistant Core has the issue?

core-2023.2

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

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

No response

[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 Change the title of 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)}}

[puddly]

The protocol warning is nothing to worry about, it will be fixed in a future release. The other warnings are saying that a device is unreachable.

[matthewhadley]

Thank you @puddly. I think I located the offline device and the warning has gone.

I’d been having to restart home assistant a lot recently due to issues with the iaqualink integration. I think restarting meant the device was not yet showing as “offline” in ZHA.

Resolved now, will close issue.