-
Notifications
You must be signed in to change notification settings - Fork 15
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
v2 API calls #6
Comments
Thanks for the info and input! I don't have an Android device to check them out, but you mean that all these calls are made from the Android Google Wifi App to the Wifi-unit itself? That's quite odd actually, I haven't seen or detected and v2-calls at all over here. Just to make sure, we're talking about this app: https://play.google.com/store/apps/details?id=com.google.android.apps.access.wifi.consumer&hl=en and this Google product: https://store.google.com/product/google_wifi? |
Yes, this is the same APK and same product. As I mentioned I was looking for a way to read the attached devices list. Whilst looking around inside the app I discovered the above URL's inside the class. You don't necessarily need an Android device to read what is in the APK. Visit ApkMirror and download the App Download & install JADX and you can have a look around yourself. I hope this helps :) |
Hi Mike, I bought a few Google Wifi’s, which have an old 8688.0.0 version of firmware from the test image channel (instead of the usual stable channel) and having field updateRequired = 0. It seems that some kind of write protection / restriction were in force in the test image firmware, preventing the execution of Recovery Mode when trying to flash a newer stable image firmware. Since I am not familiar with CrOS development, could you please advise the procedure for me to flash the Google Wifi to 9334.x.x steady channel image (downloaded from OnHub Recovery Utility). Below is my posting seeking for help in Google Help Forum, for your reference: https://groups.google.com/a/chromium.org/forum/m/#!topic/chromium-os-dev/98yOPE3UEBo https://productforums.google.com/forum/#!topic/googlewifi/etya6Mqeo-Y https://productforums.google.com/forum/#!topic/googlewifi/-AvwS-S-h2Q https://productforums.google.com/forum/#!topic/googlewifi/IH16V17l6J4 I also attached the status page of the Google Wifi (http://192.168.86.1/api/v1/status) below for your information, many thanks! { |
I found the line "Request had invalid authentication credentials..." To get an authorization token, I'm guessing we need to make a request to Any suggestions? |
@adriancampos Did you ever figure that out? |
Hi there, apologies for picking up on this dead issue. I've just implemented many of these API endpoints in a Node.js wrapper, which shows how to authenticate etc: https://github.com/JamesHawkinss/google-wifi-api-node Hope this proves useful. I have plans to develop a web dashboard for showing basic Google Wifi information, as I don't like having to use the mobile app. |
I am working to reverse the RPC version of this API. Authentication, as well as many of the HTTP methods, are implemented in C++ in this repository. If anyone has any information relating to the new (RPC) API version, please let me know! :) |
I wanted to see if I figure out how the Google Wifi Android App queries for attached devices - (which I couldn't find), but I did find a whole bunch of
API
calls.The Class I inspected was:
com.google.api.services.accesspoints.v2.AccessPoints
Some of these seem interesting, although I could not see what queries and args are being passed.
Maybe you might have an idea...
And one
v1
I hope it helps in some way
The text was updated successfully, but these errors were encountered: