core
core copied to clipboard
home-assistant
ZHA Devices no longer working since update
The problem
Zigbee devices (using ZHA integration) no longer respond to state changes (eg switch on / off). I believe this is linked to updating to the latest version (2022.9.4) however cannot be sure if this occurred straight away or took some time. I've tried reverting to 2022.8.7 but the problem still exists
Tried putting one of the existing devices (not new) that stoped responding into pairing mode & ZHA into pairing but nothing shows. Tried removing same device from HA & doing the same again - device is not detected / picked up
What version of Home Assistant Core has the issue?
2022.9.4
What was the last working version of Home Assistant Core?
Reverting to earlier versions doesn't solve problem.
What type of installation are you running?
Home Assistant Core
Integration causing the issue
ZHA?
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha
Diagnostics information
When trying to control / change the state of any ZHA connected device, button flicks over for few seconds then goes back. But no change to the device
Logger: homeassistant.components.zha.core.channels.base Source: components/zha/core/channels/base.py:486 Integration: Zigbee Home Automation (documentation, issues) First occurred: 10:23:39 AM (23 occurrences) Last logged: 10:25:10 AM
[0xD439: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>')] [0xC35E:1: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>')] [0xC35E: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>')] [0x048F:1: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>')] [0xC35E: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>')]
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
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!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
![probot-home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/36093?v=4 "Published by a pub.dev verified publisher"){kind=small}
I am having the same issues as stated above. Went to 2022.9.5 and that didn't change any results.
LOG Logger: homeassistant.components.zha.core.channels.base Source: components/zha/core/channels/base.py:486 Integration: Zigbee Home Automation (documentation, issues) First occurred: 8:05:38 PM (4 occurrences) Last logged: 8:05:39 PM
[0xA380:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xa380:1:0x0006]: Message send failure'), DeliveryError('[0xa380:1:0x0006]: Message send failure'), DeliveryError('[0xa380:1:0x0006]: Message send failure'), DeliveryError('[0xa380:1:0x0006]: Message send failure')] [0xC410:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xc410:1:0x0006]: Message send failure'), DeliveryError('[0xc410:1:0x0006]: Message send failure'), DeliveryError('[0xc410:1:0x0006]: Message send failure'), DeliveryError('[0xc410:1:0x0006]: Message send failure')] [0xA380:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0xa380:1:0x0008]: Message send failure'), DeliveryError('[0xa380:1:0x0008]: Message send failure'), DeliveryError('[0xa380:1:0x0008]: Message send failure'), DeliveryError('[0xa380:1:0x0008]: Message send failure')] [0xC410:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0xc410:1:0x0008]: Message send failure'), DeliveryError('[0xc410:1:0x0008]: Message send failure'), DeliveryError('[0xc410:1:0x0008]: Message send failure'), DeliveryError('[0xc410:1:0x0008]: Message send failure')]
Update: After being completely unresponsive (ie not responding at all) HA is now on occasion responding to the requests. When first posting this issue, the ZHA based devices we're completely unresponsive. Now they seem to work occationally albeit very slowly (a few seconds after the buttom request) & unreliably (sometime responding sometime not). Not sure if this helps.
Logger: homeassistant.components.zha.core.channels.base Source: components/zha/core/channels/base.py:486 Integration: Zigbee Home Automation (documentation, issues) First occurred: September 20, 2022 at 5:55:07 PM (8 occurrences) Last logged: 6:03:55 AM
[0x7F3B: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>')] [0x7F3B: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>')]
I'm getting the same messages:
2022-09-21 21:49:12.658 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x1AC6:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x1ac6:1:0x0006]: Message send failure'), DeliveryError('[0x1ac6:1:0x0006]: Message send failure'), DeliveryError('[0x1ac6:1:0x0006]: Message send failure'), DeliveryError('[0x1ac6:1:0x0006]: Message send failure')]
{ "home_assistant": { "installation_type": "Home Assistant Container", "version": "2022.9.5", "dev": false, "hassio": false, "virtualenv": false, "python_version": "3.10.5", "docker": true, "arch": "x86_64", "timezone": "Europe/Oslo", "os_name": "Linux", "os_version": "4.15.0-193-generic", "run_as_root": true }, "custom_components": {}, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.33.1", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.79", "zigpy-deconz==0.18.1", "zigpy==0.50.3", "zigpy-xbee==0.15.0", "zigpy-zigate==0.9.2", "zigpy-znp==0.8.2" ] }
Same issue here when upgrading to 2022.9.5. Returing to 2022.9.4 did not resolve the issue. Any solution
Same issue here after upgrading. Devices sometimes are recognized and sometimes not, but all random. Restarting the Tasmota ZHA coordinator doesn't help, nor does restarting the integration.
Same Experiencing. i've tried deleting it all but now i can't get my conbee ii to come online:
Logger: homeassistant.config_entries Source: components/zha/core/gateway.py:172 First occurred: 09.01.58 (3 occurrences) Last logged: 09.14.36
Error setting up entry ConBee II for zha Error setting up entry ConBee II, s/n: DE2292592 - dresden elektronik ingenieurtechnik GmbH for zha Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/zigpy_deconz/zigbee/application.py", line 149, in change_loop await asyncio.sleep(CHANGE_NETWORK_WAIT) File "/usr/local/lib/python3.10/asyncio/tasks.py", line 605, in sleep return await future asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for return fut.result() asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/zigpy_deconz/zigbee/application.py", line 123, in start_network await self._change_network_state(NetworkState.CONNECTED) File "/usr/local/lib/python3.10/site-packages/zigpy_deconz/zigbee/application.py", line 152, in _change_network_state await asyncio.wait_for(change_loop(), timeout=timeout) File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for raise exceptions.TimeoutError() from exc asyncio.exceptions.TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 357, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/zha/init.py", line 112, in async_setup_entry await zha_gateway.async_initialize() File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 185, in async_initialize raise exc File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 172, in async_initialize self.application_controller = await app_controller_cls.new( File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 138, in new await app.startup(auto_form=auto_form) File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 119, in startup await self.initialize(auto_form=auto_form) File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 101, in initialize await self.start_network() File "/usr/local/lib/python3.10/site-packages/zigpy_deconz/zigbee/application.py", line 125, in start_network raise FormationFailure() from e zigpy.exceptions.FormationFailure
I updated from 2022.8.7 to 2022.9.5 and run in the same issue. I use a ZHA with conbee II stick. downgrade with restore of backup did not help.
I updated the firmware of conbee II, that did not solve the issue. So I deleted all my 23 devices and re-added them. Afterthat all were working again. Sad side effect was that i had to adapt many automatizions.
two days later the issue is back, also upgrade to 2022.9.6 dont change anything.
If you're using a Conbee, make sure it's on a USB 2.0 extension cable and away from sources of interference, like SSDs, USB 3.0 ports, power supplies, wireless routers, etc.
Please post a ZHA debug log, the tracebacks alone don't contain enough information.
I use a USB 2.0 extesion, same as the last 12 month. There was also no change in the close enviroment like WLAN AP, SSD or simular.
what really puzzels me is that some bulbs are shown offline and other do show the correct status. but i cant control them from ZHA. mean i can swich on and off with direct linked remote control, and it does report the status to HA. But I cant change status from HA.
here a short log when i try to change swich on a bulb:
2022-09-23 20:49:15.172 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.processor_temperature, old_state=<state sensor.processor_temperature=59.4; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Processor temperature @ 2022-09-23T20:49:00.171547+02:00>, new_state=<state sensor.processor_temperature=58.4; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Processor temperature @ 2022-09-23T20:49:15.172341+02:00>> 2022-09-23 20:49:15.173 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.processor_use, old_state=<state sensor.processor_use=22; state_class=measurement, unit_of_measurement=%, icon=mdi:cpu-64-bit, friendly_name=Processor use @ 2022-09-23T20:49:00.172579+02:00>, new_state=<state sensor.processor_use=21; state_class=measurement, unit_of_measurement=%, icon=mdi:cpu-64-bit, friendly_name=Processor use @ 2022-09-23T20:49:15.173374+02:00>> 2022-09-23 20:49:15.174 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.memory_use_percent, old_state=<state sensor.memory_use_percent=66.5; state_class=measurement, unit_of_measurement=%, icon=mdi:memory, friendly_name=Memory use (percent) @ 2022-09-23T20:49:00.180353+02:00>, new_state=<state sensor.memory_use_percent=66.8; state_class=measurement, unit_of_measurement=%, icon=mdi:memory, friendly_name=Memory use (percent) @ 2022-09-23T20:49:15.174091+02:00>> 2022-09-23 20:49:16.207 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x641C](TRADFRIbulbE27WSglobeopal1055lm): last_seen is 39138.9975976944 seconds ago and ping attempts have been exhausted, marking the device unavailable 2022-09-23 20:49:16.207 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x641C](TRADFRIbulbE27WSglobeopal1055lm): Update device availability - device available: False - new availability: False - changed: False 2022-09-23 20:49:16.295 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x9A7D](TRADFRIbulbE27WSglobeopal1055lm): last_seen is 38941.63215112686 seconds ago and ping attempts have been exhausted, marking the device unavailable 2022-09-23 20:49:16.296 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x9A7D](TRADFRIbulbE27WSglobeopal1055lm): Update device availability - device available: False - new availability: False - changed: False 2022-09-23 20:49:17.971 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.esstisch_light> 2022-09-23 20:49:17.972 DEBUG (MainThread) [homeassistant.components.zha.entity] light.esstisch_light: setting transitioning flag to True 2022-09-23 20:49:17.973 DEBUG (MainThread) [zigpy.zcl] [0xF823:1:0x0006] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.CLUSTER_COMMAND: 1>, is_manufacturer_specific=False, direction=<Direction.Server_to_Client: 0>, disable_default_response=0, reserved=0, *is_cluster=True, *is_general=False, *is_reply=False), tsn=8, command_id=1, *direction=<Direction.Server_to_Client: 0>, *is_reply=False) 2022-09-23 20:49:17.974 DEBUG (MainThread) [zigpy.zcl] [0xF823:1:0x0006] Sending request: on() 2022-09-23 20:49:17.974 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 8 under 9 request id, data: b'010801' 2022-09-23 20:49:17.975 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (18, 9, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xF823 endpoint=1>, 260, 6, 1, b'\x01\x08\x01', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0) 2022-09-23 20:49:17.982 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 9] 2022-09-23 20:49:18.288 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x6777](TRADFRIbulbE27WSglobeopal1055lm): last_seen is 38937.528259038925 seconds ago and ping attempts have been exhausted, marking the device unavailable 2022-09-23 20:49:18.289 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x6777](TRADFRIbulbE27WSglobeopal1055lm): Update device availability - device available: False - new availability: False - changed: False 2022-09-23 20:49:19.001 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0] 2022-09-23 20:49:19.003 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,) 2022-09-23 20:49:19.009 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 9: e1 2022-09-23 20:49:19.009 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x09 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xf823 endpoint=1>, status: 0xe1 2022-09-23 20:49:19.010 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Error while sending 9 req id frame: TXStatus.MAC_CHANNEL_ACCESS_FAILURE 2022-09-23 20:49:19.010 DEBUG (MainThread) [zigpy.device] [0xf823] Delivery error for seq # 0x08, on endpoint id 1 cluster 0x0006: message send failure 2022-09-23 20:49:19.010 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xF823:1:0x0006]: command failed: 'on' args: '()' kwargs '{}' exception: '[0xf823:1:0x0006]: Message send failure' 2022-09-23 20:49:19.011 DEBUG (MainThread) [homeassistant.components.zha.entity] light.esstisch_light: starting transitioning timer for 1.25 2022-09-23 20:49:19.011 DEBUG (MainThread) [homeassistant.components.zha.entity] light.esstisch_light: turned on: {'on_off': DeliveryError('[0xf823:1:0x0006]: Message send failure')} 2022-09-23 20:49:20.261 DEBUG (MainThread) [homeassistant.components.zha.entity] light.esstisch_light: transition complete - future attribute reports will write HA state 2022-09-23 20:49:22.229 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xD267](TRADFRI bulb E27 WW 806lm): Device seen - marking the device available and resetting counter 2022-09-23 20:49:22.229 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xD267](TRADFRI bulb E27 WW 806lm): Update device availability - device available: True - new availability: True - changed: False 2022-09-23 20:49:22.279 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x6872](TRADFRI motion sensor): Device seen - marking the device available and resetting counter 2022-09-23 20:49:22.279 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x6872](TRADFRI motion sensor): Update device availability - device available: True - new availability: True - changed: False 2022-09-23 20:49:30.178 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.processor_temperature, old_state=<state sensor.processor_temperature=58.4; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Processor temperature @ 2022-09-23T20:49:15.172341+02:00>, new_state=<state sensor.processor_temperature=58.9; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Processor temperature @ 2022-09-23T20:49:30.178541+02:00>> 2022-09-23 20:49:30.179 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.processor_use, old_state=<state sensor.processor_use=21; state_class=measurement, unit_of_measurement=%, icon=mdi:cpu-64-bit, friendly_name=Processor use @ 2022-09-23T20:49:15.173374+02:00>, new_state=<state sensor.processor_use=22; state_class=measurement, unit_of_measurement=%, icon=mdi:cpu-64-bit, friendly_name=Processor use @ 2022-09-23T20:49:30.179679+02:00>> 2022-09-23 20:49:30.180 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.memory_use_percent, old_state=<state sensor.memory_use_percent=66.8; state_class=measurement, unit_of_measurement=%, icon=mdi:memory, friendly_name=Memory use (percent) @ 2022-09-23T20:49:15.174091+02:00>, new_state=<state sensor.memory_use_percent=66.6; state_class=measurement, unit_of_measurement=%, icon=mdi:memory, friendly_name=Memory use (percent) @ 2022-09-23T20:49:30.180326+02:00>>
TXStatus.MAC_CHANNEL_ACCESS_FAILURE is the Conbee explicitly refusing to transmit because it's detecting too much interference. Move the stick around or use a longer USB extension cable.
Nothing in ZHA has changed (which is why your network is still broken when you downgrade), this is an environment problem.
Hopefully this helps. I enabled the ZHA debug logs - then filtered the logs with DEBUG. If I shouldnt have filtered appologies - let me know. I as per the user above, have made no physical changes to my environment or network
The only error in your log I'm seeing is device 0x7F3B (TRADFRI bulb E14 W op/ch 400lm) being unresponsive. Try powering it off for five seconds at the switch then turning it back on, IKEA routers have a known bug where their firmware can half-freeze and cause routing issues for any devices routing through it.
I don't have logs to add atm but I believe I'm having the same issue. Since a recent update ZigBee is very unreliable. Particularly since trying to add a new bulb. Adding the bulb caused others to stop working after a few moments. I was able to remove the new one and then things recovered. Then I later tried adding a known-good bulb and it broke things again. I was able to recover again somehow but today many bulbs are not showing as connected and when I remove and re-add it doesn't look like they interview properly. Also tried reconfiguring first but it hasy no effect. Everything just seems so flaky now.
I'll add logs when I can
Same issue, since the latest update most of my zigbee switches (osram sockets) stopped working. Also door and window contacts work very unreliable. Using a ConBee2 USB. Please let me know if any specific logs are required, i will more than happy to provide them.
I might have the same issue. In my case hama thermostats do most of the time not work, do not accept any change of temperature or so by HA.
2022-09-24 18:42:53.915 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 182, Status: TXStatus.MAC_CHANNEL_ACCESS_FAILURE 2022-09-24 19:52:25.235 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 102, Status: TXStatus.MAC_CHANNEL_ACCESS_FAILURE 2022-09-24 19:52:51.326 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 113, Status: TXStatus.MAC_CHANNEL_ACCESS_FAILURE 2022-09-24 21:08:18.401 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 244, Status: TXStatus.MAC_CHANNEL_ACCESS_FAILURE
TXStatus.MAC_CHANNEL_ACCESS_FAILURE means you have a severe interference. Disable bluetooth, use USB extension cable, remove any usb3, ssd enclosurez etc
SOLVED Thanks, @Adminiuga, I removed the usb3-stick from my NUC (the usb3 stick I just installed a few days ago for proxmox backups) and it seems to work. Next step: I will get a usb3 extension cable and will try again. I was looking since days for what is going on, but I never would have expected a problem with my usb3-stick. So again, thanks.
The only error in your log I'm seeing is device 0x7F3B (
TRADFRI bulb E14 W op/ch 400lm) being unresponsive. Try powering it off for five seconds at the switch then turning it back on, IKEA routers have a known bug where their firmware can half-freeze and cause routing issues for any devices routing through it.
That was the issue, I power cycled that device as you suggested & my problem went away. Apologies for wasting your time, much appreciated. Is it possible to resolve the firmware issue by an update or its just a known bug?
Power cycling my whole home did not resolve the issue. After restarting everything, I get the following log messages:
Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 23:24:13 (54 occurrences)
Last logged: 23:24:42
[0x83F2:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x83f2:1:0x0008]: Message send failure'), DeliveryError('[0x83f2:1:0x0008]: Message send failure'), DeliveryError('[0x83f2:1:0x0008]: Message send failure'), DeliveryError('[0x83f2:1:0x0008]: Message send failure')]
[0x47DC:11:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x47dc:11:0x0300]: Message send failure'), DeliveryError('[0x47dc:11:0x0300]: Message send failure'), DeliveryError('[0x47dc:11:0x0300]: Message send failure'), DeliveryError('[0x47dc:11:0x0300]: Message send failure')]
[0xEF20:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0xef20:11:0x0006]: Message send failure'), DeliveryError('[0xef20:11:0x0006]: Message send failure'), DeliveryError('[0xef20:11:0x0006]: Message send failure'), DeliveryError('[0xef20:11:0x0006]: Message send failure')]
[0xDCD4:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0xdcd4:1:0x0008]: Message send failure'), DeliveryError('[0xdcd4:1:0x0008]: Message send failure'), DeliveryError('[0xdcd4:1:0x0008]: Message send failure'), DeliveryError('[0xdcd4:1:0x0008]: Message send failure')]
[0xDCD4:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0xdcd4:1:0x0300]: Message send failure'), DeliveryError('[0xdcd4:1:0x0300]: Message send failure'), DeliveryError('[0xdcd4:1:0x0300]: Message send failure'), DeliveryError('[0xdcd4:1:0x0300]: Message send failure')]
Very similar experience here. I have a pretty large Zigbee network with 100 devices (most powered and able to act as routers). The system was rock solid and fast under 2022.8.x after I had migrated everything from two Tuya hubs. But from 2022.9.1 onwards all kinds of issues have crept in. I have devices becoming randomly unavailable requiring power cycling and my scenes that used to be sooo much better than in Tuya are now really hit and miss. On occasions, devices will show as off in HA but are still on and vice-versa.
I am running on an Intel NUC (which does have on-board Bluetooth that I do not use but is activated in HA)
If there are logs or debugs that will help let me know.
I have been out of town and haven't had a chance to play with my system much, but I do have a hopeful update.
I changed no things with my system since my issues started occuring. I couldn't re-pair existing ZigBee devices at all. I had no changes to my setup other than updating to 2022.9.4, then I started having issues. I updated to 2022.9.7 yesterday but didn't try anything yet. As of this afternoon most of my ZigBee devices are back and running properly. The ones that weren't reconnected I was able to re-add like normal with no issues. What I don't know is if it will be stable or not. So I will come back and say if I happen to have devices start dropping out again. So give 2022.9.7 a try.
I didn't save any of them, but looking at the logs when you try and add a device in zha we're definitely different today vs when I was 9n 2022.9.4 or 2022.9.5. there is a comment now about resetting a counter for a device that reached its ping limit which was new to me (paraphrasing and off the top of my head what it said exactly. I was on mobile when re-pairing my devices).
My ZigBee network was stable for ~24 hrs and now it's back to being unresponsive.
Mine seems to change between working and not working depending how many devices I have connected. If I cut the power to one set of lights it seems to help the rest of the system after a while. Earlier in the week I tried cutting power to my downstairs hallway lights after noticing issues. After a while the issues went away. I restored power to them and issues crept in again. Last night I cut the power to my upstairs hallway lights instead, and after a while the issues went away. I restored power to them this a few hours ago but they haven't become available yet, and everything else is still working properly. If/when they come online, I expect things to start acting up again.
I have 2 IKEA bulbs acting as routers as well as an Osram. They weren't problematic before recent updates so I am hesitant to blame them. My HUSBZB-1 is right next to the downstairs hallway and not far from the upstairs hallway. I actually just moved it to where it is in attempt to reduce these issues. It used to be in a corner in my basement and worked fine.
I have a 100 devices, how many do you have?
On Fri, 30 Sept 2022, 17:19 Ryan Ewen, @.***> wrote:
Mine seems to change between working and not working depending how many devices I have connected. If I cut the power to one set of lights it seems to help the rest of the system after a while. Earlier in the week I tried cutting power to my downstairs hallway lights after noticing issues. After a while the issues went away. I restored power to them and issues crept in again. Last night I cut the power to my upstairs hallway lights instead, and after a while the issues went away. I restored power to them this a few hours ago but they haven't become available yet, and everything else is still working properly. If/when they come online, I expect things to start acting up again.
I have 2 IKEA bulbs acting as routers as well as an Osram. They weren't problematic before recent updates so I am hesitant to blame them. My HUSBZB-1 is right next to the downstairs hallway and not far from the upstairs hallway. I actually just moved it to where it is in attempt to reduce these issues. It used to be in a corner in my basement and worked fine.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/78681#issuecomment-1263770065, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4LKIGUJYYEQYZIZL252BTWA4HIJANCNFSM6AAAAAAQPLY6XM . You are receiving this because you commented.Message ID: @.***>
I am running on an Intel NUC (which does have on-board Bluetooth that I do not use but is activated in HA)
What coordinator are you using? Can you disable Bluetooth, without restarting or touching any other component of your system?
ZHA does not control routing or network operation, this is all done by the firmware on your stick. The only thing updating from 2022.8.x to 2022.9.1 would do is reboot the stick.
If you are using a Conbee, there is a known issue where it just does not route properly after a reboot (i.e. you can receive sensor updates but can't control lights), so you may want to try unplugging it, waiting a second or two, and plugging the stick back in. ZHA will reconnect to the stick in a few seconds. Update the Conbee's firmware as well.
I'm using a Raspbee II (which is basically a Conbee II in a rpi form factor). I'm not sure it's a good idea to unplug it from the GPIO after a reboot. How should I proceed here to try this theory? (also I have no idea where any potential firmware update is hosted)
If you're using a Raspbee, shut down the pi, completely unplug it from power and wait for 10s, then plug it back in. Simply rebooting may keep the Raspbee powered.
As for updating the firmware, that would have to be done through deCONZ (automatically) or manually with https://github.com/dresden-elektronik/gcfflasher using a firmware file https://deconz.dresden-elektronik.de/deconz-firmware/