I’ve got the tplink_lte integration (this one: https://www.home-assistant.io/integrations/tplink_lte/) working in order to send multiple SMS with preformatted texts and recipients via my TP-link Archer MR200 router (firmware version 1.9.00.9.1 v0001.0) After setup and reboot, it works like a charm for 10 minutes
In the logs, I can see the initial connection takes place:
2019-12-03 21:06:00 INFO (MainThread) [tp_connected.tp_connected] http://192.168.1.1/cgi/login
2019-12-03 21:06:01 INFO (MainThread) [tp_connected.tp_connected] Token url http://192.168.1.1/
2019-12-03 21:06:01 WARNING (MainThread) [homeassistant.components.tplink_lte] Connected to 192.168.1.1
Sadly, I cannot detect the router disconnecting in the logs. I think the router closes down idle connections. When I log in the router manually, the tplink_lte integration stops working from that moment on (only one user can access the router at a time). The only solution I have to be sure of a connection with the router is to restart Hass.io (v 0.102.3 running on a Pi4).
If I could find a way to renew the tplink_lte connection to the router without restarting Home Assistant, I would be well on my way!
In the end, I’m doing all this because I want to create an automation that sends an SMS to my carrier that allows for new bandwidth after a 5GB limit. The uPnP integration is logging traffic nicely, even when the tplink_lte integration stops functioning.
Currently, I’m working around the above stated problem with a second instance of Home Assistant on my NAS. I connected the two instances via websocket using remote_homeassistant (https://github.com/lukas-hetzenecker/home-assistant-remote).
If I’m close on exceeding my data limit, the RPi tells my NAS to restart Home Assistant on the NAS. When restarted, my RPi receives positive feedback and pushes the command for sending the actual SMS via the NAS and reset my utility meter.
All of this actually works, (for a day now) but because of the workaround I’m getting some weird errors which I want to address first. I’m also not sure on how stable this solution is.
With you guys you mean me talking to myself i guess
We moved to a new home which has optical fiber, never used the TP-link archer since… I looked into the open issues on the Github page of TP-Link LTE but here’s only people stuck like us. Interestingly, someone responded to this github issue yesterday.
A workaround that was not available to me at the time was reloading an integration with an automation. Post #37 on this thread shows how you might achieve this reloading of an integration.
for 10 minutes 
