14 UNAVAILABLE: Getting metadata from plugin failed with error: Cannot read property 'access_token' of undefined

Question

14 UNAVAILABLE: Getting metadata from plugin failed with error: Cannot read property 'access_token' of undefined

AgiHomebrigde opened this issue 4 years ago · 11 comments

AgiHomebrigde commented 4 years ago

I'm getting this error message after using assistant-rely for about a week.

"14 UNAVAILABLE: Getting metadata from plugin failed with error: Cannot read property 'access_token' of undefined"

All has been working properly up till yesterday.
I already configured the user again, but without any result

Did anyone encounter similar problems already?

frankhommers commented 3 years ago

Thanks!

Answer 1 · 2021-04-22T15:04:18.000Z

Same problem here!

Running version v3.3.2b

Answer 2 · 2021-04-24T15:18:01.000Z

I have recreated the project in Google developer control as described in https://greghesp.github.io/assistant-relay/docs/getting-started/configuration. Recreated the user in the assistant relay sandbox and all is working fine again.

So no root cause found yet but managed to get it up and running again.
Running v.3.2

Answer 3 · 2021-04-24T21:14:55.000Z

I can't get it to work at all on fresh install...

Answer 4 · 2021-05-01T07:22:07.000Z

Same issue again after 7 days.
It looks like the project in Google developer control gets inactive or non responsive after a week.
Anyone experience with this?

Answer 5 · 2021-06-27T12:03:29.000Z

Same problem. Every seven days is logged out from Google.
Then I uninstall the addon and reinstall with my credentials, but this is not comfortable. :/

Is there a solution for this problem?

Answer 6 · 2021-06-28T07:40:28.000Z

I've had the same issues for quite a while now as well. I even made an automation in Home Assistant to capture whenever the assistant relay would run into issues so I could fix it right away...

It's enough to delete the current user in assistant relay and add it again using the same client_secret*.json, but indeed doing this every week again is quite annoying.

edit:
This seems to be a google test 'feature' where for projects in the test status the token resets every 7 days:
https://developers.google.com/identity/protocols/oauth2#expiration

Answer 7 · 2021-06-28T08:50:45.000Z

Ever since I put the google assistant api into production, and reconfigured assistant relay the problem has not come back. Maybe worth a shot for some users.

Answer 8 · 2021-07-01T15:41:44.000Z

Where can I put the API into production?

Answer 9 · 2021-12-16T23:46:51.000Z

I would like to know as well.

Answer 10 · 2021-12-17T14:19:46.000Z

Configure the Google Assistant API as a TV Client.
Go to http://console.cloud.google.com and choose/find your Google Assistant API you just configured.
It will open a dashboard. On the left menu bar choose OAuth consent screen.
There you can configure the API from testing to production.
After that I reconfigured Assistant Relay (fresh install!) and never had any issues again (1+ year).

I don't know if this is the correct solution, but for me it did the trick and I never had to look back and it is still working to this date.
Running version v3.3.2b.