Google Assistant Linking issues (Version 0.77.2) - 405 error

[mitch]

Hi All,

I upgraded to 0.77.2 and had changed a few of my names, added new lights etc. and realised I hadn’t re-linked my Google Assistant in a while.

I followed the usual process I had done a few times before, go into Google Home app, click “un-link”, then hit “link” and now it won’t authorise against my system.

I removed my project completely from Google Projects, followed the latest instructions via: https://www.home-assistant.io/components/google_assistant/

Updated my configuration with the new project details, etc. restarted home-assistant and tried again. Still getting the same error:

405: Method Not Allowed

I was using the API_Password command to pass the password across with the information

https://hidden.duckdns.org/api/google_assistant?api_password=hidden

In my config file, I have the following for http - which is working.

http:
  # Secrets are defined in the file secrets.yaml
  api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  base_url: https://hidden.duckdns.org
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

I can also confirm that my system is remotely accessible over ssh - thinking its to do with the authentication method I am using.

Any help would be much appreciated.

[DavidFW1960 (David)]

Any problems with Google component are usually resolved by unlinking the app on your phone and then running the simulation mode again in Google Assistant (actually Google Developer Tools) and then relinking. I have done this countless times now.

[mitch]

Datamonkey, good to know I am not alone!
davidFW1960, unfortunately it is the re-linking piece that isn’t working for me. I tried running the simulation again and re-linking but I am still getting the 405 error during the linking process.

[datamonkey (Roland)]

Hi @mitch
the relinking seems to work now. At least I get a screen popping up that has “Account now linked”
but after that the Google Home app has some issue. “Can not update settings …”
And then it all starts again.
I found an old post of mine where I had the 405 error, maybe it helps you:

Setting up Google Actions for Assistant

Hi, I am very excited about this new component. I am running 0.55.2 in a docker on unRAID. Have copied the files into custom_components and the http/__ init.py __ file as well. Then I followed the instructions and created the app. It shows up for testing in Google Assistant. But when I open it I only get: 405: Method Not Allowed No logs and no errors that I can see. Any idea where to go next?

and the answer:

Setting up Google Actions for Assistant

@datamonkey Step 6.3 3. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth You probably misspelled the url, don’t forget the « auth » part at the end.

[datamonkey (Roland)]

I just found this in another post, maybe we need to add this?

Authentication Providers

homeassistant:
  auth_providers:
   - type: legacy_api_password

http:
  api_password: !secret http_password

I am not home, so can’t check if I have that or not …

[DavidFW1960 (David)]

No!

My Google Assistant Component is working without legacy. All legacy is commented out.

I think it might make a difference when you configured the component as the instructions changed. I am still using the original integration where you needed to run gactions. The newer integration seems to require the API key to be entered and if you have that integration I am sure you will require legacy_api support.

The newer integration might be simpler than the original but seems like the auth was better before.

[edif30]

Indeed. Any time a change is made to the “Draft” you must relink the account. In the past this wasn’t the case but it is now. Annoying to say the least.

[datamonkey (Roland)]

I changed from the old gactions to the new one because it did not work yesterday.
Might just try to resurect the old version …