subject:"Re\: \[weewx\-user\] Re\: Suggestion\: Re\-fill DB if sensor data is missing"

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-05 Thread Thomas Keffer

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: 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 weewx[25497]: engine: Record generation will be
> attempted in 'software'
> Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Using archive interval of
> 300 seconds (software record generation)
> Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Use LOOP data in hi/low
> calculations: 1
> Nov  5 22:34:21 RPi3_L5E weewx[25497]: manager: Daily summary version is
> 1.0
> Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Using binding 'wx_binding'
> to database 'weewx.sdb'
>
> But stille the WMR200 is providing sensor values every minute. Which value
> is used for the 5-minute-storage? An average or the latest? Or is the
> WMR200 pulled once every 5 minutes?
> There is still quite a busy log here:
>
> Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing
> live packet rx:53 live_queue_len:1
> Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop()
> Yielding live queued packet id:56
> Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing
> live packet rx:54 live_queue_len:1
> Nov  5 22:37:15 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop()
> Yielding live queued packet id:57
> Nov  5 22:37:15 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing
> live packet rx:55 live_queue_len:1
> Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop()
> Yielding live queued packet id:58
> Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D   adjust_rain
> rain_total:31.90 Rain.rain_total_last:31.90 rain_interval:0.00
> Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing
> live packet rx:56 live_queue_len:1
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-05 Thread Per Edström

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 weewx[25497]: engine: Record generation will be 
attempted in 'software'
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Using archive interval of 
300 seconds (software record generation)
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Use LOOP data in hi/low 
calculations: 1
Nov  5 22:34:21 RPi3_L5E weewx[25497]: manager: Daily summary version is 1.0
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'

But stille the WMR200 is providing sensor values every minute. Which value 
is used for the 5-minute-storage? An average or the latest? Or is the 
WMR200 pulled once every 5 minutes?
There is still quite a busy log here:

Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:53 live_queue_len:1
Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:56
Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:54 live_queue_len:1
Nov  5 22:37:15 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:57
Nov  5 22:37:15 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:55 live_queue_len:1
Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:58
Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D   adjust_rain 
rain_total:31.90 Rain.rain_total_last:31.90 rain_interval:0.00
Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:56 live_queue_len:1

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-04 Thread Andrew Milner

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!
>
> -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 you request software record generation.
>>>
>>
>> Surprised this one has not been picked up before
>>
>> 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 weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-04 Thread Thomas Keffer

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 you request software record generation.
>>
>
> Surprised this one has not been picked up before
>
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-04 Thread Thomas Keffer

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

.

Pers, if you want to try the new semantics, replace your copy of engine.py
with this one

.

-tk



On Sun, Nov 4, 2018 at 3:26 PM gjr80  wrote:

> I would suggest a bit of searching of the forums, it seems there are some
> peculiarities with the WMR200 and archive interval.
>
> Gary
>
> On Monday, 5 November 2018 05:55:08 UTC+10, Per Edström wrote:
>>
>> 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 RPi-3B_Skalet weewx[17619]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Platform
>> Linux-4.14.70-v7+-armv7l-with-debian-9.4
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Locale is
>> 'en_GB.UTF-8'
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: pid file is
>> /var/run/weewx.pid
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Using configuration
>> file /etc/weewx/weewx.conf
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Debug is 1
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Initializing engine
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Loading station type
>> WMR200 (weewx.drivers.wmr200)
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17608]: Starting weewx weather
>> system: weewx.
>> Nov  4 20:49:26 RPi-3B_Skalet systemd[1]: Started LSB: weewx weather
>> system.
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I driver
>> version is 3.3.5
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I sensor
>> map is {'outTempBatteryStatus': 'battery_status_out', 'extraTemp10':
>> 'temperature_10', 'outHumidity': 'humidity_1', 'rainRate': 'rain_rate',
>> 'extraHumid8': 'humidity_8', 'heatindex4': 'heatindex_4', 'rainTotal':
>> 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6':
>> 'heatindex_6', 'extraTemp5': 'temperature_5', 'uvFault': 'uv_fault',
>> 'extraTemp2': 'temperature_2', 'heatindex': 'heatindex_1', 'rain24':
>> 'rain_24', 'inHeatindex': 'heatindex_0', 'inTemp': 'temperature_0',
>> 'extraHumid9': 'humidity_9', 'hourRain': 'rain_hour', 'windFault':
>> 'wind_fault', 'extraHumid10': 'humidity_10', 'windchill': 'windchill',
>> 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7':
>> 'temperature_7', 'rain': 'rain', 'forecastIcon': 'forecast_icon',
>> 'pressure': 'pressure', 'extraHumid4': 'humidity_4', 'extraHumid5':
>> 'humidity_5', 'extraHumid2': 'humidity_2', 'extraHumid3': 'humidity_3',
>> 'extraTemp8': 'temperature_8', 'extraTemp9': 'temperature_9', 'extraTemp6':
>> 'temperature_6', 'heatindex5': 'heatindex_5', 'extraTemp4':
>> 'temperature_4', 'heatindex7': 'heatindex_7', 'altimeter': 'altimeter',
>> 'extraTemp3': 'temperature_3', 'heatindex2': 'heatindex_2', 'heatindex3':
>> 'heatindex_3', 'extraHumid6': 'humidity_6', 'extraHumid7': 'humidity_7',
>> 'windBatteryStatus': 'battery_status_wind', 'UV': 'uv', 'rainFault':
>> 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 'temperature_1',
>> 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 'outTempFault':
>> 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus':
>> 'battery_status_uv', 'heatindex8': 'heatindex_8', 'heatindex10':
>> 'heatindex_10', 'heatindex9': 'heatindex_9'}
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Created
>> watchdog thread to poke for live data every 30 seconds
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Created
>> USB polling thread to read block on device
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: Thread-2: I USB
>> polling device thread for live data launched
>> Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Reset
>> console device
>> Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: Thread-2: I USB
>> polling device thread signaled to start
>> Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D
>> Configuration setup
>> Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: Thread-1: I Started
>> watchdog thread live data
>> Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Log
>> sensor faults: True
>> Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Using
>> PC Time: True
>> Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Erase
>> archive data: False
>> Nov  4

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-04 Thread Per Edström

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 RPi-3B_Skalet weewx[17619]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Platform 
Linux-4.14.70-v7+-armv7l-with-debian-9.4
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Locale is 'en_GB.UTF-8'
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: pid file is 
/var/run/weewx.pid
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Using configuration 
file /etc/weewx/weewx.conf
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Debug is 1
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Initializing engine
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Loading station type 
WMR200 (weewx.drivers.wmr200)
Nov  4 20:49:26 RPi-3B_Skalet weewx[17608]: Starting weewx weather system: 
weewx.
Nov  4 20:49:26 RPi-3B_Skalet systemd[1]: Started LSB: weewx weather system.
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I driver 
version is 3.3.5
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I sensor 
map is {'outTempBatteryStatus': 'battery_status_out', 'extraTemp10': 
'temperature_10', 'outHumidity': 'humidity_1', 'rainRate': 'rain_rate', 
'extraHumid8': 'humidity_8', 'heatindex4': 'heatindex_4', 'rainTotal': 
'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6': 
'heatindex_6', 'extraTemp5': 'temperature_5', 'uvFault': 'uv_fault', 
'extraTemp2': 'temperature_2', 'heatindex': 'heatindex_1', 'rain24': 
'rain_24', 'inHeatindex': 'heatindex_0', 'inTemp': 'temperature_0', 
'extraHumid9': 'humidity_9', 'hourRain': 'rain_hour', 'windFault': 
'wind_fault', 'extraHumid10': 'humidity_10', 'windchill': 'windchill', 
'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
'temperature_7', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
'pressure': 'pressure', 'extraHumid4': 'humidity_4', 'extraHumid5': 
'humidity_5', 'extraHumid2': 'humidity_2', 'extraHumid3': 'humidity_3', 
'extraTemp8': 'temperature_8', 'extraTemp9': 'temperature_9', 'extraTemp6': 
'temperature_6', 'heatindex5': 'heatindex_5', 'extraTemp4': 
'temperature_4', 'heatindex7': 'heatindex_7', 'altimeter': 'altimeter', 
'extraTemp3': 'temperature_3', 'heatindex2': 'heatindex_2', 'heatindex3': 
'heatindex_3', 'extraHumid6': 'humidity_6', 'extraHumid7': 'humidity_7', 
'windBatteryStatus': 'battery_status_wind', 'UV': 'uv', 'rainFault': 
'rain_fault', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 'outTempFault': 
'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
'battery_status_uv', 'heatindex8': 'heatindex_8', 'heatindex10': 
'heatindex_10', 'heatindex9': 'heatindex_9'}
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Created 
USB polling thread to read block on device
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Reset 
console device
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: Thread-2: I USB polling 
device thread signaled to start
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D 
Configuration setup
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: Thread-1: I Started 
watchdog thread live data
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Log 
sensor faults: True
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Using 
PC Time: True
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Erase 
archive data: False
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Archive 
interval: 60
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Archive 
threshold: 604800
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdTimeSynch
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Finished loading 
service weewx.engine.StdTimeSynch
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdConvert
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: StdConvert target unit 
is 0x1
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Finished loading 
service weewx.engine.StdConvert
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdCalibrate
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Finished loading 
service weewx.engine.StdCalibrate
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdQC
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]:

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-04 Thread Per Edström

>
> 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 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:416
Nov  4 09:34:16 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D   Queuing
live packet rx:394 live_queue_len:1
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:417
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: manager: Added record
2018-11-04 09:34:00 CET (1541320440) to database 'weewx.sdb'
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: manager: Added record
2018-11-04 09:34:00 CET (1541320440) to daily summary in 'weewx.sdb'
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running reports
for latest time in the database.
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
phase getting live packets
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report
StandardReport
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found
configuration file /etc/weewx/skins/Standard/skin.conf for report
StandardReport
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report
StandardReport skipped due to report_timing setting
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report FTP
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found
configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report FTP
skipped due to report_timing setting
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report
RSYNC
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found
configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report RSYNC
skipped due to report_timing setting
Nov  4 09:34:21 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: W Skipped
bytes before resync:1
Nov  4 09:34:21 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D   Queuing
live packet rx:396 live_queue_len:1
Nov  4 09:34:22 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:419
Nov  4 09:34:24 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D
 Acknowledged control packet rx:24


Actually, I have noted that in order to get really useful debug information
one needs to set various DEBUG_ parameters = 1 in drivers/wmr200.py

But maybe that is how it should work? the DEBUG in weewx.conf is maybe only
for the engines and not "everything"?


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-04 Thread Andrew Milner

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 requested.



On Sunday, 4 November 2018 10:41:32 UTC+2, Per Edström wrote:
>
> 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 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D 
> genLoop() Yielding live queued packet id:416
> Nov  4 09:34:16 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D  
>  Queuing live packet rx:394 live_queue_len:1
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D 
> genLoop() Yielding live queued packet id:417
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: manager: Added record 
> 2018-11-04 09:34:00 CET (1541320440) to database 'weewx.sdb'
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: manager: Added record 
> 2018-11-04 09:34:00 CET (1541320440) to daily summary in 'weewx.sdb'
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running reports 
> for latest time in the database.
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D 
> genLoop() phase getting live packets
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report 
> StandardReport
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found 
> configuration file /etc/weewx/skins/Standard/skin.conf for report 
> StandardReport
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report 
> StandardReport skipped due to report_timing setting
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report 
> FTP
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found 
> configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report FTP 
> skipped due to report_timing setting
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report 
> RSYNC
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found 
> configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
> Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report RSYNC 
> skipped due to report_timing setting
> Nov  4 09:34:21 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: W Skipped 
> bytes before resync:1
> Nov  4 09:34:21 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D  
>  Queuing live packet rx:396 live_queue_len:1
> Nov  4 09:34:22 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D 
> genLoop() Yielding live queued packet id:419
> Nov  4 09:34:24 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D  
>  Acknowledged control packet rx:24
>
>
> Actually, I have noted that in order to get really useful debug 
> information one needs to set various DEBUG_ parameters = 1 in 
> drivers/wmr200.py
>
> But maybe that is how it should work? the DEBUG in weewx.conf is maybe 
> only for the engines and not "everything"?
>
>
> 
>  Virus-free. 
> www.avg.com 
> 
>  
> <#CAGVPPqR7wLx9wT1Z_OsXJGC2NAsJTkUTJ0Z6znxLfdkFVTZbXQ@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

2018-11-03 Thread Thomas Keffer

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 using.

As for your desire to replicate the last data point, WeeWX does not do this
for two reasons: drivers do not "make up" data, and they try not to use
caching .

So, this is not part of the shipping version of WeeWX. However, the
WeatherUnderground RESTful services does something similar, so writing an
extension to do this would be super easy [NOT TESTED]:

import weewx.restx
class GapFiller(StdService):
def __init__(self, engine, config_dict):
super(GapFiller, self).__init__(engine, config_dict)

self.cached_values = weewx.restx.CachedValues()
self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)

def new_archive_record(self, event):
self.cached_values.update(event.record, event.record['dateTime'])
event.record =
self.cached_values.get_packet(event.record['dateTime'], 600)

-tk

On Sat, Nov 3, 2018 at 2:32 AM Per Edström  wrote:

> 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 seconds
> Nov  3 10:21:16 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:21:00 CET (1541236860) to database 'weewx.sdb'
> Nov  3 10:21:16 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:21:00 CET (1541236860) to daily summary in 'weewx.sdb'
> Nov  3 10:22:16 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:22:00 CET (1541236920) to database 'weewx.sdb'
> Nov  3 10:22:16 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:22:00 CET (1541236920) to daily summary in 'weewx.sdb'
> Nov  3 10:23:17 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:23:00 CET (1541236980) to database 'weewx.sdb'
> Nov  3 10:23:17 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:23:00 CET (1541236980) to daily summary in 'weewx.sdb'
> Nov  3 10:24:17 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:24:00 CET (1541237040) to database 'weewx.sdb'
> Nov  3 10:24:17 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:24:00 CET (1541237040) to daily summary in 'weewx.sdb'
> Nov  3 10:25:17 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:25:00 CET (1541237100) to database 'weewx.sdb'
> Nov  3 10:25:17 RPi-3B_Skalet weewx[9980]: manager: Added record
> 2018-11-03 10:25:00 CET (1541237100) to daily summary in 'weewx.sdb'
> Nov  3 10:25:18 RPi-3B_Skalet weewx[9980]: cheetahgenerator: Generated 15
> files for report StandardReport in 1.18 seconds
>
> I would prefer that the DB-writing was made more seldom i.e. at the
> archive interval. Weewx could keep these 1-minute-values in memory until DB
> is to be written.
>
> Also, as this thread was started as, I would prefer Weewx to take the last
> received sensor value if there is one expected but missing i.e. the WMR200
> is not presenting it in the 1-minute-pull..
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

9 matches

Site Navigation

Mail list logo

Footer information