I had to add the following to my configuration.yaml file.
homeassistant:
external_url: “http://xxx.mydomain.com:8123”
internal_url: “http://192.168.x.x:8123”
Exact same error, that’s because it redirects to the local ip even tho I configured the things from above. Did it on multiple computers multiple browsers multiple restarts of pc and home Assistant
after a lot of trial and error, I had to make sure I was using the base URL of nabucasa https://mynabucasaurl.ui.nabu.casa/ and not the https://mynabucasaurl.ui.nabu.casa/lovelace/home and had to make the same changes to the API URI. https://mynabucasaurl.ui.nabu.casa/auth/external/callback. I am now able to see my entities in homeassistant.
not sure if this will apply to you since you are not using cloud, but thought I might share now that I got it up and running.
Have you tried accessing your HA instance via an external device rather than on your local network. For example using your mobile phone?
Sounds like, given you are using IIS, a site with your public domain has been configured to redirect via the client to your internal network address. You need a reverse proxy like ARR or Nginx to forward requests within the webserver.
Tried 4g on my mobile phone, yes. I have arr configured with forwards and stuff. Special things that might cause this, that I can configure in iis or home assistant?
You should be able to go through the authorisation flow on your phone if it can reach HA over 4G. Does that still state your internal IP in the error message if you do? It would rule out any odd behaviour in our IIS setup when used internally.
Yes, I can use home assistant fully through 4G but when I configure, the url that loads to allow access and stuff is with a redirect url to 192.168.xxxxxx so local.
I got mine to work, I think. I only see sensors for temperature and humidity from my nest thermostats, which equals to what is in the nest.docs.
The nest sensor platform lets you monitor sensors connected to your Nest devices. The SDM API supports these sensor traits:
*Temperature
* Humidity
I also have a nest doorbell, but don’t see that. Should I expect to see that as a camera? According to nest.docs camera is supported by both APIs, or is that a typo.
There is currently support for the following device types within Home Assistant:
* Binary Sensor (Legacy API Only)
* Camera (Both APIs)
* Climate (Legacy API Only)
* Sensor (Both APIs)
1 Like
Was able to complete integration up to the “Create a pull subscription” step. Does anyone have the quick and easy for that?
So, I did restart everything and used mobile 4G network. Unfortunately, it gives the exact same error:
Url was (edited for private reasons of course)https://nestservices.google.com/partnerconnections/eexxxxxxxxxxxxxxxx54c37/auth?response_type=code&client_id=xxxxxz092-7zzzzzzzzzzzzzzzzzzzm7r9gm0hqg.apps.googleusercontent.com&redirect_uri=http://192.168.68.135:8123/auth/external/callback&state=eyJ0exxxxxxxxxxxxxxxxxxxxxxx4BgDxvI&scope=https://www.googleapis.com/auth/sdm.service+https://www.googleapis.com/auth/pubsub&access_type=offline&prompt=consent
https://console.cloud.google.com/cloudpubsub/subscription/
then click +Subscription
enter any id you want with a leading letter ex. a12345
1 Like
Clear your home url smart home2 , your HA url is still visible… In your first screenshot
Have you got the internal and external addresses configured in the frontend and in configuration.yaml?
In previous posts you showed them in each but not sure if you removed it from the .yaml
I assume HA is using one of these to populate the redirect_uri parameter of the URL.
zI think I managed to authenticate, at least integrations and logs says so, but I just got a white page after I’m redirected back to home assistant.
I’m seeing this in my log:
Oct 29 20:33:49 mhub docker[22580]: 2020-10-29 20:33:49 INFO (MainThread) [homeassistant.components.nest.config_flow] Successfully authenticated
Oct 29 20:33:49 mhub docker[22580]: 2020-10-29 20:33:49 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.nest
Oct 29 20:33:49 mhub docker[22580]: 2020-10-29 20:33:49 INFO (Thread-ConsumeBidirectionalStream) [google.api_core.bidi] Thread-ConsumeBidirectionalStream exiting
Oct 29 20:33:53 mhub docker[22580]: 2020-10-29 20:33:53 INFO (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Thread-LeaseMaintainer exiting.
Oct 29 20:34:19 mhub docker[22580]: 2020-10-29 20:34:19 INFO (Thread-Heartbeater) [google.cloud.pubsub_v1.subscriber._protocol.heartbeater] Thread-Heartbeater exiting.
Oct 29 20:34:28 mhub docker[22580]: 2020-10-29 20:34:28 ERROR (MainThread) [aiohttp.server] Error handling request
Oct 29 20:34:28 mhub docker[22580]: Traceback (most recent call last):
Oct 29 20:34:28 mhub docker[22580]: File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start
Oct 29 20:34:28 mhub docker[22580]: resp = await task
Oct 29 20:34:28 mhub docker[22580]: File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 458, in _handle
Oct 29 20:34:28 mhub docker[22580]: resp = await handler(request)
Oct 29 20:34:28 mhub docker[22580]: File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
Oct 29 20:34:28 mhub docker[22580]: return await handler(request)
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 172, in forwarded_middleware
Oct 29 20:34:28 mhub docker[22580]: return await handler(request)
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
Oct 29 20:34:28 mhub docker[22580]: return await handler(request)
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
Oct 29 20:34:28 mhub docker[22580]: return await handler(request)
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
Oct 29 20:34:28 mhub docker[22580]: return await handler(request)
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
Oct 29 20:34:28 mhub docker[22580]: result = await result
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 406, in get
Oct 29 20:34:28 mhub docker[22580]: await hass.config_entries.flow.async_configure(
Oct 29 20:34:28 mhub docker[22580]: File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 146, in async_configure
Oct 29 20:34:28 mhub docker[22580]: raise UnknownFlow
Oct 29 20:34:28 mhub docker[22580]: homeassistant.data_entry_flow.UnknownFlow
I wonder if this could be related to the pubsub. To clarify, I just used the name I entered as id. Was I supposed to use the whole fqdn?
Where do you change that URL?
Right now I am receiving this error “device_id and device_name are required for private IP: http://IP:PORT/auth/external/callback”
Same here. Had to add the urls and then I was able to add the integration.
You’ll need to add your external address for the project here:
Right now in yaml but will try remove and configure in settings tomorrow. Will call back with result. Thanks so far 
Strang, mine is correct but still have an issue. I set this up as web application type.
I managed to work back through a second time and now have my thermostat temperature and humidity. In HA. Cleaning up some old projects in the Cloud console helped, although I do find the console very unintuitive.
Looking forward to seeing this develop and getting access to cameras etc in time.
1 Like