They’ve announced the protect is now discontinued, but is supported at least until it expires, which is something.
I wonder what this will mean for the integration. Especially as the integration with Google Home is now in preview, which I have signed up for.
I just followed the instructions and have all ID’ s and so on. But, at the end I was sent to a web-page (https://nestservices.google.com/partnerconnections/…). The error message was
Can’t find devices to pair with [project-name]
If your home has multiple members, the person who originally set up the home will need to migrate their Nest account to a Google Account before you can pair with [project-name].
I made sure that when I log into the Android Nest-app, that I log in with my Google account. I wasn’ t able to create a new Nest-account. So… The devices are connected to the Google account.
I am looking forward to receiving feedback how to add the Nest Protect devices.
I ran into the same issue.
Try pressing the download button while in HACS.
The add integration buton doesn’t seem to work.
Great guide,
I was wondering about “Battery Level” value.
Replaced batteries yesterday but still displaying 44% and 84%
I just got an alert in my Nest app to move my 6 Nest Protect to “Google Home”. Last time I moved my account, the debacle to keep them in Home Assistant started so I am concerned this move will break my current integration method (the one in the top post of this thread).
Can anyone confirm whether it is harmless to move the account to Google Home (from Nest App + Google account), whether it is actually better (maybe it opens up Google Home to HA integration path?), or whether I should avoid it at all costs.
I ‘moved’ mine without issue. You can see them in both Google Home, and in the Nest app. Didnt have to do anything in this component.
just updated my HA core to 2026.2.0 and needed to login again - does this occur with (every?) system-updates for you as well?
edit: the integration is now asking after every Ha reboot for the issuetoken+cookie. This is really nasty 
I dont update to .0 releases, so havent updated yet, but ‘normally’ up to this point no. Its been flawless for a really long time.
