Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-31 Thread kufuu
Im thinking that on mqtt that rapidfire is only going to post what it gets, 
Rich I increased the archive_interval to 360 and it has been posting every 
reading now, even tipped the rain and it recorded it to WU and to the db. 
will keep an eye on it to see if that stays. thks you guys

On Tuesday, October 31, 2023 at 3:24:05 PM UTC-4 kufuu wrote:

> I did a rain test, weewx is getting the payload and it didnt write it to 
> the db or send it to WU 
>
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 950.67, "rain": 0.5588, 
> "wind_speed": 0, "temperature": 7.35, "humidity": 78.11, "wind_direction": 
> 90, "rain_per_second": 0.001856478, "luminance": 81.54}, "nickname": 
> "river-wx", "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-31T18:40:05Z"}'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '81.54', 
> 'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
> '0.5588', 'rainPersecond': '0.001856478', 'windDir': '90.0', 'windSpeed': 
> '0.0'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1698777608.1629858', 'luminance': '81.54', 'outHumidity': '78.11', 
> 'outTemp': '7.35', 'pressure': '950.67', 'rain': '0.5588', 'rainPersecond': 
> '0.001856478', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-31 14:40:08 EDT 
> (1698777608): 'dateTime': '1698777608.1629858', 'luminance': '81.54', 
> 'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
> '0.5588', 'rainPersecond': '0.001856478', 'usUnits': '17', 'windDir': 
> '90.0', 'windSpeed': '0.0'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) No 
> archive topic configured.
> Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.restx: Wunderground-RF: 
> Published record 2023-10-31 14:40:08 EDT (1698777608)
> Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
> 2023-10-31 14:40:00 EDT (1698777600) to database 'weewx.sdb'
> Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
> 2023-10-31 14:40:00 EDT (1698777600) to daily summary in 'weewx.sdb'
> Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
> 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
> 'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
> 'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
> Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Oct 31 14:40:24 zero-wx weewx[21762] INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 13.95 seconds
> Oct 31 14:40:24 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.imagegenerator: Generated 
> 8 images for report SeasonsReport in 7.06 seconds
> Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.reportengine: Copied 0 
> files to /var/weewx/reports
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'SmartphoneReport' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'MobileReport' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'StandardReport' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'FTP' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'RSYNC' not enabled. Skipping.
>
> On Tuesday, October 31, 2023 at 3:16:29 PM UTC-4 vince wrote:
>
>> You might have pain running rapidfire on a pi zero due to how slow it is.
>>
>> See some of the comparative benchmarks at 
>> https://github.com/weewx/weewx/wiki/Benchmarks-of-file-and-image-generation 
>> for 
>> details.
>>
>> On Tuesday, October 31, 2023 at 11:29:56 AM UTC-7 kufuu wrote:
>>
>>> I enabled rapidfire for WU and its sending out the data every reading 
>>> now, as far as the season skin every other packet, I can live with that 
>

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-31 Thread kufuu
I did a rain test, weewx is getting the payload and it didnt write it to 
the db or send it to WU 

Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
retain: 0, payload: b'{"readings": {"pressure": 950.67, "rain": 0.5588, 
"wind_speed": 0, "temperature": 7.35, "humidity": 78.11, "wind_direction": 
90, "rain_per_second": 0.001856478, "luminance": 81.54}, "nickname": 
"river-wx", "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-10-31T18:40:05Z"}'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '81.54', 
'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
'0.5588', 'rainPersecond': '0.001856478', 'windDir': '90.0', 'windSpeed': 
'0.0'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1698777608.1629858', 'luminance': '81.54', 'outHumidity': '78.11', 
'outTemp': '7.35', 'pressure': '950.67', 'rain': '0.5588', 'rainPersecond': 
'0.001856478', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-10-31 14:40:08 EDT 
(1698777608): 'dateTime': '1698777608.1629858', 'luminance': '81.54', 
'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
'0.5588', 'rainPersecond': '0.001856478', 'usUnits': '17', 'windDir': 
'90.0', 'windSpeed': '0.0'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) No 
archive topic configured.
Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.restx: Wunderground-RF: 
Published record 2023-10-31 14:40:08 EDT (1698777608)
Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
2023-10-31 14:40:00 EDT (1698777600) to database 'weewx.sdb'
Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
2023-10-31 14:40:00 EDT (1698777600) to daily summary in 'weewx.sdb'
Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
version is 4.0
Oct 31 14:40:24 zero-wx weewx[21762] INFO weewx.cheetahgenerator: Generated 
8 files for report SeasonsReport in 13.95 seconds
Oct 31 14:40:24 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
version is 4.0
Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.imagegenerator: Generated 8 
images for report SeasonsReport in 7.06 seconds
Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.reportengine: Copied 0 
files to /var/weewx/reports
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'RSYNC' not enabled. Skipping.

On Tuesday, October 31, 2023 at 3:16:29 PM UTC-4 vince wrote:

> You might have pain running rapidfire on a pi zero due to how slow it is.
>
> See some of the comparative benchmarks at 
> https://github.com/weewx/weewx/wiki/Benchmarks-of-file-and-image-generation 
> for 
> details.
>
> On Tuesday, October 31, 2023 at 11:29:56 AM UTC-7 kufuu wrote:
>
>> I enabled rapidfire for WU and its sending out the data every reading 
>> now, as far as the season skin every other packet, I can live with that 
>> unless its not writing to the DB, I ll have to wait and see about the rain 
>> if its working right.  Thanks again
>>
>> On Tuesday, October 31, 2023 at 1:54:49 PM UTC-4 bell...@gmail.com wrote:
>>
>>> The short answer is that your archive_interval is too short for how 
>>> frequently the weather data is published. In the snippet below you can 
>>> infer that the weather data is published every 5 minutes and the 
>>> archive_interval is probably also 5 minutes. This is resulting in some 
>>> ar

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-31 Thread vince
You might have pain running rapidfire on a pi zero due to how slow it is.

See some of the comparative benchmarks at 
https://github.com/weewx/weewx/wiki/Benchmarks-of-file-and-image-generation for 
details.

On Tuesday, October 31, 2023 at 11:29:56 AM UTC-7 kufuu wrote:

> I enabled rapidfire for WU and its sending out the data every reading now, 
> as far as the season skin every other packet, I can live with that unless 
> its not writing to the DB, I ll have to wait and see about the rain if its 
> working right.  Thanks again
>
> On Tuesday, October 31, 2023 at 1:54:49 PM UTC-4 bell...@gmail.com wrote:
>
>> The short answer is that your archive_interval is too short for how 
>> frequently the weather data is published. In the snippet below you can 
>> infer that the weather data is published every 5 minutes and the 
>> archive_interval is probably also 5 minutes. This is resulting in some 
>> archival intervals not receiving a loop packet.
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT
>>
>> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:10:09 EDT
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:15:09 EDT
>>
>> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:20:08 EDT
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:25:08 EDT
>>
>> Oct 30 19:25:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> Oct 30 19:25:11 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:30:08 EDT
>>
>> Note, this is a greatly simplified explanation. WeeWX uses the received 
>> loop packet, archive_interval, and archive_delay to determine when to 
>> create an archive record from the received loop packets.
>>
>> Net, either publish the data more frequently or increase your 
>> archive_interval.
>>
>> rich
>> On Monday, 30 October 2023 at 19:35:07 UTC-4 kufuu wrote:
>>
>>> Ok, this is what I found happening, the other day when I reset the 
>>> weather station pico enviro weather it was sending the payload at 5 min 
>>> intervals example 20:06:09 and it was writing to db and sending the data to 
>>> weather underground every reading, now the clock resets ever so often on 
>>> the weather station and now its example 20:05:09 and its only recording and 
>>> sending to WU every other reading. weewx is up to date and running on a pi 
>>> zero w. Any clues ? Heres a copy of the log
>>>
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>>> retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
>>> "wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
>>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>>> "2023-10-30T23:00:05Z"}'
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>>> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>>> '1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
>>> 'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
>>> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
>>> (1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
>>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>>> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
>>> 'windSpeed': '0.0'
>>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>>> retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
>>> "wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
>>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>>> "2023-10-30T23:05:05Z"}'
>>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>>> 'outHumidity': '89.15', 'o

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-31 Thread kufuu
I enabled rapidfire for WU and its sending out the data every reading now, 
as far as the season skin every other packet, I can live with that unless 
its not writing to the DB, I ll have to wait and see about the rain if its 
working right.  Thanks again

On Tuesday, October 31, 2023 at 1:54:49 PM UTC-4 bell...@gmail.com wrote:

> The short answer is that your archive_interval is too short for how 
> frequently the weather data is published. In the snippet below you can 
> infer that the weather data is published every 5 minutes and the 
> archive_interval is probably also 5 minutes. This is resulting in some 
> archival intervals not receiving a loop packet.
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT
>
> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:10:09 EDT
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:15:09 EDT
>
> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:20:08 EDT
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:25:08 EDT
>
> Oct 30 19:25:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> Oct 30 19:25:11 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:30:08 EDT
>
> Note, this is a greatly simplified explanation. WeeWX uses the received 
> loop packet, archive_interval, and archive_delay to determine when to 
> create an archive record from the received loop packets.
>
> Net, either publish the data more frequently or increase your 
> archive_interval.
>
> rich
> On Monday, 30 October 2023 at 19:35:07 UTC-4 kufuu wrote:
>
>> Ok, this is what I found happening, the other day when I reset the 
>> weather station pico enviro weather it was sending the payload at 5 min 
>> intervals example 20:06:09 and it was writing to db and sending the data to 
>> weather underground every reading, now the clock resets ever so often on 
>> the weather station and now its example 20:05:09 and its only recording and 
>> sending to WU every other reading. weewx is up to date and running on a pi 
>> zero w. Any clues ? Heres a copy of the log
>>
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>> retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
>> "wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>> "2023-10-30T23:00:05Z"}'
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>> '1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
>> 'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
>> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
>> (1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
>> 'windSpeed': '0.0'
>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>> retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
>> "wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>> "2023-10-30T23:05:05Z"}'
>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>> 'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
>> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>> '1698707109.1076276', 'luminance': '0.0', 'outHumidity': '89.15', 
>> 'outTemp': '10.58', 'pressure': '9

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-31 Thread bell...@gmail.com


The short answer is that your archive_interval is too short for how 
frequently the weather data is published. In the snippet below you can 
infer that the weather data is published every 5 minutes and the 
archive_interval is probably also 5 minutes. This is resulting in some 
archival intervals not receiving a loop packet.

data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT
data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT
Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
data-> final loop packet is enviro/river-wx 2023-10-30 19:10:09 EDT
data-> final loop packet is enviro/river-wx 2023-10-30 19:15:09 EDT
Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
data-> final loop packet is enviro/river-wx 2023-10-30 19:20:08 EDT
data-> final loop packet is enviro/river-wx 2023-10-30 19:25:08 EDT
Oct 30 19:25:10 zero-wx weewx[6949] INFO weewx.manager: Added record
Oct 30 19:25:11 zero-wx weewx[6949] INFO weewx.manager: Added record
data-> final loop packet is enviro/river-wx 2023-10-30 19:30:08 EDT

Note, this is a greatly simplified explanation. WeeWX uses the received 
loop packet, archive_interval, and archive_delay to determine when to 
create an archive record from the received loop packets.

Net, either publish the data more frequently or increase your 
archive_interval.

rich
On Monday, 30 October 2023 at 19:35:07 UTC-4 kufuu wrote:

> Ok, this is what I found happening, the other day when I reset the weather 
> station pico enviro weather it was sending the payload at 5 min intervals 
> example 20:06:09 and it was writing to db and sending the data to weather 
> underground every reading, now the clock resets ever so often on the 
> weather station and now its example 20:05:09 and its only recording and 
> sending to WU every other reading. weewx is up to date and running on a pi 
> zero w. Any clues ? Heres a copy of the log
>
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
> "wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-30T23:00:05Z"}'
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
> 'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
> (1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
> 'windSpeed': '0.0'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
> "wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-30T23:05:05Z"}'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
> 'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1698707109.1076276', 'luminance': '0.0', 'outHumidity': '89.15', 
> 'outTemp': '10.58', 'pressure': '950.54', 'rain': '0.0', 'rainPersecond': 
> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT 
> (1698707109): 'dateTime': '1698707109.1076276', 'luminance': '0.0', 
> 'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'w

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-30 Thread kufuu
Ok, this is what I found happening, the other day when I reset the weather 
station pico enviro weather it was sending the payload at 5 min intervals 
example 20:06:09 and it was writing to db and sending the data to weather 
underground every reading, now the clock resets ever so often on the 
weather station and now its example 20:05:09 and its only recording and 
sending to WU every other reading. weewx is up to date and running on a pi 
zero w. Any clues ? Heres a copy of the log

Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
"wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
"model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-10-30T23:00:05Z"}'
Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
'0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
'0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
(1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
'0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
'windSpeed': '0.0'
Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
"wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
"model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-10-30T23:05:05Z"}'
Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
'0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1698707109.1076276', 'luminance': '0.0', 'outHumidity': '89.15', 
'outTemp': '10.58', 'pressure': '950.54', 'rain': '0.0', 'rainPersecond': 
'0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT 
(1698707109): 'dateTime': '1698707109.1076276', 'luminance': '0.0', 
'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
'0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
'windSpeed': '0.0'
Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) No 
archive topic configured.
Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record 
2023-10-30 19:05:00 EDT (1698707100) to database 'weewx.sdb'
Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record 
2023-10-30 19:05:00 EDT (1698707100) to daily summary in 'weewx.sdb'
Oct 30 19:05:11 zero-wx weewx[6949] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Oct 30 19:05:11 zero-wx weewx[6949] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Oct 30 19:05:11 zero-wx weewx[6949] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Oct 30 19:05:11 zero-wx weewx[6949] INFO weewx.restx: Wunderground-PWS: 
Published record 2023-10-30 19:05:00 EDT (1698707100)
Oct 30 19:05:12 zero-wx weewx[6949] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Oct 30 19:05:12 zero-wx weewx[6949] DEBUG weewx.manager: Daily summary 
version is 4.0
Oct 30 19:05:24 zero-wx weewx[6949] INFO weewx.cheetahgenerator: Generated 
8 files for report SeasonsReport in 12.36 seconds
Oct 30 19:05:24 zero-wx weewx[6949] DEBUG weewx.manager: Daily summary 
version is 4.0
Oc

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-30 Thread kufuu
Ok, this is what I found happening, the other day when I reset the weather 
station pico enviro weather it was sending the payload at 5 min intervals 
example 20:06:09 and it was writing to db and sending the data to weather 
underground every reading, now the clock resets ever so often on the 
weather station and now its example 20:05:09 and its only recording and 
sending to WU every other reading. weewx is up to date and running on a pi 
zero w. Any clues ?

On Sunday, October 29, 2023 at 10:54:56 AM UTC-4 kufuu wrote:

> I completely removed weewx from the pi zero and reloaded it, It seems to 
> have cleared up 2 problems I had, its writing to the to the db every 
> reading now and the rain is being recorded, Ill have to see when we get 
> some rain if that holds out.
>
>
> On Friday, October 27, 2023 at 8:58:29 AM UTC-4 kufuu wrote:
>
>> I did load DB Browser and seen that the 1697832900 packet did not record 
>> the rain in the db.
>>
>> On Thursday, October 26, 2023 at 12:03:02 PM UTC-4 kufuu wrote:
>>
>>> Thanks Rich , All the other observations are good, I don't know how to 
>>> look at the database, I do have sqlite installed however  I'm a newbie at 
>>> this.
>>>
>>> On Monday, October 23, 2023 at 9:14:26 AM UTC-4 Rich Bell wrote:
>>>
 I agree it looks like WeeWX is getting the information. The line below 
 is logged right before the loop packet is generated. This should be seen 
 in 
 the 1697833200 archive record. So no rain.
 Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
 (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
 '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'

 The line below is logged right before the loop packet is generated. 
 This should be seen in the next archive record. So 2.514 mm or .099 in.
 Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT 
 (1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25', 
 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
 '2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'

 The next thing to try is, run WeeWX from the command line. This will 
 print the loop packets and archive records to the console.

 Out of curiosity, what are the values in the database? Do the other 
 observations look correct?
 rich


 On Fri, Oct 20, 2023 at 5:10 PM kufuu  wrote:

> Using weewx mqtt from a pi pico enviro weather, had rain off and on 
> all day today and this morning the reports had .110" , after another .100 
> later weewx didnt write it to the reports, went out and manually added 
> rain 
> to try to figure out whats wrong and still didnt write it, weewx is 
> getting 
> it but dont know whats going on. Heres the script.
>
> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 936.97, "rain": 0, 
> "wind_speed": 0, "temperature": 13.52, "humidity": 77.89, 
> "wind_direction": 
> 45, "rain_per_second": 0.0, "luminance": 171.37}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-20T20:15:05Z"}'
> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '171.37', 
> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
> '0.0', 'windDir': '45.0', 'windSpeed': '0.0'
> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1697832900.6921751', 'luminance': '171.37', 'outHumidity': '77.89', 
> 'outTemp': '13.52', 'pressure': '936.97', 'rain': '0.0', 'usUnits': '17', 
> 'windDir': '45.0', 'windSpeed': '0.0'
> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
> Oct 20 16:17:01 zero-wx CRON[1104]: (root) CMD (   cd / && run-parts 
> --report /etc/cron.hourly)
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 937.04, "rain": 2.5146, 
> "wind_speed": 2.12127, "t

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-29 Thread kufuu
I completely removed weewx from the pi zero and reloaded it, It seems to 
have cleared up 2 problems I had, its writing to the to the db every 
reading now and the rain is being recorded, Ill have to see when we get 
some rain if that holds out.


On Friday, October 27, 2023 at 8:58:29 AM UTC-4 kufuu wrote:

> I did load DB Browser and seen that the 1697832900 packet did not record 
> the rain in the db.
>
> On Thursday, October 26, 2023 at 12:03:02 PM UTC-4 kufuu wrote:
>
>> Thanks Rich , All the other observations are good, I don't know how to 
>> look at the database, I do have sqlite installed however  I'm a newbie at 
>> this.
>>
>> On Monday, October 23, 2023 at 9:14:26 AM UTC-4 Rich Bell wrote:
>>
>>> I agree it looks like WeeWX is getting the information. The line below 
>>> is logged right before the loop packet is generated. This should be seen in 
>>> the 1697833200 archive record. So no rain.
>>> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
>>> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
>>> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
>>> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
>>>
>>> The line below is logged right before the loop packet is generated. This 
>>> should be seen in the next archive record. So 2.514 mm or .099 in.
>>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT 
>>> (1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25', 
>>> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
>>> '2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'
>>>
>>> The next thing to try is, run WeeWX from the command line. This will 
>>> print the loop packets and archive records to the console.
>>>
>>> Out of curiosity, what are the values in the database? Do the other 
>>> observations look correct?
>>> rich
>>>
>>>
>>> On Fri, Oct 20, 2023 at 5:10 PM kufuu  wrote:
>>>
 Using weewx mqtt from a pi pico enviro weather, had rain off and on all 
 day today and this morning the reports had .110" , after another .100 
 later 
 weewx didnt write it to the reports, went out and manually added rain to 
 try to figure out whats wrong and still didnt write it, weewx is getting 
 it 
 but dont know whats going on. Heres the script.

 Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
 retain: 0, payload: b'{"readings": {"pressure": 936.97, "rain": 0, 
 "wind_speed": 0, "temperature": 13.52, "humidity": 77.89, 
 "wind_direction": 
 45, "rain_per_second": 0.0, "luminance": 171.37}, "nickname": "river-wx", 
 "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
 "2023-10-20T20:15:05Z"}'
 Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 TopicManager data-> incoming enviro/river-wx: 'luminance': '171.37', 
 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
 '0.0', 'windDir': '45.0', 'windSpeed': '0.0'
 Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
 '1697832900.6921751', 'luminance': '171.37', 'outHumidity': '77.89', 
 'outTemp': '13.52', 'pressure': '936.97', 'rain': '0.0', 'usUnits': '17', 
 'windDir': '45.0', 'windSpeed': '0.0'
 Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
 (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
 '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
 Oct 20 16:17:01 zero-wx CRON[1104]: (root) CMD (   cd / && run-parts 
 --report /etc/cron.hourly)
 Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
 retain: 0, payload: b'{"readings": {"pressure": 937.04, "rain": 2.5146, 
 "wind_speed": 2.12127, "temperature": 13.6, "humidity": 77.04, 
 "wind_direction": 45, "rain_per_second": 0.008381999, "luminance": 82.25}, 
 "nickname": "river-wx", "model": "weather", "uid": "e6614c311b62b034", 
 "timestamp": "2023-10-20T20:20:05Z"}'
 Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 TopicManager data-> incoming enviro/river-wx: 'luminance': '82.25', 
 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
 '2.5146', 'windDir': '45.0', 'windSpeed': '2.12127'
 Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
 TopicManager da

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-27 Thread kufuu
I did load DB Browser and seen that the 1697832900 packet did not record 
the rain in the db.

On Thursday, October 26, 2023 at 12:03:02 PM UTC-4 kufuu wrote:

> Thanks Rich , All the other observations are good, I don't know how to 
> look at the database, I do have sqlite installed however  I'm a newbie at 
> this.
>
> On Monday, October 23, 2023 at 9:14:26 AM UTC-4 Rich Bell wrote:
>
>> I agree it looks like WeeWX is getting the information. The line below is 
>> logged right before the loop packet is generated. This should be seen in 
>> the 1697833200 archive record. So no rain.
>> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
>> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
>> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
>> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
>>
>> The line below is logged right before the loop packet is generated. This 
>> should be seen in the next archive record. So 2.514 mm or .099 in.
>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT 
>> (1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25', 
>> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
>> '2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'
>>
>> The next thing to try is, run WeeWX from the command line. This will 
>> print the loop packets and archive records to the console.
>>
>> Out of curiosity, what are the values in the database? Do the other 
>> observations look correct?
>> rich
>>
>>
>> On Fri, Oct 20, 2023 at 5:10 PM kufuu  wrote:
>>
>>> Using weewx mqtt from a pi pico enviro weather, had rain off and on all 
>>> day today and this morning the reports had .110" , after another .100 later 
>>> weewx didnt write it to the reports, went out and manually added rain to 
>>> try to figure out whats wrong and still didnt write it, weewx is getting it 
>>> but dont know whats going on. Heres the script.
>>>
>>> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>>> retain: 0, payload: b'{"readings": {"pressure": 936.97, "rain": 0, 
>>> "wind_speed": 0, "temperature": 13.52, "humidity": 77.89, "wind_direction": 
>>> 45, "rain_per_second": 0.0, "luminance": 171.37}, "nickname": "river-wx", 
>>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>>> "2023-10-20T20:15:05Z"}'
>>> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> incoming enviro/river-wx: 'luminance': '171.37', 
>>> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
>>> '0.0', 'windDir': '45.0', 'windSpeed': '0.0'
>>> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>>> '1697832900.6921751', 'luminance': '171.37', 'outHumidity': '77.89', 
>>> 'outTemp': '13.52', 'pressure': '936.97', 'rain': '0.0', 'usUnits': '17', 
>>> 'windDir': '45.0', 'windSpeed': '0.0'
>>> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
>>> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
>>> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
>>> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
>>> Oct 20 16:17:01 zero-wx CRON[1104]: (root) CMD (   cd / && run-parts 
>>> --report /etc/cron.hourly)
>>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>>> retain: 0, payload: b'{"readings": {"pressure": 937.04, "rain": 2.5146, 
>>> "wind_speed": 2.12127, "temperature": 13.6, "humidity": 77.04, 
>>> "wind_direction": 45, "rain_per_second": 0.008381999, "luminance": 82.25}, 
>>> "nickname": "river-wx", "model": "weather", "uid": "e6614c311b62b034", 
>>> "timestamp": "2023-10-20T20:20:05Z"}'
>>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> incoming enviro/river-wx: 'luminance': '82.25', 
>>> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
>>> '2.5146', 'windDir': '45.0', 'windSpeed': '2.12127'
>>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>>> '1697833200.808235', 'luminance': '82.25', 'outHumidity': '77.04', 
>>> 'outTemp': '13.6', 'pressure': '937.04', 'rain': '2.5146', 'usUnits': '17', 
>>> 'windDir': '45.0', 'windSpeed': '2.12127'
>>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>>> data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT 
>>> (1697833200): 'd

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-26 Thread kufuu
Thanks Rich , All the other observations are good, I don't know how to look 
at the database, I do have sqlite installed however  I'm a newbie at this.

On Monday, October 23, 2023 at 9:14:26 AM UTC-4 Rich Bell wrote:

> I agree it looks like WeeWX is getting the information. The line below is 
> logged right before the loop packet is generated. This should be seen in 
> the 1697833200 archive record. So no rain.
> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
>
> The line below is logged right before the loop packet is generated. This 
> should be seen in the next archive record. So 2.514 mm or .099 in.
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT 
> (1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25', 
> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
> '2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'
>
> The next thing to try is, run WeeWX from the command line. This will print 
> the loop packets and archive records to the console.
>
> Out of curiosity, what are the values in the database? Do the other 
> observations look correct?
> rich
>
>
> On Fri, Oct 20, 2023 at 5:10 PM kufuu  wrote:
>
>> Using weewx mqtt from a pi pico enviro weather, had rain off and on all 
>> day today and this morning the reports had .110" , after another .100 later 
>> weewx didnt write it to the reports, went out and manually added rain to 
>> try to figure out whats wrong and still didnt write it, weewx is getting it 
>> but dont know whats going on. Heres the script.
>>
>> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>> retain: 0, payload: b'{"readings": {"pressure": 936.97, "rain": 0, 
>> "wind_speed": 0, "temperature": 13.52, "humidity": 77.89, "wind_direction": 
>> 45, "rain_per_second": 0.0, "luminance": 171.37}, "nickname": "river-wx", 
>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>> "2023-10-20T20:15:05Z"}'
>> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> incoming enviro/river-wx: 'luminance': '171.37', 
>> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
>> '0.0', 'windDir': '45.0', 'windSpeed': '0.0'
>> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>> '1697832900.6921751', 'luminance': '171.37', 'outHumidity': '77.89', 
>> 'outTemp': '13.52', 'pressure': '936.97', 'rain': '0.0', 'usUnits': '17', 
>> 'windDir': '45.0', 'windSpeed': '0.0'
>> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT 
>> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37', 
>> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain': 
>> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
>> Oct 20 16:17:01 zero-wx CRON[1104]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>> retain: 0, payload: b'{"readings": {"pressure": 937.04, "rain": 2.5146, 
>> "wind_speed": 2.12127, "temperature": 13.6, "humidity": 77.04, 
>> "wind_direction": 45, "rain_per_second": 0.008381999, "luminance": 82.25}, 
>> "nickname": "river-wx", "model": "weather", "uid": "e6614c311b62b034", 
>> "timestamp": "2023-10-20T20:20:05Z"}'
>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> incoming enviro/river-wx: 'luminance': '82.25', 
>> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
>> '2.5146', 'windDir': '45.0', 'windSpeed': '2.12127'
>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>> '1697833200.808235', 'luminance': '82.25', 'outHumidity': '77.04', 
>> 'outTemp': '13.6', 'pressure': '937.04', 'rain': '2.5146', 'usUnits': '17', 
>> 'windDir': '45.0', 'windSpeed': '2.12127'
>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) 
>> data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT 
>> (1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25', 
>> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain': 
>> '2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'
>> Oct 20 16:20:00 zero-wx weewx[579] DEBUG

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

2023-10-23 Thread Rich Bell
I agree it looks like WeeWX is getting the information. The line below is
logged right before the loop packet is generated. This should be seen in
the 1697833200 archive record. So no rain.
Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT
(1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37',
'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain':
'0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'

The line below is logged right before the loop packet is generated. This
should be seen in the next archive record. So 2.514 mm or .099 in.
Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT
(1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25',
'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain':
'2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'

The next thing to try is, run WeeWX from the command line. This will print
the loop packets and archive records to the console.

Out of curiosity, what are the values in the database? Do the other
observations look correct?
rich


On Fri, Oct 20, 2023 at 5:10 PM kufuu  wrote:

> Using weewx mqtt from a pi pico enviro weather, had rain off and on all
> day today and this morning the reports had .110" , after another .100 later
> weewx didnt write it to the reports, went out and manually added rain to
> try to figure out whats wrong and still didnt write it, weewx is getting it
> but dont know whats going on. Heres the script.
>
> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
> retain: 0, payload: b'{"readings": {"pressure": 936.97, "rain": 0,
> "wind_speed": 0, "temperature": 13.52, "humidity": 77.89, "wind_direction":
> 45, "rain_per_second": 0.0, "luminance": 171.37}, "nickname": "river-wx",
> "model": "weather", "uid": "e6614c311b62b034", "timestamp":
> "2023-10-20T20:15:05Z"}'
> Oct 20 16:15:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> incoming enviro/river-wx: 'luminance': '171.37',
> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain':
> '0.0', 'windDir': '45.0', 'windSpeed': '0.0'
> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> outgoing enviro/river-wx: 'dateTime':
> '1697832900.6921751', 'luminance': '171.37', 'outHumidity': '77.89',
> 'outTemp': '13.52', 'pressure': '936.97', 'rain': '0.0', 'usUnits': '17',
> 'windDir': '45.0', 'windSpeed': '0.0'
> Oct 20 16:15:02 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> data-> final loop packet is enviro/river-wx 2023-10-20 16:15:00 EDT
> (1697832900): 'dateTime': '1697832900.6921751', 'luminance': '171.37',
> 'outHumidity': '77.89', 'outTemp': '13.52', 'pressure': '936.97', 'rain':
> '0.0', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '0.0'
> Oct 20 16:17:01 zero-wx CRON[1104]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0,
> retain: 0, payload: b'{"readings": {"pressure": 937.04, "rain": 2.5146,
> "wind_speed": 2.12127, "temperature": 13.6, "humidity": 77.04,
> "wind_direction": 45, "rain_per_second": 0.008381999, "luminance": 82.25},
> "nickname": "river-wx", "model": "weather", "uid": "e6614c311b62b034",
> "timestamp": "2023-10-20T20:20:05Z"}'
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> incoming enviro/river-wx: 'luminance': '82.25',
> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain':
> '2.5146', 'windDir': '45.0', 'windSpeed': '2.12127'
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> TopicManager data-> outgoing enviro/river-wx: 'dateTime':
> '1697833200.808235', 'luminance': '82.25', 'outHumidity': '77.04',
> 'outTemp': '13.6', 'pressure': '937.04', 'rain': '2.5146', 'usUnits': '17',
> 'windDir': '45.0', 'windSpeed': '2.12127'
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver)
> data-> final loop packet is enviro/river-wx 2023-10-20 16:20:00 EDT
> (1697833200): 'dateTime': '1697833200.808235', 'luminance': '82.25',
> 'outHumidity': '77.04', 'outTemp': '13.6', 'pressure': '937.04', 'rain':
> '2.5146', 'usUnits': '17', 'windDir': '45.0', 'windSpeed': '2.12127'
> Oct 20 16:20:00 zero-wx weewx[579] DEBUG user.MQTTSubscribe: (Driver) No
> archive topic configured.
> Oct 20 16:20:01 zero-wx weewx[579] INFO weewx.manager: Added record
> 2023-10-20 16:20:00 EDT (1697833200) to database 'weewx.sdb'
> Oct 20 16:20:02 zero-wx weewx[579] INFO weewx.manager: Added record
> 2023-10-20 16:20:00 EDT (1697833200) to daily summary in 'weewx.sdb'
> Oct 20 16:20:02 zero-wx weewx[579