Can you post your weewx.conf - with sensitive passwords removed of course.
Weewx can be set to either generate archive records from hardware or
generate them by software. If the hardware rec always has the right data
then ensure that in weewx.conf - stdArchive section - you have got record
generation set to hardware
60 second archive interval is very small - usually one uses 5 minutes (300
secs) - and may lead to other issues in generating reports etc which is
done at the archive interval - so at 60 seconds the reports may start to
backlog a little
On Saturday, 20 January 2018 10:41:05 UTC+2, Yngve Andersson wrote:
>
> Notes on ...
>
> After the Weewx program has stopped (for some reason?) And been turned off
> for a few hours, I now restart with the command "*sudo weewxd weewx.conf*
> ".
>
> There is now a list of "REC" with historically stored values from the
> time weewx stopped. Measurement values displayed here with a range of 60
> seconds and up to the current time look correct (see attached print).
> (WMR300 is initially set to log 1 time/60seconds... if now this may be
> important?). These historical "REC" are now scrolling to return to normal
> running ("LOOP" and "REC, every 900 seconds") and now again with
> "altimeter: None and barometer: None" display.
>
>
> It's tricky to describe the procedure, but I hope it's understandable.
>
>
> A thought and wonder from a novice ... if the 60 seconds measured values
> in the WMR300 are correct why not read and present the nearest
> historically stored value?
>
> Sincerely Yngve
>
> Den lördag 20 januari 2018 kl. 02:12:02 UTC+2 skrev Yngve Andersson:
>>
>> The time between two "REC" 01:45:00 - 02:00:00 is exactly 900 seconds.
>> The reading was done manually from the terminal. Also noted that reading
>> values showed "altimeter: None, appTemp: 19.6444928978, barometer: None"
>>
>> Den fredag 19 januari 2018 kl. 22:01:42 UTC+2 skrev Yngve Andersson:
>>>
>>> Thank you, *mwall *for your quick response and dedication!
>>>
>>>
>>> The time is set to 900 seconds, also tested 1200 seconds with the same
>>> result.
>>>
>>> I'm not familiar with the "sqlite3" program, so it needed an
>>> installation. Then I come so far.
>>>
>>>
>>> p...@raspberrypi <javascript:>:~$ sqlite3 /var/lib/weewx.sdb
>>>
>>> SQLite version 3.16.2 2017-01-06 16:32:41
>>>
>>> Enter ”.help” for usage hints.
>>>
>>> Sqlite> select dateTime,pressure,barometer,altimeter from archive
>>>
>>> - - >
>>>
>>>
>>>
>>> Den fredag 19 januari 2018 kl. 20:42:39 UTC+2 skrev mwall:
>>>>
>>>> yngve,
>>>>
>>>> thank you for a detailed problem description!
>>>>
>>>> wu can be very unreliable about displaying data, so we should first
>>>> ensure that weewx is getting correct data from the hardware.
>>>>
>>>> as you know, the wmr300 emits a pressure reading only every 900
>>>> seconds. so if you have an archive interval of 300 seconds, only every
>>>> 3rd
>>>> archive record will have a value for pressure.
>>>>
>>>> however, your archive interval of 900 seconds should address this.
>>>>
>>>> how often do you have records (REC not LOOP) with no
>>>> pressure/altimeter/barometer?
>>>>
>>>> you can find out easily by doing a query on the weewx database:
>>>>
>>>> sqlite3 /var/lib/weewx.sdb
>>>> select dateTime,pressure,barometer,altimeter from archive
>>>>
>>>> m
>>>>
>>>>
--
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.
