It depends on the observation type, but for most values, the average is
stored in the record.
-tk
On Mon, Nov 5, 2018 at 1:38 PM Per Edström wrote:
> I loaded the suggested engine.py and now there is only a record saved
> every 5 minutes:
>
> Nov 5 22:34:21 RPi3_L5E weewx[25497]: engine:
I loaded the suggested engine.py and now there is only a record saved every
5 minutes:
Nov 5 22:34:21 RPi3_L5E weewx[25497]: engine: Loading service
weewx.engine.StdArchive
Nov 5 22:34:21 RPi3_L5E weewx[25497]: engine: Archive will use data
binding wx_binding
Nov 5 22:34:21 RPi3_L5E
I can only guess that when similar issues have come up before people have
managed to change the hardware interval to match the software one rather
than relying on a possible override from using software generation.
On Monday, 5 November 2018 04:42:25 UTC+2, Thomas Keffer wrote:
>
> Me too!
>
>
Me too!
-tk
On Sun, Nov 4, 2018 at 6:27 PM gjr80 wrote:
> On Monday, 5 November 2018 11:48:52 UTC+10, Thomas Keffer wrote:
>>
>> Actually, looking through the code, the engine would do the same thing
>> for any type of hardware: it always reverts to the hardware archive
>> interval, even if
Actually, looking through the code, the engine would do the same thing for
any type of hardware: it always reverts to the hardware archive interval,
even if you request software record generation.
Clearly, that's wrong. I've changed this in commit c9a8c0
Sorry about that - here it is..
It seems like the config-value (300) is overridden by the WMR200-value (60).
Nov 4 20:49:26 RPi-3B_Skalet systemd[1]: Starting LSB: weewx weather
system...
Nov 4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Initializing weewx
version 3.8.2
Nov 4 20:49:26
>
> DEBUG = 1 does not give that much new information..
Nov 4 09:34:07 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:415
Nov 4 09:34:07 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D Queuing
live packet rx:393 live_queue_len:1
Nov 4 09:34:08
Tom asked for the debug log FROM WEEWX STARTUP because that is when the
information regarding the archive interval to be used is logged.
The extract you posted does not provide the required information as to why
the interval is remaining at 60 seconds rather than using the 5 minute you
have
You override the archive interval by switching to software record
generation. (record_generation = software). If WeeWX is not doing this,
there is something else wrong. Could you please show the log with debug=1,
from when you start up WeeWX? It will show details of what record
generation it is
have you set the archive_interval = 300 in the [wmr200] section of
weewx.conf - I do not know if you also need to specify the interval in
StdArchive section or not - you possibly need it in both places.
On Saturday, 3 November 2018 11:32:52 UTC+2, Per Edström wrote:
>
> No, I have 300 seconds
No, I have 300 seconds = 5 minutes as archive interval but the WMR200
overrides it.
I tried software generation but Weewx still stores every minute (I guess
the HW-interval can not be overridden in weewx.conf):
Nov 3 10:20:36 RPi-3B_Skalet weewx[9980]: ftpgenerator: ftp'd 33 files in
13.16
I assume your archive interval is also set at one minute - so you can
alternatively make your archive interval 5 minutes (300 seconds) which would
You may need to also try software archive record generation if hardware
generation is currently selected.
a) give a reading for all sensors within
12 matches
Mail list logo
