Nest integration problem with URI

Third party integrations
3

Hi, see the Troubleshooting guide for the Nest Integration https://www.home-assistant.io/integrations/nest/#troubleshooting (updated in the last few weeks)

If you still have questions, feel free to reply here.

4

sorry for the long delay in replying and no I have not

5

I thank you for taking the time to reply and I apologize for not being able to reply sooner. I have tried your revised instructions, and for this user it is still out of my skill depth.

6

You need to be able to access your home assistant from a public domain name like duckdns.org, or use nabu casa, etc. A local IP is not allowed by Google.

(You don’t need to expose it on the internet but that does make it easier)

7

Like @allenporter said. That solved my problem, Tried it again from my Nabu Casa link and worked like a charm

1 Like
8

I did try to edit the previous install but it did not work, will delete it all and try again, thank you for your time

9

Hi Allen,

I went through all the steps again and still not working. I tried my Nabua Casa link, I tried my Duckdns link. Still getting that 400 error message. Little concerned over instruction that says : start the flow all over again" do I have to do another step aside from saving the new authorized rediredt uri?

10

If you’re getting the invalid redirect_uri from Google then it means you need to 1) add the url in the error message to the authorized uri list and 2) add the integration in home assistant again.

11

Yes this is the error, when I try to add the link from the error message it does not accept as it is not a top-level domain, cant save it.

Lol, its going to be something to simple…

these are my URIs now, xxx for secrecy
https://xxxxxxxxxxxx.duckdns.org
http://192.168.x.x:xxxx/auth/external/callback ( this is the one in error message not be accepted)
((and I have even tried adding nabucasa))
https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.ui.nabu.casa/lovelace/0/auth/external/callback

12

You need to access home assistant from the hostname instead of the up address. (Because Google doesn’t allow redirect back to the IP)

13

still no joy with…
http://homeassistant.local:8123/auth/external/callback

14

ok, I got further and have a new error, I accessed the interface from the Nabu Casa url and had used that same url as the redirect…new error is now 403

Request Details

15

Got it by adding my gmail acct as a test user, thanks for your help! Appreciate the time and effort !

16

Hello,

I also have a 400 error when trying to connect.
When I want to add an URI, I cannot add the complete URI because it cannot contain access path (so something after the slash).
So I tried to add the domain with and without the port but always with https with the same result.

How can I add a complete URI when the Google console displays a message specifying I cannot type a complete URI?

EEDIT: finally I was able to bypass the displayed error and to add the complete URI.
It looks like this message can simply be ignored.
And now, it works.
Sorry for the noise :confused:

1 Like
17

Trying to follow along but getting the same error:

Error 400: invalid_request

device_id and device_name are required for private IP: http://192.168.1.XXX:8123/auth/external/callback

I have the Nabu Casa information as the Authorized redirect URIs on the google API site for the Credentials and can access the server from outside my network via the address:

https://xxxxxxxxxxxxxxxxxxxxxxxxx.ui.nabu.casa/auth/external/callback

18

Make sure you are accessing home assistant from the public name. (The url you use to access home assistant is the on ether shows up in the redirect url that Google can see.)

19

Thank you, for some reason, I was reading this in a frustrating session last night and didn’t click until this morning. All working now … again thank you!

for the laymen reading this … after you set up all your google API rights and before you set up the Nest integration within home assistant, log into your home assist via the external address ( Nabu Casa link in my case ), and then from there run your Nest integration.

2 Likes
20

I had this problem today, and I realized it was because I had opened the website with local IP address rather than the external hostname. I ended up solving this using Nabu Casa, but I think it would have also worked if I had just used the external hostname itself.

21

Hi
I wanted to say a big thanks to all the contributors here!
After many hours of messing and frustration, I’ve finally got it working on my setup!

In case it is helpful, i wanted to outline what i’ve done.

Firstly, i’ve followed the excellent github guide here @frenck -thank you so much!

So, after following the intial guide and having it fail with the dreaded 400 error, i got it working by…

  1. Using a DuckDNS address and SWAG to link a custom url ((https://xxxxx.duckdns.org)) to my HA VM (hosted on my Unraid box)… This was quite involved and took a bit of work to get the correct settings in the SWAG homeassistant.subdomain.conf config file (needed to setup the upstream port to be the IP for my HA instance ('set $upstream_app 192.168.1.254;).

  2. Adding ‘Link to OAuth2 Authorize Callback – My Home Assistant’ to the Authorised redirect URI list in the cloud console - the HA intergration setup wizard sequence kept giving a 400 error which inlcuded the ‘Link to OAuth2 Authorize Callback – My Home Assistant’ despite this not being set on the google cloud dashboard.
    I had already added my custom URL and a version with the ‘auth/external/callback’ added to the end, but these wouldnt work.

  3. Adding the ‘trusted proxies’ config to my HA config.yaml file:

http:
server_port: 8123
use_x_forwarded_for: true
trusted_proxies:

  • 192.168.1.0/24
  • 172.17.0.0/24
    ip_ban_enabled: true
    login_attempts_threshold: 5

  1. Ensure i was logged into my external HA URL BEFORE* starting the Nest setup wizard - this seems to be a critical point pointed put by others.

  2. At some point during the setup once i got past the 400 error page, i then needed to open a link that goes to my HA url. For some reason it defaulted to my local HA IP address (192.168.x.x) and would fail. I was able to go back a page/step in the browser and replace the autosuggested url with my custom extenral url (https://xxxxx.duckdns.org) and it all finally worked.

I really hope this is useful for someone!
Thanks all!

22

Hi
I wanted to say a big thanks to all the contributors here!
After many hours of messing and frustration, I’ve finally got it working on my setup!

In case it is helpful, i wanted to outline what i’ve done - i;ve just put the details in the othe related thread here:

Thanks all!