High latitude Dawn and Dusk issue

[Area4949]

The dawn and dusk sensors get set to "Unknown" in high latitude locations where the sun does not get below -6 degrees from the horizon for days or weeks. "Unknown" is a catchall error condition and maybe should be set to "Not Applicable" or perhaps set to the actual date time of the next true Dawn/Dusk which may be weeks into the future...

[pnbruckner]

Because these sensors have a device class of timestamp, they have to be either a Python datetime or None, where None is shown as "Unknown". So, it's not possible for them to have a value of something like "Not Applicable".

However, it would be possible to show the next time it does occur (even if days, weeks or months away). But would that be consistent with what users may assume (i.e., the value is sometime during the current day)?

I'll try to get some feedback on the Community Forum.

[pnbruckner]

I decided to address this issue by having all "point in time" sensors have their "yesterday, today & tomorrow" attributes remain None when the event does not occur (yesterday, today and/or tomorrow), but to have the sensor's "main" state show the next time the event occurs within the next year, assuming it does, or (as before) None / unknown if it does not.

[pnbruckner]

Change is available in beta release 4.0.0b3.

[pnbruckner]

@Area4949 any update? Did the 4.0.0 beta release (4.0.0b5 is the latest now) solve this issue for you?