If you removed the fake clock, it should start at unix epoch time zero. If it's not, it's because the module was not removed properly. See the Wiki <https://github.com/weewx/weewx/wiki/Raspberry-Pi#b-remove-the-fake-clock>.
In any case, the running an RTC is the right thing to do, particularly with a remote location that may have intermittent, or very delayed, access to NTP. -tk On Sat, Jan 20, 2018 at 11:59 AM, mwall <mw...@users.sourceforge.net> wrote: > weewx will not process data until the time is after 00:00:00 01jan2000 > utc. so perhaps your pi is reverting/starting at a time that is later than > that. > > you can make the weewx time check a bit more robust by modifying engine.py > > change this: > > while weewx.launchtime_ts < 946684800: > > to a more recent value. however, that approach can only go so far. > > the init systems also have mechanisms for delaying the start of weewx. > unfortunately, those may not do exactly what you expect. for example, you > might make weewx start after ntp, but just because ntp has started, the > system may not have a valid time. you'll have to dig deeper to tell your > init system that weewx should not start until after ntp has started AND > after ntp has set the system time. > > or put a real-time clock on the pi. > > m > > -- > 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 weewx-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
