I’ve tried the most recent version in HACS as well as manually installing 0.4.0b2 and 0.4.0b1 and am never able to get this to work. I followed the instructions up top to get the issue_token and cookie.
While the HA GUI says “Unable to connect” I do see network connections from my HA system to the IP for accounts.google.com when using tcpdump on my firewall.
I don’t see any logs for this integration in home-assistant.log so I’m not sure what else to do as far as troubleshooting goes. Any ideas anyone?
EDIT: Added a screenshot. Disregard the ‘unexpected error’ because after submitting the creds below, I get the “Failed to connect” error.
EDIT2: Solved my issue. IPv6 wasn’t getting out on my IOT vlan. Even though HA did an A and AAAA lookup, it never fell back to IPv4 for some reason. Explicitly permitted IPv6 to 443/tcp and this nest integration is now working with 0.4.0b4.
I’ve used the original API based method for years in my last home assistant install, and am about to try the beta… but I just wanted to ask… are there any security implications of sharing what looks like a Google Account cookie here? Is it only giving access to nest, or the entire google account?
(I’m not saying I don’t trust the author by the way… just assessing before committing)
Brilliant!!! Have been banging my head against the wall with the native Nest integration for months and stumbled across this today. Within 15mins, I could finally see the Nest Protect in all its glory within HA. So happy
I got my smoke detectors connected but now i want to add them to my HomeKit (Homekit bridge via Home Assistant).
I have 10 smoke detectors and get 190 entities. All of them are switches (Heads-Up,
Nightly Promise, Pathlight, Steam Check) and binary sensors, but even selecting all of them, the only things i get in HomeKit are the switches. I don’t get a smoke detector or CO detector. Is this possible?
Wireless is also supported! They just don’t support the occupancy sensor (since this one is not available via the API).
And happy to see that it still works for people. Unfortunately due to work I haven’t had much time to work on the beta version, but any contributions are welcome! Sometimes I can find some spare hours for maintenance… My plan is still to get it stable enough to promote it to a regular release
No. This most likely won’t pass the quality metrics of HA, due to this ‘weird’ authentication method. The previous (now blocked) method was great, so if someone is able to figure out a work-around, I might work on porting this to core.
Your not doing the token properly then, I had that happen the first time. Make sure you are using private browsing, and close the session after. Mines been good for a year or so now.
An other question
By using this method, using the TOKEN and COOKIES
are the values obtained through google (nest) server
or obtained directly from the device itself ?
Another question , sorry for that .
I want to buy a second Nest protect V2 ( batt), because i really like this intergration (many thx Mick)
But how do i add an extra device ten to HA , with this method
Is it just, connect to your network and add new device to your Nest app?
Will it then automatically pop-up in your HA
Test if the device communication is working in HA
I tested it once with a smoke pen , if the alarm is triggered at device, Nest app and HA . And it all works
So i tested it further, i read somewhere above this forum
Test, can also done by toggle these switches
But when i toggle these, HA pops-up with an error
“Failed to perform the action switch/turn_on. unknown error”
Is that error generated, because it cannot directly switch these (it is a wireless device)
When i try to do that in the Nest app , it pops-up with a message (change could take a day to have affect)
I’m unable to get this add-on to work with either method. Using an incognito chrome browser and trying to use the beta/cookie method, I simply end up in a loop where it keeps asking me to login to google.
