Based on the solution from ThomDietrich i made a migration to the new official Speedtest CLI by Ookla.
Update:
I´m not using this implementation anymore before @bhomeyer made a Speedtest binding that is using the Speedtest CLI by Ookla.
Why use the Speedtest CLI by Ookla instead of the speedtest-cli by Sivel?
- The speedtest-cli by Sivel uses very old technology from Ookla that is outdated
- The maximum speed of the speedtest-cli is limited
- The speedtest-cli is heavily based on the performance of the host system
- The Speedtest CLI by Ookla exports clean JSON to make it machine readable
What functionality does the Speedtest CLI by Ookla offers?
- Fully supported by Ookla with the latest speedtest technology for best results
- Output of a timestamp instead of the own timestamp by openHAB
- Output of Jitter and Ping
- Output of Bandwidth, transferred bytes and elapsed time for Down-/Upload
- Output of the used interface with Internal/External IP, MAC Address and interface name
- Output of the used Server and location
- Output of the result id and result URL
What functionality does the integration offers?
- Execute a speedtest time based or directly
- Show summarized results of the speedtest
- Export the data to a database and visualize with Grafana
- Start the speedtest from another oH instance or from a rule
Requirements
- Uninstall the speedtest-cli if already installed
- This only applies when switching form the old speedtest-cli
-
Install the Exec Binding- we don´t need this anymore becauseexecuteCommandLineworks without the Exec binding-
Exec Binding 2.5.2: You need to add the full path to your [exec.whiteliste](Security limitations in 2.5.2 exec binding) file!
-
- Install the JSONPatch Transformation
- Install the Speedtest CLI by Ookla
- Test the speedtest before you continue
- Build the rules and test
Linux
Uninstalling old packages
Uninstall the speedtest-cli
Only applies if you had it installed before, it´s not preinstalled on Debian or raspbian
I had some problems to completely uninstall the speedtest-cli and there´s no real guide on how to uninstall.
# If you installed the speedtest-cli with apt-get
sudo apt-get remove --auto-remove speedtest-cli
# If you installed the speedtest-cli with pip
sudo pip uninstall speedtest-cli
# Check for speedtest and speedtest-cli in /usr/local/bin/ and remove them
sudo rm /usr/local/bin/speedtest
sudo rm /usr/local/bin/speedtest-cli
# Check for speedtest or speedtest-cli parts in /usr/local/lib/python2.7/dist-packages and delete them
# Depending on the python version installed
# Just to be sure
apt-get update
reboot
Uninstalling the old bintray based package if you used that before
## If migrating from prior bintray install instructions please first...
sudo rm /etc/apt/sources.list.d/speedtest.list
sudo apt-get update
sudo apt-get remove speedtest
## Other non-official binaries will conflict with Speedtest CLI
# Example how to remove using apt-get
sudo apt-get remove speedtest-cli
Install the speedtest package
Based on the official install options from Ookla.
Install on Debian Buster
curl -s https://install.speedtest.net/app/cli/install.deb.sh | sudo bash
sudo apt-get install speedtest
Install on raspbian (Buster)
You won´t be able to use the above install.deb.sh because it´s not meant for raspbian
So we need to add the ookla_speedtest-cli.list manually and modify the source info
## Check if you´re running a Buster based raspbian
cat /etc/issue
## If you get "Raspbian GNU/Linux 10" you´re running a Buster based raspbian
## Start with a refresh of the package cache
sudo apt-get update
## Install the debian keyring so official repositories will be verified
sudo apt-get install debian-archive-keyring
## Ensure the required tools are installed
sudo apt-get install curl gnupg apt-transport-https
## Now we install the GPG key that is used to sign repository metadata
curl -L https://packagecloud.io/ookla/speedtest-cli/gpgkey | sudo apt-key add -
## Create the repository file and add the following lines
sudo nano /etc/apt/sources.list.d/ookla_speedtest-cli.list
ookla_speedtest-cli.list
deb https://packagecloud.io/ookla/speedtest-cli/debian/ buster main
deb-src https://packagecloud.io/ookla/speedtest-cli/debian/ buster main
## Refresh the package cache again
sudo apt-get update
## Install the speedtest package
sudo apt-get install speedtest
## Start the speedtest as the openhab user and accept the license
speedtest -u openhab speedtest
## Start the speedtest again and make sure you get the output as JSON
speedtest -u openhab speedtest -f json
openhabian@openHAB:~ $ speedtest -f json
{"type":"result","timestamp":"2021-08-08T10:06:01Z","ping":{"jitter":0.032000000000000001,"latency":11.861000000000001},"download":{"bandwidth":39311633,"bytes":285433920,"elapsed":7305},"upload":{"bandwidth":6421818,"bytes":23171040,"elapsed":3600},"isp":"<ISP>","interface":{"internalIp":"<Your-internal-IP>","name":"eth0","macAddr":"<MAC-address>","isVpn":false,"externalIp":"<Your-external-IP>"},"server":{"id":<server-Id>,"name":"Spacken.net","location":"Hagen","country":"Germany","host":"speedtest.spacken.net","port":8080,"ip":"5.9.151.176"},"result":{"id":"<result-Id>","url":"<result-URL>"}}
Thanks @StephenGray for the modified raspbian instructions
Windows
Download and install the speedtest.exe
Thanks to @KidSquid for the Windows details!
Please download the latest Speedtest CLI from the Ookla website:
Choose or create a new folder where your Speedtest CLI runs and place the downloaded speedtest.exe in this folder.
Example: D:/Tools/Speedtest/
Please run the speedtest from your commandline and use the user that runs openHAB before continuing to the next steps!
You may need to accept the GDPR and license when running speedtest for the first time.
This should be saved after the first execution.
Test the Speedtest CLI
Just type speedtest and watch the speedtest working.
Note: If you´re not using the openhab user, please use sudo -u openhab speedtest
You may need to accept the GDPR and license when running speedtest for the first time.
This should be saved after the first execution.
[13:02:28] openhab@oH-Speedtest:/$ speedtest
Speedtest by Ookla
Server: InoHost - Düsseldorf (id = 21467)
ISP: Unitymedia
Latency: 9.34 ms (2.18 ms jitter)
Download: 578.42 Mbps (data used: 621.6 MB)
Upload: 52.74 Mbps (data used: 31.5 MB)
Packet Loss: 0.0%
Result URL: https://www.speedtest.net/result/c/###
And start another test with the argument -f json or -f json-pretty to check if everything works fine.
The result should look like the following example and not start with
{"type":"log","timestamp":"2020-03-12T16:02:56Z","message":"Error: [-2] Protocol error: Did not receive HELLO","level":"error"}
as this would stop the rule from working.
Maybe you need to define a server with -s <ID>, to get a list of nearly server just use -L
I had to test some servers to find one that gives me reliable results.
[13:04:56] openhab@oH-Speedtest:/$ speedtest -f json-pretty
{
"type": "result",
"timestamp": "2020-03-12T12:05:14Z",
"ping": {
"jitter": 0.91000000000000003,
"latency": 8.4429999999999996
},
"download": {
"bandwidth": 114371030,
"bytes": 1202757605,
"elapsed": 10815
},
"upload": {
"bandwidth": 6385055,
"bytes": 25651164,
"elapsed": 4026
},
"packetLoss": 0,
"isp": "Unitymedia",
"interface": {
"internalIp": "###",
"name": "###",
"macAddr": "###",
"isVpn": false,
"externalIp": "###"
},
"server": {
"id": 17392,
"name": "myLoc managed IT AG",
"location": "Dusseldorf",
"country": "Germany",
"host": "ookla.myloc.de",
"port": 8080,
"ip": "2001:4ba1:e001:103::1"
},
"result": {
"id": "###",
"url": "###"
}
}
General information
As you can see my speedtest changed the server between the two tests and that results in two different bandwiths for my download.
Another thing you can see is the different output format for the bandwith.
While the human-readable output shows the bandwidth as Mbps the JSON output just shows the bandwidth in bits. This output can´t be changed and we need to divide the result by 125000 to get the bandwidth in Mbps.
openHAB files
Icons
I made an icon set that fits better into my openHAB sitemaps and you´re free to use it: Download
Extract all icons to the icons folder
$OPENHAB_CONF/icons/classic/
Items (speedtest.items)
Group gSpeedtest <"speedtest">
Group gSpeedChart
String SpeedtestCharts
String SpeedtestSummary "Speedtest [%s]" <"speedtest_summary"> (gSpeedtest, gPersist)
Number SpeedtestResultPing "Ping [%.3f ms]" <"speedtest_ping"> (gSpeedtest, gSpeedChart)
Number SpeedtestResultDown "Download [%.2f Mbit/s]" <"speedtest_download"> (gSpeedtest, gSpeedChart)
Number SpeedtestResultUp "Upload [%.2f Mbit/s]" <"speedtest_upload"> (gSpeedtest, gSpeedChart)
String SpeedtestRunning "Speedtest running ... [%s]" <"speedtest_run"> (gSpeedtest)
Switch SpeedtestRerun "Manuell starten" <"speedtest_reload"> (gSpeedtest)
DateTime SpeedtestResultDate "Last Run [%1$td.%1$tm.%1$tY, %1$tH:%1$tM]" <"speedtest_date"> (gSpeedtest, gPersist)
String SpeedtestResultError "Error Message [%s]" <"speedtest_error"> (gSpeedtest, gPersist)
String SpeedtestResultImage "Bild"
Sitemap (part of my default.sitemap)
Text item=SpeedtestSummary icon="speedtest"
{
Frame label="Ergebnisse"
{
Text item=SpeedtestResultDown
Text item=SpeedtestResultUp
Text item=SpeedtestResultPing
}
Frame label="Steuerung"
{
Text item=SpeedtestResultDate
Text item=SpeedtestRunning label="Speedtest [%s]" visibility=[SpeedtestRunning != "-"]
Text item=SpeedtestResultError visibility=[SpeedtestRunning == "Fehler"]
Switch item=SpeedtestRerun mappings=[ON="Start"]
}
Frame label="Statistik"
{
Image label="Letzte Messung" item=SpeedtestResultImage
Webview url="/static/chart.html" height=12 icon="speedtest_summary"
}
}
I´m using InfluxDB+Grafana to visualize the results and have them stored to have some proofs for my ISP when the speed is far under the agreed bandwidth.
Linux rule file (speedtest.rules)
val String ruleId = "Speedtest"
val Number calc = 125000 // Converting from bits to Mbits
rule "Speedtest init"
when
System started
then
createTimer(now.plusSeconds(195))
[|
if(SpeedtestRerun.state == NULL)
{
SpeedtestRerun.postUpdate(OFF)
}
if(SpeedtestRunning.state == NULL)
{
SpeedtestRunning.postUpdate("-")
}
if(SpeedtestSummary.state == NULL || SpeedtestSummary.state == "")
{
SpeedtestSummary.postUpdate("⁉ (unbekannt)")
}
]
end
rule "Speedtest"
when
Time cron "0 0/15 * * * ?" or
Item SpeedtestRerun changed from OFF to ON or
Item SpeedtestRerun received command ON
then
//logInfo(ruleId, "--> speedtest executed...")
SpeedtestRunning.postUpdate("Messung läuft...")
// execute the script, you may have to change the path depending on your system
// Please use -f json and not -f json-pretty
// openHAB 3:
var speedtestCliOutput = executeCommandLine(Duration.ofSeconds(120), "speedtest", "-f", "json")
// openHAB 2.5:
//val speedtestExecute = "speedtest -f json"
//var speedtestCliOutput = executeCommandLine(speedtestExecute, 120*1000)
// for debugging:
// var String speedtestCliOutput = "Ping: 43.32 ms\nDownload: 21.64 Mbit/s\nUpload: 4.27 Mbit/s"
//logInfo(ruleId, "--> speedtest output:\n" + speedtestCliOutput + "\n\n")
SpeedtestRunning.postUpdate("Datenauswertung...")
// starts off with a fairly simple error check, should be enough to catch all problems I can think of
if (speedtestCliOutput.startsWith("{\"type\":\"result\",") && speedtestCliOutput.endsWith("}}"))
{
var ping = Float::parseFloat(transform("JSONPATH", "$.ping.latency", speedtestCliOutput))
SpeedtestResultPing.postUpdate(ping)
var float down = Float::parseFloat(transform("JSONPATH", "$.download.bandwidth", speedtestCliOutput))
down = (down / calc)
SpeedtestResultDown.postUpdate(down)
var float up = Float::parseFloat(transform("JSONPATH", "$.upload.bandwidth", speedtestCliOutput))
up = (up / calc)
SpeedtestResultUp.postUpdate(up)
var String url = transform("JSONPATH", "$.result.url", speedtestCliOutput)
val img = url + ".png"
SpeedtestResultImage.postUpdate(img)
SpeedtestSummary.postUpdate(String::format("ᐁ %.1f Mbit/s ᐃ %.1f Mbit/s (%.0f ms)", down, up, ping))
SpeedtestRunning.postUpdate("-")
// update timestamp for last execution
val DateTimeType ResultDate = DateTimeType.valueOf(transform("JSONPATH", "$.timestamp", speedtestCliOutput))
SpeedtestResultDate.postUpdate(ResultDate)
}
else
{
SpeedtestResultPing.postUpdate(0)
SpeedtestResultDown.postUpdate(0)
SpeedtestResultUp.postUpdate(0)
SpeedtestSummary.postUpdate("(unbekannt)")
SpeedtestRunning.postUpdate("Fehler")
logError(ruleId, "--> speedtest failed. Output:\n" + speedtestCliOutput + "\n\n")
}
SpeedtestRerun.postUpdate(OFF)
end
The executeCommandLine action has a different syntax in oH 3, see Actions.
I added the oH 3 line and only commented out the oH 2.5 line.
Windows rule file (speedtest.rules)
Please check the path on line 47 and change it to match your system.
val String ruleId = "Speedtest"
val Number calc = 125000 // Converting from bits to Mbits
rule "Speedtest init"
when
System started
then
createTimer(now.plusSeconds(195))
[|
if(SpeedtestRerun.state == NULL)
{
SpeedtestRerun.postUpdate(OFF)
}
if(SpeedtestRunning.state == NULL)
{
SpeedtestRunning.postUpdate("-")
}
if(SpeedtestSummary.state == NULL || SpeedtestSummary.state == "")
{
SpeedtestSummary.postUpdate("⁉ (unbekannt)")
}
]
end
rule "Speedtest"
when
Time cron "0 0/15 * * * ?" or
Item SpeedtestRerun changed from OFF to ON or
Item SpeedtestRerun received command ON
then
//logInfo(ruleId, "--> speedtest executed...")
SpeedtestRunning.postUpdate("Measurement in Progress...")
// execute the script, you may have to change the path depending on your system
// Please use -f json and not -f json-pretty
val speedtestExecute = "D:/Tools/Speedtest/speedtest.exe -f json"
var speedtestCliOutput = executeCommandLine(speedtestExecute, 120*1000)
// for debugging:
// var String speedtestCliOutput = "Ping: 43.32 ms\nDownload: 21.64 Mbit/s\nUpload: 4.27 Mbit/s"
//logInfo(ruleId, "--> speedtest output:\n" + speedtestCliOutput + "\n\n")
SpeedtestRunning.postUpdate("Data Analysis...")
// starts off with a fairly simple error check, should be enough to catch all problems I can think of
if (speedtestCliOutput.startsWith("{\"type\":\"result\",") && speedtestCliOutput.endsWith("}}"))
{
var ping = Float::parseFloat(transform("JSONPATH", "$.ping.latency", speedtestCliOutput))
SpeedtestResultPing.postUpdate(ping)
var float down = Float::parseFloat(transform("JSONPATH", "$.download.bandwidth", speedtestCliOutput))
down = (down / calc)
SpeedtestResultDown.postUpdate(down)
var float up = Float::parseFloat(transform("JSONPATH", "$.upload.bandwidth", speedtestCliOutput))
up = (up / calc)
SpeedtestResultUp.postUpdate(up)
var String url = transform("JSONPATH", "$.result.url", speedtestCliOutput)
val img = url + ".png"
SpeedtestResultImage.postUpdate(img)
SpeedtestSummary.postUpdate(String::format("ᐁ %.1f Mbit/s ᐃ %.1f Mbit/s (%.0f ms)", down, up, ping))
SpeedtestRunning.postUpdate("-")
// update timestamp for last execution
val DateTimeType ResultDate = DateTimeType.valueOf(transform("JSONPATH", "$.timestamp", speedtestCliOutput))
SpeedtestResultDate.postUpdate(ResultDate)
}
else
{
SpeedtestResultPing.postUpdate(0)
SpeedtestResultDown.postUpdate(0)
SpeedtestResultUp.postUpdate(0)
SpeedtestSummary.postUpdate("(unknown)")
SpeedtestRunning.postUpdate("Error")
logError(ruleId, "--> speedtest failed. Output:\n" + speedtestCliOutput + "\n\n")
}
SpeedtestRerun.postUpdate(OFF)
end
Using a different openHAB instance for the speedtest
As i´m using two different openHAB instances and build my rule to transfer the values to my main instance.
The main instance is running on a raspberry pi 4 and isn´t able to measure the full speed of my bandwidth, that´s why i created a virtual machine with raspbian running with an own Gigabit port.
My current rule:
Summary
val String ruleId = "Speedtest"
val Number calc = 125000 // Converting from bits to Mbits
// Speedtest init placeholder
rule "Speedtest"
when
//Time cron "0 0 5,13 * * ?" or
Time cron "0 0/15 * * * ?" or
Item SpeedtestRerun changed from OFF to ON or
Item SpeedtestRerun received command ON
then
//logInfo(ruleId, "--> speedtest executed...")
SpeedtestRunning.postUpdate("Messung läuft...")
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestRunning/state", "text/plain", "Messung läuft...")
// execute the script, you may have to change the path depending on your system
// oH 2.5:
//val speedtestExecute = "speedtest -f json -s 28624"
//var speedtestCliOutput = executeCommandLine(speedtestExecute, 120*1000)
// openHAB 3:
var speedtestCliOutput = executeCommandLine(Duration.ofSeconds(120), "speedtest", "-f", "json")
// for debugging:
// var String speedtestCliOutput = "Ping: 43.32 ms\nDownload: 21.64 Mbit/s\nUpload: 4.27 Mbit/s"
//logInfo(ruleId, "--> speedtest output:\n" + speedtestCliOutput + "\n\n")
SpeedtestRunning.postUpdate("Datenauswertung...")
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestRunning/state", "text/plain", "Datenauswertung...")
// starts off with a fairly simple error check, should be enough to catch all problems I can think of
if (speedtestCliOutput.startsWith("{\"type\":\"result\",") && speedtestCliOutput.endsWith("}}"))
{
var ping = Float::parseFloat(transform("JSONPATH", "$.ping.latency", speedtestCliOutput))
//logInfo(ruleId, "Ping " + ping)
SpeedtestResultPing.postUpdate(ping)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultPing/state", "text/plain", ping.toString)
var float down = Float::parseFloat(transform("JSONPATH", "$.download.bandwidth", speedtestCliOutput))
down = (down / calc)
//logInfo(ruleId, "Download " + down)
SpeedtestResultDown.postUpdate(down)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultDown/state", "text/plain", String::format("%s",down))
var float up = Float::parseFloat(transform("JSONPATH", "$.upload.bandwidth", speedtestCliOutput))
up = (up / calc)
//logInfo(ruleId, "Upload " + up)
SpeedtestResultUp.postUpdate(up)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultUp/state", "text/plain", String::format("%s",up))
var String url = transform("JSONPATH", "$.result.url", speedtestCliOutput)
val img = url + ".png"
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultImage/state", "text/plain", String::format("%s",img))
SpeedtestSummary.postUpdate(String::format("ᐁ %.1f Mbit/s ᐃ %.1f Mbit/s (%.0f ms)", down, up, ping))
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestSummary/state", "text/plain", String::format("ᐁ %.1f Mbit/s ᐃ %.1f Mbit/s (%.0f ms)", down, up, ping))
SpeedtestRunning.postUpdate("-")
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestRunning/state", "text/plain", "-")
// update timestamp for last execution
val DateTimeType ResultDate = DateTimeType.valueOf(transform("JSONPATH", "$.timestamp", speedtestCliOutput))
SpeedtestResultDate.postUpdate(ResultDate)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultDate/state", "text/plain", ResultDate.toString)
//logInfo(ruleId, "--> speedtest finished.")
}
else
{
SpeedtestResultPing.postUpdate(0)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultPing/state", "text/plain", 0)
SpeedtestResultDown.postUpdate(0)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultDown/state", "text/plain", 0)
SpeedtestResultUp.postUpdate(0)
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultUp/state", "text/plain", 0)
SpeedtestSummary.postUpdate("(unbekannt)")
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestSummary/state", "text/plain", "Error")
SpeedtestRunning.postUpdate("Fehler")
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestRunning/state", "text/plain", "Fehler")
sendHttpPutRequest("http://192.168.2.10:8080/rest/items/SpeedtestResultError/state", "text/plain", speedtestCliOutput.toString)
logError(ruleId, "--> speedtest failed. Output:\n" + speedtestCliOutput + "\n\n")
}
SpeedtestRerun.postUpdate(OFF)
end
Threshold checking
I´ve build another rule to check for user defined thresholds and send Telegram messages when the bandwidth falls under a warning or critical threshold.
The rule has three values to control the rule:
warnMsg This message will be send when the downWarn or upWarn threshold matched
critMsg This message will be send when the downCrit or upWarn threshold matched
logMsg This will build a logInfo with the threshold checks
Items
Number SpeedtestResultDownStatus "Download Status"
Number SpeedtestResultUpStatus "Upload Status"
Sitemap
Text item=SpeedtestResultDown valuecolor=[SpeedtestResultDownStatus==3="red",SpeedtestResultDownStatus==2="orange",SpeedtestResultDownStatus==1="green"]
Text item=SpeedtestResultUp valuecolor=[SpeedtestResultUpStatus==3="red",SpeedtestResultUpStatus==2="orange",SpeedtestResultUpStatus==1="green"]
Rule (attach it to the speedtest.rules from above)
val telegramAction = getActions("telegram","telegram:telegramBot:bot")
val long bot1 = <BotID>
rule "Speedtest Threshold"
when
Item SpeedtestRunning changed to "-"
then
// Options to control the warn, crit and log message
var warnMsg = 0
var critMsg = 1
var logMsg = 0
// Build the strings for logging and messaging
val StringBuilder speedThreshold = new StringBuilder
val StringBuilder speedMessage = new StringBuilder
// Messsage will be build like: xMsg1 + Download/Upload + xMsg2 + +Download/Upload speed + speedValue
// Attention! Download reduced to 100 Mbps
val critMsg1 = "Attention!\n"
val critMsg2 = "critical: "
val warnMsg1 = "Warning!\n"
val warnMsg2 = "reduced to "
val speedValue = " Mbps\n"
// Import results
var down = SpeedtestResultDown.state
var up = SpeedtestResultUp.state
// Check results for threshold
// Please insert your thresholds, i used the thresholds of my ISP
var downOk = (down >= 851)
var downWarn = (down >= 501 && down <= 850)
var downCrit = (down <= 500)
var upOk = (up >= 36)
var upWarn = (up >= 16 && up <= 35)
var upCrit = (up <= 15)
// Reduce the values to full Mbits
down = down.toString.split("\\.").get(0)
up = up.toString.split("\\.").get(0)
// Logging to check if the thresholds are working
if(logMsg == 1)
{
speedThreshold.append("Results:\n")
speedThreshold.append("Download OK: " + downOk + "\n")
speedThreshold.append("Download Warning: " + downWarn + "\n")
speedThreshold.append("Download Critical: " + downCrit + "\n")
speedThreshold.append("Upload OK: " + upOk + "\n")
speedThreshold.append("Upload Warning: " + upWarn + "\n")
speedThreshold.append("Upload Critical: " + upCrit + "\n")
logInfo(ruleId, speedThreshold.toString)
}
// Check for critital and warning threshold and build a message
if(downCrit || upCrit)
{
speedMessage.append(critMsg1)
}
else if(downWarn || upWarn)
{
speedMessage.append(warnMsg1)
}
if(downCrit)
{
speedMessage.append("Download " + critMsg2 + down + speedValue)
}
if(upCrit)
{
speedMessage.append("Upload " + critMsg2 + up + speedValue)
}
if(downWarn)
{
speedMessage.append("Download " + warnMsg2 + down + speedValue)
}
if(upWarn)
{
speedMessage.append("Upload " + warnMsg2 + up + speedValue)
}
if((downCrit || upCrit) && critMsg == 1)
{
telegramAction.sendTelegram(bot1, speedMessage.toString)
}
else if((downWarn || upWarn) && warnMsg == 1)
{
telegramAction.sendTelegram(bot1, speedMessage.toString)
}
// Update the status items for colored sitemap values
if(downOk)
{
SpeedtestResultDownStatus.postUpdate(1)
}
if(downWarn)
{
SpeedtestResultDownStatus.postUpdate(2)
}
if(downCrit)
{
SpeedtestResultDownStatus.postUpdate(3)
}
if(upOk)
{
SpeedtestResultUpStatus.postUpdate(1)
}
if(upWarn)
{
SpeedtestResultUpStatus.postUpdate(2)
}
if(upCrit)
{
SpeedtestResultUpStatus.postUpdate(3)
}
end
My Environment
- Raspberry Pi4 4GB
- Raspbian GNU/Linux 10 (buster)
- openHAB 3.1
Exec Binding 2.5.1- openjdk 11.0.12 2021-07-20 LTS
- OpenJDK Runtime Environment Zulu11.50+19-CA (build 11.0.12+7-LTS)
- OpenJDK Client VM Zulu11.50+19-CA (build 11.0.12+7-LTS, mixed mode)
Conclusion
Why did i changed from the speedtest-cli by Sivel to the official Speedtest CLI by Ookla?
Because the speedtest-cli is using old technology that isn´t able to measure my available bandwith and because the tests weren´t consistent.
Using speedtest-cli
Using Speedtest CLI by Ookla
Next steps
- I´m open for suggestions
-
Windows users to test how it worksthanks KidSquid! Use the timestamp from the json output
kind regards
Michael
