Re: [weewx-user] Static image creation

[Ernest Jillson]

Well, it turns out steel gauges doesn't save the gauges as images.  Oh well.

On Mon, Jun 28, 2021 at 8:08 PM Ernest Jillson  wrote:

> Thanks, everyone.
>
> I will definitely need to grab some text from the feed or database, so
> either a simple skin or mqttwarn will work well for that. I have some
> experience with adding text to images using imagemagick. What I really
> would like is some dials. And I just came across a site with steel gauges
> that might be able to create the images I would like to add to the image
> background. Work keeps me busy, but I'm going to try to work on that a
> little at a time over the next few days.
>
> Ernie
>
> On Sun, Jun 27, 2021 at 10:53 PM Andrew Elwell 
> wrote:
>
>> On Mon, 28 Jun 2021 at 08:23, Ernest Jillson  wrote:
>> >
>> > Anyone know of any skins that can produce a static image with most
>> parameters in either text or dial format? The web pages are great, but I'd
>> love to find something that creates an image with T, MaxT, MinT, Wind,
>> Precip (at the least) and ftp it to a friend's web site.
>> >
>> > Thanks in advance,
>>
>> IThe box my webcam (actually a pi + pi camera) is on a different box
>> to my weewx host, I found the easiest way was to save the weather
>> conditions I was interested in via mqttwarn[1] which dumps it down to
>> a local file (since 'loop' outputs may not align with the timings when
>> I need to grab an image.
>>
>> The image is grabbed every 5 mins:
>> pi@stupify:~ $ crontab -l | grep cam
>> */5 5-20 * * * /home/pi/llamacam.py
>>
>> pi@stupify:~ $ cat /home/pi/llamacam.py
>> #!/usr/bin/python3
>> import io
>> import picamera
>> from PIL import Image
>> from PIL import ImageFont,ImageDraw
>> import time
>> import os
>>
>> temperaturefile = '/var/www/html/weewx/test.txt'
>> image_out = '/var/www/html/webcam/latest.jpg'
>>
>> text_overlay = '{}'.format(time.strftime('%a %Y-%m-%d %H:%M %Z'))
>> #print(os.path.getmtime(temperaturefile),time.time(),(time.time() -
>> os.path.getmtime(temperaturefile)))
>> if (time.time() - os.path.getmtime(temperaturefile)<= 300):
>> with open(temperaturefile, "r") as f:
>> temperature = float(f.read())
>> text_overlay += ', Outside Temp: {:.1f}°C'.format(temperature)
>> else:
>> text_overlay += ' (No temperature reading available)'
>>
>>
>> # Create the in-memory stream
>> stream = io.BytesIO()
>> with picamera.PiCamera() as camera:
>> camera.led = False
>> camera.resolution = (1920,1080)
>> camera.start_preview()
>> time.sleep(2)
>> camera.capture(stream, format='jpeg')
>> # "Rewind" the stream to the beginning so we can read its content
>> stream.seek(0)
>> image = Image.open(stream)
>>
>> # add logo to bottom rightt
>> overlay = Image.open("lw_logo.png");
>> image.paste(overlay, (1400,750 ), overlay)
>>
>> # add text too
>> font = ImageFont.truetype("Miriam.ttf", 36)
>> draw = ImageDraw.Draw(image)
>> draw.text((50, 1020), text_overlay, font=font, fill='rgb(0, 168, 162)')
>>
>> image.save(image_out)
>>
>>
>>
>>
>> And that dumps out the following image
>>
>>
>> [1] https://github.com/jpmens/mqttwarn
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAANX9yecbCTDTG3C5rezSqpftPcKZ%2BAZOcLOh43XqDw8caEufg%40mail.gmail.com
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAC5oUmMnvLYyOFPWAuAiig3uVAP3o7DEb2Z-e6ws0%2BFMPMtg2g%40mail.gmail.com.

RE: [weewx-user] Adding additional Fields

[purchase]

Ah, thanks. I couldn’t find that, my google skills suck!

 

Thanks again.

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Monday, June 28, 2021 7:02 PM
To: weewx-user 
Subject: Re: [weewx-user] Adding additional Fields

 

http://www.weewx.com/docs/customizing.htm#add_archive_type

 

On Mon, Jun 28, 2021 at 5:55 PM Mitchell Tuckness mailto:purch...@maladomini.com> > wrote:

Is there a way to easily add additional fields to the database? I don't know 
much about databases and management of them, but I got a few more sensors and 
it seems like the database doesn't have fields for the sensors.

 

I show the weewx database as having:

 

| archive_day_soilMoist1|

| archive_day_soilMoist2|

| archive_day_soilMoist3|

| archive_day_soilMoist4|

 

And I need to add:

| archive_day_soilMoist5|

| archive_day_soilMoist6|

| archive_day_soilMoist7|

| archive_day_soilMoist8|

 

Is there a way to do this easily, or is someone knows the commands to do to add 
them it would be appreciated if you could let me know how!

 

Thanks

-- 
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 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0fcadef0-aa56-43d6-8dee-7d452bcf579bn%40googlegroups.com
 

 .

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/d0T93MUE2ec/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDg-H%3DvgApSc8mjSUKMX7PfmnEh7euy-tK-VKde1soPrw%40mail.gmail.com
 

 .

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0b6501d76c84%24762c8130%2462858390%24%40maladomini.com.

Re: [weewx-user] Adding additional Fields

[Tom Keffer]

http://www.weewx.com/docs/customizing.htm#add_archive_type

On Mon, Jun 28, 2021 at 5:55 PM Mitchell Tuckness 
wrote:

> Is there a way to easily add additional fields to the database? I don't
> know much about databases and management of them, but I got a few more
> sensors and it seems like the database doesn't have fields for the sensors.
>
> I show the weewx database as having:
>
> | archive_day_soilMoist1|
> | archive_day_soilMoist2|
> | archive_day_soilMoist3|
> | archive_day_soilMoist4|
>
> And I need to add:
> | archive_day_soilMoist5|
> | archive_day_soilMoist6|
> | archive_day_soilMoist7|
> | archive_day_soilMoist8|
>
> Is there a way to do this easily, or is someone knows the commands to do
> to add them it would be appreciated if you could let me know how!
>
> Thanks
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0fcadef0-aa56-43d6-8dee-7d452bcf579bn%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDg-H%3DvgApSc8mjSUKMX7PfmnEh7euy-tK-VKde1soPrw%40mail.gmail.com.

[weewx-user] Adding additional Fields

[Mitchell Tuckness]

Is there a way to easily add additional fields to the database? I don't 
know much about databases and management of them, but I got a few more 
sensors and it seems like the database doesn't have fields for the sensors.

I show the weewx database as having:

| archive_day_soilMoist1|
| archive_day_soilMoist2|
| archive_day_soilMoist3|
| archive_day_soilMoist4|

And I need to add:
| archive_day_soilMoist5|
| archive_day_soilMoist6|
| archive_day_soilMoist7|
| archive_day_soilMoist8|

Is there a way to do this easily, or is someone knows the commands to do to 
add them it would be appreciated if you could let me know how!

Thanks

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0fcadef0-aa56-43d6-8dee-7d452bcf579bn%40googlegroups.com.

Re: [weewx-user] Static image creation

[Ernest Jillson]

Thanks, everyone.

I will definitely need to grab some text from the feed or database, so
either a simple skin or mqttwarn will work well for that. I have some
experience with adding text to images using imagemagick. What I really
would like is some dials. And I just came across a site with steel gauges
that might be able to create the images I would like to add to the image
background. Work keeps me busy, but I'm going to try to work on that a
little at a time over the next few days.

Ernie

On Sun, Jun 27, 2021 at 10:53 PM Andrew Elwell 
wrote:

> On Mon, 28 Jun 2021 at 08:23, Ernest Jillson  wrote:
> >
> > Anyone know of any skins that can produce a static image with most
> parameters in either text or dial format? The web pages are great, but I'd
> love to find something that creates an image with T, MaxT, MinT, Wind,
> Precip (at the least) and ftp it to a friend's web site.
> >
> > Thanks in advance,
>
> IThe box my webcam (actually a pi + pi camera) is on a different box
> to my weewx host, I found the easiest way was to save the weather
> conditions I was interested in via mqttwarn[1] which dumps it down to
> a local file (since 'loop' outputs may not align with the timings when
> I need to grab an image.
>
> The image is grabbed every 5 mins:
> pi@stupify:~ $ crontab -l | grep cam
> */5 5-20 * * * /home/pi/llamacam.py
>
> pi@stupify:~ $ cat /home/pi/llamacam.py
> #!/usr/bin/python3
> import io
> import picamera
> from PIL import Image
> from PIL import ImageFont,ImageDraw
> import time
> import os
>
> temperaturefile = '/var/www/html/weewx/test.txt'
> image_out = '/var/www/html/webcam/latest.jpg'
>
> text_overlay = '{}'.format(time.strftime('%a %Y-%m-%d %H:%M %Z'))
> #print(os.path.getmtime(temperaturefile),time.time(),(time.time() -
> os.path.getmtime(temperaturefile)))
> if (time.time() - os.path.getmtime(temperaturefile)<= 300):
> with open(temperaturefile, "r") as f:
> temperature = float(f.read())
> text_overlay += ', Outside Temp: {:.1f}°C'.format(temperature)
> else:
> text_overlay += ' (No temperature reading available)'
>
>
> # Create the in-memory stream
> stream = io.BytesIO()
> with picamera.PiCamera() as camera:
> camera.led = False
> camera.resolution = (1920,1080)
> camera.start_preview()
> time.sleep(2)
> camera.capture(stream, format='jpeg')
> # "Rewind" the stream to the beginning so we can read its content
> stream.seek(0)
> image = Image.open(stream)
>
> # add logo to bottom rightt
> overlay = Image.open("lw_logo.png");
> image.paste(overlay, (1400,750 ), overlay)
>
> # add text too
> font = ImageFont.truetype("Miriam.ttf", 36)
> draw = ImageDraw.Draw(image)
> draw.text((50, 1020), text_overlay, font=font, fill='rgb(0, 168, 162)')
>
> image.save(image_out)
>
>
>
>
> And that dumps out the following image
>
>
> [1] https://github.com/jpmens/mqttwarn
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAANX9yecbCTDTG3C5rezSqpftPcKZ%2BAZOcLOh43XqDw8caEufg%40mail.gmail.com
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAC5oUmO1NR42S0Ex1_jR02obe6AHNxjZFiDUcXjF88z8%2BLA_dg%40mail.gmail.com.

Re: [weewx-user] Re: lightning sensor made at home cheaply - WORKS!

[Eric K]

There we go!  
Now, I have proof its counting higher than 1!  :)


[image: AS3935 Lightning sensor working.PNG]

Here's my graph config from the Belchertown graphs.conf file:

*[[chart3]]*
*title = Lightning*
*[[[lightning_strike_count]]]*
*yAxis = 0*
*yAxis_label = "Number of Strikes"*
*stacking = normal*
*color = "orange"*
*lineWidth = 0*
*marker*
*enabled = true*
*radius = 4*
*states*
*[hover]*
*lineWidthPlus = 0*
*[[[lightning_distance]]]*
*yAxis = 1*
*yAxis_label = "Distance (miles)"*

*stacking = normal*
*color = "blue"*
*lineWidth = 0*
*marker*
*enabled = true*
*radius = 3*
*states*
*[hover]*
*lineWidthPlus = 0*

These are my settings in the Tasmota firmware for the AS3935:
17:48:03.739 CMD: AS3935settings
*17:48:03.753 MQT: tele/AS3935/RESULT = 
{"AS3935_Settings":{"Gain":"Indoors","NFfloor":7,"uVrms":146,"Tunecaps":2,"MinNumLight":1,"Rejection":2,"Wdthreshold":2,"MinNFstage":0,"NFAutoTime":4,"DisturberAutoTime":1,"Disturber":"On","NFauto":"Off","Disturberauto":"Off","NFautomax":"On","Mqttlightevent":"On","Mqttnoirqevent":"On"}}*
The last 2 surpress MQTT messages when there's no lightning events.
Reference:  https://tasmota.github.io/docs/AS3935/

There have been a LOT of close strikes detected in the last 15 mintues!
This is from the Tasmota console of the ESP-12F module (with AS3935 sensor 
connected):
17:58:07.173 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T17:58:07","AS3935":{"Event":4,"Distance":1,"Energy":372650,"Stage":7}}
17:58:34.168 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T17:58:34","AS3935":{"Event":4,"Distance":1,"Energy":155946,"Stage":7}}
17:59:36.153 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T17:59:36","AS3935":{"Event":4,"Distance":1,"Energy":0,"Stage":7}}
18:00:02.150 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:00:02","AS3935":{"Event":4,"Distance":1,"Energy":77455,"Stage":7}}
18:00:14.167 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:00:14","AS3935":{"Event":4,"Distance":1,"Energy":14477,"Stage":7}}
18:01:34.195 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:01:34","AS3935":{"Event":4,"Distance":1,"Energy":16,"Stage":7}}
18:01:54.162 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:01:54","AS3935":{"Event":4,"Distance":1,"Energy":42975,"Stage":7}}
18:02:33.154 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:02:33","AS3935":{"Event":4,"Distance":1,"Energy":55903,"Stage":7}}
18:04:02.170 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:04:02","AS3935":{"Event":4,"Distance":1,"Energy":59064,"Stage":7}}
18:04:26.163 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:04:26","AS3935":{"Event":4,"Distance":1,"Energy":0,"Stage":7}}
18:04:45.170 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:04:45","AS3935":{"Event":4,"Distance":1,"Energy":25788,"Stage":7}}
18:05:12.146 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:05:12","AS3935":{"Event":4,"Distance":1,"Energy":22788,"Stage":7}}
18:05:50.188 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:05:50","AS3935":{"Event":4,"Distance":1,"Energy":17632,"Stage":7}}
18:07:22.161 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:07:22","AS3935":{"Event":4,"Distance":1,"Energy":51215,"Stage":7}}
18:08:29.185 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:08:29","AS3935":{"Event":4,"Distance":1,"Energy":62226,"Stage":7}}
18:08:34.168 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:08:34","AS3935":{"Event":4,"Distance":1,"Energy":148630,"Stage":7}}
18:08:40.172 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:08:40","AS3935":{"Event":4,"Distance":1,"Energy":25560,"Stage":7}}
18:11:16.176 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:11:16","AS3935":{"Event":4,"Distance":1,"Energy":208620,"Stage":7}}
18:12:17.187 MQT: tele/AS3935/SENSOR = 
{"Time":"2021-06-28T18:12:17","AS3935":{"Event":4,"Distance":1,"Energy":67149,"Stage":7}}

On Monday, June 28, 2021 at 5:51:11 PM UTC-5 Eric K wrote:

> IT'S WORKING!  
> There is another thunderstorm approaching and it's capturing distances AND 
> strike count!
> [image: image.png]
>
>
> On Mon, Jun 28, 2021 at 1:45 PM Eric Koester  wrote:
>
>> Thanks for that idea, Rich.
>>
>> Yesterday, I opened up the AS3935_Event to allow event 4 to pass through, 
>> because event 4 is "storm overhead".
>> So, now the AS3935_Event message could contain a 1 or a 4.
>>
>> *[[[AS3935_Event]]]*
>> *filter_out_message_when = 0, 2, 3, 5, 6, 7, 8, 9*
>> *conversion_type = int*
>>
>> I am trying this correction to change the event number to be a 1.
>>
>> *[StdCalibrate]*
>> *[[Corrections]]*
>>
>> *outTemp = outTemp - 1.5*
>> *barometer = barometer + 1.23*
>> *lightning_strik

Re: [weewx-user] wmr100.py / OverflowError: mktime argument out of range

[Tom Keffer]

For some reason, your WMR200 emitted a clock packet with some bad numbers
in it. Try this version of wmr100.py. It catches and logs the error, rather
than crashing. Let me know how it works.

-tk


On Tue, Jun 22, 2021 at 3:19 AM markusk  wrote:

>
> weewx with WMRS200 running fine since january - anyone got an idea why i
> got this tonight and/or how to avoid it?:
>
>
> Jun 22 00:35:16 raspberrypi weewx[21495] INFO weewx.manager: Added record
> 2021-06-22 00:35:00 CEST (1624314900) to database 'weewx.sdb'
> Jun 22 00:35:16 raspberrypi weewx[21495] INFO weewx.manager: Added record
> 2021-06-22 00:35:00 CEST (1624314900) to daily summary in 'weewx.sdb'
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:15:19: New
> client connected from 172.18.0.1 as weewx_698a3f6e (p2, c1, k60).
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:15:19: Client
> weewx_698a3f6e disconnected.
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:20:17: New
> client connected from 172.18.0.1 as weewx_4b5f85fb (p2, c1, k60).
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:20:17: Client
> weewx_4b5f85fb disconnected.
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:25:18: New
> client connected from 172.18.0.1 as weewx_e92e6132 (p2, c1, k60).
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:25:18: Client
> weewx_e92e6132 disconnected.
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:30:20: New
> client connected from 172.18.0.1 as weewx_8d9f7aa4 (p2, c1, k60).
> Jun 22 00:35:16 raspberrypi 34110015c165[628]: 2021-06-21T22:30:20: Client
> weewx_8d9f7aa4 disconnected.
> Jun 22 00:35:16 raspberrypi weewx[21495] INFO weewx.restx: MQTT: Published
> record 2021-06-22 00:35:00 CEST (1624314900)
> Jun 22 00:35:16 raspberrypi weewx[21495] INFO weewx.restx: OWM: Published
> record 2021-06-22 00:35:00 CEST (1624314900)
> Jun 22 00:35:16 raspberrypi weewx[21495] INFO weewx.restx: PWSWeather:
> Published record 2021-06-22 00:35:00 CEST (1624314900)
> Jun 22 00:35:17 raspberrypi weewx[21495] INFO weewx.cheetahgenerator:
> Generated 8 files for report SeasonsReport in 1.60 seconds
> Jun 22 00:35:18 raspberrypi weewx[21495] INFO weewx.imagegenerator:
> Generated 16 images for report SeasonsReport in 0.69 seconds
> Jun 22 00:35:18 raspberrypi weewx[21495] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Jun 22 00:35:18 raspberrypi weewx[21495] INFO weewx.cheetahgenerator:
> Generated 1 files for report MobileReport in 0.03 seconds
> Jun 22 00:35:18 raspberrypi weewx[21495] INFO weewx.imagegenerator:
> Generated 4 images for report MobileReport in 0.13 seconds
> Jun 22 00:35:18 raspberrypi weewx[21495] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx/mobile
> Jun 22 00:35:20 raspberrypi weewx[21495] INFO weewx.cheetahgenerator:
> Generated 11 files for report Belchertown in 1.88 seconds
> Jun 22 00:35:20 raspberrypi weewx[21495] INFO weewx.reportengine: Copied 2
> files to /var/www/html/weewx/belchertown
> Jun 22 00:36:07 raspberrypi kernel: [9277996.404380] brcmfmac:
> brcmf_cfg80211_set_power_mgmt: power save enabled
> Jun 22 00:40:24 raspberrypi weewx[21495] INFO weewx.manager: Added record
> 2021-06-22 00:40:00 CEST (1624315200) to database 'weewx.sdb'
> Jun 22 00:40:24 raspberrypi weewx[21495] INFO weewx.manager: Added record
> 2021-06-22 00:40:00 CEST (1624315200) to daily summary in 'weewx.sdb'
> Jun 22 00:40:24 raspberrypi weewx[21495] INFO weewx.restx: MQTT: Published
> record 2021-06-22 00:40:00 CEST (1624315200)
> Jun 22 00:40:24 raspberrypi weewx[21495] INFO weewx.restx: OWM: Published
> record 2021-06-22 00:40:00 CEST (1624315200)
> Jun 22 00:40:24 raspberrypi weewx[21495] INFO weewx.restx: PWSWeather:
> Published record 2021-06-22 00:40:00 CEST (1624315200)
> Jun 22 00:40:25 raspberrypi weewx[21495] INFO weewx.cheetahgenerator:
> Generated 8 files for report SeasonsReport in 1.54 seconds
> Jun 22 00:40:26 raspberrypi weewx[21495] INFO weewx.imagegenerator:
> Generated 16 images for report SeasonsReport in 0.72 seconds
> Jun 22 00:40:26 raspberrypi weewx[21495] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Jun 22 00:40:26 raspberrypi weewx[21495] INFO weewx.cheetahgenerator:
> Generated 1 files for report MobileReport in 0.03 seconds
> Jun 22 00:40:26 raspberrypi weewx[21495] INFO weewx.imagegenerator:
> Generated 4 images for report MobileReport in 0.13 seconds
> Jun 22 00:40:26 raspberrypi weewx[21495] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx/mobile
> Jun 22 00:40:28 raspberrypi weewx[21495] INFO weewx.cheetahgenerator:
> Generated 11 files for report Belchertown in 1.63 seconds
> Jun 22 00:40:28 raspberrypi weewx[21495] INFO weewx.reportengine: Copied 2
> files to /var/www/html/weewx/belchertown
> Jun 22 00:41:07 raspberrypi weewx[21495] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Jun 22 00:41:07 raspberrypi weewx[21495] INFO weewx.engine: Shutt

Re: [weewx-user] Re: lightning sensor made at home cheaply

[Eric Koester]

IT'S WORKING!
There is another thunderstorm approaching and it's capturing distances AND
strike count!
[image: image.png]


On Mon, Jun 28, 2021 at 1:45 PM Eric Koester  wrote:

> Thanks for that idea, Rich.
>
> Yesterday, I opened up the AS3935_Event to allow event 4 to pass through,
> because event 4 is "storm overhead".
> So, now the AS3935_Event message could contain a 1 or a 4.
>
> *[[[AS3935_Event]]]*
> *filter_out_message_when = 0, 2, 3, 5, 6, 7, 8, 9*
> *conversion_type = int*
>
> I am trying this correction to change the event number to be a 1.
>
> *[StdCalibrate]*
> *[[Corrections]]*
>
> *outTemp = outTemp - 1.5*
> *barometer = barometer + 1.23*
> *lightning_strike_count = 1 if AS3935_Event > 0 else None*
>
> I'll report back on the results.
>
>
>
>
>
> On Mon, Jun 28, 2021 at 1:15 PM bell...@gmail.com 
> wrote:
>
>> Eric,
>> I would think just renaming AS3935_Event to lightning_strike_count (via
>> name = lightning_strike_count) should work. This gets the value into the
>> WeeWX pipeline and since lightning_strike_count has a default accumulator
>> that extracts the sum, you should be all set. Meaning something like this.
>> AS3935_Event
>>   # MQTT messages with and event value in the following will be ignored.
>>   filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
>>   conversion_type = int
>>   name = lightning_strike_count
>> rich
>>
>> On Sunday, 27 June 2021 at 19:15:41 UTC-4 Eric K wrote:
>>
>>> Reference:  https://github.com/weewx/weewx/wiki/Accumulators
>>>
>>> 1. It says that lightning_strike_count is one of the default accumulator
>>> variables, so I believe that means I do NOT need to declare it in an
>>> [Accumulators] section of weewx.conf?
>>>
>>> 2. Where do I put the code that alerts WeeWX that a lightning strike
>>> occurred?
>>> In the [MQTTSubscribeService] section of the weewx.conf file?
>>>
>>> 3. How do I tell WeeWX that a lightning strike has occurred?
>>> Set lightning_strike_count =1 and let the accumulator function add 1 to
>>> the total for me?
>>>
>>> Like this?
>>>
>>> [MQTTSubscribeService]
>>>
>>> [[[tele/AS3935/SENSOR]]]
>>> Time
>>> ignore = true
>>>
>>> AS3935_Event
>>> # Use the default variable name from MQTT
>>> # MQTT messages with and event value in the following
>>> will be ignored.
>>> filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
>>> conversion_type = int
>>> *lightning_strike_count = 1*
>>>
>>> AS3935_Distance
>>> # Use the default variable name from MQTT.
>>>
>>> AS3935_Energy
>>> name = lightning_energy
>>>
>>> AS3935_Stage
>>> ignore = true
>>> On Friday, June 25, 2021 at 8:15:48 PM UTC-5 Eric K wrote:
>>>
 I've made some progress and I have MQTT messages getting received into
 MQTTSubscribe and put into the weewx database file!

 Here's the relevant section from the MQTTSubscribe section of
 weewx.conf:

 *[MQTTSubscribeService]*

 *enable = true*

 *host = localhost*

 *port = 1883*

 *keepalive = 60*

 *username = None*

 *password = None*

 *binding = loop*

 *[[message_callback]]*

 *type = json*

 *[[[tele/AS3935/SENSOR]]]*
 *Time*
 *ignore = true*

 *AS3935_Event*
 *# Use the default variable name from MQTT*
 *# MQTT messages with and event value in the following
 will be ignored.*
 *filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9*
 *conversion_type = int*

 *AS3935_Distance*
 *# Use the default variable name from MQTT.*

 *AS3935_Energy*
 *name = lightning_energy*

 *AS3935_Stage*
 *ignore = true*

 Here are a few lines from the /var/log/syslog showing the AS3935
 messages coming in and getting conditionally ignored.
 So, we know that part is working.


 *Jun 25 19:50:46 pi3 weewx[31711] DEBUG user.MQTTSubscribe: (Service)
 MessageCallbackProvider data-> incoming topic: tele/AS3935/SENSOR, QOS: 0,
 retain: 0, payload:
 b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'*
 *Jun 25 19:50:46 pi3 weewx[31711] INFO user.MQTTSubscribe: (Service)
 MessageCallbackProvider on_message_json filtered out tele/AS3935/SENSOR :
 b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'
 with AS3935_Event=[0, 2, 3, 4, 5, 6, 7, 8, 9]*

 Then, in the Corrections section of weewx.c

[weewx-user] Re: Using two station sources into a single instance of WeeWx

[weewx-user]

one approach looks something like this:

1) run two instances of weewx, one for the vantage, and one for the airmar.

weewxd /etc/weewx/vantage.conf
weewxd /etc/weewx/airmar.conf

be sure that the two configuration files refer to:
 - separate databases, e.g., /var/lib/weewx/vantage.sdb and 
var/lib/weewx/airmar.sdb
 - separate HTML_ROOT, e.g., /var/www/vantage and /var/www/airmar

that way you can verify that each component works, no matter how you might 
combine data later

2) create a skin that combines the data, with a structure like this:

mkdir /etc/weewx/skins/combined
/etc/weewx/skins/combined/skin.conf
/etc/weewx/skins/combined/index.html.tmpl

the skin.conf will indicate different databases for images, like this:

[ImageGenerator]
...
[[day_images]]
# show barameter from both stations in the barometer graph
[[[daybarometer]]]
vantage
data_binding = vantage_binding
data_type = barometer
label = vantage
airmar
data_binding = airmar_binding
data_type = barometer
label = airmar
# show only airmar in the wind graph
[[[daywindspeed]]]
windSpeed
data_binding = airmar_binding
windGust
data_binding = airmar_binding

the index.html.tmpl will use data bindings for any references to variables 
(see the customization guide for the syntax for that).


3) create a config file, say 'combined.conf', just for generating reports 
from the combined databases.

...
[Station] 
...
station_type = unspecified

[StdReport]
[[combined]] 
skin = combined

[DataBindings]
[[vantage_binding]]
database = vantage_sqlite
manager = weewx.wxmanager.WXDaySummaryManager
table_name = archive
schema = schemas.wview.schema
[[airmar_binding]]
database = vantage_sqlite
manager = weewx.wxmanager.WXDaySummaryManager
table_name = archive
schema = schemas.wview.schema

[Databases]
[[vantage_sqlite]]
database_name = vantage.sdb
database_type = SQLite
[[airmar_sqlite]]
database_name = airmar.sdb
database_type = SQLite

4) finally, run wee_reports regularly (e.g., via cron) with your combined 
config file (and customized skin)

wee_reports /etc/weewx/combined.conf

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e1fd92aa-3440-4b91-92c6-d4dd39ea61e9n%40googlegroups.com.

Re: [weewx-user] Re: lightning sensor made at home cheaply

[Eric Koester]

Thanks for that idea, Rich.

Yesterday, I opened up the AS3935_Event to allow event 4 to pass through,
because event 4 is "storm overhead".
So, now the AS3935_Event message could contain a 1 or a 4.

*[[[AS3935_Event]]]*
*filter_out_message_when = 0, 2, 3, 5, 6, 7, 8, 9*
*conversion_type = int*

I am trying this correction to change the event number to be a 1.

*[StdCalibrate]*
*[[Corrections]]*

*outTemp = outTemp - 1.5*
*barometer = barometer + 1.23*
*lightning_strike_count = 1 if AS3935_Event > 0 else None*

I'll report back on the results.





On Mon, Jun 28, 2021 at 1:15 PM bell...@gmail.com 
wrote:

> Eric,
> I would think just renaming AS3935_Event to lightning_strike_count (via
> name = lightning_strike_count) should work. This gets the value into the
> WeeWX pipeline and since lightning_strike_count has a default accumulator
> that extracts the sum, you should be all set. Meaning something like this.
> AS3935_Event
>   # MQTT messages with and event value in the following will be ignored.
>   filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
>   conversion_type = int
>   name = lightning_strike_count
> rich
>
> On Sunday, 27 June 2021 at 19:15:41 UTC-4 Eric K wrote:
>
>> Reference:  https://github.com/weewx/weewx/wiki/Accumulators
>>
>> 1. It says that lightning_strike_count is one of the default accumulator
>> variables, so I believe that means I do NOT need to declare it in an
>> [Accumulators] section of weewx.conf?
>>
>> 2. Where do I put the code that alerts WeeWX that a lightning strike
>> occurred?
>> In the [MQTTSubscribeService] section of the weewx.conf file?
>>
>> 3. How do I tell WeeWX that a lightning strike has occurred?
>> Set lightning_strike_count =1 and let the accumulator function add 1 to
>> the total for me?
>>
>> Like this?
>>
>> [MQTTSubscribeService]
>>
>> [[[tele/AS3935/SENSOR]]]
>> Time
>> ignore = true
>>
>> AS3935_Event
>> # Use the default variable name from MQTT
>> # MQTT messages with and event value in the following
>> will be ignored.
>> filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
>> conversion_type = int
>> *lightning_strike_count = 1*
>>
>> AS3935_Distance
>> # Use the default variable name from MQTT.
>>
>> AS3935_Energy
>> name = lightning_energy
>>
>> AS3935_Stage
>> ignore = true
>> On Friday, June 25, 2021 at 8:15:48 PM UTC-5 Eric K wrote:
>>
>>> I've made some progress and I have MQTT messages getting received into
>>> MQTTSubscribe and put into the weewx database file!
>>>
>>> Here's the relevant section from the MQTTSubscribe section of weewx.conf:
>>>
>>> *[MQTTSubscribeService]*
>>>
>>> *enable = true*
>>>
>>> *host = localhost*
>>>
>>> *port = 1883*
>>>
>>> *keepalive = 60*
>>>
>>> *username = None*
>>>
>>> *password = None*
>>>
>>> *binding = loop*
>>>
>>> *[[message_callback]]*
>>>
>>> *type = json*
>>>
>>> *[[[tele/AS3935/SENSOR]]]*
>>> *Time*
>>> *ignore = true*
>>>
>>> *AS3935_Event*
>>> *# Use the default variable name from MQTT*
>>> *# MQTT messages with and event value in the following
>>> will be ignored.*
>>> *filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9*
>>> *conversion_type = int*
>>>
>>> *AS3935_Distance*
>>> *# Use the default variable name from MQTT.*
>>>
>>> *AS3935_Energy*
>>> *name = lightning_energy*
>>>
>>> *AS3935_Stage*
>>> *ignore = true*
>>>
>>> Here are a few lines from the /var/log/syslog showing the AS3935
>>> messages coming in and getting conditionally ignored.
>>> So, we know that part is working.
>>>
>>>
>>> *Jun 25 19:50:46 pi3 weewx[31711] DEBUG user.MQTTSubscribe: (Service)
>>> MessageCallbackProvider data-> incoming topic: tele/AS3935/SENSOR, QOS: 0,
>>> retain: 0, payload:
>>> b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'*
>>> *Jun 25 19:50:46 pi3 weewx[31711] INFO user.MQTTSubscribe: (Service)
>>> MessageCallbackProvider on_message_json filtered out tele/AS3935/SENSOR :
>>> b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'
>>> with AS3935_Event=[0, 2, 3, 4, 5, 6, 7, 8, 9]*
>>>
>>> Then, in the Corrections section of weewx.conf, I am using a conditional
>>> statement to assign the AS3935 distance data to the weewx stock variable
>>> lightning_distance.
>>> I wasn't sure if my syntax was correct, but lightning distance data is
>>> appearing in the weewx database, so it appears to be working.
>>>
>>> *[StdCalibrate]*
>>>
>>> *[[Corrections]]*
>>>
>>> * 

[weewx-user] Re: lightning sensor made at home cheaply

[bell...@gmail.com]

Eric,
I would think just renaming AS3935_Event to lightning_strike_count (via 
name = lightning_strike_count) should work. This gets the value into the 
WeeWX pipeline and since lightning_strike_count has a default accumulator 
that extracts the sum, you should be all set. Meaning something like this.
AS3935_Event
  # MQTT messages with and event value in the following will be ignored.
  filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
  conversion_type = int
  name = lightning_strike_count
rich

On Sunday, 27 June 2021 at 19:15:41 UTC-4 Eric K wrote:

> Reference:  https://github.com/weewx/weewx/wiki/Accumulators
>
> 1. It says that lightning_strike_count is one of the default accumulator 
> variables, so I believe that means I do NOT need to declare it in an 
> [Accumulators] section of weewx.conf?
>
> 2. Where do I put the code that alerts WeeWX that a lightning strike 
> occurred?
> In the [MQTTSubscribeService] section of the weewx.conf file?
>
> 3. How do I tell WeeWX that a lightning strike has occurred?
> Set lightning_strike_count =1 and let the accumulator function add 1 to 
> the total for me?
>
> Like this?
>
> [MQTTSubscribeService]
>
> [[[tele/AS3935/SENSOR]]]
> Time
> ignore = true
>
> AS3935_Event
> # Use the default variable name from MQTT
> # MQTT messages with and event value in the following will 
> be ignored.
> filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
> conversion_type = int
> *lightning_strike_count = 1*
>
> AS3935_Distance
> # Use the default variable name from MQTT.
>
> AS3935_Energy
> name = lightning_energy
>
> AS3935_Stage
> ignore = true
> On Friday, June 25, 2021 at 8:15:48 PM UTC-5 Eric K wrote:
>
>> I've made some progress and I have MQTT messages getting received into 
>> MQTTSubscribe and put into the weewx database file!
>>
>> Here's the relevant section from the MQTTSubscribe section of weewx.conf:
>>
>> *[MQTTSubscribeService]*
>>
>> *enable = true*
>>
>> *host = localhost*
>>
>> *port = 1883*
>>
>> *keepalive = 60*
>>
>> *username = None*
>>
>> *password = None*
>>
>> *binding = loop*
>>
>> *[[message_callback]]*
>>
>> *type = json*
>>
>> *[[[tele/AS3935/SENSOR]]]*
>> *Time*
>> *ignore = true*
>>
>> *AS3935_Event*
>> *# Use the default variable name from MQTT*
>> *# MQTT messages with and event value in the following 
>> will be ignored.*
>> *filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9*
>> *conversion_type = int*
>>
>> *AS3935_Distance*
>> *# Use the default variable name from MQTT.*
>>
>> *AS3935_Energy*
>> *name = lightning_energy*
>>
>> *AS3935_Stage*
>> *ignore = true*
>>
>> Here are a few lines from the /var/log/syslog showing the AS3935 messages 
>> coming in and getting conditionally ignored.
>> So, we know that part is working.
>>
>>
>> *Jun 25 19:50:46 pi3 weewx[31711] DEBUG user.MQTTSubscribe: (Service) 
>> MessageCallbackProvider data-> incoming topic: tele/AS3935/SENSOR, QOS: 0, 
>> retain: 0, payload: 
>> b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'*
>> *Jun 25 19:50:46 pi3 weewx[31711] INFO user.MQTTSubscribe: (Service) 
>> MessageCallbackProvider on_message_json filtered out tele/AS3935/SENSOR : 
>> b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'
>>  
>> with AS3935_Event=[0, 2, 3, 4, 5, 6, 7, 8, 9]*
>>
>> Then, in the Corrections section of weewx.conf, I am using a conditional 
>> statement to assign the AS3935 distance data to the weewx stock variable 
>> lightning_distance.
>> I wasn't sure if my syntax was correct, but lightning distance data is 
>> appearing in the weewx database, so it appears to be working.
>>
>> *[StdCalibrate]*
>>
>> *[[Corrections]]*
>>
>> *outTemp = outTemp - 1.5*
>> *barometer = barometer + 1.23*
>> *lightning_distance = AS3935_Distance if AS3935_Event == 1 else 
>> None*
>>
>> Finally, I looked in the weewx.sdb database file and saw 3 lightning 
>> events listed in the variables lightning_distance and lightning_energy!
>> See attached.
>>
>> I don't have the lightning_strike_count getting accumulated, yethave 
>> to try and figure out which of the accumulator type to use.
>>
>> Progress.
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, June 16, 2021 at 1:37:57 PM UTC-5 Eric K wrote:
>>
>>> Very cool, Rich!
>>> I'll put some effort into it.
>>>
>>> Based on your earlier coaching, I've been able to successfully accept 
>>> MQTT data from every sensor I've tried, includ

[weewx-user] Re: lightning sensor made at home cheaply

[bell...@gmail.com]

Eric,
That is great that you have something working.* Since it is working, I 
wouldn't change anything*. But, I am surprised that you needed 
'lightning_distance = AS3935_Distance if AS3935_Event == 1 else None'  in 
the StdCalibrate section. With MQTTSubscribe filtering by event values, I 
would have thought the following would have been enough.
AS3935_Distance
  name = lightning_distance

Anyway, happy to hear that have something working. 
rich

On Sunday, 27 June 2021 at 19:15:41 UTC-4 Eric K wrote:

> Reference:  https://github.com/weewx/weewx/wiki/Accumulators
>
> 1. It says that lightning_strike_count is one of the default accumulator 
> variables, so I believe that means I do NOT need to declare it in an 
> [Accumulators] section of weewx.conf?
>
> 2. Where do I put the code that alerts WeeWX that a lightning strike 
> occurred?
> In the [MQTTSubscribeService] section of the weewx.conf file?
>
> 3. How do I tell WeeWX that a lightning strike has occurred?
> Set lightning_strike_count =1 and let the accumulator function add 1 to 
> the total for me?
>
> Like this?
>
> [MQTTSubscribeService]
>
> [[[tele/AS3935/SENSOR]]]
> Time
> ignore = true
>
> AS3935_Event
> # Use the default variable name from MQTT
> # MQTT messages with and event value in the following will 
> be ignored.
> filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9
> conversion_type = int
> *lightning_strike_count = 1*
>
> AS3935_Distance
> # Use the default variable name from MQTT.
>
> AS3935_Energy
> name = lightning_energy
>
> AS3935_Stage
> ignore = true
> On Friday, June 25, 2021 at 8:15:48 PM UTC-5 Eric K wrote:
>
>> I've made some progress and I have MQTT messages getting received into 
>> MQTTSubscribe and put into the weewx database file!
>>
>> Here's the relevant section from the MQTTSubscribe section of weewx.conf:
>>
>> *[MQTTSubscribeService]*
>>
>> *enable = true*
>>
>> *host = localhost*
>>
>> *port = 1883*
>>
>> *keepalive = 60*
>>
>> *username = None*
>>
>> *password = None*
>>
>> *binding = loop*
>>
>> *[[message_callback]]*
>>
>> *type = json*
>>
>> *[[[tele/AS3935/SENSOR]]]*
>> *Time*
>> *ignore = true*
>>
>> *AS3935_Event*
>> *# Use the default variable name from MQTT*
>> *# MQTT messages with and event value in the following 
>> will be ignored.*
>> *filter_out_message_when = 0, 2, 3, 4, 5, 6, 7, 8, 9*
>> *conversion_type = int*
>>
>> *AS3935_Distance*
>> *# Use the default variable name from MQTT.*
>>
>> *AS3935_Energy*
>> *name = lightning_energy*
>>
>> *AS3935_Stage*
>> *ignore = true*
>>
>> Here are a few lines from the /var/log/syslog showing the AS3935 messages 
>> coming in and getting conditionally ignored.
>> So, we know that part is working.
>>
>>
>> *Jun 25 19:50:46 pi3 weewx[31711] DEBUG user.MQTTSubscribe: (Service) 
>> MessageCallbackProvider data-> incoming topic: tele/AS3935/SENSOR, QOS: 0, 
>> retain: 0, payload: 
>> b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'*
>> *Jun 25 19:50:46 pi3 weewx[31711] INFO user.MQTTSubscribe: (Service) 
>> MessageCallbackProvider on_message_json filtered out tele/AS3935/SENSOR : 
>> b'{"Time":"2021-06-25T19:50:46","AS3935":{"Event":0,"Distance":0,"Energy":0,"Stage":7}}'
>>  
>> with AS3935_Event=[0, 2, 3, 4, 5, 6, 7, 8, 9]*
>>
>> Then, in the Corrections section of weewx.conf, I am using a conditional 
>> statement to assign the AS3935 distance data to the weewx stock variable 
>> lightning_distance.
>> I wasn't sure if my syntax was correct, but lightning distance data is 
>> appearing in the weewx database, so it appears to be working.
>>
>> *[StdCalibrate]*
>>
>> *[[Corrections]]*
>>
>> *outTemp = outTemp - 1.5*
>> *barometer = barometer + 1.23*
>> *lightning_distance = AS3935_Distance if AS3935_Event == 1 else 
>> None*
>>
>> Finally, I looked in the weewx.sdb database file and saw 3 lightning 
>> events listed in the variables lightning_distance and lightning_energy!
>> See attached.
>>
>> I don't have the lightning_strike_count getting accumulated, yethave 
>> to try and figure out which of the accumulator type to use.
>>
>> Progress.
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, June 16, 2021 at 1:37:57 PM UTC-5 Eric K wrote:
>>
>>> Very cool, Rich!
>>> I'll put some effort into it.
>>>
>>> Based on your earlier coaching, I've been able to successfully accept 
>>> MQTT data from every sensor I've tried, including from a Sonoff Zigbee 
>>> Bridge with a bunch of 

Re: [weewx-user] Re: The data statement stopped

[Blaise Cacramp]

Ok, I understood what the "dump" does
(It's in progress)

Le 28-06-21 à 11:03, gjr80 a écrit :
The link I provided had two distinct steps. First removing the 
batteries from the console to reset the console, if that does not help 
then the second step is to use wee_device to first dump the logger 
contents (this is important as it maximises the chance of recovering 
missing data) and then clear the logger memory. Did you do any of 
these steps? What were the results? Note you need to stop WeeWX before 
running wee_device.


I don’t see how plugging in another station will recover any missing 
data, at best you will have a mix of data from two different stations


--
Cet email a fait l'objet d'une analyse antivirus par AVG.
http://www.avg.com

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/db44524f-b616-4375-b2be-0ba28438d731%40gmail.com.

[weewx-user] Re: The data statement stopped

[gjr80]

The link I provided had two distinct steps. First removing the batteries 
from the console to reset the console, if that does not help then the 
second step is to use wee_device to first dump the logger contents (this is 
important as it maximises the chance of recovering missing data) and then 
clear the logger memory. Did you do any of these steps? What were the 
results? Note you need to stop WeeWX before running wee_device.

I don’t see how plugging in another station will recover any missing data, 
at best you will have a mix of data from two different stations.

Gary
On Monday, 28 June 2021 at 18:48:41 UTC+10 blaise@gmail.com wrote:

> Well,
> Restart is not enough. I have a second small terminal (Vantage Vue). Can I 
> plug it instead of the big time to recover missing data?
>
> Le lundi 28 juin 2021 à 09:48:14 UTC+2, gjr80 a écrit :
>
>> It may be corrupt station memory. Try working through the steps under 
>> Corrupt 
>> station memory 
>> 
>>  in 
>> the Troubleshooting Davis stations 
>> 
>>  wiki 
>> entry.
>>
>> Gary
>>
>> On Monday, 28 June 2021 at 17:05:32 UTC+10 blaise@gmail.com wrote:
>>
>>>
>>> Hello,
>>> The data statement stopped yesterday at 15:20 UTC 0
>>> I do not really understand.
>>> Files: 
>>> https://drive.google.com/drive/folders/1htphBZfpfKex7CCh6Uq8_jS_lJd7_Wuz?usp=sharing
>>>
>>> Well to you,
>>> PC
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/45338199-241d-471c-be4c-ac41948777f0n%40googlegroups.com.

[weewx-user] Re: The data statement stopped

[P C]

Well,
Restart is not enough. I have a second small terminal (Vantage Vue). Can I 
plug it instead of the big time to recover missing data?

Le lundi 28 juin 2021 à 09:48:14 UTC+2, gjr80 a écrit :

> It may be corrupt station memory. Try working through the steps under Corrupt 
> station memory 
> 
>  in 
> the Troubleshooting Davis stations 
> 
>  wiki 
> entry.
>
> Gary
>
> On Monday, 28 June 2021 at 17:05:32 UTC+10 blaise@gmail.com wrote:
>
>>
>> Hello,
>> The data statement stopped yesterday at 15:20 UTC 0
>> I do not really understand.
>> Files: 
>> https://drive.google.com/drive/folders/1htphBZfpfKex7CCh6Uq8_jS_lJd7_Wuz?usp=sharing
>>
>> Well to you,
>> PC
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/728f291e-7967-4f5c-8880-f37f9ba322fen%40googlegroups.com.

[weewx-user] Re: The data statement stopped

[gjr80]

It may be corrupt station memory. Try working through the steps under Corrupt 
station memory 

 in 
the Troubleshooting Davis stations 

 wiki 
entry.

Gary

On Monday, 28 June 2021 at 17:05:32 UTC+10 blaise@gmail.com wrote:

>
> Hello,
> The data statement stopped yesterday at 15:20 UTC 0
> I do not really understand.
> Files: 
> https://drive.google.com/drive/folders/1htphBZfpfKex7CCh6Uq8_jS_lJd7_Wuz?usp=sharing
>
> Well to you,
> PC

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2230c865-1d86-4e1c-bb38-0788aa440d52n%40googlegroups.com.

[weewx-user] The data statement stopped

[P C]

Hello,
The data statement stopped yesterday at 15:20 UTC 0
I do not really understand.
Files: 
https://drive.google.com/drive/folders/1htphBZfpfKex7CCh6Uq8_jS_lJd7_Wuz?usp=sharing

Well to you,
PC

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0ad54113-1091-431e-a27b-9dbff2d978efn%40googlegroups.com.