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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃毃 馃摙 Google home endpoints returning 403 #44
Comments
It looks like this issue started to roll out 28.06.19 around 02:24 AM (CET) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hey @ludeeus, just wanted to let you know: It's just adding another header and changing the base url. I think Home Assistant allows modules to store settings (like a token)? |
Thanks for that @rithvikvibhu :) Storing tokens in HA is not a problem. Getting the token, on the other hand, looks like it may be too much for most users (require a rooted android device) Currently I do not own any android devices, so I'm not able to test/dig myself. |
Yeah, I'm really interested in how the app first gets the token. Maybe while signing in? Might be able to make the same requests. |
Haha. That's definitely weird. Enjoy it while it lasts xD. Edit: Just checked and even mine has the same behavior. Why can't they just stay on something for a while :/ |
Have you found any solution yet? |
No, not yet, and I doubt I will anytime soon (Unless google decides to give you the option to get this token from their dev pages.) |
Google Assistant already does that and works in Home Assistant so isn't it possible to get that information with that integration? |
I don't see a token in any of the responses there. |
Ok i am no expert but there is a lot of commands you can use there and if there is too hard to get local api working maybe it's possible to get informations over that API instead. https://developers.google.com/actions/smarthome/reference/rpc/google.home.graph.v1 What i think it does is running something like this when starting the google home app or similar command to get information of all devices. https://developers.google.com/actions/smarthome/reference/rest/v1/devices/sync |
Here i found something too https://developers.google.com/actions/smarthome/concepts/local |
Since GoogleLocalApi is now working Anyway to bring this integration working ? |
That's a great news! @tyjtyj |
I have a few around @eliseomartelli I'll see if I can do some restructuring here this week to change the port and add an authorization header to the requests. |
Google has pushed an update to google home devices.
All API endpoints with the exception of
/setup/eureka_info
not returns403
(Unauthorized).This change renders this library 95% useless and if not a workaround is discovered this will be deprecated and archived.
The text was updated successfully, but these errors were encountered: