I am still on HA 0.117.6 and have done the additional instructions of setting up the subscription, and put the subscription name as the subscriber_id and still I only get updates when I manually reload the nest integration. Is this working for other people? Or the people that are saying it’s working on a newer beta version? Also I am not using appdaemon.
The new integration code that’s working is only in 0.118.0b2.
it aborts when I try to add the integration “nest”
I’m just getting a pop-up. nothing in the log…
I’m on 0.117.5
I’ve tried adding the logitech integration (for the harmony hub) and that went fine.
No I’m using the home computer for this, connected to the home network. Already tried to disable the firewall but no luck.
Have you rebooted after adding the 4 config lines to configuration.yaml?
He can add the integration via local IP (which fails to complete since it’s local IP) but cannot seem to get past absolute step 1 (add integration) when using public IP so that tends to indicate the configuration.yaml is okay…
Was that via your public URL?
Could you possibly test from completely outside your network (both Nest and Logitech)?
yes rebooting was done after adding the 4 lines in the config yaml.
I also just tried on the office network using my public URL but still the same issue.
What are you using for your URLs? Others have had this issue when URLs were not set correctly. Can you get to your HA instance from outside your network?
@mostlychris I can access my HA instance from outside my network.
I’m using the following url : https://xxxxxxxxxxxxxx.ui.nabu.casa/lovelace/default_view
What are your URL settings in Home Assistant?
Google Nest is currently experiencing a major outage.
Upgraded to 0.1180b3 30 minutes ago, and got weird Internal server errors from https://smartdevicemanagement.googleapis.com/v1/enterprises/xxxxxx-xxx-xxxxx
After debugging, triple-checking credentials, resetting pubsub-settings and testing both in homeassistant and with curl, I decided to check the Nest-app. “There was a problem while connecting to the Nest Service”.
Guess I will have to wait a bit to make sure the integration is working 
@mostlychris The external url in HA general settings was incorrect. 
Now the integration Nest is available but it returns the following error
The redirect URI in the request, https://xxxxxxxxx.ui.nabu.casa/lovelace/default_view/auth/external/callback, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/${your_client_id}?project=${your_project_number}
I followed the link and I got the message =
You do not have at least one of the following rights
Project
clientauthconfig.brands.get
clientauthconfig.clients.get
iam.serviceAccounts.list
oauthconfig.testusers.get
oauthconfig.verification.get
resourcemanager.projects.get
Sounds like you haven’t set your authorized URIs correctly here:
I’m in the realm of guessing on your error, but it would seem that you are not using the account your nest stuff is on and/or not the account you originally set up all the Google stuff with. You might need to use an incognito window and go to the developer console with the correct account.
1 Like
We’re back…actually a couple of hours ago.
Yes, I noticed but then got busy…
Hello! Thanks for working on this. I followed the very nice steps by someone above and I got it all approved, but the integration is not showing up after reboot. Do I just need to wait before I can find it? Not sure why, I followed them to a T and am glad everything accepted what I entered… Lol
Did you add the nest integration to your configuration.yaml?
nest:
client_id: !secret new_nest_client_id
client_secret: !secret new_nest_secret
project_id: !secret new_nest
subscriber_id: projects/projectname/subscriptions/subscriber_id
Yes I did add this to the config.yaml and it didn’t give me errors when I checked it.