Speedtest Binding: My Experience and Insights

Hi everyone, I wanted to share my experience with the Ookla Speedtest Binding in openHAB. I recently installed it to monitor my network performance, and I must say, it’s been a great addition to my setup!

Setup and Configuration
I followed the official documentation to configure the binding. The most important step was installing the Ookla Speedtest CLI on my system. Once that was done, setting up the binding in openHAB was straightforward. I configured it to run a speed test every hour, which provides consistent data without overwhelming my system.

Channels and Data
The variety of channels available is impressive. From download and upload speeds to ping latency and jitter, it gives a comprehensive view of my internet connection. I particularly like the resultUrl channel, which provides a direct link to the test results on Ookla’s website. This has been handy for troubleshooting with my ISP.

Automation and Rules
I created a simple rule to trigger a speed test whenever my router restarts. This helps me monitor the connection stability post-reboot. Here’s a snippet of my rule:
java
rule “Run Speedtest after Router Reboot”
when
Item Router_Status changed to “Online”
then
executeCommandLine(“/usr/bin/speedtest”)
end

This integration has been seamless and very useful.

Tips for New Users

  • Ensure the Speedtest CLI is correctly installed and accessible by the openHAB user.
  • Test the CLI manually before integrating it into the binding to avoid any issues.
  • Explore the server list feature to find the optimal test server for your location.

Questions and Discussions
Has anyone experienced any issues with the binding? I’d love to hear how others are using it creatively. For instance, how do you handle the data collected from the speed tests? Do you log it, visualize it, or use it for alerts?

Overall, I’m really satisfied with the Speedtest Binding. It’s a powerful tool for anyone looking to monitor their network performance within openHAB. Happy automating!