Open bib2 opened 6 years ago
@triller-telekom maybe you can have a look into this.
I have debugged the scheduler code in the past and already moved the time to 30 seconds after midnight because it was more reliable this way. Though, this was just a guess of me.
I have absolutely no clue what's wrong with the scheduler in this case. We will probably have to live with it until someone works on replacing the scheduler with https://github.com/eclipse/smarthome/issues/4295.
I have the same issue. For me it seems that only happens after a restart and it normalizes after a few hours after restart, but needs more testing. I'm on 2.4 M6 now and I didn't have this problem before.
can you guys try M7? One user reported that he doesn't have this issue anymore on M7 Ref: https://community.openhab.org/t/design-pattern-time-of-day/15407/233
I was the one who wrote this... I need some further testing, but I haven't had this error since then...
I have 3 astro things defined. 1x sun 1x moon 1x sun-additional (workaround with another location for getting a small offset)
Most of the time, i get 30sec after midnigt 3 schedulings for the things. But sometimes, i only get 2 schedulings. This happens sometimes 2 times a week, sometimes it is working a month without any problems. After i restart openhab service, i check the logs and then i get 3 schedulings again.
Now i´m on openhab 2.4 snapshot #1338, but this error is there for long time, maybe 1 or 2 years, every now and then.
I have a workaround, which is comparing now with the time of the astro-sun event sunrise start, but in cases the new day is not scheduling, it compares with the datetime of the day before. (the datetime is persisted in my installation, so i always have a datetime in my item).
Here is more information about the problem... https://community.openhab.org/t/rollershutter-rule-with-astro-binding-not-working-every-day/49910