Any other of you where the speedtest not working after todays update ?
I keep getting
Entity not available: sensor.speedtest_download
Entity not available: sensor.speedtest_upload
Entity not available: sensor.speedtest_ping
Any other of you where the speedtest not working after todays update ?
I keep getting
Entity not available: sensor.speedtest_download
Entity not available: sensor.speedtest_upload
Entity not available: sensor.speedtest_ping
Maybe because of the breaking change
https://www.home-assistant.io/blog/2019/02/20/release-88/
Same here. I’ve seen the breaking change and updated my config accordingly, but this is what I get in the log:
2019-02-21 12:56:25 INFO (MainThread) [homeassistant.loader] Loaded speedtestdotnet from homeassistant.components.speedtestdotnet
2019-02-21 12:56:25 INFO (MainThread) [homeassistant.setup] Setting up speedtestdotnet
2019-02-21 12:56:25 ERROR (MainThread) [homeassistant.setup] Error during setup of component speedtestdotnet
Traceback (most recent call last):
File "/opt/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py", line 151, in _async_setup_component
hass, processed_config)
File "/opt/homeassistant/lib/python3.5/site-packages/homeassistant/components/speedtestdotnet/__init__.py", line 53, in async_setup
conf = config[DOMAIN]
KeyError: 'speedtestdotnet' ```
The error that @Diginorse mentioned is just the result then.
The release notes say;
Split out speedtest into a component and a sensor platform
The new schedule format is annoying. Makes it difficult to only run at peak times. Guess I’ll have to call it manually from an automation with multiple time triggers.
Old way was much easier:
- platform: speedtest
minute: 2
hour:
- 18
- 19
- 20
- 21
- 22
- 23
monitored_conditions:
- ping
- download
- upload
I solved the problem myself … I am using a separate yaml file that sets up different sensors (and this is where the old speedtest sensor went into). This can no longer be used (because the sensors are set up automatically now), so I added speedtestdotnet directly to configuration.yaml and the error when away (after restarting the service).
@tmeringer thanks for the info but I have a follow up question… which file did you place the monitored_conditions and minute parms?