Ok, I am guessing here as I am not familiar with the WMR200 or its driver. In essence, the driver is talking to the WMR200, obtaining a record, adjusting the timestamp of the record and finding it is earlier than the last record in the weewx archive (28 Aug 2016 23:25), discarding the record and then getting the next record. This sort of behaviour can occur when you first start up with stations that have a logger that can store a history. Looking at the weewx Hardware comparison page <http://weewx.com/hwcmp.html>, the WMR200 stores up to 41760 odd records, at 1 minute that is about 29 days so it will eventually catch up (worst case it might take 41760 records being processed 2 or 3 per second or 41760/3 sec = approx 3 hrs 50 min). You could clear the WMR200 memory (not sure how that is done - check the manual) or you could leave it run, once the received record is timestamped after the last archived record you should see the incoming record being saved and reports run. Once the log history has been processed the system should settle down into the normal save archive record, run reports rhythm.
One thing though, given the problems you have had gettting this working with your station, is the old data in your weewx archive in fact simulator data? If so you probably don't want to keep that (it will mess up your stats), in fact you probably don't want to wait 4 odd hours, delete the data and then wait another 4 odd hours. If you want to get rid of all of the old data your best bet is to stop weewx, delete the file /var/lib/weewx/weewx.sdb then start weewx. This will start you off with a clean database and weewx should start downloading the history again. Gary -- 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.
