Google-Nest Offical Device Access Console Finally Released!

No succes… tried several times. I will do all the steps all over again

No, additional temperature sensors are not supported by the Nest API, which only returns a single Temperature sensor.

1 Like

Thanks for the quick response! That’s unfortunate to hear though.

Still have issues with my Thermostat Card Updating. I can change it just fine, but the temp sensor doesnt seem to be changing. It only updates when I restart HA. Thoughts?

Try to follow this. Please let us know if you need more help.

https://maartendamen.com/ha-nest-sdm

Not receiving updates is most likely a problem with the subscriber_id. The integration instructions have been updated to make that more clear that it needs to be the full subscription name including the path.

Thx. I tried this one for 3-4 times… But let me do it all over again. I 'll let you now the outcome

Painstakingly follow the instructions in post #263 and also this guide. I kept missing/skipping the last page (#4) of that guide. After 7 or 8 tries I got it working…

mine were not recognized automatically and I have 8 of them in my house … can anyone help me?

Hello,

my data not updated but I don’t see “unacked message” in Google Cloud Platform console

Any other idea ?

If I relaunch the integration I have a update.

Thx

Do you have other Nest devices that were detected? If not, it’s probably an issue with your integration setup - I initially had issues because I entered the subscriber name rather than the full “project” path as the subscriber_id element.

Other than that I’m not really qualified to offer assistance - I find the Google console unintuitive to use - but I have faith that the community will iron out these early days issues based on my experience with HA.

Still the same error…
xxx.duckdns.org heeft de verbinding geweigerd.

Probeer dit eens:

  • Controleer de verbinding
  • Controleer de proxy en firewall

My logs show:

xxxx.duckdns.org heeft de verbinding geweigerd.

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/system_health/ init .py”, line 212, in async_check_can_reach_url
await session.get(url, timeout=5)
File “/usr/local/lib/python3.8/site-packages/aiohttp/client.py”, line 551, in _request
await resp.start(conn)
File “/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py”, line 907, in start
self._continue = None
File “/usr/local/lib/python3.8/site-packages/aiohttp/helpers.py”, line 656, in exit
raise asyncio.TimeoutError from None
asyncio.exceptions.TimeoutError

my https result:

https://xxxx.duckdns.org:8123/auth/external/callback?state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmbG93X2lkIjoiYzk2YWNhMmE4MjgxNDZkYmIxOWNkYmU4ODFkNDRjYjYifQ.CfNL181iYOGKLGyvet5hzuJ8gcw8qWTL4qZjSh-qYbE&code=4/0AY0e-g4m7hWuJimox_BTPPScK10LrIkKEoyokwD7SriLouHISFVyWWfnIsVZJqkD6FbSqA&scope=https://www.googleapis.com/auth/sdm.service%20https://www.googleapis.com/auth/pubsub

hi,
does this component work with google home or google home mini or google wifi?

See https://www.home-assistant.io/integrations/nest/#overview-supported-devices which lists the supported devices for the component discussed here.

Also see other integrations like these:


yes the doorbell was recognized and works so far, but the nest hubs were not recognized …

added the nest integration to my hassio and added relevant info to the config and the nest hello camera works perfectly.

However I want a light to come on when a person is detected, I would have thought google would have had this feature in google home but alas it doesn’t exist. Looked at a couple of options linked to in this thread for the sensors to be read by ha but I appear to be failing every time, what am I doing wrong?

I’ve been trying for a couple of days, and have been unable to get the integration working (though have found some of the advice above very helpful for getting past earlier problems.)
I have HA 0.118.4 running on Docker. Supervisor Version 2020.11.0.
I use DuckDNS

After following the steps carefully, I have a configuration.yaml that looks like this:
nest:
client_id: 6xxxx-jxxx.apps.googleusercontent.com
client_secret: xxxxx
project_id: xxxxx
subscriber_id: projects/xxxxx/subscriptions/xxxx
(which is the Subscription name, though I’ve also used the subscription topic)

I get to step 36. Allow each popup. but instead of ‘Done!’ I get
'This site can’t be reached xxxxx.duckdns.org unexpectedly closed the connection.

Any ideas?

The motion detection events will be added to the integration at a later point it sounds like.

1 Like

If I have integrated nest, can I no longer integrate google cast? I always get a message from google cast when I want to set this up “canceled, only a single configuration of google cast is necessary”

Follow these steps slowly, precisely and carefully (all 4 pages):

  1. Get Started
  2. Authorize an Account
  3. Use the API
  4. Subscribe to Events

I was missing the last step and after re-doing the entire sequence for the nth time, when I did that step my updates were instant rather than once after a restart of the integration.

&/or follow Post 263

https://console.nest.google.com/device-access/project/ebff85b2

This…

is used to create topic in console.cloud.google.com (Step 4 of 4)…

and then create the subscription for that topic…

which is your nest_subscriber_id:

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

https://console.cloud.google.com/apis/credentials?project=home-assistant-
APIs & Services
Credentials
OAuth 2.0 ID:

nest_client_id: 305307960111-e1cnd1a19hfsn1p6oha2f7umdd58kfi3.apps.googleusercontent.com

OAuth 2.0 Secret:

nest_client_secret: xxxxxxxxx-xxxxxxxxxxxxxx

https://console.nest.google.com/device-access/
Project ID:

nest_project_id: ebff85b2-5277-45ea-b794-6e6e76109995

https://console.cloud.google.com/cloudpubsub/topic/list?
Pub/Sub
Subscriptions
Subscription name

nest_subscriber_id: projects/home-assistant-295423/subscriptions/nest
1 Like