I have recently run into an odd problem where overnight, the time update seems to “stop” for a period. I presume this is an NTP issue, but the behavior is really strange.
On any reboot of the Pi (openhabian) or restart of OH, time comes up correctly. More and frequently, notably since upgrading to 2.5.6 (and now 2.5.7, but I don’t know if the version update matters or not), overnight the time must “hang” at some point such that my morning, when the time should be (for example) 8:00 am, August 12, 2020, OH believes it is 2:48 am. As a result, the Astro bindings are all off for triggers. On the other hand, I have set up a morning alarm (ala the tutorials), and that will trigger just fine at the right time - only the Astro binding doesn’t recognize the right time and won’t trigger events correctly. For example, say the alarm is supposed to go off at 7:00 am tomorrow. At night, before bed, everything is running correctly. At 7:00 the alarm goes off correctly, but as part of the alarm rule, it should open blinds if it is daylight outside. The system believes it to be 2:48 am, so it’s not yet daylight, so the blinds don’t open. Yet the alarm still goes off. The NTP time is 2:48 am (even though the alarm went off correctly).
This is really strange, and I’m not sure where to start looking for the problem. It’s inconsistent, so it doesn’t happen every day, but it does happen frequently (3-4 times per week). Alarm functions work, but the system time is wrong. Astro won’t work because it believes the time is different than it is. It’s perplexing…
I found a similar topic on this some time ago, and checked for multiple, duplicate Things, but there’s nothing like that I can find that would create an obvious conflict.
Any ideas on where to begin checking this out?