API documentation and other access points

[Aypac]

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?

[MrMarble]

Hello Aypac!
Glad you like the wrapper!

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.
This wrapper was made by reversing the javascript and the requests made by the router dashboard. If the same dashboard is used with other router models it should work.

[Bobu5]

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

[MrMarble]

He is using selenium, basically he is using the same web portal that you would use but automated with python.
My implementation directly uses the same API that the web portal uses to communicate with the router by skipping the web part.

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.

[bjmc]

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.