Just managed to get this working for the first time. I’m on raspberry pi / hassios, and had a couple of workarounds needed to get the cookies thing going as mentioned above.
The main one is that @imick seems to be suggesting everyone install @nicoinch 's fork, which gives you the cookies fields to paste into when you set it up.
Also I had to manually install the fork as HACS wouldnt let me install nico’s one via the UI. That involved installing an FTP plugin so i could transfer the files to the HACS custom_components folder.
Also also FWIW I can’t see the integration in the hacs/integrations display (where I could see mick’s one installed via the UI). Hope this is useful for anyone else struggling - corrections welcome.
Posted this on the Home Assistant Community Forum. I have an issue with the Nest Protect. It stopped working after the install of 20230503.1.
I have tried to re-authorize using the cookie and issue token but it doesn’t want to budge. Any ideas?
Thank you
This is the error log:
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/nest_protect/init.py:126
Integration: Nest Protect (documentation, issues)
First occurred: 09:14:59 (1 occurrences)
Last logged: 09:14:59
Error setting up entry Nest Protect for nest_protect
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/nest_protect/__init__.py", line 126, in async_setup_entry
hass.config_entries.async_setup_platforms(entry, PLATFORMS)
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'
Yesterday we had a small fire in kitchen. Nest Protect speak out this issue so we were in time to get in action. After we settled down and everything was over I checked my HA. (I have automation that triggers a notification alarm) but this didn’t fired… No state change on the specific Nest protect was registered.
So my question will be: Is this add-on really working?
Would be great if you can create an issue on GitHub and we can investigate, when you have time. I have to say that other people did also notice this in the past, but we haven’t been able to gather any good logs. In my case it did work…
This morning I started work on trying to migrate my Nest Protects to Google so I can start using your custom component. I ran into an issue with Google - apparently you can’t migrate Nest Protects to Google G-Suite accounts. Totally rediculous since all my other Google products are tied to my G-Suite acount (Google Home, Mini’s, etc).
My question is if I create a separate account (gmail) for the Nest units, would this still work? I already have Google minis in HA using my G-Suite account, so not sure if this can use a different account just for the Nest units. Thanks!
The authentication method of Google Accounts is not ideal anymore as well. You would need to use the beta version of the Nest Protect component, and extract manually your session / cookies. This method has also still quite some issues on our GitHub.
TLDR: the Nest Protect component does not work super super reliable at the moment due to changes on the Google side
Thanks! I was able to locate the beta version and extract the session / cookie - and everything is working! Hopefully Google doesn’t further limit things. Honestly, your custom component provides more information and is much better than I had with the original Nest API in HA.
Obviously you worked this out and got it working - but I also got stung - my entire ecosystem is based on a very old G-Suite account, so had to setup a new vanilla @gmail.com account to get things going.
So far so good, but what a PITA! I’ve only linked them to HA so far - haven’t bothered trying to link into my existing Google Home setup yet.
Thanks for this! I recently noticed my Nest Protect integration said it needed to be “Reconfigured”. It prompted me for an access token which I couldn’t find. Came here, scrolled to the latest entries and found yours.
Downloaded v0.4.0b2 as of today and followed the beta instructions you linked and got the needed info. The only thing that was weird is the prompt in HA to configure it has two textfield entries, which I assumed were for the issue_token and cookies info. But they aren’t labeled. I just once again assumed the first one was for issue_token and the second for cookies. That did the trick, and then it recognized all of my devices.
This integration (v0.4.0b2) is working for me also. I first tried with my old, free Google Workspace account but as expected this did not worked. After that I used my Gmail account with succes. This is working without problems. Thanks to everybody for all the efforts.
