-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
HA 2025.11 warning... #262
Comments
It does say it is only a warning and it will stop working in a years time. I will make the required change in due course. Thanks for reporting |
It is possible that this warning will not be possible to remove, it seems that HA core is moving towards all integrations (certainly those that use co-ordinators) having a config entry. Because o365 is setup from yaml, it doesn't have a config entry. I'm not sure this may not be solvable without removing the co-ordinators. Given that I have written replacement integrations, which don't have this problem, a wholesale migration to those may be required (in particular when they finally make it onto HACS default). |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
2024-11-11 13:06:53.071 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'o365' uses
async_config_entry_first_refresh
, which is only supported for coordinators with a config entry and will stop working in Home Assistant 2025.11 at custom_components/o365/helpers/setup.py, line 87: await sensor_coordinator.async_config_entry_first_refresh(), please create a bug report at https://github.com/RogerSelwyn/O365-HomeAssistant/issuesIs this something to worry about?
The text was updated successfully, but these errors were encountered: