I have found the Speedtest ping sensor to be very unreliable, reporting round trip times of 400ms or more when any other ping tester on my network reports a more reasonable ~25ms (to google.com).
Thanks for the share For speedtest it’s too short tests in all matters to be really efficient !
For ping be careful to use some reliable servers for ping (DNS servers are not done for ping answers so answer time might be moving a lot due to server charges, all the more the google ones that are using a worldwide system with bunch of servers behind a unique public IP). I have setup mine to use some main websites in my country to get a better image
Sorry for the technical explanation but to make it short and easier, just use some physical IP (less and less easy to find but it means an IP that points to a single physical server to get a real accurate measure (well at best
Sorry but you never ping a domain but a host and right don’t ping Host IP that are multi-hosts (not always easy to guess but most big services like google, facebook are always multi-hosts unless only public IP adress
nope, domain name or FQDN (Fully Qualified Domain Name) you specify is resolved to one or more IPs and your ping program uses one of these IPs for doing the ping !
Is that published by Ookla? ABB has their own ookla site too but you can only access that through the portal on ABB - there’s no ID you can use in the speedtest.net sensor for it.
ABB is my RSP. I’ve changed over to pinging their primary DNS server as I was still seeing the occasional +300ms result form pinging 8.8.8.8. So maybe the speedtest sensor was correct after all. Or maybe I was seeing multi-host issues. Or maybe ABB has a problem.
If this runs well on AAB’s DNS IP for a few days I’ll look at finding a single IP outside ABB’s network.
I just have to work out how to add another bar graph for % data used this month as I’m not on an unlimited plan and would like to compare this to the month used graph. I managed to change the total text from Unlimited to 500GB easy enough.
I’ve tried the shell command with and without quotes. Calling the service from the dev tools does nothing. I did change it to executable. The path is correct.