-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Integration stops working after update HA Core 2025.1.0 #397
Comments
Same problem. Asks for reauthentication and token. |
Mick is going to need your logs, device diagnostics and all that fun stuff. FWIW working here on 2025.1.0 with no issues. |
Same problem here. Log message here:
|
Same TEMP_CELSIUS error here.. The const is deprecated and now gone. See https://github.com/home-assistant/core/issues/108991 should be a simple fix. did not go from beta to production? |
Please update to the latest version. Most likely you are using a fork and not this integration. Easiest is to remove the |
solved! Thank you iMicknl |
Hi, 2025-01-05 14:14:27.836 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Nest Protect for nest_protect |
How did you install 0.4.0? This code is not present anymore, so it is impossible to face this error if you installed it correctly.. |
That solved it for me. I removed the old integration from the Home Assistant integrations page. Then I searched for and downloaded 'Nest Protect' in HACS. Then go back to the integrations page and search for 'Nest Protect' and then follow the steps. |
I'm not sure what happened with removing the old install and installing 0.4.0 but I just repeated the process and this time it worked. Thanks!! |
The problem
Integration no longer works after HA Core 2025.1.0 update.
What version of this integration (ha-nest-protect) has the issue?
0.4.0
What version of Home Assistant Core has the issue?
2025.1.0
Device / Model
4 devices (Nest Protect)
Diagnostics information
No response
Home Assistant log
Logs
Additional information
No response
The text was updated successfully, but these errors were encountered: