Open zhengliw opened 3 days 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!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
This problem is caused by the hassio
integration (https://www.home-assistant.io/integrations/hassio/) not loading. You have a Supervised install so hassio
should be loaded.
Can you post a debug log of your entire startup sequence? This isn't really a ZHA problem.
Hmm, that's weird since I run the container version actually. Debug log following...
Here you go!
2024-11-09 22:29:39.915 WARNING (SyncWorker_0) [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-11-09 22:29:39.916 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_miot 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-11-09 22:29:39.917 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate 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-11-09 22:29:39.918 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya 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-11-09 22:29:39.919 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_gateway3 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-11-09 22:29:42.891 WARNING (ImportExecutor_0) [homeassistant.const] UnitOfConductivity.MICROSIEMENS was used from xiaomi_gateway3, this is a deprecated enum member which will be removed in HA Core 2025.11.0. Use UnitOfConductivity.MICROSIEMENS_PER_CM instead, please report it to the author of the 'xiaomi_gateway3' custom integration
2024-11-09 22:29:43.185 WARNING (SyncWorker_8) [py.warnings] /usr/local/lib/python3.12/site-packages/tzlocal/unix.py:193: UserWarning: Can not find any timezone configuration, defaulting to UTC.
warnings.warn("Can not find any timezone configuration, defaulting to UTC.")
2024-11-09 22:29:43.571 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from xiaomi_gateway3, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'xiaomi_gateway3' custom integration
2024-11-09 22:29:43.637 WARNING (ImportExecutor_0) [homeassistant.core] Config was used from frigate, this is a deprecated alias which will be removed in HA Core 2025.11. Use homeassistant.core_config.Config instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:43.646 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_CLASS_DIRECTORY was used from frigate, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaClass.DIRECTORY instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:43.649 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_CLASS_IMAGE was used from frigate, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaClass.IMAGE instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:43.652 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_CLASS_MOVIE was used from frigate, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaClass.MOVIE instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:43.655 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_CLASS_VIDEO was used from frigate, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaClass.VIDEO instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:43.658 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_TYPE_IMAGE was used from frigate, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.IMAGE instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:43.661 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_TYPE_VIDEO was used from frigate, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.VIDEO instead, please report it to the author of the 'frigate' custom integration
2024-11-09 22:29:45.449 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_AWAY was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_AWAY instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-09 22:29:45.453 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_HOME was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_HOME instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-09 22:29:45.455 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_NIGHT was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_NIGHT instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-09 22:29:45.459 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_DISARMED was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.DISARMED instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-09 22:29:45.462 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-09 22:29:54.798 ERROR (SyncWorker_13) [aiodhcpwatcher] Cannot watch for dhcp packets: [Errno 1] Operation not permitted
Are you using xiaomi_gateway3 for zigbee? I do and have [had; see edit below] the same problem, I guess. I've updated to HA core-2024.11.1 two days ago and it worked until this morning, when a faulty device was plugged in and triggered the circuit breaker, what resulted in a restarted of the gateway and some other devices. The server wasn't affected, so there's no data corruption. Restarting HomeAssistant also didn't help. I've seen that the Gateway3 integration wasn't running, so I upgraded it to https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.6, now that works again. I guess this integration broke some time ago on a HomeAssistand update, but the gateway was still configured for zsh, so zigbee worked and I hadn't to configure it. After the power fail it might be now in a state where it doesn't work with the old zsh configuration or something. Maybe the updated configuration is just running but not configuring the gateway correctly. Gateway firmware is 1.5.0_0027 and I'm unable to update it.
ZHA is now still not starting and I can't configure it. I can't add another configuration and I don't want to delete the existing one, because re-pairing and -configuring all the devices is pain.
In my case (dark theme; HomeAssistant as docker container), I get an empty popup on the first try configuring it instead of the http 500 response.
Edit: Some reboots later (I've disabled my zhs-enable_quirks in configuration.yaml, powercycled the gateway again, rebooted the whole server, ...) it told me the encription key has changed and it reccomends recovering it from backup, so I let it do and some devices worked again. After that I undid my changes in the configuration.yaml and made another restart to load it and now everything works fine again; problem solved for me. I can also open the configuration now without error. I guess the problem is that changing the configuration won't work until the xiaomi_gateway3 integration configures the gateway to work with it, what took some time. But it might be more complicated when the gateway can't be reached because the ip adress changed or so.
same problem here!
I am trying to add the integration to Home Assistant Container
I assume something upstream, container-specific broke... Or maybe some logic involved in ZHA tried to do something specific to supervised systems?
Are you using xiaomi_gateway3 for zigbee? I do and have [had; see edit below] the same problem, I guess. I've updated to HA core-2024.11.1 two days ago and it worked until this morning, when a faulty device was plugged in and triggered the circuit breaker, what resulted in a restarted of the gateway and some other devices. The server wasn't affected, so there's no data corruption. Restarting HomeAssistant also didn't help. I've seen that the Gateway3 integration wasn't running, so I upgraded it to https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.6, now that works again. I guess this integration broke some time ago on a HomeAssistand update, but the gateway was still configured for zsh, so zigbee worked and I hadn't to configure it. After the power fail it might be now in a state where it doesn't work with the old zsh configuration or something. Maybe the updated configuration is just running but not configuring the gateway correctly. Gateway firmware is 1.5.0_0027 and I'm unable to update it.
ZHA is now still not starting and I can't configure it. I can't add another configuration and I don't want to delete the existing one, because re-pairing and -configuring all the devices is pain.
In my case (dark theme; HomeAssistant as docker container), I get an empty popup on the first try configuring it instead of the http 500 response.
Edit: Some reboots later (I've disabled my zhs-enable_quirks in configuration.yaml, powercycled the gateway again, rebooted the whole server, ...) it told me the encription key has changed and it reccomends recovering it from backup, so I let it do and some devices worked again. After that I undid my changes in the configuration.yaml and made another restart to load it and now everything works fine again; problem solved for me. I can also open the configuration now without error. I guess the problem is that changing the configuration won't work until the xiaomi_gateway3 integration configures the gateway to work with it, what took some time. But it might be more complicated when the gateway can't be reached because the ip adress changed or so.
Yep, i still use it, but I don't believe it's relevant to this issue...
Same problem. Running HA in a container and trying to configure Zigbee HA integration.
2024-11-11 13:54:50.150 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
return await func(self, request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
return await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
return await self._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
return await super()._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
result = await self._flow_mgr.async_init(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1301, in async_init
flow, result = await self._async_init(flow_id, handler, context, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1336, in _async_init
result = await self._async_handle_step(flow, flow.init_step, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 517, in _async_handle_step
result: _FlowResultT = await getattr(flow, method)(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 535, in async_step_user
return await self.async_step_choose_serial_port(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 177, in async_step_choose_serial_port
ports = await list_serial_ports(self.hass)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 108, in list_serial_ports
multipan_manager = await silabs_multiprotocol_addon.get_multiprotocol_addon_manager(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/singleton.py", line 52, in async_wrapped
result = await func(hass)
^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/homeassistant_hardware/silabs_multiprotocol_addon.py", line 71, in get_multiprotocol_addon_manager
manager = MultiprotocolAddonManager(hass)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/homeassistant_hardware/silabs_multiprotocol_addon.py", line 128, in __init__
super().__init__(
File "/usr/src/homeassistant/homeassistant/components/hassio/addon_manager.py", line 112, in __init__
self._supervisor_client = get_supervisor_client(hass)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/singleton.py", line 42, in wrapped
hass.data[data_key] = func(hass)
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 383, in get_supervisor_client
hassio: HassIO = hass.data[DOMAIN]
~~~~~~~~~^^^^^^^^
KeyError: 'hassio'
Must be a hassio issue indeed: while integration with ZHA was failing for me the whole night on the :latest or :stable version, once I pulled the previous stable (2024.10) of home assistant, it worked like a charm.
Had the same issue on HA container. Switched to 2024.10 like @theredone-1 mentioned, fixed the problem for me. Now I am kinda hesitant to put it back on :latest ...
Rolling back HA container to 2024.10.4 resolved the issue for me too.
Seems like an issue within the latest few updates then
The problem
I failed to configure ZHA, on the first time trying to configure it, the config flow screen shows this:
500 Internal Server Error Server got itself in trouble
On the second attempt, the screen just times out until nginx, which I configured HA to be proxied through, returns a gateway timeout.
Before this reinstallation, I had ZHA configured already but it fails to load. I suspected that it's because of some actions I performed on the UI and it led to some inconsistencies in the database etc, but after the reinstallation it's still not working. So this is on a pretty fresh install (only a few HACS plugins enabled). To sort out HACS problems, I've tried safe mode, no success either...
What version of Home Assistant Core has the issue?
core-2024.11.1
What was the last working version of Home Assistant Core?
No response
Edit: According to comments, this used to work on 2024.10
https://github.com/home-assistant/core/issues/130248#issuecomment-2471121347
What type of installation are you running?
Home Assistant Container
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?
Additional information
Please let me know if I can assist you further!