-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
API documentation and other access points #3
Comments
Hello Aypac! Unfortunately I have not found any API information, the only thing I have found have been firmware images to decompile in which I did not find much information. |
probably off-topic but, any chance that the API that this guy has stumbled upon is the same api that Deco use? https://github.com/fazalfarhan01/TP-Link-Router-Controller |
He is using selenium, basically he is using the same web portal that you would use but automated with python. I doubt that it will work the same, since the web interface of the router will have different options to the Deco, it is possible that my implementation could work changing the calls for the corresponding ones of that model. |
Rather than de-compiling firmware binaries, it might be possible to glean information looking at the source releases https://www.tp-link.com/us/support/gpl-code/ and/or sniffing network traffic from the Deco mobile app using something like wireshark. |
Thanks for this wrapper!
I could not find any reference to the API used and if it is applicable to any other access point than the M4. Do you have any information on either of those points?
The text was updated successfully, but these errors were encountered: