Speedtest integration wont work

Third party integrations
3

I have the same error since this morning

speedtest --json --server 29238 --share
Traceback (most recent call last):
File “/usr/bin/speedtest”, line 11, in
load_entry_point(‘speedtest-cli==2.0.0’, ‘console_scripts’, ‘speedtest’)()
File “/usr/lib/python3/dist-packages/speedtest.py”, line 1832, in main
shell()
File “/usr/lib/python3/dist-packages/speedtest.py”, line 1729, in shell
secure=args.secure
File “/usr/lib/python3/dist-packages/speedtest.py”, line 1009, in init
self.get_config()
File “/usr/lib/python3/dist-packages/speedtest.py”, line 1081, in get_config
map(int, server_config[‘ignoreids’].split(’,’))
ValueError: invalid literal for int() with base 10: ‘’

4

Where do you get this options screen? After installing the integration, I don’t get any options at all.

5

Same here and after installation if I open the options there’s text

Error
Config flow could not be loaded
6

Same issue here. This integration worked well until few days ago. I removed and reinstalled then now I lost all its sensors and it cannot recreate them.

7

its a known issue, there is an issue with upstream speedtest-cli componenet as ookla have changed something

ValueError: invalid literal for int() with base 10: ‘’ by ligrevx · Pull Request #769 · sivel/speedtest-cli (github.com)

1 Like
8

For me this odd behaviour started with 2021.2 or 3
But now it’s totally dead…
Well, maybe I’ll test the Fast.com integration…

9

Thanks a lot.
I did the change like explained in this post and it’s working now

Change line where the error is located by this one:

map(int, [server_no for server_no in server_config[‘ignoreids’].split(’,’) if server_no])

10

just bear in mind if you upgrade it will get wiped till fixed in the upstream component, unless you copy down as a custom component

11

I have been getting continual errors with this anyway for a few weeks now anyway before the total failure today so I’ve switched to running it on the Debian host using the ookla cli. No failures anymore so I’m thinking I might just stick with that going forward.

12

That maybe the way to go, the speedtest-cli hasn’t had any updates since 2019

1 Like
13

I’ve logged an issue on Github to hopefully get someone to look at this - Speedtest integration no longer works. · Issue #48853 · home-assistant/core (github.com)

14

there is already one
SpeedTest throws unhandled exception in 2021.4.0 · Issue #48803 · home-assistant/core (github.com)

15

Thanks - closed mine and referred to that one.

16

The upstream component has just been fixed and a PR to fix HA has just been submitted, should be in next ha update.

2 Likes
17

I just updated to 2021.4.0 and mine is broken too now.
image
I will have to wait for PR to filter through to next update.

This is a problem with today’s interconnected world.
The domino effect!

18

The issue wasnt with the update, it would have happened after you had restarted on previous version, it was just a coincidence that the issue appeared around same time as HA released new version.

2021.4.1 has been released and has the updated upstream component referenced so will fix the issue

19

Thanks for the heads up. Yep mine works now after 2021.4.1 loaded

20

2021.4.1 also fixed it for me.

21

I’ve just updated to 2021.4.4 and works for me now :slight_smile:

22

Is SpeedTest having drinking problems? Feels like it works 1/2 the time and doesn’t have the time. Running 2021.4.4 and it’s been a hot-mess of inconsistency for the past few weeks. Get it together SpeedTest!