[weewx-user] Database entries

[Daidl Himself]

Hi,
I got a GW2000 and several sensors and use them with the gw1000 driver. So 
far so good, the most temeratures and stuff is automatically logged fine. 
But, I would like to see trends from the battery values as well. Searching 
in the manuals let me learn, the data needs to be mapped to a field, either 
creating new ones, or map to existing ones, which are "free". So, I checked 
the "schemas.wview_extended.schema" that is used an made some mappings in 
the weewx.conf: 






































*[GW1000]# This section is for the Ecowitt Gateway driver.# How 
often to poll the API, default is every 20 seconds:poll_interval = 20  
  # The driver to use:driver = user.gw1000ip_address = 
192.168.179.113port = 45000show_all_batt = True
[[field_map_extensions]]extraTemp8 = temp9rain = 
p_rainstormRain = p_raineventrainRate = p_rainrate
dayRain = p_raindayweekRain = p_rainweekmonthRain = 
p_rainmonthyearRain = p_rainyearBatteryStatus1 = ws90_batt  
  BatteryStatus2 = wh51_ch1_battBatteryStatus3 = wh51_ch2_batt  
  BatteryStatus4 = wn34_ch1_batt BatteryStatus5 = wh45_batt 
BatteryStatus6 = wh75_ch1_batt signal1 = ws90_sig signal2 = 
wh51_ch1_sig signal3 = wh51_ch2_sig signal4 = wn34_ch1_sig 
signal5 = wh45_sig signal6 = wh31_ch1_sig signal7 = wh31_ch2_sig   
  signal8 = wh31_ch3_sig*

The Temperature and the rain data is all fine, but the battery data can be 
shown as $latest and $current, but the image generator just produced empty 
fields. Looks for me, as the "BatteryStatus" fields are not storred in the 
database. How can I advice this, and how can I check if there are already 
part of a group (I would guess energy would make sense, as the value is 
Volt)

thanks a lot by the way, for this fantastic peace of software and user 
friendly documentation.



-- 
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/437461fd-ddf9-49c6-a10b-a8ba8737690fn%40googlegroups.com.

Re: [weewx-user] Database entries

['Rainer Lang' via weewx-user]

in principle all seems to be correct in weewx.conf

now, how to check the database: get yourself the sqlitebrowser and look 
it up yourself


sudo apt-get install sqlitebrowser

 you will have to load your database and you can see everything, all 
records etc.


but you may have a unit problem as the Ecowitt battery status comes over 
either as integer values (0, 1, 2, 3) or as voltage e.g. 1.64


As far as I know Gary has described this in the Ecowitt Gateway WiKi

therefore the units to be used (which may be different from 
wsview_extended schema) need to be added to

extensions.py

https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states

and make sure you have the respective entries in your extension.py

e.g.
weewx.units.obs_group_dict['wh51_ch1_batt'] = 'group_volt'
weewx.units.obs_group_dict['wn34_ch1_batt'] = 'group_volt'

and
weewx.units.obs_group_dict['wh31_ch1_batt'] = 'group_count'
etc.

the signal levels should also belong to group_count

try that ...


On 10.08.2023 10:48, Daidl Himself wrote:

Hi,
I got a GW2000 and several sensors and use them with the gw1000 
driver. So far so good, the most temeratures and stuff is 
automatically logged fine.
But, I would like to see trends from the battery values as well. 
Searching in the manuals let me learn, the data needs to be mapped to 
a field, either creating new ones, or map to existing ones, which are 
"free". So, I checked the "schemas.wview_extended.schema" that is used 
an made some mappings in the weewx.conf:



/[GW1000]
    # This section is for the Ecowitt Gateway driver.

    # How often to poll the API, default is every 20 seconds:
    poll_interval = 20

    # The driver to use:
    driver = user.gw1000
    ip_address = 192.168.179.113
    port = 45000

    show_all_batt = True

    [[field_map_extensions]]

        extraTemp8 = temp9
        rain = p_rain
        stormRain = p_rainevent
        rainRate = p_rainrate
        dayRain = p_rainday
        weekRain = p_rainweek
        monthRain = p_rainmonth
        yearRain = p_rainyear
        BatteryStatus1 = ws90_batt
        BatteryStatus2 = wh51_ch1_batt
        BatteryStatus3 = wh51_ch2_batt
        BatteryStatus4 = wn34_ch1_batt
    BatteryStatus5 = wh45_batt
    BatteryStatus6 = wh75_ch1_batt
    signal1 = ws90_sig
    signal2 = wh51_ch1_sig
    signal3 = wh51_ch2_sig
    signal4 = wn34_ch1_sig
    signal5 = wh45_sig
    signal6 = wh31_ch1_sig
    signal7 = wh31_ch2_sig
    signal8 = wh31_ch3_sig/

The Temperature and the rain data is all fine, but the battery data 
can be shown as $latest and $current, but the image generator just 
produced empty fields. Looks for me, as the "BatteryStatus" fields are 
not storred in the database. How can I advice this, and how can I 
check if there are already part of a group (I would guess energy would 
make sense, as the value is Volt)


thanks a lot by the way, for this fantastic peace of software and user 
friendly documentation.


--
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/437461fd-ddf9-49c6-a10b-a8ba8737690fn%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/c70d2781-c886-7e6c-d81d-71a37f1d788e%40gmail.com.

RE: [weewx-user] Re: weewx with rtl-davis - Installation Assistance?

[John Argue]

Not yet – busy in summer but have acquired a raspberry pi 4 and will try it 
with the script as soon as things settle down a bit.

 

From: weewx-user@googlegroups.com  On Behalf Of 
Rob Fissel
Sent: August 5, 2023 8:54 AM
To: weewx-user 
Subject: [weewx-user] Re: weewx with rtl-davis - Installation Assistance?

 

Did you have any luck with this? I'm facing a similar problem. 

On Saturday, April 1, 2023 at 10:38:15 AM UTC-4 arg...@xplornet.ca 
  wrote:

I have tried installing rtldavis on both a pi3+ and a debian 11 proxmox vm.  I 
have no problems with receiving packets from a Davis Vue - packets are 
consistently received every 3 seconds or so and look correct.  However - on 
both machines I get the same error (which you would expect - consistently 
wrong)!!

 

weewx doesn't appear to process the packets from the rtldavis driver and errors 
out every 150 seconds with  the following error:

 

 INFO weewx.engine: Main loop exiting. Shutting engine down.

debian weewx[10816] INFO user.rtldavis: shutdown process 
/home/pi/work/bin/rtldavis -tf US -tr 1
debian weewx[10816] INFO user.rtldavis: rtldavis with pid 11073 killed
 debian weewx[10816] CRITICAL __main__: Caught WeeWxIOError: rtldavis process 
stalled

 

Has anyone successfully installed rtldavis recently and can help with this 
issue?

 

I used vince skahans install script modified to use golang-1.15 - see attached.

I set LD_LIBRARY_PATH to the librtlsdr.so instance

weewx.conf points to rtldavis as station type.

user pi is member of sudoers 

I have also included the syslog of the installation, the install script and 
weewx.conf

 

I am not a proficient user of Debian - any suggestions gratefully received.

 

-- 
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/bGiQPuOljqs/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/08137d3c-da45-4821-aeec-92b9f9fd5cd4n%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/01d9cb84%245b4a5520%2411deff60%24%40xplornet.ca.

Re: [weewx-user] Database entries

[Daidl Himself]

Hi,

thats sounds good, and sqlightbrowser tells me the BatterieStatus fiels are 
empty, most likely a type mismatch as you say. 
Just wonder, if I map wh51_ch1_batt to  * BatteryStatus2*,  I need to 
mention  * BatteryStatus2* in extension.py. righ?



Rainer Lang schrieb am Donnerstag, 10. August 2023 um 12:51:54 UTC+2:

> in principle all seems to be correct in weewx.conf
>
> now, how to check the database: get yourself the sqlitebrowser and look it 
> up yourself
>
> sudo apt-get install sqlitebrowser 
>
>  you will have to load your database and you can see everything, all 
> records etc.
>
> but you may have a unit problem as the Ecowitt battery status comes over 
> either as integer values (0, 1, 2, 3) or as voltage e.g. 1.64
>
> As far as I know Gary has described this in the Ecowitt Gateway WiKi
>
> therefore the units to be used (which may be different from 
> wsview_extended schema) need to be added to 
> extensions.py
>
> https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states
>
> and make sure you have the respective entries in your extension.py
>
> e.g.
> weewx.units.obs_group_dict['wh51_ch1_batt'] = 'group_volt'
> weewx.units.obs_group_dict['wn34_ch1_batt'] = 'group_volt'
>
> and
> weewx.units.obs_group_dict['wh31_ch1_batt'] = 'group_count'
> etc.
>
> the signal levels should also belong to group_count
>
> try that ...
>
>
> On 10.08.2023 10:48, Daidl Himself wrote:
>
> Hi,
> I got a GW2000 and several sensors and use them with the gw1000 driver. So 
> far so good, the most temeratures and stuff is automatically logged fine. 
> But, I would like to see trends from the battery values as well. Searching 
> in the manuals let me learn, the data needs to be mapped to a field, either 
> creating new ones, or map to existing ones, which are "free". So, I checked 
> the "schemas.wview_extended.schema" that is used an made some mappings in 
> the weewx.conf: 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[GW1000] # This section is for the Ecowitt Gateway driver. # 
> How often to poll the API, default is every 20 seconds: poll_interval = 
> 20 # The driver to use: driver = user.gw1000 ip_address = 
> 192.168.179.113 port = 45000 show_all_batt = True 
> [[field_map_extensions]] extraTemp8 = temp9 rain = 
> p_rain stormRain = p_rainevent rainRate = p_rainrate   
>   dayRain = p_rainday weekRain = p_rainweek monthRain = 
> p_rainmonth yearRain = p_rainyear BatteryStatus1 = 
> ws90_batt BatteryStatus2 = wh51_ch1_batt BatteryStatus3 = 
> wh51_ch2_batt BatteryStatus4 = wn34_ch1_batt BatteryStatus5 = 
> wh45_batt BatteryStatus6 = wh75_ch1_batt signal1 = ws90_sig 
> signal2 = wh51_ch1_sig signal3 = wh51_ch2_sig signal4 = 
> wn34_ch1_sig signal5 = wh45_sig signal6 = wh31_ch1_sig signal7 
> = wh31_ch2_sig signal8 = wh31_ch3_sig*
>
> The Temperature and the rain data is all fine, but the battery data can be 
> shown as $latest and $current, but the image generator just produced empty 
> fields. Looks for me, as the "BatteryStatus" fields are not storred in the 
> database. How can I advice this, and how can I check if there are already 
> part of a group (I would guess energy would make sense, as the value is 
> Volt)
>
> thanks a lot by the way, for this fantastic peace of software and user 
> friendly documentation.
>
> 
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/437461fd-ddf9-49c6-a10b-a8ba8737690fn%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/002dccfa-1e56-4c8d-8cdb-44fbd8e9285cn%40googlegroups.com.

Re: [weewx-user] Database entries

['Rainer Lang' via weewx-user]

If the predefined unit of a database field changes (i.e. you want it to 
be changed), weewx needs to be told how to interprete the value stored 
in this field.
Entries in extensions.py will override the default unit definitions 
weewx keeps in a table at runtime (the obs_group_dict).


E.g.
you have more than 4 soil moisture sensors
SM1 - SM4 you can simply assign to the wsview_extended database field 
soilMoist1-4
but you have 6 SM sensors and want to use the soilTemp1-2 fields to 
store the values
be it via a field_map_extension or via an assignment in [StdCalibrate] 
[[Corrections]]


the default unit for SoilTemp1 is degree_celsius - you want it to be 
percent, you enter in extensions.py

weewx.units.obs_group_dict['soilTemp1'] = 'group_percent'

you have to make an entry for each database field whose unit 
interpretation you want to change

weewx.units.obs_group_dict['soilTemp2'] = 'group_percent'
as you want to use the database fields SoilTemp1 and SoilTemp2, but 
don't want °C to be shown in the reports


so it's always the database field name

in the above example - the default unit for soilMoisture1-4 is cb 
(centibar) which is the unit group "group_moisture" - you may want it to 
be percent as we did for SM5-6

then you will have to add 4 entries to extensions.py
weewx.units.obs_group_dict['soilMoist1'] = 'group_percent'
weewx.units.obs_group_dict['soilMoist2'] = 'group_percent'
weewx.units.obs_group_dict['soilMoist3'] = 'group_percent'
weewx.units.obs_group_dict['soilMoist4'] = 'group_percent'

If you have only 2 WH51 and want to display their readings in percent, 
you only need the first two entries


now you should know which field name to put in extensions.py for your 
WH51 battery status ... 😎


changes in extensions.py become only effective after a restart of weewx !

On 10.08.2023 17:06, Daidl Himself wrote:

Hi,

thats sounds good, and sqlightbrowser tells me the BatterieStatus 
fiels are empty, most likely a type mismatch as you say.
Just wonder, if I map wh51_ch1_batt to /BatteryStatus2/,  I need to 
mention /BatteryStatus2/ in extension.py. righ?




Rainer Lang schrieb am Donnerstag, 10. August 2023 um 12:51:54 UTC+2:

in principle all seems to be correct in weewx.conf

now, how to check the database: get yourself the sqlitebrowser and
look it up yourself

sudo apt-get install sqlitebrowser

 you will have to load your database and you can see everything,
all records etc.

but you may have a unit problem as the Ecowitt battery status
comes over either as integer values (0, 1, 2, 3) or as voltage
e.g. 1.64

As far as I know Gary has described this in the Ecowitt Gateway WiKi

therefore the units to be used (which may be different from
wsview_extended schema) need to be added to
extensions.py

https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states

and make sure you have the respective entries in your extension.py

e.g.
weewx.units.obs_group_dict['wh51_ch1_batt'] = 'group_volt'
weewx.units.obs_group_dict['wn34_ch1_batt'] = 'group_volt'

and
weewx.units.obs_group_dict['wh31_ch1_batt'] = 'group_count'
etc.

the signal levels should also belong to group_count

try that ...


On 10.08.2023 10:48, Daidl Himself wrote:

Hi,
I got a GW2000 and several sensors and use them with the gw1000
driver. So far so good, the most temeratures and stuff is
automatically logged fine.
But, I would like to see trends from the battery values as well.
Searching in the manuals let me learn, the data needs to be
mapped to a field, either creating new ones, or map to existing
ones, which are "free". So, I checked the
"schemas.wview_extended.schema" that is used an made some
mappings in the weewx.conf:


/[GW1000]
    # This section is for the Ecowitt Gateway driver.

    # How often to poll the API, default is every 20 seconds:
    poll_interval = 20

    # The driver to use:
    driver = user.gw1000
    ip_address = 192.168.179.113
    port = 45000

    show_all_batt = True

    [[field_map_extensions]]

        extraTemp8 = temp9
        rain = p_rain
        stormRain = p_rainevent
        rainRate = p_rainrate
        dayRain = p_rainday
        weekRain = p_rainweek
        monthRain = p_rainmonth
        yearRain = p_rainyear
        BatteryStatus1 = ws90_batt
        BatteryStatus2 = wh51_ch1_batt
        BatteryStatus3 = wh51_ch2_batt
        BatteryStatus4 = wn34_ch1_batt
BatteryStatus5 = wh45_batt
BatteryStatus6 = wh75_ch1_batt
    signal1 = ws90_sig
    signal2 = wh51_ch1_sig
    signal3 = wh51_ch2_sig
    signal4 = wn34_ch1_sig
    signal5 = wh45_sig
    signal6 = wh31_ch1_sig
    signal7 = wh31_ch2_sig
    signal8 = wh31_ch3_sig/

The Temperature and the rain data is all fine, but the battery
data can be shown as $latest an

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Wow - thanks, Tom!

That actually sound pretty straight forward and almost too easy ;)
Once I have the GPS receiver hooked up to my LTE router; I will try it out!

😇

On Wed, Aug 9, 2023 at 5:54 PM Tom Keffer  wrote:

> One way of doing this...
>
> Station altitude, latitude, and longitude are always obtained from an
> instance of StationInfo
> ,
> held in the engine. From this, various views are constructed, including
> what's used as a tag, such as $station.altitude.
>
> So, with every new archive record you could replace that instance with a
> fresh instance, created in a WeeWX service, using updated values.
> The instance is available as engine.stn_info in the service.
>
> How does your service get its information? One way would be to add new
> observation types altitude, latitude, and longitude to the archive record.
> Then your new service can get the values from there.
>
> If you also want values in the database, add altitude,  longitude, and
> latitude to the schema and they will automatically be populated if the
> archive record holds matching types.
>
> That's off the top of my head. It's a nice approach because it does not
> involve modifying any base weewx code. But, I'm sure I've missed
> something...
>
> -tk
>
>
> On Wed, Aug 9, 2023 at 8:00 AM Stefan Gliessmann <
> stefan.gliessm...@gmail.com> wrote:
>
>> After running into major issues with my LTE router in my RV, weewx and
>> Belchertown w/ MQTT are up and running :)
>> Check it out here: https://t.ly/4icFe
>>
>> My RV router is actually a serious professional LTE router which can
>> provide GPS data, too (once I have a GPs receiver installed).
>> Now, I still have to figure out how to push the GPS data into weewx db
>> and have weewx use it for the weather forecasts using aeris within the
>> Belchertown skin.
>> Since I have MQTT already working and my router can send the GPS data as
>> MQTT packages, maybe that is a way to do so.
>> In weewx.conf the long, latitude and altitude are specified. Is there a
>> way to not update these in the weewx.conf, but have them read from the db
>> and considered accordingly?
>>
>> Thanks for brainstorming this with me ;)
>>
>> TIA,
>> Stefan
>>
>> On Monday, July 31, 2023 at 4:25:05 AM UTC+2 Cameron D wrote:
>>
>>> This would be my suggestion as well.  Certainly use a dedicated DB for
>>> the task, then populate it according to the effort you want to put into it.
>>> Options would be:
>>>
>>>- custom GPS unit along the lines Vince suggested
>>>- use a normal in-car GPS unit that records your tracks and
>>>download/export data each day.  I combine my car and walking gps tracks 
>>> for
>>>geotagging photos.
>>>- manually enter data once a day
>>>
>>> When I do long trips, I often take a simple handheld temp/RH logger that
>>> I download occasionally - every few days.
>>> I also have a second table with one row per day, where I manually enter
>>> comments about where the device was located and anything unusual that might
>>> have influenced the results.  Probably less necessary in an RV with fixed
>>> locations, but my logger might end up left inside the tent, outside the
>>> tent, or left inside the car on different days.  This table could also
>>> double as a more general diary.
>>>
>>> On Sunday, 30 July 2023 at 6:39:28 am UTC+10 vince wrote:
>>>
 On Saturday, July 29, 2023 at 1:11:25 PM UTC-7 Stefan Gliessmann wrote:

 That would work. But I would miss out on the location and elevation
 data … I would like to include location in a database …


 Sure. Get a GPS module for your pi and write a little script to seed a
 custom field in the db.   Shouldn't be a big deal.  Just write to a
 secondary sqlite db.



>>> --
>> 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/c0a89ba0-e981-4e58-8a3b-9412bbd0b1c4n%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/Fwd1BvCfCoM/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/CAPq0zECNoy6YbZTHN7DvwhN0n0SEJF5AR4GYEWEjf0hdkomcAA%40mail.gmail.com
> 

Re: [weewx-user] Installing weewx without root access

[Matthew Fields]

Thanks. Will see if that route works a bit better... Was definitely 
figuring I'd have to do something with cron to get it running on boot.

On Wednesday, August 9, 2023 at 11:50:44 PM UTC-4 vince wrote:

> If you're willing to do so, the easiest way is to install the v5 beta via 
> 'pip' within a python virtual environment, as that defaults to running 
> without any privileges required.   Getting it to startup on boot might be 
> your only issue that I can think of.  I suppose you could write yourself a 
> crontab entry that runs as you on boot as one approach you might try.
>
> On Wednesday, August 9, 2023 at 7:26:11 PM UTC-7 Graham Eddy wrote:
>
>> read up on python ‘virtual environment’ (venv) to get your libraries etc 
>> in place.
>> running it while not logged in - best way depends upon your o/s (eg user 
>> mode of systemd)
>> *⊣GE⊢*
>>
>> On 10 Aug 2023, at 2:06 am, Matthew Fields  wrote:
>>
>> Might seem like an odd request, but I'm trying to find some guidance on 
>> installing weewx as a normal user on a shared linux host without root 
>> access.
>>
>> I'll be using websockets to get weather station data (Tempest 
>> Weatherflow), so I don't need serial or USB access on the server. My goal 
>> is to have weewx run on a shared cloud webserver (hosted by Bluehost). As a 
>> shared server, I do not have root access so I have to run it as a normal 
>> user.
>>
>> I have access to the compiler, so I've been trying to install with the 
>> python installation instructions. I manage to get everything installed, 
>> though I keep running into a lot of fun trying getting weewx to run. I'm 
>> sure it has to be configuration settings I need to make, missing python 
>> modules, etc.
>>
>> Rather than beating my head endlessly, has anyone installed weewx in a 
>> shared environment without root access (like bluehost)? Anyone know of any 
>> installation guidance for such an environment?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4272f256-db69-4a31-ae68-956f2ba6a6dcn%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/35ac45a1-01fd-46f2-9755-5192b5ebff69n%40googlegroups.com.

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[michael.k...@gmx.at]

Is [[Corrections]] in the hierarchy below  [StdCalibrate]?

Like this:

[StdCalibrate]
[[Corrections]]
lightning_distance = lightning_distance if lightning_strike_count > 
0 else None

If yes and you don't find a solution, post your whole weewx.conf as an 
attachment, but don't forget to obfuscate any sensitive data like logins, 
passwords etc. before uploading.
Stefan Gliessmann schrieb am Donnerstag, 10. August 2023 um 18:40:44 UTC+2:

> The correction was in weewx.conf (and I just restarted weewx another 
> time), but it still shows the distance from earlier this week.
> I also added the Accumulator from last to min for lighting_distance.
>
> Still no change in the graph ...
>
> This is in graph.conf for Belchertown skin:
>
> [[chart6]]
> title = Lightning
> [[[lightning_strike_count]]]
> yAxis = 0
> yAxis_min = 0
> yAxis_tickInterval = 1
> 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_min = 0
> yAxis_label = "Distance (km)"
>
> stacking = normal
> color = "blue"
> lineWidth = 0
> marker
> enabled = true
> radius = 3
> states
> [hover]
> lineWidthPlus = 0
>
> This is in weewx.conf:
>
> [[Corrections]]
> lightning_distance = lightning_distance if lightning_strike_count 
> > 0 else None
>
> and
>
> [Accumulator]
>
> # Start Ecowitt Gateway driver extractors
> [[daymaxwind]]
> extractor = last
> [[lightning_distance]]
> extractor = min
> [[lightning_strike_count]]
> extractor = sum
> [[lightningcount]]
> extractor = last
> [[lightning_last_det_time]]
> extractor = last
>
> and what it looks like:
>
> [image: Screenshot 2023-08-10 at 18.30.15.png]
>
> being in sync w/ the db ...
>
> [image: Screenshot 2023-08-10 at 18.32.26.png]
>
> I continue to be puzzled ...
>
> Any additional ideas what I should check?
>
> TIA,
> Stefan
>
>
> On Thu, Aug 10, 2023 at 5:47 PM Stefan Gliessmann  
> wrote:
>
>> Hmm - it looks different in my sdb ...
>>
>> [image: Screenshot 2023-08-10 at 17.43.28.png]
>>
>> I will double check if I added the correction lightning_distance = 
>> lightning_distance if lightning_strike_count > 0 else None correctly in 
>> weewx.conf ...
>>
>>
>> On Wed, Aug 9, 2023 at 6:40 PM michael.k...@gmx.at  
>> wrote:
>>
>>> I have an ecowitt WH57 and exactly the same correction 
>>> term: lightning_distance = lightning_distance if lightning_strike_count > 0 
>>> else None
>>> [image: 2023-08-09 18_35_16-The weather in AT, Salzburg, Hallein, Rif - 
>>> Brave.png]
>>>
>>> And just a few mintues ago, there were lightnings detected:
>>>
>>> The little yellow dot between 25 and 30km. 
>>>
>>>
>>> I've queried the database:
>>> select datetime, lightning_distance, lightning_strike_count from archive 
>>> order by datetime desc;
>>>
>>> [image: 2023-08-09 18_37_13-Window.png]
>>> Just as excpected.
>>>
>>> I don't know how your chart handles this, the above chart is a scatter 
>>> chart with the lightning distance on the y-axis and the size of the dot is 
>>> equivalent to the lightning_strike_count. What does your database show with 
>>> the above query?
>>> Stefan Gliessmann schrieb am Mittwoch, 9. August 2023 um 16:49:45 UTC+2:
>>>
 Hello everybody ;)

 I have a smilier issue with last lightning distance been charted ...
 I used the above information to generate my chart which looks like this:

 [image: Screenshot 2023-08-09 at 16.43.03.png]

 This is with 
 [[Corrections]]
 lightning_distance = lightning_distance if 
 lightning_strike_count > 0 else None

 I do not have an AcuRite, but an Ecowitt lightning detector ...

 Any hint to have the distance been zero when there isn't and lightning 
 would be appreciated.

 TIA,
 Stefan
 On Thursday, June 15, 2023 at 6:03:12 AM UTC+2 William Reading wrote:

> I was going to submit a pull request to fix this and realized that the 
> Atlas driver uses "strike_count" and the rest of them use 
> "strikes_total", 
> so fixing the defaults would be a breaking change. I went ahead and just 
> put the delta in my weewx.conf file to work around it.
>
> [[sensor_map]]
> ...
> atlas_lightning_strike_count = strike_count..AcuriteAtlasPacket
> ...
>
> [[deltas]]
> lightning_strike_count = atlas_lightning_strike_count
> On Wednesday, June 14, 2023 at 12:5

Re: [weewx-user] Database entries

[Daidl Himself]

Great, got it. You made my day :-)

Rainer Lang schrieb am Donnerstag, 10. August 2023 um 17:38:34 UTC+2:

> If the predefined unit of a database field changes (i.e. you want it to be 
> changed), weewx needs to be told how to interprete the value stored in this 
> field.
> Entries in extensions.py will override the default unit definitions weewx 
> keeps in a table at runtime (the obs_group_dict). 
>
> E.g. 
> you have more than 4 soil moisture sensors
> SM1 - SM4 you can simply assign to the wsview_extended database field 
> soilMoist1-4
> but you have 6 SM sensors and want to use the soilTemp1-2 fields to store 
> the values
> be it via a field_map_extension or via an assignment in [StdCalibrate] 
> [[Corrections]]
>
> the default unit for SoilTemp1 is degree_celsius - you want it to be 
> percent, you enter in extensions.py
> weewx.units.obs_group_dict['soilTemp1'] = 'group_percent'
>
> you have to make an entry for each database field whose unit 
> interpretation you want to change
> weewx.units.obs_group_dict['soilTemp2'] = 'group_percent'
> as you want to use the database fields SoilTemp1 and SoilTemp2, but don't 
> want °C to be shown in the reports
>
> so it's always the database field name
>
> in the above example - the default unit for soilMoisture1-4 is cb 
> (centibar) which is the unit group "group_moisture" - you may want it to be 
> percent as we did for SM5-6
> then you will have to add 4 entries to extensions.py
> weewx.units.obs_group_dict['soilMoist1'] = 'group_percent'
> weewx.units.obs_group_dict['soilMoist2'] = 'group_percent'
> weewx.units.obs_group_dict['soilMoist3'] = 'group_percent'
> weewx.units.obs_group_dict['soilMoist4'] = 'group_percent'
>
> If you have only 2 WH51 and want to display their readings in percent, you 
> only need the first two entries
>
> now you should know which field name to put in extensions.py for your WH51 
> battery status ... 😎
>
> changes in extensions.py become only effective after a restart of weewx !
> On 10.08.2023 17:06, Daidl Himself wrote:
>
> Hi,
>
> thats sounds good, and sqlightbrowser tells me the BatterieStatus fiels 
> are empty, most likely a type mismatch as you say. 
> Just wonder, if I map wh51_ch1_batt to  * BatteryStatus2*,  I need to 
> mention  * BatteryStatus2* in extension.py. righ?
>
>
>
> Rainer Lang schrieb am Donnerstag, 10. August 2023 um 12:51:54 UTC+2:
>
>> in principle all seems to be correct in weewx.conf
>>
>> now, how to check the database: get yourself the sqlitebrowser and look 
>> it up yourself
>>
>> sudo apt-get install sqlitebrowser 
>>
>>  you will have to load your database and you can see everything, all 
>> records etc.
>>
>> but you may have a unit problem as the Ecowitt battery status comes over 
>> either as integer values (0, 1, 2, 3) or as voltage e.g. 1.64
>>
>> As far as I know Gary has described this in the Ecowitt Gateway WiKi
>>
>> therefore the units to be used (which may be different from 
>> wsview_extended schema) need to be added to 
>> extensions.py
>>
>> https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states
>>
>> and make sure you have the respective entries in your extension.py
>>
>> e.g.
>> weewx.units.obs_group_dict['wh51_ch1_batt'] = 'group_volt'
>> weewx.units.obs_group_dict['wn34_ch1_batt'] = 'group_volt'
>>
>> and
>> weewx.units.obs_group_dict['wh31_ch1_batt'] = 'group_count'
>> etc.
>>
>> the signal levels should also belong to group_count
>>
>> try that ...
>>
>>
>> On 10.08.2023 10:48, Daidl Himself wrote:
>>
>> Hi,
>> I got a GW2000 and several sensors and use them with the gw1000 driver. 
>> So far so good, the most temeratures and stuff is automatically logged 
>> fine. 
>> But, I would like to see trends from the battery values as well. 
>> Searching in the manuals let me learn, the data needs to be mapped to a 
>> field, either creating new ones, or map to existing ones, which are "free". 
>> So, I checked the "schemas.wview_extended.schema" that is used an made some 
>> mappings in the weewx.conf: 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *[GW1000] # This section is for the Ecowitt Gateway driver. # 
>> How often to poll the API, default is every 20 seconds: poll_interval = 
>> 20 # The driver to use: driver = user.gw1000 ip_address = 
>> 192.168.179.113 port = 45000 show_all_batt = True 
>> [[field_map_extensions]] extraTemp8 = temp9 rain = 
>> p_rain stormRain = p_rainevent rainRate = p_rainrate   
>>   dayRain = p_rainday weekRain = p_rainweek monthRain = 
>> p_rainmonth yearRain = p_rainyear BatteryStatus1 = 
>> ws90_batt BatteryStatus2 = wh51_ch1_batt BatteryStatus3 = 
>> wh51_ch2_batt BatteryStatus4 = wn34_ch1_batt BatteryStatus5 = 
>> wh45_batt BatteryStatus6 = wh75_ch1_batt signal1 = ws90_sig 
>> signal2 = wh51_ch1_sig   

Re: [weewx-user] Re: weewx with rtl-davis - Installation Assistance?

[vince]

FWIW - I did get this to work on v5 beta with some tweaks in my install 
script solely due to the weewx commands being a little different than v4 
and earlier, but it was a little bit of a struggle here too.   I had to do 
a lot of plugging/unplugging the rtl_sdr dongle as it seemed to lock up 
with device in use when I was trying to run things in the foreground. 

Eventually weewx succeed interactively before I tried it from systemd

(weewx-venv) pi@pi4jr:~/weewx-data $ weewxd
LOOP:   2023-08-10 12:41:54 PDT (1691696514) 'altimeter': 'None', 
'appTemp': 'None', 'barometer': 'None', 'cloudbase': 'None', 'dateTime': 
'1691696514', 'dewpoint': 'None', 'ET': 'None', 'heatindex': 'None', 
'humidex': 'None', 'inDewpoint': 'None', 'maxSolarRad': '0.0', 'pressure': 
'None', 'rainRate': '0.0', 'txBatteryStatus': '0', 'usUnits': '1', 
'windchill': 'None', 'windDir': '325.3162055335968', 'windrun': 'None', 
'windSpeed': '2.0'
LOOP:   2023-08-10 12:41:57 PDT (1691696517) 'altimeter': 'None', 
'appTemp': 'None', 'barometer': 'None', 'cloudbase': 'None', 'dateTime': 
'1691696517', 'dewpoint': 'None', 'ET': 'None', 'heatindex': 'None', 
'humidex': 'None', 'inDewpoint': 'None', 'maxSolarRad': '0.0', 'outTemp': 
'70.1', 'pressure': 'None', 'rainRate': '0.0', 'txBatteryStatus': '0', 
'usUnits': '1', 'windchill': '70.1', 'windDir': '325.3162055335968', 
'windrun': 'None', 'windSpeed': '2.0'

In repeated previous repetitions I got the following and needed to 
unplug/replug it to get it to release. 

(weewx-venv) pi@pi4jr:~/weewx-data $ rtldavis -tf US -v -tr 1
12:40:37.537010 rtldavis.go VERSION=0.15
12:40:37.537808 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=0 receiveWindow=300 
actChan=[0] maxChan=1
12:40:37.537957 undefined=false verbose=true disableAfc=false deviceString=0
12:40:37.539019 BitRate: 19200
12:40:37.539132 SymbolLength: 14
12:40:37.539222 SampleRate: 268800
12:40:37.539704 Preamble: 1100101110001001
12:40:37.539840 PreambleSymbols: 16
12:40:37.539941 PreambleLength: 224
12:40:37.540165 PacketSymbols: 80
12:40:37.540687 PacketLength: 1120
12:40:37.540778 BlockSize: 512
12:40:37.540866 BufferLength: 2048
usb_claim_interface error -6
12:40:37.603160 resource busy

Also saw the same 'killed' thing you saw:

(weewx-venv) pi@pi4jr:~/weewx-data $ rtldavis -tf US -v
12:35:28.026250 rtldavis.go VERSION=0.15
12:35:28.026668 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=0 receiveWindow=300 
actChan=[0] maxChan=1
12:35:28.026720 undefined=false verbose=true disableAfc=false deviceString=0
12:35:28.026986 BitRate: 19200
12:35:28.027010 SymbolLength: 14
12:35:28.027031 SampleRate: 268800
12:35:28.027051 Preamble: 1100101110001001
12:35:28.027071 PreambleSymbols: 16
12:35:28.027091 PreambleLength: 224
12:35:28.027111 PacketSymbols: 80
12:35:28.027131 PacketLength: 1120
12:35:28.027151 BlockSize: 512
12:35:28.027171 BufferLength: 2048
Detached kernel driver
Found Rafael Micro R820T tuner
12:35:28.488329 tr=0 ch=0 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
0 0 0 0 0 0 0 0]
12:35:28.488722 Hop: {ChannelIdx:0 ChannelFreq:902419338 FreqError:0 
Transmitter:0}
Exact sample rate is: 268800.001367 Hz
12:35:28.667136 GetTunerGain: 0 Db
12:35:28.667276 SetFreqCorrection 0 ppm Successful
12:35:28.671473 Init channels: wait max 135 seconds for a message of each 
transmitter
12:37:30.504786 m1: -0.217316 l: 224 c: 16 x: [-0.31 -0.28 -0.30 -0.28 0.21 
0.19 0.11 -0.35 -0.34 -0.28 -0.33 -0.33 -0.30 -0.28 -0.31 -0.30]
12:37:30.504885 TRANSMITTER 0 SEEN
12:37:30.505103 tr=0 ch=19 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
0 0 0 0 0 0 0 0]
12:37:30.505277 Hop: {ChannelIdx:19 ChannelFreq:911952597 FreqError:0 
Transmitter:0}
12:37:30.505324 applied freqCorrection=0
12:37:33.068797 m1: -0.211359 l: 224 c: 16 x: [0.13 -0.32 -0.30 -0.28 -0.21 
0.22 0.08 -0.37 -0.35 -0.33 -0.27 -0.27 -0.26 -0.29 -0.32 -0.26]
12:37:33.068901 E000E9780100BE3D 2 0 0 0 0 msg.ID=0
12:37:33.068981 tr=0 ch=41 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
0 0 0 0 0 0 0 0]
12:37:33.069075 Hop: {ChannelIdx:41 ChannelFreq:922991108 FreqError:0 
Transmitter:0}
12:37:33.069125 applied freqCorrection=0
12:37:35.630621 m1: -0.129377 l: 224 c: 16 x: [-0.18 0.21 0.20 0.17 0.16 
0.12 -0.01 -0.36 -0.32 -0.33 -0.32 -0.26 -0.31 -0.28 -0.29 -0.28]
12:37:35.630806 5000E9FF7100F302 3 0 0 0 0 msg.ID=0
12:37:35.630935 tr=0 ch=25 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
0 0 0 0 0 0 0 0]
12:37:35.631082 Hop: {ChannelIdx:25 ChannelFreq:914963100 FreqError:0 
Transmitter:0}
12:37:35.631177 applied freqCorrection=0
12:37:38.192505 m1: -0.248779 l: 224 c: 16 x: [-0.33 -0.30 -0.27 -0.25 
-0.13 0.09 -0.29 -0.30 -0.30 -0.26 -0.28 -0.30 -0.27 -0.26 -0.27 -0.25]
12:37:38.192952 9000E905018E11BE 4 0 0 0 0 msg.ID=0
12:37:38.193281 tr=0 ch=8 freqCorr=0 lastFreqError=0, freqerrTrChList=[0 0 
0 0 0 0 0 0 0 0]
12:37:38.193627 Hop: {ChannelIdx:8 ChannelFreq:906433342 FreqError:0 
Transmitter:0}
12:37:38.193682 applied freqCorrection=0
Killed

And...

Aug 10 12:42:15 pi4jr weewx[478] INFO

[weewx-user] rtl_davis logging pct good packets

[vince]

Likely a dumb question - but for the rtl_davis users out there did you need 
to do anything to get it to log the percent good packets to the db ?

The driver is logging pct_good ok to syslog but I'm not following the code 
to see what (if anything) I need to do to get it to log to rxCheckPercent 
in the db

I 'thought' that it should go there automagically from the driver code but 
it isn't happening here

(weewx-venv) pi@pi4jr:~/weewx-data/bin/user $ journalctl -u weewx -g 
"pct_good" -f -n 400
-- Journal begins at Tue 2023-05-02 17:36:11 PDT. --
Aug 10 13:12:17 pi4jr python3[2417]: weewx[2417] INFO user.rtldavis: sensor 
map is: {'pressure': 'pressure', 'inTemp': 'temp_in', 'windSpeed': 
'wind_speed', 'windDir': 'wind_dir', 'outTemp': 'temperature', 
'outHumidity': 'humidity', 'inHumidity': 'humidity_in', 'rainRate': 
'rain_rate', 'radiation': 'solar_radiation', 'UV': 'uv', 'soilTemp1': 
'soil_temp_1', 'soilTemp2': 'soil_temp_2', 'soilTemp3': 'soil_temp_3', 
'soilTemp4': 'soil_temp_4', 'leafTemp1': 'leaf_temp_1', 'extraHumid1': 
'humid_1', 'extraHumid2': 'humid_2', 'soilMoist1': 'soil_moisture_1', 
'soilMoist2': 'soil_moisture_2', 'soilMoist3': 'soil_moisture_3', 
'soilMoist4': 'soil_moisture_4', 'leafWet1': 'leaf_wetness_1', 'leafWet2': 
'leaf_wetness_2', 'rxCheckPercent': 'pct_good_all', 'txBatteryStatus': 
'bat_iss', 'supplyVoltage': 'supercap_volt', 'referenceVoltage': 
'solar_power', 'windBatteryStatus': 'bat_anemometer', 'rainBatteryStatus': 
'bat_leaf_soil', 'outTempBatteryStatus': 'bat_th_1', 'inTempBatteryStatus': 
'bat_th_2', 'extraTemp1': 'pct_good_0', 'extraTemp2': 'pct_good_1', 
'extraTemp3': 'pct_good_2', 'leafTemp2': 'pct_good_3', 
'consBatteryVoltage': 'freqError0', 'hail': 'freqError1', 'hailRate': 
'freqError2', 'heatingTemp': 'freqError3', 'heatingVoltage': 'freqError4'}
Aug 10 13:20:15 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 116 missed=   1 pct_good= 
99.15
Aug 10 13:25:15 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 116 missed=   1 pct_good= 
99.15
Aug 10 13:30:15 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 115 missed=   2 pct_good= 
98.29
Aug 10 13:35:15 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 117 missed=   0 
pct_good=100.00
Aug 10 13:40:14 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  116 count= 116 missed=   0 
pct_good=100.00
Aug 10 13:45:14 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 111 missed=   6 pct_good= 
94.87
Aug 10 13:50:16 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 114 missed=   3 pct_good= 
97.44
Aug 10 13:55:16 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 112 missed=   5 pct_good= 
95.73
Aug 10 14:00:16 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 107 missed=  10 pct_good= 
91.45
Aug 10 14:05:16 pi4jr python3[2417]: weewx[2417] DEBUG user.rtldavis: 
ARCHIVE_STATS: station 1: max_count=  117 count= 112 missed=   5 pct_good= 
95.73

-- 
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/4d714dd3-2685-4504-a18f-571c69884ac3n%40googlegroups.com.

[weewx-user] Average wind direction

[Phil D]

Hello everyone,

I am trying to create an sql query from the archive_day_xxx tables to find 
the daily and monthly values ​​of the average wind direction that we 
retrieve in the variables $day.wind.vecdir and $month.wind.vecdir.
I tried several things from the archive_day_wind and archive_day_winDir 
tables but without finding the exact values.
Anyone know how to find them?
sorry for the google translate
Thanks in advance
Phil

-- 
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/a48e7046-a3b7-4dcf-bf84-62077a5c4364n%40googlegroups.com.

[weewx-user] Re: Average wind direction

[michael.k...@gmx.at]

There is no average direction, what you are looking for is the direction of 
a vector, the resulting vector (speed, direction) of all measuerements of a 
given timespan. I am not too familiar with all database tables and entries, 
but I thinking of the parts I know, I doubt that you can retrieve the 
vector an it's direction by a query (at least with a considerable simple 
one). 

What is your use case and why can't you use the provided variables you have 
mentioned?

Phil D schrieb am Freitag, 11. August 2023 um 05:58:31 UTC+2:

> Hello everyone,
>
> I am trying to create an sql query from the archive_day_xxx tables to find 
> the daily and monthly values ​​of the average wind direction that we 
> retrieve in the variables $day.wind.vecdir and $month.wind.vecdir.
> I tried several things from the archive_day_wind and archive_day_winDir 
> tables but without finding the exact values.
> Anyone know how to find them?
> sorry for the google translate
> Thanks in advance
> Phil

-- 
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/0d856397-4479-439e-80ee-e7bfbd799285n%40googlegroups.com.