Error - No servers defined

[MrSuicideParrot]

Even when the server is defined, the speedtest addon stopped working.

s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun speedtest (no readiness notification)
s6-rc: info: service legacy-services successfully started
[14:00:37] INFO: Starting speed test
{"type":"log","timestamp":"2023-06-24T13:00:37Z","message":"Configuration - No servers defined (NoServersException)","level":"error"}
[14:00:37] DEBUG: Speedtest output: 
./run: line 46: *8/10000: syntax error: operand expected (error token is "*8/10000")
./run: line 47: *8/10000: syntax error: operand expected (error token is "*8/10000")
[14:00:38] INFO: --------- Speed test ended ---------
[14:00:38] INFO: Download measured: 
[14:00:38] INFO: Upload: 
[14:00:38] INFO: Ping: 
[14:00:38] INFO: --------- ---------
./run: line 26: 4: unbound variable
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[JOHLC]

I am seeing the same,

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun speedtest (no readiness notification)
s6-rc: info: service legacy-services successfully started
[22:29:27] INFO: Starting speed test
{"type":"log","timestamp":"2023-07-11T02:29:27Z","message":"Configuration - No servers defined (NoServersException)","level":"error"}
[22:29:27] DEBUG: Speedtest output: 
./run: line 46: *8/10000: syntax error: operand expected (error token is "*8/10000")
./run: line 47: *8/10000: syntax error: operand expected (error token is "*8/10000")
[22:29:27] INFO: --------- Speed test ended ---------
[22:29:27] INFO: Download measured: 
[22:29:27] INFO: Upload: 
[22:29:27] INFO: Ping: 
[22:29:27] INFO: --------- ---------
./run: line 26: 4: unbound variable
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I tried a reinstall and that seemed to resolve.

[MrSuicideParrot]

I haven't been able to figure out the reason behind this bug. In my case I was using a server that was decommissioned. When I changed to other Speedtest server everything went back to normal.
Are you specifying a Speedtest server? (If yes, could you share with me to recreate this bug) Or you are trying to run without a server?

[pove]

Hey @MrSuicideParrot, awesome add-on! It's much more accurate than the official integration, by far. I noticed that the best results are specifying the server id, but what would happen if the server goes down in the future? How can I get an alert or notification if something goes wrong? I have an automation that checks the speed every morning just as an historic that I check from while to while.

[MrSuicideParrot]

You can create an automation that notifies you if the sensor was not updated during a time window bigger than the one you configure to run periodically. If the server goes down, the addon will fail and not update the measurements.

Here is an example of an automation that does exactly that:

alias: Speedtest haven't been updated notification 
description: ""
trigger:
  - platform: template
    value_template: >-
      {{ as_timestamp( utcnow() ) | int > as_timestamp(
      states.sensor.speedtest_ping.last_changed ) | int + 34*60 }}
condition: []
action:
  - service: notify.home_assistant
    data:
      message: Speed test measurements haven't been updated for 4 hours.
mode: single

Don't forget to configure your own notification service.