Speedtest.net removes ping server config daily

[pollocluck]

The problem

Speedtest.net does not poll with automation instruction given in the linked documentation. I disabled polling for updates for the service and the automation activates automatically every 3 hours as I set it, but the values for the ping, upload, and download sensors are "Unavailable".

This has happened to me before when my test server was randomly removed from my configuration and I added a different one. Even when I select the "auto detect" option it seemingly fixes it, but shortly after the "select test server" drop-down gets cleared and I have to select a test server again.

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

speedtest.net

Link to integration documentation on our website

https://www.home-assistant.io/integrations/speedtestdotnet/

Diagnostics information

No response

Example YAML snippet

alias: Speedtest.com
description: Updates with an internet speed test every 3 hours.
triggers:
  - trigger: time_pattern
    hours: /3
conditions: []
actions:
  - action: homeassistant.update_entity
    data:
      entity_id:
        - sensor.speedtest_download
        - sensor.speedtest_ping
        - sensor.speedtest_upload
mode: single

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

Hey there @rohankapoorcom, @engrbm87, mind taking a look at this issue as it has been labeled with an integration (speedtestdotnet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of speedtestdotnet can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign speedtestdotnet Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

speedtestdotnet documentation speedtestdotnet source _{^{(message by IssueLinks)}}

[teymur1988]

Hi there,

I have the same issue. How do we fix this. All 3 sensors become unavailable after some time, no matter which server I select.

[jcdex69]

Same issue here

[Guruleenyc]

Me too 🥺

[dsfsdbvxc]

Yup, same for me with all 3 sensors

[BufuMerlin]

Same issue!

[ianfretwell]

Same.

As if there's some automatic blocking going on with the speedtest servers if they are hit too many times from the same address perhaps ?

[amraohs]

Having the same problem. It runs into error: "Error fetching speedtestdotnet data: Unable to connect to servers to test latency." After that it seems not to be polling any more.

[Arnaud73]

Same problem here: 2025-05-17 11:33:58.683 ERROR (MainThread) [homeassistant.components.speedtestdotnet.coordinator] Error fetching speedtestdotnet data: Unable to connect to servers to test latency.

[eon123]

Same here

[narsaw]

Same issue

[BettySwallocks]

Same issue, starting looking for alternative broadband tester integrations.

[infinitytec]

Curiously, I began to notice this after I stopped having it poll for updates.

I have now re-enabled that and will see what happens.

[infinitytec]

Curiously, I began to notice this after I stopped having it poll for updates.

I have now re-enabled that and will see what happens.

Update: yes, after re-enabling its ability to poll for updates and disabling my automation that I was using to try to run it less frequently the issue goes away.

[Samay97]

Same issue

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[infinitytec]

Running a test again to see if this is still happening.

[infinitytec]

Can confirm: the issue persists.