search

pnbruckner / ha-illuminance

Home Assistant Illuminance Sensor
The Unlicense
153 stars 16 forks source link

Feature Request: fallback when weather sensor fails #27

Closed rigrig closed 2 weeks ago

rigrig commented 2 years ago

The last Home Assistant update broke OpenWeatherMap, resulting in the illuminance sensor returning unknown, (log: No attribution attribute: weather.openweathermap.)
My automations expect a numeric value (to prevent flickering the lights when illuminance is unknown during HA restart), so didn't turn on my lights when it got dark.

Maybe instead of bailing out when it can't find/handle current conditions, the illuminance sensor could just fall back to ignoring the weather sensor, so lights at least still turn on/off according to day/night?

pnbruckner commented 2 years ago

Good idea. In fact, I can even make using a weather entity optional, which would just give the curve based solely on sun position.

luberk8 commented 8 months ago

Good idea. In fact, I can even make using a weather entity optional, which would just give the curve based solely on sun position.

Did you ever add the weather entity being optional feature? I would like to use your tool "backwards", i.e. calculate "cloudiness" based on an actual sensor

pnbruckner commented 8 months ago

@luberk8, no, not yet. In theory the "fallback" feature could do it, but the current implementation expects to see the weather entity at least once, and until it does, the sensor's state will be "unknown". I've been meaning to change that, but I could also explicitly make the weather entity optional. I kind of have that on my "to do" list, just haven't gotten around to it. I'll try to do it sooner rather than later.

rrooggiieerr commented 1 month ago

give the curve based solely on sun position

I would be very interested in this option but understand this is not yet implemented as weather data source is stil a required argument. Any plans to implement this?

pnbruckner commented 1 month ago

Yes, but with all the work I recently did on the Life360 integration, which is now broken, yet again, this kind of got pushed to the "back burner." I'll try to do this soon.

pnbruckner commented 4 weeks ago

@rigrig, @luberk8, @rrooggiieerr, I just released 5.5.0b0 that makes the weather entity optional. It hopefully also handles the case of a "bad" weather entity at startup better, but that's yet to be seen. If you give the beta a try, let me know how it works for you.