Hi, Since the end result is not what you expect you really want to follow your data from start to finish to see where it is being lost. You have looked at the file being generated by your bash script and it appears to have valid data. The next step is to look at what is being emitted by the fileparse driver. There are a couple of ways you can do this, since you already have WeeWX installed you could run WeeWX directly. <http://weewx.com/docs/usersguide.htm#Running_directly> This will show you the WeeWX augmented loop packets being emitted by the fileparse driver on the console. It will also show you the archive records being synthesised by WeeWX, the archive records are what are used to populate your reports. Alternatively, you could run the fileparse driver directly, refer to the comments in the last few lines of fileparse.py for how to do this, something like this should work (untested):
$ PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/fileparse.py This will show you only the loop packets emitted by the fileparse driver, this is exactly what fileparse passes to WeeWX when WeeWX is run. If correct data is being emitted by the fileparse driver then you need to look at WeeWX itself, if incorrect or no data is being emitted then you have an issue with the driver and it's processing of/acces to the raw data. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/97a1d7dc-db61-4d92-b502-ef10adc25833%40googlegroups.com.
