Ditto for me as well. I'm on ver 3 restart doesn't fix it, excerpt from syslog
Mar 26 08:32:53 debian8vm weewx[1392]: vantage: gentle wake up of console successful Mar 26 08:32:53 debian8vm weewx[1392]: engine: Clock error is -0.16 seconds (positive is fast) Mar 26 08:32:53 debian8vm weewx[1392]: vantage: Getting archive packets since 2017-03-26 02:00:00 BST (1490490000) Mar 26 08:32:53 debian8vm weewx[1392]: vantage: gentle wake up of console successful Mar 26 08:32:55 debian8vm weewx[1392]: vantage: Retrieving 513 page(s); starting index= 1 Mar 26 08:32:55 debian8vm weewx[1392]: vantage: DMPAFT complete: page timestamp 2017-03-17 10:15:00 GMT (1489745700) less than final timestamp 2017-03-26 02:00:00 BST (1490490000) Mar 26 08:32:55 debian8vm weewx[1392]: vantage: Catch up complete. Mar 26 08:32:55 debian8vm weewx[1392]: engine: Starting main packet loop. Mar 26 08:32:55 debian8vm weewx[1392]: vantage: gentle wake up of console successful Mar 26 08:32:55 debian8vm weewx[1392]: vantage: Requesting 200 LOOP packets. Mar 26 08:32:55 debian8vm weewx[1392]: vantage: gentle wake up of console successful Odd timestamp but that is what it spits out. Fixed with clear-memory as above. Nigel -- 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.
