Hi All,
For those that want to leverage the opportunity to see additional info regarding the ISP and Speedtest Host I have a working example that you can use freely. Just ad the the sections below in your environment.
You can (but not need to) target a specific server as outlined in this tutorial in the above posts. I personally use a nearby server and edited that call in the speedtest.rules file:
val speedtestExecute = "speedtest -f json -s 13883"
Frame label="Speedtest Provider Details"
{
Text item=SpeedtestISP
Text item=SpeedtestId
Text item=SpeedtestName
Text item=SpeedtestLocation
Text item=SpeedtestCountry
Text item=SpeedtestHost
}
Rules (speedtest.rules)
Just use this in the main section of your speedtest.rules file
Hej @Bredmich - really nice solution! Congrats.
As you seem to have more knowledge about speedtests a question concerning the principle difference between the solutions.
The network binding offers as well a speedtest. Here one can define the speedtest server to use (e.g. the anycasted server adress http://speedtest.tele2.net) , as well as the file to use (as e.g. described here by Tele2. I tried to benchmark the use of the network binding against the use of the Speedtest by Ookla. I get the same results, when both use the same server (and not the one, which is set by default in the network binding)
Do you think there is a principle difference in the two approaches (except, that the Speedtest CLI results are way more detailed) ?
Hi Martin,
i´m afraid i can´t answer that from a technical point of view.
A Speedtest i basically just a down-/upload that is measured.
I don´t think that there´s a difference between a speedtest measured by the network-binding or with the Speedtest CLI.
But that´s just my point of view and maybe someone has more knowledge about Speedtests.
i´m sorry but i can´t tell you what this error means, cause it´s coming from the Speedtest CLI and not openHAB.
Whats your value for val speedtestExecute = "speedtest -f json"?
It seems like the speedtest itself runs fine but you´re getting the typ:log with the message [11] Cannot read from socket: Resource temporarily unavailable right before the correct output.
Maybe you should try to contact Ookla directly: support@ookla.com
Thanks for your scripts
I have also migrated my previous scripts to this version. Now the speedtests are constant and much faster with the previous speedtest_cli…
I thought that my ISP is not so great that’s why I get these variations in speed, but it turns out not
Ps.: Now I will have to migrate this rule to Python (NGRE)…
I have installed before Sivel’s implementation on my Raspberry Pi and found performance issues so I upgraded to a Raspberry Pi 2 and obtained better results. Recently I started having problems with servers not being available even though they were working on speedtest.net, so I found out about Ookla’s implementation.
I’m curious about Speedtest CLI by Ookla. Does anybody know if this implementation is proprietary software? Because I already verified way less processing required by Ookla’s implementation on my Raspberry Pi 2, but I could not find a repository in Ookla’s GitHub Team related to the cli.
Just wanted to update @Bredmich that I have added a small enhancement to your excellent implementation of the OH speed test.
With my whole family at home all on the internet, using Zoom, Microsoft Teams, and other video conferencing platforms speed was always a concern. In fact when other members experienced video issues they were always blaming the internet bandwidth which I was keeping an eye on thanks to your great work.
So if I was on a call and they wanted to know how our internet connection was performing they were a bit out of luck as they don’t typically interact with OH via the GUI…only through Alexa!
So I created a routine in Node-Red that pulls the speed values from OH and makes them available via a question to an Amazon Echo Device.
Human - “Alexa, what is the internet speed at the house?”
Alexa - " "Looks like the download speed is 956 Mega Bits, The upload speed is 42 Mega Bits, and the packet ping time is 5 Milliseconds"
It works flawlessly and with all the traffic going on in the house it makes it a bit easier on me that the fam can do a bit of investigating before they call on me to assist.
Happy to share the flow with any one who wants/needs it.
Hey @sujitrp maybe a bit late for an anwer, but i had this problem too and it was on side of the speedtest provider ookla.
I have reported it and they have fixed that very quick.
Just if someone is facing similiar problems a report to the test provider should be a valid solution.
Sorry i just got back to the exec binding version without whitelisting because it wasn´t working as excepted in the first release.
Maybe i should give it another try…
I would guess this is an error with apt-key as the key isn´t from Ookla.
This key is also used for other packages.
Try to contact them over twitter: https://twitter.com/Speedtest