Speedtest.net integration showing wildly slower speeds than running from OS

[fender4645]

Not sure if this is the right place to post.

I’m running HA on Docker using the official docker image (v. 2021.1.3). I’ve had the Speedtest.net integration installed for a few months and I consistently see it report about 1/3 of speed that I can from the host OS. I finally got around to doing some actual tests. I ran the speedtestdotnet.speedtest service in HA and configure to run against a specific server. That pulled in a download of 352Mbps. I then immediately ran a speedtest from the host OS (Ubuntu 20.04) using the official CLI and it came back with 929Mbps. I did this a few times with similar results.

Is this expected? I understand that Docker could have a bit of networking overhead but I’m using “host” network mode and I have other containers that will download files much closer to the expected 900Mbps range.

[wmaker (Tommy Long)]

My experience as well. I now use the official ookla binary to run the actual tests.

Here are a couple of threads you may find useful:

Add the official speedtest cli

Open a terminal, change to the homeassistant user, run the program and accept the two license agreements: pi@hassbian:~ $ sudo -u homeassistant -H -s homeassistant@hassbian:/home/pi $ speedtest --f json-pretty Configuration.yaml: - platform: command_line name: Speedtest command: "speedtest --f json-pretty" value_template: "{{ value_json.download['bandwidth'] }}" command_timeout: 30 scan_interval: 1800 Result: [image]

Speedtest server ID

I’ll mention a setup I did several months ago (so I may have forgotten some of the details) which maybe rather more complicated than it should be, but something you may be able to use. In essence I use a python script that calls a speedtest binary developed by OOKLA called Speedtest CLI. The python script uses the server-id of my choosing. I call the script (using HA shell command) whenever I need it to run it using an automation. The script parses the returned values from the binary and in t…

[fender4645]

Oh nice. I didn’t think of actually connecting it to the Ookla binary. Will give that a try. Thanks!