Hallo,
seit ein paar Tagen angemeldet und schon komme ich mit dem 2. Problem um die Ecke
Ich habe vorgestern meinen Hichi Wifi Lesekopf in mein HA Setup eingepflegt bekommen, dieser läuft auch perfekt.
Nach ca. 5 Stunden gingen alle Zigbee Geräte offline, also mir wird „nicht verfügbar“ angezeigt im Dashboard.
Ob es mit dem Hichi zusammenhängt weiß ich nicht
Danach habe ich den Zigbee Stick mehrfach neu angelegt als USB Stick, mehrfach neu konfiguriert, den Channel bereits gewechselt
Setup:
Conbee 2 Stick, läuft über ZHA
Homeserver mit Proxmox drauf, dort ist HA installiert
Das Setup läuft nun seit einigen Monaten konstant durch, das einzige was geändert wurde, war der Hichi.
Ich habe auch bereits den Hichi vom Netz genommen und komplett vom System gelöscht, leider ohne Erfolg
Auch lassen sich die Zigbee Geräte nicht mehr neu anlernen, werden einfach nicht mehr erkannt wenn ich sie suche und resette, somit muss es ja am Stick liegen?
Hat jemand eine Idee was ich noch machen könnte?
Sevi
18. März 2024 um 20:52
2
Hallo zusammen,
ich schalte mich mal auf dieses Thema auf, da ich seit kurzem (vielleicht mit der neuen HA-Version 2024.3) das gleiche Problem habe. Alle meine Zigbee-Geräte wechseln ihren Zustand alle paar Sekunden auf nicht verfügbar. Entität XX “Attribute Updated event was fired” oder Entität XY Firmware ausgeschaltet etc.
Als Zigbee Bridge verwende ich Sonoff ZB geflasht mit Tasmota.
Mir ist aufgefallen, dass sich die Integration ständig neu initialisiert.
Scheinbar gibt es mit dieser Version 2024.3 Probleme, die bereits auf Github leider nicht abschließend diskutiert werden.
offen 12:02AM - 16 Mar 24 UTC
geschlossen 03:17PM - 02 Apr 24 UTC
integration: zha
### The problem
I have 3 separate systems and all 3 are having the same issue. … One system is a HA Yellow and the other two are RPi4 setups. This started after upgrading to 2024.03.0. This wasn't happening with 2024.02.xx versions.
Core 2024.3.1
Supervisor 2024.03.0
Operating System 12.1
Frontend 20240307.0

### What version of Home Assistant Core has the issue?
2024.3.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
Zigbee
### 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?
```txt
Home Assistant Core
2024-03-14 14:54:47.357 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nodered 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
2024-03-14 14:54:47.360 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs 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
2024-03-14 14:54:57.513 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Away, Turn on lights at dusk' failed to setup actions and has been disabled: Unknown entity '1c008d74b34ca8d1c20c5032c45dffd3'
2024-03-14 14:54:57.518 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Away, Turn off light' failed to setup actions and has been disabled: Unknown entity '1c008d74b34ca8d1c20c5032c45dffd3'
2024-03-14 14:55:01.888 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-03-14 14:55:11.130 WARNING (MainThread) [zigpy.application] Zigbee channel 25 utilization is 80.38%!
2024-03-14 14:55:11.130 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
2024-03-14 14:55:17.591 WARNING (MainThread) [homeassistant.components.media_player] Updating dlna_dmr media_player took longer than the scheduled update interval 0:00:10
2024-03-14 14:55:17.591 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.samsung_qn85cd_85_2 is taking over 10 seconds
2024-03-14 15:06:11.138 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:06:11.177 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:06:12.131 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:06:12.169 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:06:12.203 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:13:30.570 ERROR (MainThread) [frontend.js.latest.202403070] Uncaught error from Safari 16.6 on Mac OS 10.15.7
Script error.
null
@:0:0
2024-03-14 15:32:57.285 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:32:57.341 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:32:57.372 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:36:11.306 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:36:12.314 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:36:24.306 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:36:24.341 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 15:36:24.383 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 16:06:11.554 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 16:06:11.586 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 16:06:11.624 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xBD6C)
2024-03-14 16:06:12.372 WARNING (MainThread) [bellows.zigbee.application] NWK conflict is reported for 0xbd6c
2024-03-14 16:06:12.542 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85E0)
2024-03-14 16:06:12.581 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85E0)
2024-03-14 16:06:12.626 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85E0)
2024-03-14 16:06:31.911 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85F9)
2024-03-14 16:06:31.960 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85F9)
2024-03-14 16:06:32.032 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85F9)
2024-03-14 16:06:51.946 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85F9)
2024-03-14 16:06:52.010 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85F9)
2024-03-14 16:06:52.041 WARNING (MainThread) [zigpy.application] Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x85F9)
2024-03-14 16:06:53.395 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 342, in request
return await req.result
^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 63, in wrap_zigpy_exceptions
yield
File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 83, in wrapper
return await RETRYABLE_REQUEST_DECORATOR(func)(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
### Additional information
_No response_