michael, there are a couple of issues at play here, but they all result from having a bogus system time.
1) if the system time is bogus, then anything that weewx saves to the database will have a bogus time stamp. this results in current weather data being saved with a timestamp of 1970, or a timestamp in the past that conflicts with data already saved, or a timestamp in the future that then conflicts when the clock is adjusted to the correct time. 2) the weewx uptime is reported incorrectly 3) fake hardware clock really screws things up, because it sets the time to something close to ok, but still very much not ok. this will result in the same symptoms as (1). in weewx 3.4 there is a fix to prevent weewx from doing anything until the system clock is at least somewhat sane. this addresses many instances of (1), but it does not deal with (3). in weewx 3.6 there is a fix that addresses (2). the best thing to do is to install a realtime clock on the pi. in lieu of that, at the very least you should remove fake hardware clock, otherwise you risk polluting your database with bogus times. https://github.com/weewx/weewx/wiki/Raspberry-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 [email protected]. For more options, visit https://groups.google.com/d/optout.
