yes, i see it , but without entities (normal in my case)
when i clicked on the intergtaion + , i needed to logon, i had the callback url (nabucasa) and i was able to approve my google hub to talk with that project api
strange, I was able to allow access to my HA via that callback URL (nabucasa) and nothing shows up on my integration page. did you add any lines to your configuration.yaml
no, only those 4 secrets, but it was before i added the UI, didnt needed to change anything else
after or before the auth process, did google ask you to allow devices ? did you also see that page?
i was asked to approve my google camera to share access with that project id , i turned it it to ON (sliders)
With the release of this new base integration in 0.117.x , can some kind soul give an idiotās guide to getting the Google side setup?
Iāve done the Device Access (I think), but am struggling with the Google Cloud side (subscriber).
Iāve been through the Google documentation and the integrations page but thereās some gaps that I just cannot seem to bridge.
Is there some more complete documentation somewhere that covers the process end to end?
6 Likes
Yes I saw that page and I had multiple sliders not sure what my issue is
I think I followed the process and got to the point where I add the integration to HA and after going to Configuration - Integration - +, I try to add Nest and I get the following Aborted popup:
Nothing in logs. I too can use the idiotās guide.
Update:
I got mine to work, had to add the following in configuration.yaml
homeassistant:
external_url: āhttp://xxx.xxx.com:8123ā
internal_url: āhttp://192.168.x.x:8123ā
Have you created your yaml also, needs to be done first before adding the UI
@pergola.fabio for now only temperature and humidity entities show up with the .117 integration as mentioned on the release notes.
Also, there is an open bug at the moment - the devices update on HA reboot however no further updates occur:
If you mean my configuration.yaml I add the following:
nest:
client_id: --my_idā
client_secret: --my_secretā
project_id: --my_idā
subscriber_id: --my_idā
The subscriber_id was confusing to me, but I think I did that right.
@martheijnen do you subscribe to Nabu Casa? If so, add your Nabu Casa address to the list of URIās eg:
https://xxx.ui.nabu.casa/config/integrations
https://xxx.ui.nabu.casa/auth/external/callback
I also added that to my external address in Configuration -> General -> External URL:
https://xxx.ui.nabu.casa/
1 Like
Unfortunately, this is not the case for me. I use my own server and domain and IIS.
I had issues getting the redirect URL to work, but what finally worked for me was this:
myurlhere.duckdns.org/auth/external/callback
Including that and https://www.google.com in my redirect URLs worked for me.
Can you share where you configured it? I cannot add / and such for example
1 Like
Was for me to test curl as described in the long steps guide by google itself (linked in the integration page)
The redirect URL is specified on the OAuth client ID. Go to https://console.cloud.google.com/apis/credentials and edit the OAuth credential to add the redirect URLs.
1 Like
Iām not sure the google.com URL is required for the redirect URL but step 2 in the Nest Device Access quick start guide has google.com as a redirect URL: https://developers.google.com/nest/device-access/authorize
It may work with a valid redirect URL substituted for google.com in the link there, Iām not sure.
Yes, the Google domain was only needed for authorising using their guide.
All you should need to get it working in HA is the https://xxx/auth/external/callback redirect URL
Great
Does anybody know how I can force home Assistant to use the public URL instead of the private up. I have it configured correctly but not use nabu casa.
Are you still getting the same error as screenshotted on this post or are you getting a new one after the various changes suggested above in several posts?