Google-Nest Offical Device Access Console Finally Released!

[mostlychris (Chris)]

Your OAuth stuff is not correct.

Make sure you have specified {url}/auth/external/callback in your Authorized URIs page on the Google side.

[dbrunt (Daniel)]

@EspElement

http://www.xxx.duckdns.org:8123/auth/external/callback

Chris is correct. http://www.xxx.duckdns.org:8123/auth/external/callback needs to be in your OAuth Client Authorized URI’s. However, I am questioning the URL. Every other DuckDNS URL I’ve seen (including mine) does not have www. What’s the URL you use from outside your network to access HA?

For me, my configuration.yaml looks like this:

homeassistant:
  customize: !include customize.yaml
  packages: !include_dir_named packages/

and I specify the URL’s in Configuration, General:

[danielgauci]

I was planning on building my own smart doorbell using a Shelly + regular doorbell along with a CCTV camera above the doorway, however with the current sale of the Nest Hello (£80 off), I was actually considering getting it instead now that the Nest API is open. Given that the Nest Hello takes care of notifying the Google Home Minis on its own, I will only need Home Assistant to know when the doorbell was flashed in order to flash an LED strip in the living room.

Has anyone been using the Nest Hello along with Home Assistant and is happy with the integration?

[EspElement (Joshua Mark McCollum)]

Went back thru and it finally made it! Thanks a bunch.

1. The homeassistant: ymal cannot be on its own page. I had it set for homeassistant: !include but for this, it would not work.
2. Making sure I had the proper quotes. I copied the external_url thing from a page above, and for some reason there was an error in there.
3. Adding www. instead of just http://xxxx.duckdns.org:8123 made a difference. In fact, that may be what caused the final issue not to work, I added the www. to it as well when I redid the steps for the API.

Thanks!!!
Joshua

[dbrunt (Daniel)]

I don’t think the URL needs " "
This passes config check:

homeassistant:
  customize: !include customize.yaml
  packages: !include_dir_named packages/
  external_url: http://URL.duckdns.org:8123

In future, can you use Prefomatted text option (the </> button) for your code segments?
It inserts ``` before and after the code block (which you can type manually of course). They need to be on their own line in your post edit.
For inline code prepend/append the text with single back quote, or select the text and click the </> button…

[EspElement (Joshua Mark McCollum)]

Interesting. This is what I ended up with and worked… LOL
external_url: “http://www.xxxx.duckdns.org:8123”
internal_url: “http://xxxx:8123”

[MiguelAngelLV (Miguel Ángel)]

With 0.118 my Nest Hello is working!

But… I only get a camera, any way of get chime press event?

[PlopDropper]

are you getting an RTSP stream URL? Would love to record footage

[enribomber]

Hi guys. Just updated to 0.118 and got climate. but it’s not updating!! temperature and humidity also not updating. Wasn’t supposed to be solved with 0.118 release?

[Townsmcp (James T)]

@enribomber Use these instructions:

Google-Nest Offical Device Access Console Finally Released!

I dont know if this will help anyone, however I have documented the setup in a much easier way than the Google docs show: Prerequisites - obtain external address and add the subdomain location /auth/external/callback, eg with Nabu Casa (NOTE - do not add a port to the address): https://[xxx].ui.nabu.casa/auth/external/callback For non Nabu Casa users (probably need to add your port number): https://[your_external_url]/auth/external/callback Browse to https://console.nest.google.com/device-…

PS yes it is resolved in 0.118.0b0 onwards

[keithcroshaw]

Your Nest Hello is giving you video through the new update.
I’m still on a Nest account and I’m waiting to jump but I don’t want to until everything is ready.
I only have a Nest Hello.

[pergola.fabio]

i now have my google hub as an camera entity , is this new since 118? i dont see it in rls notes
ok, seems a new feature

is there a way to activate the camera of a google hub from HA ?

[bastero (Juan Carlos)]

@rickokin I’m new to this so bear with me…I’ve managed to get the client_id and client_secret, but where do i get the code part from?

[mostlychris (Chris)]

@bastero

@rickokin I’m new to this so bear with me…I’ve managed to get the client_id and client_secret , but where do i get the code part from?

Code is part of the URL for grant type. You don’t need to add that.

[MiguelAngelLV (Miguel Ángel)]

I think so…

You can use camera.record and it works fine.

[mostlychris (Chris)]

@allenporter Is there a way to round the returned values?

[bastero (Juan Carlos)]

@mostlychris Thanks Chris! I’m at the stage in the set up, where I need to ‘Initiate events’ to have the devices publish.

Where do I get the access-token from to run the curl command?.

[Domenic_DeBonis]

Out of curiosity, did anyone else have any issues with HACS after upgrading to .118? All my nest stuff is fine and working as expected but HACS keeps failing on restart

Nevermind* I saw user comments stating that we needed to update HACS to latest version for it to work.

@mostlychris had provided this on the .118 update thread
I did this to upgrade:

1. SSH into HA or open a terminal.
2. Run the command here in the same directory as your configuration.yaml: https://hacs.xyz/docs/installation/manual_cli

[marcelod (garliclord)]

Thanks for this, much clearer than the official docs. I had my subscriber_id wrong and updates are now instant.

[timothyle97 (Timothy Le)]

Thank you for this! I also had an issue with trying to get the subscriber ID correct and this helped greatly.