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):
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
I solved it.
By removing the port 8123 in the google url forward https://console.developers.google.com/apis/credentials/
and also in the external url in hassio ( where you can add the external and internal url).
Spend more than 15 hours retrying over and over but this did the trick!!! YEAH!!!
Thank you so much. I must have started from scratch six times, and this worked straightaway. Can this be included in the instructions ?
Great to hear it is working. I still have one issue and that is that my humidity and temp sensor do not update. Is this working on your side?
Followed all the steps and got everything working on the latest version of HA.
but it seems the sensors don’t refresh, anything particular to be done about that?
It would be worth you reading back up this thread. Here is the most recent post on the subject I think.
Also worth reading this - Subscribe to Events | Device Access | Google for Developers
Or this - Google-Nest Offical Device Access Console Finally Released! - #263 by Townsmcp
Thank you! I’d almost stumbled into the right sequence after several attempts but would never have got the cloud pub/sub part of it you added. That seems to explain why I had an integration that showed data but wouldn’t update. Having worked through this it’s now all working as expected.
1 Like
If I change the target temp in Home Assistant, it updates instantly on the Nest; But not the other way round: changing the target temp on the Nest is not reflected in the card in Home Assistant. I’m not sure about the actual temperature- that takes a little longer to change in real life, so I’ll need to wait for real differential, but it looks like the reported Home Assistant temperature lags the Nest.
Yay!
Only 15 hours? I think I spent double or even triple that to get it working!!
I started on Sep 22nd…
I know I started my posts obliterating what I thought was sensitive info but now in hindsight I think the only potentially sensitive info is the OAuth 2.0 secret. Considering all of the hoops and hurdles we have to navigate (and all of the failures!), I fail to see how a hacker armed with all of the info could make use of any of it without knowing your google account credentials, which is why I did not conceal any of my info in my last post except for the oauth secret.
1 Like
no 8123, I can acces my system via https://xxxxx.duckdns.org ( without a port number). Tested it via my iphone with wifi turned off
1 Like
Double check the subscriber id matches the subscription name.
https://console.cloud.google.com/cloudpubsub/topic/list?
Pub/Sub
Subscriptions
Subscription name
nest_subscriber_id: projects/home-assistant-295423/subscriptions/nest