-
-
Notifications
You must be signed in to change notification settings - Fork 89
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 (MainThread) [homeassistant.helpers.frame] Detected that custom integration will stop working #1483
Comments
same for mine, I've upgraded to the latest OCPP, core, supervisor, OS, frontend etc. My log I can still see sensor readings, and I can control - charger control, availability, reset and unlock, but max current entity although available can't be changed and generates error notifications |
Same issue for me after updating to Core 2025.x |
Sadly for my installation, this did not work. I've reinstalled several times also. I can see all the sensors and switches as per normal, but the charge rate can't be adjusted |
Describe the bug
Warning appearing in Home Assistant logs during startup:
WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'ocpp' calls
device_registry.async_get_or_create
referencing a non existingvia_device
('ocpp', '01JETVDSDMS8Q5CGSNK763N169'), with device info: {'identifiers': {('ocpp', 'charger')}, 'via_device': ('ocpp', '01JETVDSDMS8Q5CGSNK763N169')} at custom_components/ocpp/button.py, line 57: async_add_devices(entities, False). This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/lbbrhzn/ocpp/issuesTo Reproduce
Steps to reproduce the behavior:
Expected behavior
No warning to appear
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: