Tinkerer what port do you have your HA running on? I couldn’t get Google to show the authorise web page at first, but then I added :8123 to my duckdns address in the google url box and it worked but stuck at the unable to update in the google home app now. My next step is to change my Hass.io port to 443 and see if that works.
Call it 8123 (it’s not, but it doesn’t matter).
This means that I’ve got the port specified in the URLs where required.
I got it to work by adding my Hass port to the project.json!
1 Like
I finally got this to work after fighting with this issue for too long.
For the record, in my case the issue was that Firefox (which is my default browser on android, and is used for the webview) was logged into the wrong google account.
I opened Firefox, went to google.com, signed out, and signed in with the same google account I used to set up the action on Google. After that it linked correctly.
3 Likes
I spent FOREVER working on this, and this solved it. I was logged into the wrong account in Firefox on Android, which was my default browser.
1 Like
i got also an auth error
i cant figure out where my problem is
Had this exact same issue. except with chrome. I noticed the signin process fires up a browser and seems to just use the currently signed in user for its authentication. Of course, this will fail as the account signed into google on the browser wasn’t authenticated for the test hass app i had created. simply signing out fixed it!
good spot!!
1 Like
had exactly the same issue and your solution worked like a charm… Thanks.
Redid all the steps with HASS port updated in project.json and it just worked after that.
1 Like
Glad i managed to help someone! How are you getting on with it?
I struggled with this a week ago… The problem was that the phone used to configure the Google Home app had more than one Google accounts configured, and the account used with Google Home was different from the account assigned to Chrome (which is used for the authorization)
2 solutions are available:
-
make sure the user assigned in the GH app is the same as the user assigned in Chrome.
-
in the permission settings of your Google Action project, make sure all the Google accounts of your phone are assigned to the “Project / Editor” permission.
Cheers !
For me the problem was that somehow my port forwarding does not properly work. I set up a forwarding from 443 to 8123 but when trying to open the URL i need to add 8123.
So I configured everything in the setup and added :8123 to the end of my-ha-url. But I did not explicitly open the 8123 to 8123 Port in the Router (in the Setup this rule is called ha_test).
When I did that I was able to use the https:// URL and the 8123 without any error.
Hey Guys,
I have found a FIX,
on the actions on google console where you setup all the information under the top option “Actions” check the fulfillment URL, I had forgotten to add my home assistant port number to it.
https://[youraddress.org]:8123/api/google_assistant
The part in bold is what i forgot to add, obviously substitute your address in.
Hope this fixes things for other people too
3 Likes
For all of you guys having trouble linking your account and getting the “Could not update the setting” error.
I’ve been trying to get this to work for months and finally got it working.
Google assistant uses a browser on android to do it’s oath flow. If you have signed in on another google account in your default browser it may keep using that account even if you sign out. Every time I tried to link my account I would unknowingly attempt to link it to one of my other accounts. My solution is to download a new browser app, preferably never used on your device previously. When you go to add your test app in the google assistant it should ask you what browser app you want to use. Select the one you just downloaded. It should give you a sign in page. Sign in with your correct account and linking should succeed.
1 Like
i have the problem already, and got only 1 account on the phone and port 8123 in the project.json, is also see in the hass log, that the auth is true but 
it doesnt add anything
After pulling my hair out for a few hours, trying most of the solutions, and still not being able to add my “[test] HASS” device, I figured out my issue and thought it might help others.
First, my symptoms were exactly the same as everyone else: Unable to add the Home Control device in Google Home on Android.
I was even able to see it hitting my HASS instance with no errors:
2018-02-16 22:17:19 INFO (MainThread) [homeassistant.components.http] Serving /api/google_assistant/auth to 192.168.1.14 (auth: True)
2018-02-16 22:17:19 INFO (MainThread) [homeassistant.components.google_assistant.auth] user login in from Google Assistant
After noticing the IP was on my local network, and thinking of how OAuth works, and how forcing an “outside” connection helped others, I tried the same thing…but that didn’t work either.
I then realized my external IP may have changed, breaking my DNS. Indeed that was the cause and once I fixed that, the 3-way communication between my phone-Google-HASS worked and I was able to add the device.
(I should note that - although I was using the FQDN the entire time, DNS Host Mapping on my internal network masked the issue until I tried hitting it from outside.)
here it still does not work.
I already tried these solutions and none worked:
-
- add :8123 at the the url
-
- install a new navigator
-
- delete and create a new project
-
- client_id of all sizes and shapes
I am linking my smartphone to Google assistant. I go into the settings of Google Assistant and select Home Control. I successfully added devices if I use my Hotmail account. If I try to use my Gmail account then I get the error “Couldn’t update settings. Check your connection”.
Is this an issue specific to gmail?
I get the same on another device. Hotmail works fine and I get this error for gmail
Would like to know how to fix this as well. Its not a Gmail issue though as my actions app only works with my main Gmail…
Did you mean you got it done but want to add more users to be able to control your devices?