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

HA 2025.11 warning... #262

Open
Corvus71 opened this issue Nov 11, 2024 · 3 comments
Open

HA 2025.11 warning... #262

Corvus71 opened this issue Nov 11, 2024 · 3 comments
Labels

Comments

@Corvus71
Copy link

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/issues

Is this something to worry about?

@RogerSelwyn
Copy link
Owner

RogerSelwyn commented Nov 11, 2024

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

@RogerSelwyn
Copy link
Owner

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).

@RogerSelwyn RogerSelwyn pinned this issue Nov 23, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants