-
Notifications
You must be signed in to change notification settings - Fork 28
Feature request: Internet 4g/5g failover detection #145
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
Comments
I have an TL-MR6400 and also would like to have LTE status information to reboot when disconnected. |
I'd like to add a further request for this, the failover on the X50-5G can be a little frustrating, especially because the core Deco app doesn't seem to want to inform us or log it! Having HA react to and log the failover, and possibly use the LTE stats too will certainly create a much better monitoring solution than I currently have. Many Thanks, Robert |
Not the solution you guys are hopping, but I've used a docker container: Uptime Kuma to monitor my X50-5G and the other X50 AP. Another thing I've noticed, and it's quite well documented on TP-Link forums, is that LTE devices do repeated reconnections to strengthen their signal to the surrounding antennas; even our phones do the same from time to time. One way to bring some stability with a 4G/5G router is to have it restart daily (schedule reboot) - in my case every day at 4am. |
This should work with the Ipv4 connType that was added last week? |
Unfortunately it doesn't seem to have worked on X55/X50 setup, the new IPv4 always reported 4g, after the 2.5 update the new entity (replacing IPv4) Connection Type is always Unavailable. Has anyone seen different behaviour? |
I have a Deco X50 4g router and it would be great to detect when my main internet connection drops and the router use LTE as failover. It would also be great to be able to check 4G connection status.
I would like to be able to create an automation that send an alert when internet is failed over to LTE.
I don't know if the failover status is available in the API but the LTE status seems to be available with get_lte_status
Best regards from Roland
The text was updated successfully, but these errors were encountered: