Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
AgiHomebrigde opened this issue Apr 18, 2021 · 11 comments

Comments

@AgiHomebrigde
Copy link

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"

image

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

Did anyone encounter similar problems already?

@Martvse
Copy link

Martvse commented Apr 22, 2021

Same problem here!
pi 4
Running version v3.3.2b

@AgiHomebrigde
Copy link
Author

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

@Milithor
Copy link

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

@AgiHomebrigde
Copy link
Author

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?

@Chappi09
Copy link

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?

@RoboMagus
Copy link

RoboMagus commented Jun 28, 2021

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

@Martvse
Copy link

Martvse commented Jun 28, 2021

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.

@Chappi09
Copy link

Chappi09 commented Jul 1, 2021

Where can I put the API into production?

@frankhommers
Copy link

I would like to know as well.

@Martvse
Copy link

Martvse commented Dec 17, 2021

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.

Knipsel

@frankhommers
Copy link

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants