I found a solution that results in the DB and WU being updated each minute.
First, I set weewx config back to the original settings:
[StdArchive]
archive_interval = 60
archive_delay = 5
Then I changed the driver to output two types of loop packets:
a) if there was no data received from the dat
This also updates the DB and WU every minute:
[StdArchive]
archive_interval = 1
archive_delay = 10
I tried archive_interval = 0 but got a divide by zero exception. I assume
that is because the software tried to calculate an average for the archive
record by dividing the # of loop records re
The "429" error is fixed. Thanks Karen and Tom.
The 2 minute update problem, I changed the driver to poll the hardware
(serial port) every 15 seconds, but the database still updated every 2
minutes. After playing with several parameters in the driver and
weewx.conf I finally got the database t
First, a note on how weewxd works: the driver blocks, waiting for data to
come in. The program cannot do anything while it is blocked. Once data
comes in, then it can proceed, emit a LOOP packet, then the rest of the
program can process it.
Your fileparse polling interval is 60 seconds. This means
After writing a new driver for my station and configuring weewx to support
its data stream I was able to run weewx live for a few minutes, then shut
it down to check SYSLOG (debug=2).
There appears to be two problems (see attached syslog excerpt):
a) The database and reports are updating on two
