Google assistant not linking since 0.80

Configuration
1

I followed the instructions to set the new authentication for Google Assistant, however I cannot get it to work. Started over from scratch, but with no result.

When trying to link the test app through the google assistant app (IOS) I first get the login screen, and when I complete the credentials I get the message “accounts now linked”. When I then click “ready” the app gives the message “something went wrong. please try again”.

Im using the caddy addon of bestlibre, maybe this has something to do with it? But I can reach my HA.

On 0.80 I got the following in my system log:

XXX.XX.XXX.XX - - [16/Oct/2018:18:50:08 +0200] “GET /auth/authorize?response_type=code&client_id=https://oauth-redirect.googleusercontent.com/&redirect_uri=https://oauth-redirect.googleusercontent.com/r/XXXXXXXXX&scope=email+name&state=LONG_RANDOM_STRING HTTP/2.0” 302 0
XXX.XX.XXX.XX - - [16/Oct/2018:18:50:08 +0200] “GET /frontend_latest/authorize.html?response_type=code&client_id=https://oauth-redirect.googleusercontent.com/&redirect_uri=https://oauth-redirect.googleusercontent.com/r/XXXXXXXXX&scope=email+name&state=EVEN_LONGER_RANDOM_STRING HTTP/2.0” 200 1877
XXX.XX.XXX.XX - - [16/Oct/2018:18:50:08 +0200] “GET /auth/providers HTTP/2.0” 200 96
XXX.XX.XXX.XX - - [16/Oct/2018:18:50:09 +0200] “POST /auth/login_flow HTTP/2.0” 200 170
XXX.XX.XXX.XX - - [16/Oct/2018:18:51:18 +0200] “GET /api/states HTTP/1.1” 200 12999
XXX.XX.XXX.XX - - [16/Oct/2018:18:51:57 +0200] “POST /auth/login_flow/XXXXXXXXXXXXXXXXXXXXX HTTP/2.0” 200 181
XX.XXX.XX.XXX - - [16/Oct/2018:18:51:58 +0200] “POST /auth/token HTTP/1.1” 200 316

After updating to 0.80.1 I don’t get this message anymore.

Also tried to keep the configuration as simple as possible by only adding the project id and api key. Also without result.

What can I try next?

2

I’m in the same boat. Initially it was because I had multiple users and some still logged in to the old ‘app’. Last night it was all working and this morning nothing. It keeps saying ‘:ooks like XXXXX is unvailable’.

Oddly enough it works perfect from the phone but not my google home.

3

Did you guys manage to get this working? I’m struggling too, updated today to 0.80.3 and I they don’t want to talk. When I link my app through the assistant app it does the oauth redirect, says ‘accounts now linked’, but the assistant app never updates to reflect this. I can repeat this step multiple times with no luck.

4

I tried migrating but it just wouldn’t work so I started over from scratch but found an issue with the app/project linking. If I linked the new project things wouldn’t work until every device still attached to the old project unlinked the old project. Eventually I managed to get everything working and now it’s all as it should be.

5

Sorry, when you say ‘every device attached to the old project’ - what do you mean by every device? I had GA set up, tried migrating to the oauth auth method which didn’t work so I tried starting over. I’ve removed the old project although it’s in the halfway-deleted state to give you time to recover it. Technically it’s gone though, and neither of them show as linked in the GA app.

6

Yes i did. For me the trick was to reload/refresh the app in the simulator of Google actions. Difficult to explain, but if you open the simulator in Google actiins, just above the language, there is an option to change the version. After I did this the account linked fine and all devices were added.

7

I have multiple users using my GA instance. Until the old one was removed from all of those accounts I couldn’t get anything to work.

8

I can’t get it to work, no matter what.

@Try2Fly Do you have multiple version on the list or only “VERSION - Draft”?

@forsquirel What do you exactly mean by “Until the old one was removed from all of those accounts”?

9

Ok, I solved it. Apparently old instance of HA (0.7x) was running in the background. Once I’ve killed it and started 0.81 again it finally worked.

10

I had this same issue. It would display a message indicating that the app is authorized but would not redirect to the Google Assistant app and complete the action. I tried to link another app (Harmony this time) and it would do the same thing. I realized that I am not using Chrome as my default browser on Android. Once I set the default browser to Chrome then everything worked just fine.

11

I still couldn’t get this to work. Like everyone else, I tried to migrate from 0.79. The reason I updated was that Google Assistant kept saying it couldn’t sync my device. But the commands worked fine on the old version.

So after updating to 0.81.2 I did the steps to migrate. That resulted in “Account linking failed” message in the pop up browser window when trying to add the app from Google Home or Google Assistant. I tried with iOS and Android. With Safari and on Android with Chrome, Firefox and the default Android browser. Same response. Caches cleared and checked I was logged in to the right account.

So I tried to start the Google integration from scratch. Deleted the old app and created a new one. Now I can see two entries of “[test] my test app”. Both redirect me to the HA login and both give the “Account linking failed” followed by a redirect to Google Home/Assistant and the error response. “Something went wrong. Try again.”

12

I also had multiple test apps. Only one of them worked. But it did tell me the account was successfully linked. So it looks like one of your URLs is incorrect.
Make sure all links to your system are correct, also the one under build > actions> action.devices.
And then update the version in the simulator. That worked for me.

13

There is breaking change for google assistant since ha 0.80

Check your new setting according to this page. https://www.home-assistant.io/components/google_assistant/

14

Same results here,
After upgrading HA from 0.77 to 0.81, reconfigured google assistant settings.
When trying to re-link, I can enter HA credentials but the google assistant skips the room assignment screen, and goes back to devices screen.
No HA device is present.

15

Just keep trying it. Eventually it will work. Again I think this is a Google Home app sync/issue.

16

Have tried it at least ten times. Same result. Will keep trying.
With the old auth it worked like a charm.

17

I have disabled the expose_by_default setting in configuration.yaml
First try relinking, gives error
After a couple of minutes the exposed devices are there!? Very strange!

18

After upgrading the google home app it seems to be more responsive.
They have also added the option to give other housemates access to the devices configured in the app.

19

Finally got this solved.
The problem was my self signed certificates. As soon as I started using Let’s Encrypt the problems went away.