Google-Nest Offical Device Access Console Finally Released!

Following on from my 401 issue, can’t there be a problem here on this screen?

That screen is normal as we’ve/you’ve/I’ve not tested and obtained approval from Google for commercial use. You are the developer and you are sharing your own information with yourself. Just click ‘Next’…

Thanks for the feedback. And the 401 error I came across above? Could you guide me how to debug, or where to look for a solution?

401: invalid_client
The OAuth client was not found

I would say your nest_client_id is wrong…

nest_client_id: 305307960111-e1cnd1a19hfsn1p6oha2f7umdd58kfi3.apps.googleusercontent.com
nest_client_secret: xxxxxxxxx-xxxxxxxxxxxxx
nest_project_id: ebff85b2-5277-45ea-b794-6e6e76109995
nest_subscriber_id: projects/home-assistant-295423/subscriptions/nest

In the end, I reset everything and everything seems to work. Thank you very much for your help

By setting subscriber_id: projects/nest-297402/subscriptions/Nest in my configuration.yaml it started to work. It wasnt with the sdm path

is anybody here successfully using a nest cam from this integration? When I click my camera, if it loads, there’s a significant delay/lag (7-10 seconds). When it doesnt load, it seems to cause some weirdness with HA lovelace (pages sorta stop loading, then i’m forced to restart HA).

Per my post way up there ^

1 Like

Not totally expected but I found some problems with expiring stream urls that I am working on fixing here https://github.com/home-assistant/core/issues/42793 where a new stream worker is created for every time the url changes every X minutes.

Its hard to diagnose because it generally works for me, but I have it running on a beefy machine.

Happy to investigate more if you raise new issues with debug logging turned up as described in troubleshooting.

I’m not sure it has anything to do with the host specs that HA is hosted on, but maybe? I’m running on an i7 nuc with 8GB of mem. I’m happy to help you troubleshoot if you’d let me know what debuggers to turn on? Upon first glance, I don’t really see any errors that seem to relate to this.

edit: sorry, missed as described in troubleshooting. - I’ll check that and see what I can find before raising an issue

Been trying to get this going for hours now… Im able to setup everything but im not getiting updates and Im getting high amounts of unacknowleged messages in my google cloud. my sunscriber_id is set to my subscription name in the cloud Im lost why its not working…

Hello,

I have a problem with new beta 1.0 version of HA. Lovelace climate card does not get updated according to the changes I make to the thermostat. Device on-off and temperature changes are not in sync.

Everything works great on 118.4 so I reverted back to this version.

My setup:

nest:
  client_id: xxxxxxxxxxxxxxxx.apps.googleusercontent.com
  client_secret: xxxxxxxxxx
  project_id: xxxxxxxxxxxxxx
  subscriber_id: projects/homeassistant-xxxxxx/subscriptions/Nest

Just wanted to say thanks, works just perfect :love_you_gesture:

Be super careful to follow the instructions :wink:

Mine is working fine…

image

It would help to see specific screen shots of your settings from your nest device access console, google cloud console and your nest: integration settings (except for your OAuth client secret)…

FWIW, I had an issue with the Zigbee integration back when I went from 0.117.x to 0.118.0b0. I posted my issue and then restored to 0.117.x. They then asked for debug logs so I upgraded again to 0.118.0b0 and my issue did not return…

sure heres my configuration.yaml entry

nest:
  client_id: !secret nest_client_id
  client_secret: !secret nest_client_secret
  project_id: !secret nest_project_id
  subscriber_id: !secret nest_subscriber_id

and my secrets.yaml

# nest
nest_client_id: abunchoflettersandnumbers.apps.googleusercontent.com
nest_client_secret: xxxxxxxxxitsthesecretiwasgivenxxxxxx
nest_project_id: 453f9765-8155-41ae-95b5-547ae798a806
nest_subscriber_id: projects/hass-297518/subscriptions/HASS

as far as the reduction we see in unacknoledged messages i believe is just expiring messages and i havent been messing with it as much I dont think any are recieved. clicking controls on the thermostat in hass instantly makes change on the thermostat but it isnt reflected in hass and the unacknowledged message count grows…

1 2 3

I’m having the same issue with the Thermostat on 0.118.4. The actual thermostat will receive any commands won’t reflect in HA.

1 Like

Does this match your HA setting:

image

image

my external url is https but otherwise yes