Speedtest.net


The speedtestdotnet component uses the Speedtest.net web service to measure network bandwidth performance.

Enabling this component will automatically create the Speedtest.net Sensors for the monitored conditions (below).

By default, a speed test will be run every hour. The user can change the update frequency in the configuration by defining the scan_interval for a speed test to run.

Configuration

For the server_id check the list of available servers.

To add Speedtest.net sensors to your installation, add the following to your configuration.yaml file:

Once per hour, on the hour (default):

# Example configuration.yaml entry
speedtestdotnet:

Configuration Variables

monitored_conditions

(list)(Optional)Sensors to display in the frontend.

Default value: All keys

ping

Reaction time in ms of your connection (how fast you get a response after you’ve sent out a request).

download

The download speed (Mbit/s).

upload

The upload speed (Mbit/s).

server_id

(integer)(Optional)Specify the speed test server to perform the test against.

scan_interval

(time)(Optional)Minimum time interval between updates. Supported formats: scan_interval: 'HH:MM:SS', scan_interval: 'HH:MM' and Time period dictionary (see example below).

Default value: 60 minutes

manual

(boolean)(Optional)true or false to turn manual mode on or off. Manual mode will disable scheduled speed tests.

Default value: false

Time period dictionary example

scan_interval:
  # At least one of these must be specified:
  days: 0
  hours: 0
  minutes: 3
  seconds: 30
  milliseconds: 0

Service

Once loaded, the speedtestdotnet component will expose a service (speedtestdotnet.speedtest) that can be called to run a Speedtest.net speed test on demand. This service takes no parameters. This can be useful if you have enabled manual mode.

action:
  service: speedtestdotnet.speedtest

This component uses speedtest-cli to gather network performance data from Speedtest.net. Please be aware of the potential inconsistencies that this component may display.

When Home Assistant first starts up, the values of the speed test will show as Unknown. You can use the service speedtestdotnet.speedtest to run a manual speed test and populate the data or just wait for the next regularly scheduled test. You can turn on manual mode to disable the scheduled speed tests.

Examples

In this section, you find some real-life examples of how to use this component.

Run periodically

Every half hour of every day:

# Example configuration.yaml entry
speedtestdotnet:
  scan_interval:
    minutes: 30
  monitored_conditions:
    - ping
    - download
    - upload

Using as a trigger in an automation

# Example configuration.yaml entry
automation:
  - alias: "Internet Speed Glow Connect Great"
    trigger:
      - platform: template
        value_template: "{{ states('sensor.speedtest_download')|float >= 10 }}"
    action:
      - service: shell_command.green

  - alias: "Internet Speed Glow Connect Poor"
    trigger:
      - platform: template
        value_template: "{{ states('sensor.speedtest_download')|float < 10 }}"
    action:
      - service: shell_command.red

Notes

  • When running on Raspberry Pi, just note that the maximum speed is limited by its 100 Mbit/s LAN adapter. The Raspberry Pi 3+ models comes with a Gigabit LAN adapter which supports a maximum throughput of 300 Mbit/s.
  • Running this component can have negative effects on the system’s performance as it requires a fair amount of memory.
  • Entries under monitored_conditions only control what entities are available in Home Assistant, it does not disable the condition from running.
  • If ran frequently, this component has the ability to use a considerable amount of data. Frequent updates should be avoided on bandwidth-capped connections.
  • While running, your network capacity is fully utilized. This may have a negative effect on other devices in use the network such as gaming consoles or streaming boxes.