Speedtest.net Setup Error

Hey Guys,

Recently made a new home-assistant server on Docker. HA version 2022.3.5.
Unable to configure Speedtest.net without having this error pop out.

Screenshot (47)

The red cloud icon on the top right, indicates cloud needed. However, I’m trying to avoid setting up the cloud (for privacy reasons).

My last HA server that was version 2021.9, on a Jetson Nano… Didnt have issues when setting up Speedtest.net. (I didn’t use the cloud back then either)

Does anyone have any idea on some loop holes I can do in order to setup speedtest without the use of cloud.

Note: I have looked for bug reports about this issue, there were none.

Logs:

2022-03-20 12:21:54 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SpeedTest' for speedtestdotnet integration not ready yet: <urlopen error [Errno -3] Try again>; Retrying in background

Thanks for your time :slight_smile:

How do you expect to test your connection speed to the internet if you won’t let this integration contact the internet?

3 Likes

I didn’t have cloud in my previous HA setup yet speedtest.net was configured in ease. And worked properly. My previous set up was HA core version 2021.9, Jetson Nano.

Now its on container

It was still contacting the server to run the up/down and ping tests. That is external, so considered a cloud resource.

I’m also using the container setup on 2022.3.3.

Whatever you mean by “cloud” in your sentence, the speedtest needs internet access because, well, it measures internet speeds.

Hey Koying,

Yes I know how Speedtest works, I see the problem wasn’t that I didn’t setup the cloud. But it was that my HA has issues connecting to the internet in general.

I confirmed it in my log book which showed many connection errors from my integrations. HA is not even showing weather, updater, and HACS sensor is “unknown”. HACS has been “starting up” for 3 days now :confused:
When I enter info page, my System Health is loading indefinitely

Yet the computer where HA sits, has a great connection.

Hi,

I have the same problem, But your comment is not helpful !!

My Cloud service is connected and yet when I ping speedtest that fails from the CLI unless i use nslookup speedtest.net and then ping will reply.

So is the issue related to DNS and its ability to resolve speedtest for the App or something other?

Cleared the DNS cache and restarted the service also.

Spun up another VM in case my original VM was corrupted and same issue.

Positive comments would be appreciatted as i see this topic alot and yet nobody seems to have a fix so far.

Thanks in advance,
Tim

For example;
[core-ssh ~]$ ping speedtest .net
ping: bad address ‘speedtest .net’
[core-ssh ~]$ nslookup speedtest .net
Server: 127.0.0.11
Address: 127.0.0.11#53

Name: speedtest .net
Address: 151.101.66.219
Name: speedtest .net
Address: 151.101.194.219
Name: speedtest .net
Address: 151.101.2.219
Name: speedtest .net
Address: 151.101.130.219
Name: speedtest .net
Address: 2a04:4e42:600::731
Name: speedtest .net
Address: 2a04:4e42:200::731
Name: speedtest .net
Address: 2a04:4e42:400::731
Name: speedtest .net
Address: 2a04:4e42::731

[core-ssh ~]$ ping speedtest .net
PING speedtest .net (151.101.66.219): 56 data bytes
64 bytes from 151.101.66.219: seq=0 ttl=56 time=17.194 ms
64 bytes from 151.101.66.219: seq=1 ttl=56 time=17.090 ms
^C
— speedtest .net ping statistics —
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 17.090/17.142/17.194 ms
[core-ssh ~]$

I had to add a space between speedtest and .net to post :slight_smile:

That’s because it was not a reply to you.