home-assistant[bot]
commented
3 hours ago Hey there @bdraco, @rfverbruggen, mind taking a look at this issue as it has been labeled with an integration (rachio) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `rachio` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign rachio` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
rachio documentation rachio source (message by IssueLinks)
The problem
Detected that integration 'rachio' 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.This is logged on every start.
What version of Home Assistant Core has the issue?
2024.11.1
What was the last working version of Home Assistant Core?
2024.10.X
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Rachio
Link to integration documentation on our website
https://www.home-assistant.io/integrations/rachio/
Diagnostics information
Detected that integration 'rachio' 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 homeassistant/components/rachio/init.py, line 96: await base.status_coordinator.async_config_entry_first_refresh(), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+rachio%22Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
The coordinators are part of the config entry, so I'm not sure what is supposed to be used here... Maybe just
coordinator.async_refresh()?I didn't see anything in the dev blog that mentioned this change.