-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
google_assistant.request_sync failed #20251
Comments
i receive error in webpage and this in log
tanks u |
me to |
For update entity in Google assistant I disconnect and reconnect my app google platform. |
The disconnect option is the last one for me, because everything in the routines will delete |
@pszafer Didn't work in my case |
Same problem here, stopped working, don't know really when. Using the latest 0.86
Automation yaml
|
Same here, giving the action a name also doesn't work. The only difference is that I get a 403:
|
Unlinking and linking again did the trick, not really a solution tho. Might be because of this |
Same here. Stop syncing after upgrade from 84 to 85 |
Same problem here. Is there a chance to fix it without unlinking? I don't want to setup the hole stuff again and again. :( |
@TheJulianJES Hm your right. My draft was timed out. But why do i need an active draft for sync but not for the daily usage? After reactivating the draft i recieved an forbidden error. Maybe my Auth-Token was invalid after the reactivating? Could it be? |
Also my draft was timed out. I re do a test. But now i can not resync AND use google assistant at all. 0.86.3 |
Unlink and relink google assistant in GH app restored the link. |
I have tried to unlink and relink, but now on both my wife's and my own device it won't relink again. EDIT: |
Same here. Error 403
|
Same here: I have the account linked but the "ok google sync my devices" don't work. |
Same here
|
Push failed: <Response [404]>: <title>Error 404 (Not Found)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/logos/errorpage/error_logo-150x54.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/logos/errorpage/error_logo-150x54-2x.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/logos/errorpage/error_logo-150x54-2x.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/logos/errorpage/error_logo-150x54-2x.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style>404. That’s an error. That’s all we know. |
try to reenable the simulator. for me working |
What @freemiumdev mentioned worked for me too. Go to https://console.actions.google.com/ then Test > Simulator and then run the test again which will re-enable it. |
|
Having almost the same problem. When i call google_assistant.request_sync i get 2 errors: First: and Second:
If i say "Ok Google, sync devices", i have no errors, and the devices sync ok. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I have the same log error without using google assistant... |
I'm still experiencing the issue and would love to have the issue reopened. |
Reenabling the simulator did the job for me |
For anyone that might be getting the 403 error. Try going to your API credentials, click the OAuth2.0 API edit button, and then just save it again. Don't ask me why it works but thats what I did when I just received a 403. Soon as I saved the API again (didn't change any settings), sync worked again. Weird. |
Same here
|
thanks @freemiumdev ! it works back again! ;) |
No description provided.
The text was updated successfully, but these errors were encountered: