Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SpeedTest intergration won't retry after an error

See original GitHub issue

The problem

The SpeedTest integration stops working if it encounters an error and can only be recovered by doing an integration reload.

The error I see is:

Logger: homeassistant.components.speedtestdotnet
Source: helpers/update_coordinator.py:223
Integration: Speedtest.net ([documentation](https://www.home-assistant.io/integrations/speedtestdotnet), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+speedtestdotnet%22))
First occurred: 24 May 2022, 19:00:06 (1 occurrences)
Last logged: 24 May 2022, 19:00:06

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

And after that moment it will become unavailable.

What version of Home Assistant Core has the issue?

2022.5.5

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?

Logger: homeassistant.components.speedtestdotnet
Source: helpers/update_coordinator.py:223
Integration: Speedtest.net (documentation, issues)
First occurred: 24 May 2022, 19:00:06 (1 occurrences)
Last logged: 24 May 2022, 19:00:06

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

Additional information

No response

Issue Analytics

State:
Created a year ago
Reactions:7
Comments:23 (3 by maintainers)

Top GitHub Comments

5reactions

TekFancommented, Aug 25, 2022

Well, I digged a bit to find an alternative solution and found this. Works like a charm and, cherry on the cake, it finally gives accurate results where the integration always gave me inaccurate figures like ping times systematically over 60ms and beyond where the speedtest desktop app was reliably around 10ms. So for my part, I definitively trashed the integration which was useless anyway.

Now, remains to be seen how stable this cli solution will be in the coming days…

4reactions

X4LD1M0commented, Jun 16, 2022

I agree. Since it runs once an hour, why doesn’t it retry the next time. I would expect it should keep retrying every time it should run, e.g. every hour it should run.