-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Description
Description
After upgrading Home Assistant to 2025.12.0 I started getting a warning in the Repairs/Logs related to the solaredgeoptimizers custom integration.
Home Assistant reports that the integration calls device_registry.async_get_or_create with a via_device that does not exist in the device registry. The warning message also says this will stop working in a future HA version and asks to open an issue for this integration.
The integration still works for me (I can see per-optimizer entities and use them in my dashboard), but the warning appears on every restart.
Home Assistant version
- Core: 2025.12.0
- Installation type: (e.g. Home Assistant OS / Container / Supervised / Core)
solaredgeoptimizers version
- Installed via: HACS
- Version: 1.2.2
Log warning
Full warning from Settings → System → Logs:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:350
First occurred: 09:48:52 (1 occurrences)
Last logged: 09:48:52
Detected that custom integration 'solaredgeoptimizers' calls
'device_registry.async_get_or_create' referencing a non existing 'via_device'
(('solaredgeoptimizers', '01K6TDB1SMG06Q98M9DYRGPM6E')), with device info:
{'hw_version': '21081644-83',
'identifiers': {('solaredgeoptimizers', '21081644-83')},
'manufacturer': '',
'model': '',
'name': '1.0.1',
'via_device': ('solaredgeoptimizers', '01K6TDB1SMG06Q98M9DYRGPM6E')}
at custom_components/solaredgeoptimizers/sensor.py, line 103: async_add_entities.
This will stop working in Home Assistant 2025.12.0, please create a bug report at
https://github.com/ProudElm/solaredgeoptimizers/issues
(Values like identifiers, hw_version, via_device will of course be specific to my system.)
Steps to reproduce
Install solaredgeoptimizers via HACS and configure it (SolarEdge inverter with optimizers).
Upgrade Home Assistant to 2025.12.0.
Restart Home Assistant.
Open Settings → System → Logs or Repairs.
Expected
No warning from solaredgeoptimizers about via_device.
Actual
A warning as shown above is logged on each restart.
Additional context
I use the integration to read each panel/optimizer separately and show them in a custom dashboard. Functionally it still works fine; this report is only about the deprecation warning regarding device_registry.async_get_or_create and via_device.
Metadata
Metadata
Assignees
Labels
No labels