You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if your weather sensor goes offline (Accuweather only allows 50 API calls a day and sometimes if you restart HA several times you can blow this limit and end up with a Weather sensor with a state of None).
If this happens then BT does not initialise and the logs just contain
2024-09-10 10:36:13.841 INFO (MainThread) [custom_components.better_thermostat.climate] better_thermostat Playroom Thermostat: Starting version 1.6.0. Waiting for entity to be ready...
2024-09-10 10:36:13.841 INFO (MainThread) [custom_components.better_thermostat.climate] better_thermostat Playroom Thermostat: waiting for weather entity with id 'weather.home' to become fully available...
2024-09-10 10:36:13.841 INFO (MainThread) [custom_components.better_thermostat.climate] better_thermostat Bedroom Thermostat: Starting version 1.6.0. Waiting for entity to be ready...
2024-09-10 10:36:13.841 INFO (MainThread) [custom_components.better_thermostat.climate] better_thermostat Bedroom Thermostat: waiting for weather entity with id 'weather.home' to become fully available...
Whilst the weather is a nice to have I think BT should not stop if it cannot get weather sensor
Same here: the batteries in my weather sensor ran out, and the BT stopped working—despite having configured a weather service as a fallback that could have been used.
What is the feature?
Allow BT to ignore a missing weather sensor
Description
Currently if your weather sensor goes offline (Accuweather only allows 50 API calls a day and sometimes if you restart HA several times you can blow this limit and end up with a Weather sensor with a state of None).
If this happens then BT does not initialise and the logs just contain
Whilst the weather is a nice to have I think BT should not stop if it cannot get weather sensor
Additional Information
Similar to #1383 but more specific
The text was updated successfully, but these errors were encountered: