Google-Nest Offical Device Access Console Finally Released!

Camera Integration would be awesome!

3 Likes

Climate, too!

Currently on the fence about replacing my nest thermostat with an ecobee… I have been saved by NOT upgrading my nest account before the switch but at this point I don’t see myself purchasing any more Nest products other than the minis.

Maybe if this API gets updated I can carry on a bit longer with the nest thermostat.

1 Like

How to use this code in Home Assistant today? https://github.com/allenporter/python-google-nest-sdm

1 Like

Following currently using starling and HA to get everything in HomeKit

Would be nice if camera support + streaming capability was added, so not just still image view

1 Like

The initial first proof of concept using only temp / humidity sensors is checked into the main branch, but not released yet. This code is going into the existing nest integration so you can always check there for the latest instructions. One released, setup instructions will be there.

Support for cameras, climate, etc still coming.

9 Likes

Thank you Allen! I’ve already got the Google side ready with my Nest thermostat…

Shame that no Nest Protect data is available.

2 Likes

Hi, I was wondering. I see all kinds of solutions using NodeRed flows and custom plugins.
Is this going to be the only way to configure or should i be more patience and wait for an official HA Integration if i don’t like the hassle.

Thanks!

I would wait.
With how successful people have been with hacking their own things together, an official thermostat and camera probably aren’t that far away in comparison to how long works with nest has been in a zombie state.

Hi Keith,

Thanks for responding. The only thing i got is the nest doorbell, it would be nice to utilize the camera feed but i bought it a couple of weeks after the closed the old api so i am getting used to it and will wait some more.

Al the guys working on it,:partying_face: Big thanks to your effort! :partying_face:

1 Like

Hey, so great!

New nest integration gives error:

I am running from public url but it redirects to local IP which i cannot add to authorized redirect uri, but have added the public URL.

Configuration.yaml:

 http:
   external_url: smarthome2.xx.xx
   internal_url: 192.168.68.xxx:8123

Do you maybe know what’s going wrong @allenporter ?

thanks

I’ve just had success after a very technical setup!! I did not find the google documentation easy to follow!

I had the same error as you Mart, but I then got it working by setting up in the Nest integration via the external URL. ie login and access home assistant via the external URL and then setup the nest integration. It then callsback to the external URL you access via, rather than the internal.

Probably worth adding that to the setup guide…

Thanks @BenW That’s exactly what I did. I configured the integration through the public URL and still got redirected to the local ip. What’s causing this?

You need to open Home Assistant via the external url in order to authenticate. You can’t authenticate an application over an internal network.

Edit: missed your reply; did you open HA with the external URL?

1 Like

Ye, I used the public URL to start home assistant.
Exactly what I did, but it still redirects to the local IP. My configuration.yaml has the setup of the url/local/public correct right (see configyaml snappit below). Where else is this possibly wrong configured?

 http:
   external_url: smarthome2.xx.xx
   internal_url: 192.168.68.xxx:8123

Not sure if it matters but have you got the URLs set via Configuration -> General ?

I set them there rather than in the yaml

Got it configured there, yes.

Is there any place where I can hard configure the redirect url to be public instead of the local IP within the integration config maybe?