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
72.32k stars 30.26k forks source link

EmberStatus.DELIVERY_FAILED: 102 #106076

Closed RalJan closed 9 months ago

RalJan commented 9 months ago

The problem

Hello, I recently started receiving this message (see subject) several times a day. The only remedy is to restart the HA The log says something about ConnectioPoolLimit=10 Where can this be set?

Thanks for your help

Hardware: Pi4 with Skyconnect Os:

Core 2023.12.1
Supervisor 2023.11.6
Operating System 11.2
Frontend 20231208.2

What version of Home Assistant Core has the issue?

2023.12.1

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

No response

Link to integration documentation on our website

No response

Diagnostics information

Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/commands.py:238 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 20:49:28 (3 occurrences) Last logged: 20:49:38

[547058481216] Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102> Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 64, in wrap_zigpy_exceptions yield File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 84, in wrapper return await RETRYABLE_REQUEST_DECORATOR(func)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/util.py", line 138, in retry return await func() ^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/init.py", line 377, in request return await self._endpoint.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/endpoint.py", line 253, in request return await self.device.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 299, in request await self._application.request( File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 829, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 825, in send_packet raise zigpy.exceptions.DeliveryError( zigpy.exceptions.DeliveryError: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service return await service.entity_service_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 580, in async_handle_light_on_service await light.async_turn_on(**filter_turn_on_params(light, params)) File "/usr/src/homeassistant/homeassistant/components/zha/light.py", line 360, in async_turn_on result = await self._on_off_cluster_handler.on() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 83, in wrapper with wrap_zigpy_exceptions(): File "/usr/local/lib/python3.11/contextlib.py", line 155, in exit self.gen.throw(typ, value, traceback) File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 75, in wrap_zigpy_exceptions raise HomeAssistantError(message) from exc homeassistant.exceptions.HomeAssistantError: Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 9 months ago

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, 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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zha documentation zha source (message by IssueLinks)

dmulcahey commented 9 months ago

This means the light you are trying to control is unreachable. Any chance it is a smart bulb that could be powered off at the switch? If not, it may have fallen off the Zigbee network.

pringleprng commented 9 months ago

Having this same issue but also related the others having to restart HA for it come back online. Only recently started doing this ever since update. HUSBZB

arctix85 commented 9 months ago

Same here, the issue started with the latest update. Pi 4 with Skyconnect

ctron commented 9 months ago

I have the same issue. Seems to have worked but now doesn't. Running latest HA version on the Yellow board.

Interestingly, this affects a smart light bulb, not the thermometers (battery powered, in the same room). Moving the bulb into another room makes it work again. Then again, that worked flawlessly before some recent update, and before running the bulb on the Philips Hue bridge, which is even further away.

enzy commented 9 months ago

I am having the same problems starting with the 2023.12 update. I have the HA SkyConnect.

A device (mainly mains-powered SONOFF 01MINIZB, but also a few battery-powered sensors occasionally) is reachable and controllable until I restart the HA, then it does not recover until I power cycle the device.

Interestingly not all the devices are lost, just "problematic" ones. I did change one in place for another piece and it works without a problem.

arctix85 commented 9 months ago

For me the problem affects three independent light strips by tint (Müller Licht) which were working fine before for a year. IKEA and Aquara battery powered is still working though.

pringleprng commented 9 months ago

Still an issue

tjerkw commented 9 months ago

This issue started with home asssitent update.. Rebooting ha helps. But after a while Zigbee stops working, system gets slower eventually leading to this error.

A lot of people have this issue: https://community.home-assistant.io/t/failed-to-deliver-message-emberstatus-delivery-failed-102/592145

Basically zigbee is not reliable anymore.

RalJan commented 9 months ago

Hi, finally not even reboot solves anything. To the Router Point I have at least one in every room.. What are the options? do I have to forget about HA all together? Or should I return to ConBee instead of Skyconnect? If so is there an "easy" path?

:-( HELP...

puddly commented 9 months ago

@RalJan Please upload a ZHA debug log after letting the system run, from a clean boot, for a few hours.

RalJan commented 9 months ago

home-assistant.log @puddly HTH

RalJan commented 9 months ago

Hi all, is there slight chance that this problem can be solved? I hope so...

Does anyone got an Ideahow I can rid of this integration, I'm not able to find it on my system

WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_ac_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Thanks ever so much Ralf

RalJan commented 9 months ago

Hi all, looks as this was an OSI Layer 1 Problem... so a shielded USB.Cable and SSD Case solved any interference trouble. thanks to everyone