-
Notifications
You must be signed in to change notification settings - Fork 224
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
Comments
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. |
I can't get it to work at all on fresh install... |
Same issue again after 7 days. |
Same problem. Every seven days is logged out from Google. Is there a solution for this problem? |
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: |
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. |
Where can I put the API into production? |
I would like to know as well. |
Configure the Google Assistant API as a TV Client. 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. |
Thanks! |
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?
The text was updated successfully, but these errors were encountered: