Hi there, this isn’t fixed and I’m experiencing the same problem during all DST switches. It affected me in OH2.4 last October, and now under OH2.5 during today’s DST switch.
I’m using it for the blinds and the civilDawn event with:
configured in the PaperUI. Now, due to my latitude, effectively the blinds open 07:45 all year round, except for +/- 2 weeks around December 21st, so I could just switch to a time-based event.
But I think I can surmise what is going on here. The Earliest and Latest times probably get internally stored as some DateTime object with a timezone attached. So on my still running OH instance that would be 07:45 CET, and well, technically that is the time that they opened this morning, except I’m in CEST now, and them opening at 08:45 wall clock time isn’t what was intended.
So the code is technically correct, but unhelpful.
A restart of the OH instance will of course fix this, as the process will then start up in the CEST timezone and base all calculations off of that.
My fix now is to try with these cronjob entries that should do the trick, but it’s still a bug.
# In Mar/Oct, restart OH _if_ the timezone has changed compared to yesterday (DST switch)
21 3 * 3,10 7 root test `date +%%Z -d "1 day ago"` = `date +%%Z` || service openhab2 restart
# grep "astro.*civilDawn" events.log.7 events.log
events.log.7:2020-03-28 07:45:00.010 [vent.ChannelTriggeredEvent] - astro:sun:10587c17:civilDawn#event triggered START
events.log.7:2020-03-28 07:45:00.013 [vent.ChannelTriggeredEvent] - astro:sun:10587c17:civilDawn#event triggered END
events.log:2020-03-29 08:45:00.006 [vent.ChannelTriggeredEvent] - astro:sun:10587c17:civilDawn#event triggered START
events.log:2020-03-29 08:45:00.011 [vent.ChannelTriggeredEvent] - astro:sun:10587c17:civilDawn#event triggered END
Note that 2020-03-28 is CET and 2020-03-29 is CEST, basically.
@ljsquare please don’t restart your OH instance today and let me know what happens tonight