You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:324
First occurred: 23:29:09 (1 occurrences)
Last logged: 23:29:09
Detected that the integration 'zha' device_registry. async_get_or_create and references a non-existent via_device ('zha', e0:79:8d:ff:fe:1a:28:9b), with device info: {'connections': {('zigbee', '0c:ef:f6:ff:fe:5b:48:31')}, 'identifiers': {('zha', '0c:ef:f6:ff:fe:5b:48:31')}, 'manufacturer': 'eWeLink', 'model': 'SNZB-03P', 'name': 'eWeLink SNZB-03P', 'via_device': ('zha', e0:79:8d:ff:fe:1a:28:9b)} at homeassistant/components/zha/helpers. py, line 1177: _async_add_entities(entities_to_add, update_before_add=False). This will no longer work in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+zha%22
Translated with DeepL.com (free version)
What version of Home Assistant Core has the issue?
core-2025.1.1
What was the last working version of Home Assistant Core?
Detected that integration 'zha' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('zha', e0:79:8d:ff:fe:1a:28:9b), with device info: {'connections': {('zigbee', '0c:ef:f6:ff:fe:5b:48:31')}, 'identifiers': {('zha', '0c:ef:f6:ff:fe:5b:48:31')}, 'manufacturer': 'eWeLink', 'model': 'SNZB-03P', 'name': 'eWeLink SNZB-03P', 'via_device': ('zha', e0:79:8d:ff:fe:1a:28:9b)} at homeassistant/components/zha/helpers.py, line 1177: _async_add_entities(entities_to_add, update_before_add=False). This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+zha%22
Additional information
I currently have no problems, I just have this error in the logs
The text was updated successfully, but these errors were encountered:
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.
The problem
I have the following error in my logs:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:324
First occurred: 23:29:09 (1 occurrences)
Last logged: 23:29:09
Detected that the integration 'zha'
device_registry. async_get_or_create
and references a non-existentvia_device
('zha', e0:79:8d:ff:fe:1a:28:9b), with device info: {'connections': {('zigbee', '0c:ef:f6:ff:fe:5b:48:31')}, 'identifiers': {('zha', '0c:ef:f6:ff:fe:5b:48:31')}, 'manufacturer': 'eWeLink', 'model': 'SNZB-03P', 'name': 'eWeLink SNZB-03P', 'via_device': ('zha', e0:79:8d:ff:fe:1a:28:9b)} at homeassistant/components/zha/helpers. py, line 1177: _async_add_entities(entities_to_add, update_before_add=False). This will no longer work in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+zha%22Translated with DeepL.com (free version)
What version of Home Assistant Core has the issue?
core-2025.1.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
zha
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
config_entry-zha-291c4c3abb8d345a8825e5d8f9290329.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I currently have no problems, I just have this error in the logs
The text was updated successfully, but these errors were encountered: