Skip to content
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

Detected that custom integration 'irm_kmi' uses async_config_entry_first_refresh, which is only supported for coordinators with a config entry at custom_components/irm_kmi/__init__.py, line 27 #64

Closed
jdejaegh opened this issue Dec 29, 2024 · 0 comments · Fixed by #65
Assignees
Labels
bug Something isn't working

Comments

@jdejaegh
Copy link
Owner

Warning is triggered when using the repair flow (when the zone has been moved outside Benelux for example). It produces the following log lines:

2024-12-29 15:44:24.696 ERROR (MainThread) [custom_components.irm_kmi.coordinator] The zone zone.home is now out of Benelux and forecast is only available in Benelux.Associated device is now disabled.  Move the zone back in Benelux and re-enable to fix this
2024-12-29 15:45:11.775 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'irm_kmi' uses `async_config_entry_first_refresh`, which is only supported for coordinators with a config entry at custom_components/irm_kmi/__init__.py, line 27: await coordinator.async_config_entry_first_refresh(). This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant