Speedtest no works - Entity unavailable

[ninjax95]

The problem

Hello, I have a problem, the data is not displayed, I uninstalled and reinstalled several times but it does not work.

In the logs, I have this message: [homeassistant.components.speedtestdotnet] Finished fetching speedtestdotnet data in 0.340 seconds (success: False).

Here is my setup: Home Assistant 2022.10.3 Supervisor 2022.10.0 Operating System 9.2 UI: 20221010.0 - latest

What version of Home Assistant Core has the issue?

2022.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Speedtest

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

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! _{^{(message by CodeOwnersMention)}}

---

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

[thecode]

It might be a DNS issue, what happens if you run the test in your browser? https://www.speedtest.net/

[FranckH250]

Same Issue for me The test is working in a browser

Home Assistant 2022.10.3 Supervisor 2022.10.0 Operating System 9.2 Interface utilisateur : 20221010.0 - latest

[jurasjo]

I sometimes have similar issue. I have set up an automation which reloads config for Speedtest integration after status changes to "unavailable" for over 1 minute. You can try this way, maybe it will work for you as well. alias: Speedtest reload config description: "" trigger:

• platform: state entity_id:
  • sensor.speedtest_download to: unavailable for: hours: 0 minutes: 1 seconds: 0 condition: [] action:
• service: homeassistant.reload_config_entry data: {} target: device_id: 25ee36fd96abcb63d865ccacd3dd961c mode: single ``

[nurikk]

Same issue here

[nurikk]

Removing it and installing it again solved the problem

[ninjax95]

It might be a DNS issue, what happens if you run the test in your browser? https://www.speedtest.net/

It's works in an other browser but entity not works in HA.

[ninjax95]

Removing it and installing it again solved the problem

No works for me, i tried 3 times

[metbril]

I sometimes have similar issue. I have set up an automation which reloads config for Speedtest integration after status changes to "unavailable" for over 1 minute.

Actually, you don't need to reload the config, but you can also just update the download entity to manually run a speedtest. It will usually continue running after that. This is what I do:

alias: Force speedtest
description: >-
  Force speedtest when download unavailable for 1 minute. Fix for accidental
  failure of the integration.
trigger:
  - platform: state
    entity_id:
      - sensor.speedtest_download
    to: unavailable
    for:
      hours: 0
      minutes: 1
      seconds: 0
condition: []
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id: sensor.speedtest_download
mode: single

[metbril]

And possibly a duplicate of #62172?

[jurasjo]

I can give it a try,

[ninjax95]

sensor.speedtest_download

Don't work for me, entity always unavailable

[Kaszys]

Same problem here

[metbril]

@ninjax95 what not? There are 2 workarounds. Both?

[bacquy]

Same problem here

[ninjax95]

There are 2 workarounds

Certainly two workarounds that do not work for me! And I could have thought that it's me who makes things wrong but I'm not the only one... I bring clarifications, the speednet addon does not work from the start, at no time do the entities become available.

[Claudio1L]

same here

[robotek87]

I sometimes have similar issue. I have set up an automation which reloads config for Speedtest integration after status changes to "unavailable" for over 1 minute.

Actually, you don't need to reload the config, but you can also just update the download entity to manually run a speedtest. It will usually continue running after that. This is what I do:

alias: Force speedtest
description: >-
  Force speedtest when download unavailable for 1 minute. Fix for accidental
  failure of the integration.
trigger:
  - platform: state
    entity_id:
      - sensor.speedtest_download
    to: unavailable
    for:
      hours: 0
      minutes: 1
      seconds: 0
condition: []
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id: sensor.speedtest_download
mode: single

Perfect! Thank you :)

[falphonso]

Homeassistant : 2022.10.5 Supervisor 2022.10.0 Operating System 9.3 Interface utilisateur : 20221010.0 - latest

Same error. Tried to reload the Speedtest.net integration config with the tip given in some comments above, but with no luck. The 3 entities created stay unavailable. Tried to delete the integration, restart HA, reconfigure the integration with no luck either. Opened the website in my browser in my home network, fqdn resolves in my home network. Pinged www.speedtest.net from the HA terminal console, it was successfull too.

But I have this error message in the logs :

Logger: homeassistant.components.speedtestdotnet Source: helpers/update_coordinator.py:182 Integration: Speedtest.net (documentation, issues) First occurred: 21:40:31 (1 occurrences) Last logged: 21:40:31

Error fetching speedtestdotnet data: Unable to connect to servers to test latency.

[sylvaindd]

I have the same problem, I tried debugging it.

When I use speedtest-cli (python) I get an error on https://www.speedtest.net/speedtest-servers-static.php?threads=8&x=1667417452426.0

I tried accessing this URL from multiple IPs in France, none worked. I tried from a server in Germany and it worked.

The Speedtest Windows App, web browser app and official cli work fine.

So I guess there is an issue with their infrastructure depending on the location.

They must have changed the "new cli" not to use this URL anymore.

[DarKOrange75]

Sale issue for me this integration has stopped working weeks ago…

[browetd]

Speedtest is working in my instance located in Belgium but is not working for my instance in France... What is very strange is that in France, I cannot choose a server to target, I only have "Auto-Detect" as option while in Belgium I have a menu to choose a specific server if I want... Should be a bug linked with specific locations... Just to complete my comment: on both locations I can use "speedtest" in a browser without any issues... so the problem is within HA...

I have the following error message in the logs from France:

[homeassistant.components.speedtestdotnet] Error fetching speedtestdotnet data: Unable to connect to servers to test latency.

[anthosz]

I have the same problem, I tried debugging it.

When I use speedtest-cli (python) I get an error on https://www.speedtest.net/speedtest-servers-static.php?threads=8&x=1667417452426.0

I tried accessing this URL from multiple IPs in France, none worked. I tried from a server in Germany and it worked.

The Speedtest Windows App, web browser app and official cli work fine.

So I guess there is an issue with their infrastructure depending on the location.

They must have changed the "new cli" not to use this URL anymore.

Same issue, did you try to contact them in the doubt?

[sylvaindd]

I have the same problem, I tried debugging it. When I use speedtest-cli (python) I get an error on https://www.speedtest.net/speedtest-servers-static.php?threads=8&x=1667417452426.0 I tried accessing this URL from multiple IPs in France, none worked. I tried from a server in Germany and it worked. The Speedtest Windows App, web browser app and official cli work fine. So I guess there is an issue with their infrastructure depending on the location. They must have changed the "new cli" not to use this URL anymore.

Same issue, did you try to contact them in the doubt?

I did, but didn't get any answer...

[ronniegarcia]

I have the same problem here (France). Anyway the server list endpoint may have changed to : https://www.speedtest.net/api/js/servers

Source : https://twitter.com/blogdju/status/1568639600498704386 (french)

[kernelkraut]

Entity is available for about 20 minutes after a reboot... Then it becomes "Unavailable. The only way to keep it "available" is to keep the automatic polling enabled. Disabling the automatic polling results in "Unavailable". I've removed and reinstalled it, i've created automations to reload it, nothing works.

I'm not sure who thought it was a great idea to remove the option to configure polling and make it run every hour?

[ninjax95]

Hi, Does anyone have a solution, it's still relevant

Thanks

[anthosz]

Hi, Does anyone have a solution, it's still relevant

Thanks

Disabled on my side, seem's not maintained anymore.. (down since more 6 month on FR servers)

[Timv1]

I have the same problem with the sensors being unavailabe. I have a script that updates the speed everyday at 11:30. If the script runs by itself it will finisih in les than 1 second. Finished at 20 februari 2023 om 11:30:01 (runtime: 0.74 seconds)

When i give a manual run trigger of the same script it does update the speedtest entitiys. and the script runs longer. Finished at 20 februari 2023 om 15:29:16 (runtime: 10.01 seconds)

So it works with manual trigger, not automatic once every day.

`alias: Speedtest pollling description: "" trigger:

• platform: time at: "11:30:00" condition: [] action:
• service: homeassistant.update_entity target: entity_id:
  • sensor.speedtest_download
  • sensor.speedtest_upload data: {} mode: single `

[sylvaindd]

Just tried with this PR in local, and it works ! I guess this could be manually imported into HA Docker container while waiting on a release.

[browetd]

Hi, Does anyone have a solution, it's still relevant Thanks

Disabled on my side, seem's not maintained anymore.. (down since more 6 month on FR servers)

I have the same issue: speedtest integration not working in France for months (entities unavailable) but working fine in Belgium (I have two HA instances: same versions (Core, OS and Supervisor) on ProxMox, same hardware, two identical environments)... I tried different programs from Github using speedtest on a local Unix computer, but it seems they are all having the same issue for France: they cannot reach server(s)... Than I installed the program directly from the Speedtest website and in this case it is working fine... Therefore and as I am using Icinga2 as well, I moved the speedtest from HA (I removed the integration) to Icinga2, I wrote a quick shell program to test the internet speed and I am sending back the data to HA via MQTT into the same entities and it is working perfectly well... So the problem is maybe an obsolete speedtest version in HA...

[DarKOrange75]

Hi, Does anyone have a solution, it's still relevant

Thanks

Hi, I removed this integration as it is not working now for months… Instead I installed Speedtest-cli and it works flawlessly! Follow this tutorial (in French)

https://forum.hacf.fr/t/integrer-speedtest-cli-officielle-a-home-assistant/15436

Enjoy!

[bucklevision]

I can confirm this is very odd, the integration runs largely OK if left to 1hr updates, but if I push it to 15 minute updates, the update entity runs (0.34 seconds) but does not update any variables, or error. As soon as one of these updates returns a null, the entity becomes unavailable. The history shows the intermittent problem.

[Falcon4Tech]

I think the problem might be that everyone is running the test at the same time (synchronizing the clock and running on the hour). When I moved the test for several dozen seconds forward, the problem disappeared.

[Hagendaz989]

It will run for me until I select a specific server, but if left on auto select it runs like it should but speeds are way off.

[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.