> OK - but I still think it would be good if weewx never set the clock +/- > 6 h from a DST change, or maybe just never set the clock from 2300 to > 0500 daily.
I agree something like that would be good. For now, I’ve got DST enter/exit times specified in my weewx.conf files through to 2040 and drivers that ignore set_time around those transitions. > On Mar 28, 2021, at 7:23 AM, Greg Troxel <[email protected]> wrote: > > > John Kline <[email protected]> writes: > >> You have to be unlucky to see the issue. If WeeWX decided to set the >> time on the console within the hour of setting the clock back one hour >> when entering standard time, the clock setting would be one hour off. >> >> Having said that, I believe this is a bit off topic as this issue >> doesn’t result in memory having to be cleared; and the issue being >> reported in this thread seems to require clearing memory. > > OK - but I still think it would be good if weewx never set the clock +/- > 6 h from a DST change, or maybe just never set the clock from 2300 to > 0500 daily. Once the console clock is ok this should only be slow drift > and rare. But maybe I am missing something. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/322C44AB-92DD-4984-B98B-AD37836F8538%40johnkline.com.
