-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning on home assistant Core for ZHA integration #134585
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
same warning here: |
same here Logger: homeassistant.helpers.frame Detected that integration 'zha' calls |
@toto25550 In the ZHA visualization tab, can you search for |
@puddly Not the person you're asking, but I received the same error as well. I looked up the device in my error and it's just a leak detector. I checked my topology and I'm noticing that all but 3 devices are missing connections but are reporting correctly. I introduced a mains powered device earlier and then disconnected its power, so I'm not sure if that's causing the missing connection lines or not, but it does seem bizarre (it's been several hours since I removed the mains powered device). |
@esand Thanks! In the message, there are actually multiple IEEE addresses listed: Detected that integration 'zha' calls `device_registry.async_get_or_create` referencing a non existing `via_device`
('zha', 00:12:4b:00:2f:8a:b5:ea), with device info: {'connections': {('zigbee', '00:12:4b:00:2f:b2:a5:fa')},
^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^
'identifiers': {('zha', '00:12:4b:00:2f:b2:a5:fa')}, 'manufacturer': 'eWeLink', 'model': 'DS01',
'name': 'eWeLink DS01', 'via_device': ('zha', 00:12:4b:00:2f:8a:b5:ea)} 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. The first one is the device itself. The second one is the "via_device" the warning is complaining about. I'm unable to reproduce this locally so I'm trying to figure out what exactly the pattern here is. Is the second device something you see in your visualization? Or only the first? |
Sorry - for me, the via device is my main controller (I have only one, no routers at the moment - all my devices are battery powered). The second device in my error was one of my water leak sensors.
When I check my ZHA visualization, I see all my devices (incl the unplugged new one I adopted), but only 3 of them have connection lines going to my controller. Before in 2024.12.5, they would all have a connection to my controller - but I confirmed that the devices without connection lines still appear to be working and HA can see their current info. |
Hello Informations Appareil |
I also had this warning. 2025-01-04 10:37:14.066 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'zha' calls The device in my warning is a Philips Hue motion detector. It and all my other devices appear to be working correctly. I'm not missing any connections in my visualization. |
same here (SONOFF ZigBee 3.0 USB Dongle Plus)
|
same here (Sonoff CC2652P with Zstack 20240710 firmware) Detected that integration 'zha' calls |
Here Sonoff dongle-e with Firmware: 7.4.4.0 build 0
Il Dom 5 Gen 2025, 00:05 drumbelabu ***@***.***> ha scritto:
… same here (Sonoff CC2652P with the Zstack 0710 firmware)
Detected that integration 'zha' calls device_registry.async_get_or_create
referencing a non existing via_device ('zha', 00:12:4b:00:2b:5f:55:99),
with device info: {'connections': {('zigbee', '00:17:88:01:0b:cf:38:cf')},
'identifiers': {('zha', '00:17:88:01:0b:cf:38:cf')}, 'manufacturer':
'Signify Netherlands B.V.', 'model': 'SML003', 'name': 'Signify Netherlands
B.V. SML003', 'via_device': ('zha', 00:12:4b:00:2b:5f:55:99)} 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
—
Reply to this email directly, view it on GitHub
<#134585 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5RUO2BJNLOS6LGR2OG2M32JBSNNAVCNFSM6AAAAABUSLTMR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGQZTINRYG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Seeing the same with a SONOFF device...
In my case, I have 3 "01MINIZB" devices, and all seem to be working as expected. The one refenced is:
The address |
Same problem here since 2024-12-25 00:00. |
Same warning for me. However, my zigbee devices (all buttons) are still working except one (TS0041 Detected that integration 'zha' calls Logger: zha.zigbee.cluster_handlers [0xCD22:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected Logger: bellows.types.named Unknown status <EmberStatus.LIBRARY_NOT_PRESENT: 181>, converting to generic <sl_Status.FAIL: 1> |
here's my turn to say I have the same problem! however apart from the message in the logs, that doesn't seems to affect anything else, everything is up and running and I still can add new ZigBee devices (in fact I would not have noticed the error message if I didn't had to go check the log to troubleshoot an old custom integration that is outdated and not related to this issue at all). Here's the message I have: Detected that integration 'zha' calls Hope it get fixed before that make problems haha! issues are always fixed pretty quickly I don't worry too much |
Just to be clear, this is just a deprecation warning about code, it has no side effects whatsoever and isn't itself a problem! |
Same with sonoff: |
@puddly In case this helps at all... the error still shows up on 2025.1.1 which bumped ZHA to 0.45 which also bumped zigpy and quirks to their latest releases too (but I'm sure you know all this 😄). I also noticed that the IEEE mentioned in the |
@esand Good call on the missing quotes, that was indeed the issue! The EUI64 object for |
Glad I mentioned it - I was going to say something the other day, but while looking at the code, I noticed a number of other places that seemed to pass the IEEE as an object, not putting it through str() first and so I thought it was OK. Knowing this was indeed the issue, may want to check for other areas that deal with the same object and make sure they're casting it when necessary as well? 😄 |
The problem
Detected that integration 'zha' calls
device_registry.async_get_or_create
referencing a non existingvia_device
('zha', 00:12:4b:00:2f:8a:b5:ea), with device info: {'connections': {('zigbee', '00:12:4b:00:2f:b2:a5:fa')}, 'identifiers': {('zha', '00:12:4b:00:2f:b2:a5:fa')}, 'manufacturer': 'eWeLink', 'model': 'DS01', 'name': 'eWeLink DS01', 'via_device': ('zha', 00:12:4b:00:2f:8a:b5:ea)} 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,What version of Home Assistant Core has the issue?
Core-2025.1.0
What was the last working version of Home Assistant Core?
Core-2025.1.0
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zigbee
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha
Diagnostics information
Detected that integration 'zha' calls
device_registry.async_get_or_create
referencing a non existingvia_device
('zha', 00:12:4b:00:2f:8a:b5:ea), with device info: {'connections': {('zigbee', '00:12:4b:00:2f:b2:a5:fa')}, 'identifiers': {('zha', '00:12:4b:00:2f:b2:a5:fa')}, 'manufacturer': 'eWeLink', 'model': 'DS01', 'name': 'eWeLink DS01', 'via_device': ('zha', 00:12:4b:00:2f:8a:b5:ea)} 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,Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: