Thanks for that, Gary
Running fileparse.py directly works
mt-dev@weewx:~$ PYTHONPATH=/usr/share/weewx python
/usr/share/weewx/user/fileparse.py
2020-01-06 20:32:35 EST (1578360755) {'pressure': 29.17, 'usUnits': 1,
'dateTime': 1578360755}
When I run weewx directly, the pressure data is collected
mt-dev@weewx:~$ sudo weewxd /etc/weewx/weewx.conf
LOOP: 2020-01-06 20:18:09 EST (1578359889) altimeter: 30.1414615854,
dateTime: 1578359889, maxSolarRad: None, pressure: 29.17, rainRate: 0,
usUnits: 1
LOOP: 2020-01-06 20:23:09 EST (1578360189) altimeter: 30.1414615854,
dateTime: 1578360189, maxSolarRad: None, pressure: 29.17, rainRate: 0,
usUnits: 1
REC: 2020-01-06 20:20:00 EST (1578360000) altimeter: 30.1414615854,
dateTime: 1578360000.0, ET: None, interval: 5, maxSolarRad: None, pressure:
29.17, rainRate: 0.0, usUnits: 1
LOOP: 2020-01-06 20:23:09 EST (1578360189) altimeter: 30.1414615854,
dateTime: 1578360189, maxSolarRad: None, pressure: 29.17, rainRate: 0,
usUnits: 1
My reports are still blank, however.
I don't believe it is a permissions issue, as the files are being modified
-rw-r--r-- 1 root root 17K Jan 6 20:23 index.html
On Monday, January 6, 2020 at 6:10:23 AM UTC-5, gjr80 wrote:
>
> 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/d86e8059-cd4b-4734-9e65-a467986312dc%40googlegroups.com.
