Google-Nest Offical Device Access Console Finally Released!

@thedave1022 See above. subscribe to events not done &/or subscriber_id is wrong
@ronniebee You’re still not there yet???

Hi,
The HA team here is just me :slight_smile: when developed the integration. I’d gladly welcome contributions to improve the docs via sending a pull request. I’m currently focused on building out features and debugging the core functionality.

1 Like

Allen. I’ll see if I can help…

@TechBrain64 your welcome. I did message the OP a opulent of weeks ago asking him to sticky my post to the first post so people might find the instructions easier to find but :man_shrugging:

@allenporter I’m happy to help to when your wanting help on the documentation. I have the Nabu Casa angle covered and @dbrunt you use DuckDNS/local hosting method don’t you? I’m sure bewteen us we can work together to help Allen

Yes, I am just ‘ducky’ here!

(I prolly should annie up for Nabu Casa and contribute to the cause though…)

Currently sitting in my office sleep deprived after fighting with Nest / HA lastnight switching between a couple of youtube videos and the official guide.

Cannot wait to get home and give this a go!

I ran all the steps in the get-started guide. All commands run fine. Still the same issue. If I reboot HA or reload the integration the thermostats update. Otherwise nothing.

I set everything up according to the instructions, but in the last step of connecting the integration in Home Assistant, it reports an error:

Error 400: invalid_request
Invalid parameter value for redirect_uri: Raw IP addresses not allowed: https://200.200.1.10:8123/auth/external/callback

I access my Home Assistant via https://xyz.duckdns.org/ and everything works perfectly.

Unfortunately, the update does not work. Where can the problem be?

Have you used the IP in your HASS config, rather than your duckdns URL? Under Configuration, General tab.

Check out the latest troubleshooting instructions https://www.home-assistant.io/integrations/nest/#troubleshooting

You need to update the allowed redirect urls to match the url printed on that error message.

Check out the new updated troubleshooting instructions for not receiving updates https://www.home-assistant.io/integrations/nest/#troubleshooting

My settings in “general” look like this
home assistant nest

I tried to change my settings several times, but to no avail. I’m posting two screens of the problem below.

It is clear that it is not possible to set it this way

When you are setting the integration up, are you doing it via the external address? (To be honest your internal address looks strange, you’d normally expect it to be 192.168.x.x:8123).

The address is OK, it is set on the router that if port 443 arrives (which is https communication), it automatically redirects it to the home assistant 200.200.1.10:8123. So it’s the same

Anyone have ideas where could the problem be?

The URI set the OAUTH client needs to be the duckdns one, which it looks like you have done but your screenshots don’t show it after you have saved it. You then need to access your HASS instance and set up the integration via the duckdns url, not via the IP. I would guess you are using IP, which is why you are seeing it in the invalid request error you have posted.

If you aren’t accessing via IP, then hopefully one of the guys who use duckdns can help.

I guess I don’t quite understand. Please send me the screen of the place you are talking about. Thanks

When you access your hass instance to setup the Nest integration you need to access it via https://xxxx.duckdns.org/

Bingo, that was it. Thanks a lot.

We moved on and came across this error :slight_smile:

Doesn’t mean anything to me. Are you sure you have the URI right on the OAUTH Credentials page, should be https://xxx.duckdns.org/auth/external/callback ?

Bear in mind the first error told you you can’t use raw ip, so it doesn’t mean you have the right URI yet. But I thought if URI was incorrect it came up with a 500 error.

Might also be worth checking your client ID and secret are correct in your config, because that would identify the oauth credential I think. The ID and secret are shown on your OAUTH credential page, would have been at top right of one of your screenshots (with the URI on).