Hello Francesco, The log has identified a bug which has now been fixed and a new file uploaded to GitHub. Basically I had refactored some of the network access code (to avoid duplicating the code for both the historic and current record access) and I had not transferred over a variable initialisation. The problem only shows up when there are a lot of network access failures during the retrieval of historic records.
A couple of (possibly unrelated) comments if I may: - I suspect that your network is a little shaky in that you seem to be getting a lot of FTP errors and also my driver gets a lot of timeouts. - I note that the system time is updated (from NTP) some time after weewx is up and running. Weewx starts at 22:05:25, the system continues until 22:25:20 (with a big jump form 22:05:58 to 22:17:01) and then at 22:29:06, the next message is that the time has been corrected to 22:43:19. This may have an impact on the timestamps of the records written to the database. Also see the weewx Users Guide seciton on 'Clock skew' (although that talks about problems with the clock in the future rather than in the past) - the 'action 17' error message is a well known problem with Raspbian (https://blog.dantup.com/2016/04/removing-rsyslog-spam-on-raspberry-pi-raspbian-jessie/) which can be easily stopped. - if you are running from an SD card, then you might like to write the log files to a ram-disk. I know that this means you lose the logs after a system crash/reboot but it can preserve the life of the SD card. (I also have the whole weewx folder, including the generated HTML files, on a NFS drive on my NAS for the same reason). Susan On Wednesday, September 6, 2017 at 7:05:17 AM UTC+10, Francesco Scaramella wrote: > > Here's the log of my station. The whole first part is with the old driver > for HP100 WiFi. The last part is what happens in weewx after installing the > new version of the driver... hopefully it is indicative! > >> >>
