[weewx-user] Re: weectl import csv KeyError: 'source_field'

[tarob...@gmail.com]

And I just realized what the issue was with the "Unknow units 
'unix-epoch'". Changed units from 'unix-epoch' to 'unix_epoch' and now it 
seems to be working. My older "csv-import.conf" is now working with the 
weectl import.

On Sunday, April 21, 2024 at 12:57:49 PM UTC-4 tarob...@gmail.com wrote:

> Using my old import-csv.conf file (attached), I get the following error:
>
> sudo weectl import --import-config=/home/piToad/Documents/csv-import.conf 
> --dry-runUsing configuration file /etc/weewx/weewx.conf
>
> This is a dry run. Nothing will actually be done.
> Starting weectl import...
>  Unknown units 'unix-epoch' specified for field 'dateTime' in 
> /home/piToad/Documents/csv-import.conf.
>  Nothing done, exiting.
>
> On Sunday, April 21, 2024 at 12:27:22 PM UTC-4 tarob...@gmail.com wrote:
>
>> Hello,
>>
>> I am trying to import some missing data via CSV file. I've done this 
>> numerous times pre weewx 5.0 and weectl (using wee_import). I've setup a 
>> new import config file using the new layout for [[FieldMap]]. I've attached 
>> the import config I used. However, during the --dry-run I am getting the 
>> below error. I've attached the config file.
>>
>> Column Headings: 
>> ['Timestamp','d5n1Temp', 'd5n1humid', 'd5n1Pres', 'rain5n1', 
>> 'windSpeed5n1',
>>'windAvg', 'windDir', 'UV', 'luminosity', 'd5n1Humid', 'rain',
>>'windSpeed', 'inTemp', 'inHumid', 'LiTemp', 'LiHumid', 'LiStrikes',
>>'LiDistance', 'LiPres', 'GTemp', 'GHumid', 'radiation']
>>
>> It's a source_field error but can't figure out which source_field is 
>> giving the error. I've looked them over but could be missing one.
>>
>> sudo weectl import 
>> --import-config=/home/piToad/Documents/csv-import-weectl.conf --dry-run
>> Using configuration file /etc/weewx/weewx.conf
>> This is a dry run. Nothing will actually be done.
>> Starting weectl import...
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/import_cmd.py", line 82, in import_func
>> weectllib.import_actions.obs_import(config_dict,
>>   File "/usr/share/weewx/weectllib/import_actions.py", line 54, in 
>> obs_import
>> source_obj = 
>> weeimport.weeimport.Source.source_factory(config_dict['config_path'],
>> 
>>  ^
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 316, in 
>> source_factory
>> return get_object(module_class)(config_path,
>>^
>>   File "/usr/share/weewx/weeimport/csvimport.py", line 110, in __init__
>> self.map = self.parse_map(_map,
>>
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 551, in parse_map
>> _mapped_source_fields = [config['source_field'] for field, config in 
>> _map.items()]
>> 
>> ^^
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 551, in 
>> _mapped_source_fields = [config['source_field'] for field, config in 
>> _map.items()]
>>  ~~
>>   File "/usr/lib/python3/dist-packages/configobj/__init__.py", line 554, 
>> in __getitem__
>> val = dict.__getitem__(self, key)
>>   ^^^
>> KeyError: 'source_field'
>>
>

-- 
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/34977516-8d00-4cb9-80ea-5b6d3ee8d333n%40googlegroups.com.

[weewx-user] Re: weectl import csv KeyError: 'source_field'

[tarob...@gmail.com]

Using my old import-csv.conf file (attached), I get the following error:

sudo weectl import --import-config=/home/piToad/Documents/csv-import.conf 
--dry-runUsing configuration file /etc/weewx/weewx.conf
This is a dry run. Nothing will actually be done.
Starting weectl import...
 Unknown units 'unix-epoch' specified for field 'dateTime' in 
/home/piToad/Documents/csv-import.conf.
 Nothing done, exiting.

On Sunday, April 21, 2024 at 12:27:22 PM UTC-4 tarob...@gmail.com wrote:

> Hello,
>
> I am trying to import some missing data via CSV file. I've done this 
> numerous times pre weewx 5.0 and weectl (using wee_import). I've setup a 
> new import config file using the new layout for [[FieldMap]]. I've attached 
> the import config I used. However, during the --dry-run I am getting the 
> below error. I've attached the config file.
>
> Column Headings: 
> ['Timestamp','d5n1Temp', 'd5n1humid', 'd5n1Pres', 'rain5n1', 
> 'windSpeed5n1',
>'windAvg', 'windDir', 'UV', 'luminosity', 'd5n1Humid', 'rain',
>'windSpeed', 'inTemp', 'inHumid', 'LiTemp', 'LiHumid', 'LiStrikes',
>'LiDistance', 'LiPres', 'GTemp', 'GHumid', 'radiation']
>
> It's a source_field error but can't figure out which source_field is 
> giving the error. I've looked them over but could be missing one.
>
> sudo weectl import 
> --import-config=/home/piToad/Documents/csv-import-weectl.conf --dry-run
> Using configuration file /etc/weewx/weewx.conf
> This is a dry run. Nothing will actually be done.
> Starting weectl import...
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/import_cmd.py", line 82, in import_func
> weectllib.import_actions.obs_import(config_dict,
>   File "/usr/share/weewx/weectllib/import_actions.py", line 54, in 
> obs_import
> source_obj = 
> weeimport.weeimport.Source.source_factory(config_dict['config_path'],
> 
>  ^
>   File "/usr/share/weewx/weeimport/weeimport.py", line 316, in 
> source_factory
> return get_object(module_class)(config_path,
>^
>   File "/usr/share/weewx/weeimport/csvimport.py", line 110, in __init__
> self.map = self.parse_map(_map,
>
>   File "/usr/share/weewx/weeimport/weeimport.py", line 551, in parse_map
> _mapped_source_fields = [config['source_field'] for field, config in 
> _map.items()]
> 
> ^^
>   File "/usr/share/weewx/weeimport/weeimport.py", line 551, in 
> _mapped_source_fields = [config['source_field'] for field, config in 
> _map.items()]
>  ~~
>   File "/usr/lib/python3/dist-packages/configobj/__init__.py", line 554, 
> in __getitem__
> val = dict.__getitem__(self, key)
>   ^^^
> KeyError: 'source_field'
>

-- 
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/3ae8edb0-9438-423e-9342-1b6c95735f0an%40googlegroups.com.
# EXAMPLE CONFIGURATION FILE FOR IMPORTING FROM CSV FILES
#
# Copyright (c) 2009-2019 Tom Keffer  and Gary Roderick.
# See the file LICENSE.txt for your rights.

##

# Specify the source. Available options are:
#   CSV - import obs from a single CSV format file
#   WU - import obs from a Weather Underground PWS history
#   Cumulus - import obs from a one or more Cumulus monthly log files
#   WD - import obs from a one or more WD monthly log files
# Format is:
#   source = (CSV | WU | Cumulus)
source = CSV

##

[CSV]
# Parameters used when importing from a CSV file

# Path and name of our CSV source file. Format is:
#   file = full path and filename
file = /var/tmp/dataCorrection.csv

# The character used to separate fields. Format is:
#   delimiter = 
# Default is , (comma).
delimiter = ','

# If there is no mapped interval field how will the interval field be
# 

[weewx-user] weectl import csv KeyError: 'source_field'

[tarob...@gmail.com]

Hello,

I am trying to import some missing data via CSV file. I've done this 
numerous times pre weewx 5.0 and weectl (using wee_import). I've setup a 
new import config file using the new layout for [[FieldMap]]. I've attached 
the import config I used. However, during the --dry-run I am getting the 
below error. I've attached the config file.

Column Headings: 
['Timestamp','d5n1Temp', 'd5n1humid', 'd5n1Pres', 'rain5n1', 'windSpeed5n1',
   'windAvg', 'windDir', 'UV', 'luminosity', 'd5n1Humid', 'rain',
   'windSpeed', 'inTemp', 'inHumid', 'LiTemp', 'LiHumid', 'LiStrikes',
   'LiDistance', 'LiPres', 'GTemp', 'GHumid', 'radiation']

It's a source_field error but can't figure out which source_field is giving 
the error. I've looked them over but could be missing one.

sudo weectl import 
--import-config=/home/piToad/Documents/csv-import-weectl.conf --dry-run
Using configuration file /etc/weewx/weewx.conf
This is a dry run. Nothing will actually be done.
Starting weectl import...
Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 66, in main
namespace.func(namespace)
  File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File "/usr/share/weewx/weectllib/import_cmd.py", line 82, in import_func
weectllib.import_actions.obs_import(config_dict,
  File "/usr/share/weewx/weectllib/import_actions.py", line 54, in 
obs_import
source_obj = 
weeimport.weeimport.Source.source_factory(config_dict['config_path'],

 ^
  File "/usr/share/weewx/weeimport/weeimport.py", line 316, in 
source_factory
return get_object(module_class)(config_path,
   ^
  File "/usr/share/weewx/weeimport/csvimport.py", line 110, in __init__
self.map = self.parse_map(_map,
   
  File "/usr/share/weewx/weeimport/weeimport.py", line 551, in parse_map
_mapped_source_fields = [config['source_field'] for field, config in 
_map.items()]

^^
  File "/usr/share/weewx/weeimport/weeimport.py", line 551, in 
_mapped_source_fields = [config['source_field'] for field, config in 
_map.items()]
 ~~
  File "/usr/lib/python3/dist-packages/configobj/__init__.py", line 554, in 
__getitem__
val = dict.__getitem__(self, key)
  ^^^
KeyError: 'source_field'

-- 
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/01940de3-e0ef-4d5f-a242-483e16d82d81n%40googlegroups.com.
# EXAMPLE CONFIGURATION FILE FOR IMPORTING FROM CSV FILES
#
# Copyright (c) 2009-2019 Tom Keffer  and Gary Roderick.
# See the file LICENSE.txt for your rights.

##

# Specify the source. Available options are:
#   CSV - import obs from a single CSV format file
#   WU - import obs from a Weather Underground PWS history
#   Cumulus - import obs from a one or more Cumulus monthly log files
#   WD - import obs from a one or more WD monthly log files
# Format is:
#   source = (CSV | WU | Cumulus)
source = CSV

##

[CSV]
# Parameters used when importing from a CSV file

# Path and name of our CSV source file. Format is:
#   file = full path and filename
file = /home/piToad/Documents/dataCorrection.csv

# The character used to separate fields. Format is:
#   delimiter = 
# Default is , (comma).
delimiter = ','

# If there is no mapped interval field how will the interval field be
# determined for the imported records. Available options are:
#   derive - Derive the interval field from the timestamp of successive
#records. This setting is best used when the imported records
#are equally spaced in time and there are no missing records.
#   conf   - Use the interval setting from weewx.conf. This setting is
#best used if the records to be imported have been produced by
#WeeWX using the same archive interval as set in weewx.conf on
#this machine.
#   x  - Use a fixed interval of x minutes for every record. This
#setting is best used if the records to be imported are
#equally based in time but there are some missing records.
#
# Note: If there is a mapped interval field then this setting will be
#   ignored.
# Format is:
 

[weewx-user] Re: 2 harware sources one database how to?

[tarob...@gmail.com]

If all you are looking for is pressure and inside temp, depending on your 
setup, you could add a BME280 sensor (pressure, temp, and humidity). It 
used these 
instructions: https://github.com/bdwilson/acurite/blob/master/Pressure.md

And then add the bme280 weewx extension. Then you can run SDR as your 
driver and the bme280 data will be added as a service call.

On Tuesday, March 12, 2024 at 4:14:53 AM UTC-4 Greg from Oz wrote:

> I have a question:
> What happens if I get the same records from the SDR and the USB?
> Is there a way to filter out the USB fineoffset data fields I don't need 
> because they will be coming from the SDR?
> I only need inside temperature and pressure from the USB.
> I tried to comment out all the fields I didn't need in the fine offset 
> driver but that failed.
> /opt/weewx/weewx-venv/lib/python3.11/site-packages/weewx/drivers/fousb.py
>
> Back to the drawing board.
>
>
> On Tuesday 12 March 2024 at 12:51:38 UTC+11 Greg from Oz wrote:
>
>> Yeah I think I will do the same . I was leaning that way because 
>> everything else looked too hard.
>> I have MQTT already set up.
>> Thanks
>>
>> On Tuesday 12 March 2024 at 10:44:15 UTC+11 bell...@gmail.com wrote:
>>
>>> My solution was to run rtl_433 as a separate service that publishes to 
>>> MQTT. I then run MQTTSubscribe to augment the station/driver data. I 
>>> already had the MQTT infrastructure, so it was a minor lift for me.
>>> Some more information is here, 
>>> https://groups.google.com/g/weewx-user/c/svsbOxWvPZc/m/eLA6lhyJAAAJ.
>>> rich
>>>
>>> On Monday 11 March 2024 at 01:49:59 UTC-4 Greg from Oz wrote:
>>>
 Hi,
 I have spent hours trying to figure out how to have 2 hardware sources 
 (sdr and fineoffset USB console) and get most data from the sdr and just 
 the barometer and inside temperature from the fine offset USB console.

 I just want all the data from both devices to go into the one database.

 Is this even possible?

 I have found examples of 2 hardware devices and 2 databases but I don't 
 want that.

 The reason I want to do this is because the console is showing a lot of 
 :
 ERROR weewx.drivers.fousb: get_observations failed: [Errno 19] No such 
 device (it may have been disconnected)

 The only way to fix those errors is to turn the console on and off 
 which I have automated but it is doing it a lot lately and and it is even 
 showing up on my graphs.

 If I can't get the barometer and inside temperature I won't be 
 heartbroken but it would be nice to be able to do that.

 If I can get it to work I can just reset the console when it stops 
 working and not have the barometer and inside temp but I should be able to 
 at least get the majority of the data.

 Is there any documentation with examples anywhere? I did find something 
 about creating a service but that looked way to complicated for my 
 paygrade.

 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/cfc5cd8a-a23d-4ecd-a879-bb941cd476ben%40googlegroups.com.

[weewx-user] Re: weewx-sdr howto document available on git hub

[tarob...@gmail.com]

Thank you Vince! So when I've setup SDR driver previously, the rtl_sdr 
package was required but looking at your how-to, only the rtl_433 is 
needed. I will say getting rtl_sdr on debian bookworm was a challenge as it 
had to be built from source.

On Wednesday, March 6, 2024 at 8:13:19 PM UTC-5 bell...@gmail.com wrote:

> I only hesitate to share because I know just enough about systemd to be 
> dangerous. One should NOT use these as a template but as additional 
> information to learn from.
> The rtl_433 file. There is additional lines because  I use 
> https://pushover.net to monitor things related to WeeWX
> # systemd unit configuration file for rtl_433
> #
>
> [Unit]
> Description=rtl_433 service
> Documentation=https://github.com/merbanan/rtl_433/README.md
> # StartLimitIntervalSec=5
> After=syslog.target network.target
>
> StartLimitIntervalSec=500
> StartLimitBurst=5
>
> [Service]
> Environment=UUID=replace_me
> Restart=on-failure
> RestartSec=5s
>
> # Type=exec
> #ExecStart=/usr/local/bin/rtl_433 -M utc -F json -F 
> mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]
> ExecStart=/usr/local/bin/rtl_433 -M utc -F 
> mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]
>
> ## ExecStartPre runs before, the "-" in the beginning is to let systemd 
> continue even on non-zero exit
> ExecStartPre=-/bin/bash -c "curl -fsS -m 10 --retry 5 -o /dev/null 
> https://hc-ping.com/$UUID;
>
> ## ExecStopPost runs after, no matter if ExecStart was success or not. The 
> "-" in the beginning is like ExecStartPre
> ExecStopPost=-/bin/bash -c "curl -fsS -m 10 --retry 5 -o /dev/null 
> https://hc-ping.com/$UUID/fail;
>
>
> # Restart script if stopped
> #Restart=always
> # Wait 30s before restart
> #RestartSec=30s
>
> # Tag things in the log
> # View with: sudo journalctl -f -u rtl_433 -o cat
> #SyslogIdentifier=rtl_433
>
>
> # NOTE: only works in systemd v236+
> #   Debain "stretch" includes v232, "buster" includes v239
> # Note also the user must be able to create the file and logrotate must be 
> amended to rote the log.
> StandardOutput=file:/var/log/rtl_433.log
> StandardError=file:/var/log/rtl_433.log
>
> #StandardOutput=syslog
> #StandardOutput=null
> #StandardError=syslog
>
> # To run as a non-root user, uncomment and set username and group here:
> #User=pi
> #Group=pi
>
> [Install]
> WantedBy=multi-user.target  
>
>
> My WeeWX file. I hacked this up in 4.x. I would think 5.x would work just 
> fine.
>
> # source bellrichm-configs weewx/multi/systemd
> [Unit]
> Description=WeeWX gather %i data 
> Documentation=https://weewx.com/docs
>
> Requires=time-sync.target
> After=time-sync.target
> RequiresMountsFor=/home
>
> [Service]
> ExecStart=/home/weewx/bin/weewxd --log-label=weewx-%i  /home/weewx/%i.conf
> StandardOutput=null
> # To run as a non-root user, uncomment and set username and group here:
> User=pi
> Group=pi
>
> [Install]
> WantedBy=multi-user.target
>
> Yup MQTTSubscribe runs as either driver or service. Nothing special to 
> running as a driver.
> rich
>
> On Wednesday 6 March 2024 at 17:20:42 UTC-5 vince wrote:
>
>> Nice.  Lets see your system service file(s) to match !
>>
>> How would you use that way as a driver and not even need to user 
>> weewx-sdr ?  Not remembering if MQTT subscribe can run as a driver.  I just 
>> run it as an extension.
>>
>> On Wednesday, March 6, 2024 at 2:06:27 PM UTC-8 bell...@gmail.com wrote:
>>
>>> Vince,
>>> Nice write up.
>>> Begin shameless plug…
>>> Since I am heavily invested in reading things from MQTT, I just run 
>>> rtl_433 as a separate service and subscribe to the topic. I did this 
>>> primarily to get the data in a service and secondarily to get sensors that 
>>> were not ’mapped’.
>>> The service invocation, ‘ExecStart=/usr/local/bin/rtl_433 -M utc -F 
>>> mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]’
>>> And one topic config looks like this
>>> [[topics]]
>>> ignore = True
>>> [[[message]]] type = individual # Upright freezer (basement) 
>>> [[[rtl_433/weather-data/devices/Acurite-606TX/77/temperature_C]]] ignore = 
>>> False unit_system = METRIC name = extraTemp8 
>>>
>>> It may seem more complicated, but since I was invested in MQTT, it 
>>> actually simplified it. This was primarily because I could treat rtl_433 as 
>>> a separate service
>>>
>>> End plug
>>>
>>> On Wednesday 6 March 2024 at 16:14:25 UTC-5 vince wrote:
>>>
 In working with another weewx user to help him gets his SDR station 
 online, it was clear that lots of people (like me) have some problems 
 really understanding some of the rtl-433 and sdr documentation that is out 
 there.

 After working through it end-to-end a few times on both ubuntu and on a 
 raspberry pi, I wrote up the whole setup as a howto with examples mainly 
 for future-me but I thought it might be of general interest.  At worst 

Re: [weewx-user] weewx v5.0.1 upgrade problem

[tarob...@gmail.com]

This solved my problem, adding user ‘weewx’ to the ‘plugdev’ group using 
the usermod command.

'sudo usermod -aG plugdev weewx'

On Tuesday, February 6, 2024 at 10:23:15 AM UTC-5 matthew wall wrote:

> when you install rtl-sdr, it typically, but not always, installs udev 
> rules for *many* sdr devices.  the udev rules that it installs make it 
> possible for anyone in the 'plugdev' group to read/write to the sdr 
> device.  (this is true when you install rtl-sdr from source - if you 
> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
> this configuration please let us know)
>
> weewx v4 runs as root:root, so it has access to the sdr device no matter 
> what the udev rules might be
>
> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
> non-root user (for pip installs).  so udev rules are required.
>
> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
> (it would continue to run as root - we changed in 5.0.1 because overall 
> security and best practice)
>
> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
> since the user 'weewx' is not in the plugdev group.  you can either added 
> the user weewx to the plugdev group, or modify the udev rules to use 
> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>
> sudo usermod -aG plugdev weewx
>
> for a pip install, be sure that the user running weewx is in the 'plugdev' 
> group.
>
> restart of the weewxd daemon is almost certainly required so that the 
> daemon process has the right group.  reboot is not necessary.
>
> m
>

-- 
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/c37d5d14-ba2e-4c5e-a05e-e924e6094f72n%40googlegroups.com.

[weewx-user] Re: Aucrite sensor stopped working - does it need re-registration?

[tarob...@gmail.com]

What driver are you using?

On Monday, January 22, 2024 at 2:46:51 AM UTC-5 ken.r...@gmail.com wrote:

> I setup Weewx 3.9.1 about 6yrs ago when Acurite dropped support for their 
> SmartHub, and haven't upgraded since.
>
> Recently I moved home and lost a sensor in one of the packing boxes and 
> then found it again after the battery had been flat for almost 6 months. It 
> displays temperature and humidity and the repeater flickers when it 
> transmits, but weewx is not recording any data for that sensor ID#.
>
> Acurite gave instructions on how to register a sensor, but as the turned 
> off the server that support SmartHubs I can't do that
>
> https://support.acurite.com/hc/en-us/articles/360021588913-Add-a-Sensor-to-the-My-AcuRite-Dashboard-
>
> I found these instructions for weewx but I'm getting errors when I try to 
> sniff
> https://github.com/matthewwall/weewx-interceptor
>
> [root]# PYTHONPATH=bin python /usr/share/weewx/user/interceptor.py 
> --conf=/etc/weewx/weewx.conf --device=acurite-bridge --mode=sniff 
> --iface=ens3 --filter="src XXX.XXX.XXX.XXX and dst port 80"
> Traceback (most recent call last):
>   File "/usr/share/weewx/user/interceptor.py", line 212, in 
> import weewx.drivers
> ImportError: No module named weewx.drivers
>
> Could the sensor have lost it's ID? The reset button on the sensor doesn't 
> help. What else can I try?
>

-- 
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/f3ae953d-5a80-442a-99a6-4365b5f01f5bn%40googlegroups.com.

Re: [weewx-user] Re: WDC Skin

[tarob...@gmail.com]

Thank you, sorry should've looked that up on bug with 3.4.

I realized I needed to update the weewx.conf HTML_ROOT section after 
posting. All is working now, thank you David!

On Saturday, January 13, 2024 at 6:58:24 PM UTC-5 David Bätge wrote:

> *Just upgraded to the new 3.4.0 skin (from 3.1.1). I am getting the 
> following error when the reports run.*
>
> This bug was introduced with 3.4, please see here: 
> https://github.com/Daveiano/weewx-wdc/issues/191#issuecomment-1877890285 
> or 
> https://github.com/Daveiano/weewx-wdc/discussions/218#discussioncomment-7470782
>
> *I also changed the base path in skin.conf to /weewx/wdc/ and still trying 
> to send the generated files to /weewx/*
>
> You want to change the HTML_ROOT, not the base_path. See 
> https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
>  
> or 
> https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
>  
> and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>
> tarob...@gmail.com schrieb am Freitag, 12. Januar 2024 um 21:35:44 UTC+1:
>
>> Just upgraded to the new 3.4.0 skin (from 3.1.1). I am getting the 
>> following error when the reports run.
>>
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> Evaluation of template /etc/weewx/skins/weewx-wdc/index.html.tmpl failed 
>> with exception ''
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>  Ignoring template /etc/weewx/skins/weewx-wdc/index.html.tmpl
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>  Reason: could not convert string to float: 'geocode=34.743313'
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>   Traceback (most recent call last):
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in 
>> generate
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>   unicode_string = compiled_template.respond()
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "_etc_weewx_skins_weewx_wdc_index_html_tmpl.py", line 267, in 
>> respond
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
>> 1708, in _handleCheetahInclude
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>   self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "_etc_weewx_skins_weewx_wdc_includes_body_alternative_inc.py", 
>> line 286, in respond
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
>> 1708, in _handleCheetahInclude
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>   self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "_etc_weewx_skins_weewx_wdc_includes_forecast_inc.py", line 
>> 256, in respond
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
>> 1708, in _handleCheetahInclude
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>   self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "_etc_weewx_skins_weewx_wdc_includes_forecast_table_inc.py", 
>> line 1749, in respond
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "_etc_weewx_skins_weewx_wdc_includes_forecast_table_inc.py", 
>> line 520, in __errorCatcher65
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>> File "", line 1, in 
>> Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
>>   ValueError: could not convert string to float: 'geocode=34.743313'
>> Jan 12 15:30:50 raspberrypiNAS weewx[19495] INFO weewx.cheetahgenerator: 
>> Generated 11 files for report WdcReport in 19.02 seconds
>> Jan 12 15:30:50 raspberrypiNAS weewx[19495] INFO weewx.reportengine: 
>> Copie

Re: [weewx-user] Re: WDC Skin

[tarob...@gmail.com]

Just upgraded to the new 3.4.0 skin (from 3.1.1). I am getting the 
following error when the reports run.

Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
Evaluation of template /etc/weewx/skins/weewx-wdc/index.html.tmpl failed 
with exception ''
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
 Ignoring template /etc/weewx/skins/weewx-wdc/index.html.tmpl
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
 Reason: could not convert string to float: 'geocode=34.743313'
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  Traceback (most recent call last):
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in 
generate
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  unicode_string = compiled_template.respond()
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_index_html_tmpl.py", line 267, in 
respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1708, in _handleCheetahInclude
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_body_alternative_inc.py", 
line 286, in respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1708, in _handleCheetahInclude
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_forecast_inc.py", line 
256, in respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1708, in _handleCheetahInclude
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_forecast_table_inc.py", 
line 1749, in respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_forecast_table_inc.py", 
line 520, in __errorCatcher65
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "", line 1, in 
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  ValueError: could not convert string to float: 'geocode=34.743313'
Jan 12 15:30:50 raspberrypiNAS weewx[19495] INFO weewx.cheetahgenerator: 
Generated 11 files for report WdcReport in 19.02 seconds
Jan 12 15:30:50 raspberrypiNAS weewx[19495] INFO weewx.reportengine: Copied 
0 files to /var/www/html/weewx

I also changed the base path in skin.conf to /weewx/wdc/ and still trying 
to send the generated files to /weewx/

Thanks,
Troy

On Sunday, August 27, 2023 at 10:14:41 AM UTC-4 David Bätge wrote:

> Hi Mau,
>
> yes, the wiki realy includes a lot of information. I guess you are missing 
> the base_path setting, see 
> https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
>  
> and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>
>
>
> Mau Hernandez schrieb am Mittwoch, 23. August 2023 um 01:00:26 UTC+2:
>
>> I just found your Wiki!  Will 
>> give that a shot! 
>>
>> On Tuesday, August 22, 2023 at 3:45:36 PM UTC-7 Mau Hernandez wrote:
>>
>>> Hi David,
>>>
>>> New user of WeeWx and found this thread with your Skin which Im trying 
>>> to install. I saw above that data might be needed so hopefully that 
>>> explains why Im getting a blank page but the Menu's are showing.
>>>
>>> I used the DEB package to do fresh install in a Debian machine. 
>>> Everything was setup and accesible at http://IP/weewx/. When I select 
>>> any submenu on the skin I see it goes back to root http://IP/about.html so 
>>> I probably missed a sym-link during setup? (http://IP/weewx/about.html 
>>> should 
>>> be the correct? ) 
>>>
>>> Thanks for your help
>>>
>>> [image: Screenshot 2023-08-22 at 3.37.53 PM.png]
>>> On Friday, August 18, 2023 at 7:17:21 AM UTC-7 David Bätge wrote:
>>>
 Great, I will include the change in the next release! 

 gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 13:44:22 
 UTC+2:

> Hi David
>
> I was to fast, it seems to work with the new main.ja.
>
> Thanks 

[weewx-user] Re: Belchertown - lost condition images on homepage

[tarob...@gmail.com]

I actually figured out my issue. In the belchertown skin.conf, I had 
forecast_enabled set to 0. Changed it to 1 and the images are now showing 
up.

On Sunday, March 5, 2023 at 11:30:22 AM UTC-5 tarob...@gmail.com wrote:

> Did you solve this issue? Having the same after new installation. I 
> remember seeing this before and cannot remember how I solved it.
>
> On Friday, June 24, 2022 at 3:53:00 AM UTC-4 Uwe S. wrote:
>
>> Hi all, 
>>
>> i've set up sucessfully the Belchertown skin, but somewhere in between i 
>> lost the current condition images:
>>
>>
>> [image: belcher.jpg]
>>
>> Any ideas how to get it back?
>>
>> 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/a82c8414-0121-4720-b6f1-f5309f31e5f3n%40googlegroups.com.

[weewx-user] Re: Belchertown - lost condition images on homepage

[tarob...@gmail.com]

Did you solve this issue? Having the same after new installation. I 
remember seeing this before and cannot remember how I solved it.

On Friday, June 24, 2022 at 3:53:00 AM UTC-4 Uwe S. wrote:

> Hi all, 
>
> i've set up sucessfully the Belchertown skin, but somewhere in between i 
> lost the current condition images:
>
>
> [image: belcher.jpg]
>
> Any ideas how to get it back?
>
> 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/65c4ab0d-9501-4dd9-944d-a1bef0d159d4n%40googlegroups.com.

[weewx-user] Re: wee_extension - ModuleNotFoundError: No module named 'configobj

[tarob...@gmail.com]

Weewx was originally installed using python3 (running on rpi 4 with buster)

Running  "ps axu | grep wee"

root 15080 15.8  3.3 122252 64084 ?Sl   Nov04 388:36 python3 
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
/etc/weewx/weewx.conf
pi   31454  0.0  0.0   7244   580 pts/0S+   06:30   0:00 grep 
--color=auto wee

And running "cat /etc/default/weewx"

WEEWX_PYTHON=python3
WEEWX_PYTHON_ARGS=
WEEWX_BINDIR=/usr/share/weewx
WEEWX_BIN=/usr/bin/weewxd
WEEWX_CFG=/etc/weewx/weewx.conf
On Sunday, November 6, 2022 at 12:24:32 AM UTC-4 vince wrote:

> Guessing you installed weewx using python2 originally.
>
> Lets see what you're actually running.
>
> Try "ps axu | grep wee" and it should show us which python version you're 
> running.
>
> An example will look something like the following for a python3 packaged 
> install on debian 11:
>
> root 394  0.2  2.2 103192 22496 ?Sl   21:20   0:00 python3 
> /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
> /etc/weewx/weewx.conf
>
> Also for a packaged install, run "cat /etc/default/weewx" which should 
> agree.
>
> On the same deb11 system, mine looks like:
>
> WEEWX_PYTHON=python3
> WEEWX_BINDIR=/usr/share/weewx
> WEEWX_BIN=/usr/bin/weewxd
> WEEWX_CFG=/etc/weewx/weewx.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/b56ec71b-3456-4276-bb72-2593e80d2b37n%40googlegroups.com.

[weewx-user] wee_extension - ModuleNotFoundError: No module named 'configobj

[tarob...@gmail.com]

Getting an error when trying to use wee_extension. I've just upgraded to 
4.9.1 but I'm not sure if this is from upgrade or related to a python 
upgrade.

weewx is running fine, collecting data and I see no errors in the logs. 
When I run wee_extension I get the following:

Traceback (most recent call last):
  File "/usr/share/weewx/wee_extension", line 13, in 
import weecfg.extension
  File "/usr/share/weewx/weecfg/__init__.py", line 23, in 
import configobj
ModuleNotFoundError: No module named 'configobj

Running sudo systemctl status weewx
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (running) since Fri 2022-11-04 14:34:54 EDT; 1 day 5h ago
 Docs: man:systemd-sysv-generator(8)
  Process: 15064 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
Tasks: 2 (limit: 3720)
   CGroup: /system.slice/weewx.service
   └─15080 python3 /usr/share/weewx/weewxd --daemon 
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Any ideas? I tried running sudo install python3-configobj but getting 
latest is already installed. Not sure what else to do. The extension I have 
are all working as expected.

-- 
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/964d7907-aca8-4a3a-9dc0-f3fb21b9263fn%40googlegroups.com.

Re: [weewx-user] Re: WDC Skin

[tarob...@gmail.com]

in the content area or 
>>> the possibility to prioritize them. As an optional skin setting for 
>>> example. But if they could in any way be made as small as the ones in the 
>>> new bootstrap skin "fuzzy-archer 3.0" this would be amazing. If you two 
>>> could ever mix up your skins, this would probably be the most functional 
>>> and clear skin ever :) 
>>>
>>> These are just suggestions though, I know tastes are different, but imo 
>>> weewx stil lacks an interactive alternative or version of the very clear 
>>> seasons skin where nearly all values and graphs are visible at a glance. I 
>>> just like to zoom in if needed, instead of scrolling.
>>>
>>> *Do you mean like an export Button on the Desktop Application to export 
>>> all data as HTML pages? Well you can also use the WDC Skin with weewx and 
>>> import all data to weewx via csv, generate the report and there you go ;)*
>>>
>>> Well, true, nearly forgot about that option. That way, a custom menu 
>>> entry in the WDC Skin to e.g. station info/news content would be the icing 
>>> on the cake :)
>>>
>>>
>>>
>>> tarob...@gmail.com schrieb am Montag, 30. Mai 2022 um 19:34:33 UTC+2:
>>>
>>>> It's working without errors. Thanks again!
>>>>
>>>> On Mon, May 30, 2022 at 11:16 AM David Bätge  
>>>> wrote:
>>>>
>>>>> Thank you very much!
>>>>>
>>>>> I was able to reproduce the issue you described. It was like I said, 
>>>>> due to missing data (days without any values). I will include a Bugfix 
>>>>> for 
>>>>> this in the next release. Attached is an updated stats_util.py.
>>>>>
>>>>> Again - Thank you very much. Every feedback is appreciated!
>>>>>
>>>>> tarob...@gmail.com schrieb am Montag, 30. Mai 2022 um 12:53:56 UTC+2:
>>>>>
>>>>>> Shared the db via drive. Haven't tried the updated stats but will let 
>>>>>> you know when I do.
>>>>>>
>>>>>> On Sun, May 29, 2022, 8:13 PM David Bätge  
>>>>>> wrote:
>>>>>>
>>>>>>> Ok, I ran the skin successfully with the Simulator driver for a few 
>>>>>>> hours. Curious about what happens if I stop weewx for some days and 
>>>>>>> then 
>>>>>>> restart it, the driver should resume producing data with the current 
>>>>>>> date/time. But in the meantime there is missing data, I guess.
>>>>>>>
>>>>>>> Did you try the updated stats_util.py (
>>>>>>> https://github.com/Daveiano/weewx-wdc/commit/49c4a42dfa2d4eb4b4226f9c676f98f99a260019
>>>>>>> )?
>>>>>>>
>>>>>>> Would be great to get the DB, would save me some time trying things 
>>>>>>> out :)
>>>>>>>
>>>>>>> tarob...@gmail.com schrieb am Sonntag, 29. Mai 2022 um 23:28:53 
>>>>>>> UTC+2:
>>>>>>>
>>>>>>>> Here's the conf.
>>>>>>>>
>>>>>>>> On Sun, May 29, 2022 at 5:12 PM David Bätge  
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Oh ok, in that case, if you could post your weewx.conf, that's 
>>>>>>>>> enough I think. Thank you very much!
>>>>>>>>>
>>>>>>>>> tarob...@gmail.com schrieb am Sonntag, 29. Mai 2022 um 18:05:45 
>>>>>>>>> UTC+2:
>>>>>>>>>
>>>>>>>>>> I'm testing this on my "Test" weewx on a 2nd raspberry pi. It's 
>>>>>>>>>> running in simulation mode so I don't think there are any missing 
>>>>>>>>>> values. 
>>>>>>>>>> If you still need the db let me know.
>>>>>>>>>>
>>>>>>>>>> Troy
>>>>>>>>>>
>>>>>>>>>> On Sat, May 28, 2022, 2:54 PM David Bätge  
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> From the logs, it looks like there are some temperature values 
>>>>>>>>>>> missing in your database (that's where the NoneType came from). 
>>>>>>>>

[weewx-user] Re: WDC Skin

[tarob...@gmail.com]

 28 12:35:35 raspberrypi weewx[8931] ERROR weewx.cheetahgenerator:  
   File "", line 1, in 
May 28 12:35:35 raspberrypi weewx[8931] ERROR weewx.cheetahgenerator:  
   File "/usr/share/weewx/user/stats_util.py", line 175, in 
get_climatological_day
May 28 12:35:35 raspberrypi weewx[8931] ERROR weewx.cheetahgenerator:  
 return len(list(days))
May 28 12:35:35 raspberrypi weewx[8931] ERROR weewx.cheetahgenerator:  
   File "/usr/share/weewx/user/stats_util.py", line 173, in 
May 28 12:35:35 raspberrypi weewx[8931] ERROR weewx.cheetahgenerator:  
 days = filter(lambda x: x.raw >= value, list(day_series.data))
May 28 12:35:35 raspberrypi weewx[8931] ERROR weewx.cheetahgenerator:  
 TypeError: '>=' not supported between instances of 'NoneType' and 'float'
May 28 12:35:35 raspberrypi weewx[8931] INFO weewx.cheetahgenerator: 
Generated 9 files for report WdcReport in 14.05 seconds
May 28 12:35:35 raspberrypi weewx[8931] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx/wdc

On Friday, May 27, 2022 at 8:25:38 PM UTC-4 david@gmail.com wrote:

> Yes, that's correct, I think weewx wants the zip to contain only one 
> folder which contains the whole extension. (if you want to directly install 
> from zip without the "extract to folder" step)
>
> Glad I could help you!
>
> tarob...@gmail.com schrieb am Samstag, 28. Mai 2022 um 02:19:15 UTC+2:
>
>> Got it working. I see it can't install from zip. Need to extract to 
>> directory and install from that location. Thank you.
>>
>> On Friday, May 27, 2022 at 5:31:53 PM UTC-4 david@gmail.com wrote:
>>
>>> The file location is correct, but you need to use the .zip which is 
>>> attached to a release.
>>>
>>> The latest release is v1.2.0, the download path for the zip is 
>>> https://github.com/Daveiano/weewx-wdc/releases/download/v1.2.0/weewx-wdc-v1.2.0.zip
>>> Release page is here: 
>>> https://github.com/Daveiano/weewx-wdc/releases/tag/v1.2.0 (its the 
>>> first linked zip)
>>>
>>> *Background*: The files in the src/ directory are the Source files 
>>> (TypeScript, SCSS). When creating a release, the source files get 
>>> transformed and optimized, the output location of these transformed files 
>>> is the location from the install.py. The release.zip should contain all 
>>> these transformed files (like service-worker.js), but if you download the 
>>> current state of the repo, these files are not included, hence the error. 
>>>
>>> Please let me know if this helps and solves the problem, I will also add 
>>> a notice about it on the readme page.
>>>
>>> tarob...@gmail.com schrieb am Freitag, 27. Mai 2022 um 14:30:21 UTC+2:
>>>
>>>> Trying to install from zip (also tried from tar.gz) and getting the 
>>>> following:
>>>>
>>>> "sudo wee_extension --install=weewx-wdc.zip
>>>> Request to install 'weewx-wdc.zip'
>>>> Extracting from zip archive weewx-wdc.zip
>>>> Traceback (most recent call last):
>>>>   File "/usr/share/weewx/wee_extension", line 92, in 
>>>> main()
>>>>   File "/usr/share/weewx/wee_extension", line 84, in main
>>>> ext.install_extension(options.install)
>>>>   File "/usr/share/weewx/weecfg/extension.py", line 130, in 
>>>> install_extension
>>>> self.install_from_dir(extension_dir)
>>>>   File "/usr/share/weewx/weecfg/extension.py", line 183, in 
>>>> install_from_dir
>>>> shutil.copy(source_path, destination_path)
>>>>   File "/usr/lib/python3.7/shutil.py", line 245, in copy
>>>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>>>   File "/usr/lib/python3.7/shutil.py", line 120, in copyfile
>>>> with open(src, 'rb') as fsrc:
>>>> FileNotFoundError: [Errno 2] No such file or directory: 
>>>> '/var/tmp/weewx-wdc-1.2.0/skins/weewx-wdc/service-worker.js'
>>>> "
>>>>
>>>> I can see the service-worker.js is located in a different directory 
>>>> than where the install is looking. It is located 
>>>> "weewx-wdc-1.2.0\skins\weewx-wdc\src\js\service-worker.js"
>>>>
>>>> On Thursday, May 26, 2022 at 8:49:31 AM UTC-4 david@gmail.com 
>>>> wrote:
>>>>
>>>>> Thank you for your feedback, very appreciated!
>>>>>
>>>>> *Is it possible to set custom values for font and graph size, amount 
>>>>> of ro

[weewx-user] Re: WDC Skin

[tarob...@gmail.com]

Got it working. I see it can't install from zip. Need to extract to 
directory and install from that location. Thank you.

On Friday, May 27, 2022 at 5:31:53 PM UTC-4 david@gmail.com wrote:

> The file location is correct, but you need to use the .zip which is 
> attached to a release.
>
> The latest release is v1.2.0, the download path for the zip is 
> https://github.com/Daveiano/weewx-wdc/releases/download/v1.2.0/weewx-wdc-v1.2.0.zip
> Release page is here: 
> https://github.com/Daveiano/weewx-wdc/releases/tag/v1.2.0 (its the first 
> linked zip)
>
> *Background*: The files in the src/ directory are the Source files 
> (TypeScript, SCSS). When creating a release, the source files get 
> transformed and optimized, the output location of these transformed files 
> is the location from the install.py. The release.zip should contain all 
> these transformed files (like service-worker.js), but if you download the 
> current state of the repo, these files are not included, hence the error. 
>
> Please let me know if this helps and solves the problem, I will also add a 
> notice about it on the readme page.
>
> tarob...@gmail.com schrieb am Freitag, 27. Mai 2022 um 14:30:21 UTC+2:
>
>> Trying to install from zip (also tried from tar.gz) and getting the 
>> following:
>>
>> "sudo wee_extension --install=weewx-wdc.zip
>> Request to install 'weewx-wdc.zip'
>> Extracting from zip archive weewx-wdc.zip
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_extension", line 92, in 
>> main()
>>   File "/usr/share/weewx/wee_extension", line 84, in main
>> ext.install_extension(options.install)
>>   File "/usr/share/weewx/weecfg/extension.py", line 130, in 
>> install_extension
>> self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 183, in 
>> install_from_dir
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.7/shutil.py", line 245, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.7/shutil.py", line 120, in copyfile
>> with open(src, 'rb') as fsrc:
>> FileNotFoundError: [Errno 2] No such file or directory: 
>> '/var/tmp/weewx-wdc-1.2.0/skins/weewx-wdc/service-worker.js'
>> "
>>
>> I can see the service-worker.js is located in a different directory than 
>> where the install is looking. It is located 
>> "weewx-wdc-1.2.0\skins\weewx-wdc\src\js\service-worker.js"
>>
>> On Thursday, May 26, 2022 at 8:49:31 AM UTC-4 david@gmail.com wrote:
>>
>>> Thank you for your feedback, very appreciated!
>>>
>>> *Is it possible to set custom values for font and graph size, amount of 
>>> rows and border size so everything including graphs could be made visible 
>>> at a glance without or less scrolling?*
>>> Currently, this is not possible. The skin uses the IBM Carbon Design 
>>> System, so these values are more or less predefined. But you are right, 
>>> using the space and layouting all the graphs were one of the most 
>>> challenging parts of this. I am also not yet 100% happy with it. Perhaps I 
>>> could predefine some "Spacing variations", like a dense one and a wide one 
>>> for example.
>>>
>>> *Any chance for a web version of the weather data center, so one could 
>>> publish the visualized csv's to the web? Or even comibne it with weewx live 
>>> data in one page? Just a thought*
>>> Do you mean like an export Button on the Desktop Application to export 
>>> all data as HTML pages? Well you can also use the WDC Skin with weewx and 
>>> import all data to weewx via csv, generate the report and there you go ;)
>>> f4n...@gmail.com schrieb am Donnerstag, 26. Mai 2022 um 12:04:58 UTC+2:
>>>
>>>> Thanks a lot for this skin (and the weather data visualizing app), 
>>>> looks very clean! 
>>>>
>>>> Is it possible to set custom values for font and graph size, amount of 
>>>> rows and border size so everything including graphs could be made visible 
>>>> at a glance without or less scrolling?
>>>>
>>>> Any chance for a web version of the weather data center, so one could 
>>>> publish the visualized csv's to the web? Or even comibne it with weewx 
>>>> live 
>>>> data in one page? Just a thought
>>>> david@gmail.com schrieb am Samstag, 14. Mai 2022 um 13:13:39 UTC+2:
>>>>
>>>>> Hi guys!
>

[weewx-user] Re: WDC Skin

[tarob...@gmail.com]

Trying to install from zip (also tried from tar.gz) and getting the 
following:

"sudo wee_extension --install=weewx-wdc.zip
Request to install 'weewx-wdc.zip'
Extracting from zip archive weewx-wdc.zip
Traceback (most recent call last):
  File "/usr/share/weewx/wee_extension", line 92, in 
main()
  File "/usr/share/weewx/wee_extension", line 84, in main
ext.install_extension(options.install)
  File "/usr/share/weewx/weecfg/extension.py", line 130, in 
install_extension
self.install_from_dir(extension_dir)
  File "/usr/share/weewx/weecfg/extension.py", line 183, in install_from_dir
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.7/shutil.py", line 245, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.7/shutil.py", line 120, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/tmp/weewx-wdc-1.2.0/skins/weewx-wdc/service-worker.js'
"

I can see the service-worker.js is located in a different directory than 
where the install is looking. It is located 
"weewx-wdc-1.2.0\skins\weewx-wdc\src\js\service-worker.js"

On Thursday, May 26, 2022 at 8:49:31 AM UTC-4 david@gmail.com wrote:

> Thank you for your feedback, very appreciated!
>
> *Is it possible to set custom values for font and graph size, amount of 
> rows and border size so everything including graphs could be made visible 
> at a glance without or less scrolling?*
> Currently, this is not possible. The skin uses the IBM Carbon Design 
> System, so these values are more or less predefined. But you are right, 
> using the space and layouting all the graphs were one of the most 
> challenging parts of this. I am also not yet 100% happy with it. Perhaps I 
> could predefine some "Spacing variations", like a dense one and a wide one 
> for example.
>
> *Any chance for a web version of the weather data center, so one could 
> publish the visualized csv's to the web? Or even comibne it with weewx live 
> data in one page? Just a thought*
> Do you mean like an export Button on the Desktop Application to export all 
> data as HTML pages? Well you can also use the WDC Skin with weewx and 
> import all data to weewx via csv, generate the report and there you go ;)
> f4n...@gmail.com schrieb am Donnerstag, 26. Mai 2022 um 12:04:58 UTC+2:
>
>> Thanks a lot for this skin (and the weather data visualizing app), looks 
>> very clean! 
>>
>> Is it possible to set custom values for font and graph size, amount of 
>> rows and border size so everything including graphs could be made visible 
>> at a glance without or less scrolling?
>>
>> Any chance for a web version of the weather data center, so one could 
>> publish the visualized csv's to the web? Or even comibne it with weewx live 
>> data in one page? Just a thought
>> david@gmail.com schrieb am Samstag, 14. Mai 2022 um 13:13:39 UTC+2:
>>
>>> Hi guys!
>>>
>>> I just wanted to do some advertisement for a new weewx Skin, I 
>>> developed: https://github.com/Daveiano/weewx-wdc
>>>
>>> The visual part is based on another weather app, I wrote earlier this 
>>> year: https://daveiano.github.io/weather-data-center/
>>>
>>> Please feel free to check it out, a working demo is hosted here: 
>>> https://www.weewx-hbt.de/
>>>
>>> Key features included:
>>> - Clear and beautiful UI thanks to IBM Carbon and nivo
>>> - Configurable Statistic Tiles and Diagram tiles
>>> - Combinable diagrams via skin.conf
>>> - Responsive
>>> - Day, week, month, year and all-time pages
>>> - Archive and NOAA Reports
>>> - Almanac
>>> - Translated for DE and EN
>>> - Tabular representation with Carbon Data Tables
>>>
>>> I consider the skin as feature-complete but I will do some updates in 
>>> the coming weeks to optimize some things like responsiveness or perhaps add 
>>> some more statistics. 
>>>
>>> I am a software developer but I never worked with python before. I have 
>>> been looking for an opportunity to work with python for a long time, so 
>>> working with weewx and creating a skin did that for me. I am really caught 
>>> by how things work together in weewx, a great piece of software.
>>>
>>

-- 
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/b1847b3a-f3cc-48f5-ab37-fcd276a34e00n%40googlegroups.com.

Re: [weewx-user] UV Index - Seasons Skin 4.7 update

[tarob...@gmail.com]

Sorry I did not provide a log, I didn't see any errors when the reports 
were generated by weewx. I did check the /var/www/weewx folder and found 
that the UV figures naming convention changed. Went from "..uv.png" to 
"..UV.png" for the corresponding day, week, month, and year. i.e for day 
"dayuv.png" to "dayUV.png". I updated the index.html.tmpl file and that 
fixed the issue.

On Monday, March 21, 2022 at 8:28:19 AM UTC-4 tke...@gmail.com wrote:

> What did change is how the skin decides which plots to generate and 
> include.
>
> However, it is impossible to do a diagnosis without the log. See the wiki 
> article *Help! Posting to weewx-user 
> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>*.
>
> On Mon, Mar 21, 2022 at 4:57 AM tarob...@gmail.com  
> wrote:
>
>> After updating to weewx v 4.7 and also updating the Seasons skin to 4.7, 
>> I've noticed the UV graph no longer updates. UV data is there as I see it 
>> in current conditions as well as the statistics section. The radiation 
>> graph updates as expected as well, just seems the UV graph is stuck with 
>> date/time stamp of just before the v4.7 upgrade. Did the UV imagine 
>> generator/naming convention for the graph change in this update?
>>
>> Thanks,
>> Troy
>>
>> -- 
>> 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/469aca7e-800b-429d-95c9-0e7d02a141c6n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/469aca7e-800b-429d-95c9-0e7d02a141c6n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/6fae24a4-53cb-4d0a-b678-a7b3c6ed6476n%40googlegroups.com.

[weewx-user] UV Index - Seasons Skin 4.7 update

[tarob...@gmail.com]

After updating to weewx v 4.7 and also updating the Seasons skin to 4.7, 
I've noticed the UV graph no longer updates. UV data is there as I see it 
in current conditions as well as the statistics section. The radiation 
graph updates as expected as well, just seems the UV graph is stuck with 
date/time stamp of just before the v4.7 upgrade. Did the UV imagine 
generator/naming convention for the graph change in this update?

Thanks,
Troy

-- 
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/469aca7e-800b-429d-95c9-0e7d02a141c6n%40googlegroups.com.

[weewx-user] Re: Hi All, I am running weewx-sdr/MQTT loop packets with Belchertown skin. I have an Acurite 0645M lightning detector, and I've been having major trouble getting it to display the "delta

[tarob...@gmail.com]

Does lightning data show up correctly if you graph it? I have the following 
in the graph.conf for the Belchertown Skin:

[homepage]
...
[[daylightning]]
title = Lightning (hourly total)
time_length = today
aggregate_type = sum
aggregate_interval = 3600
type = column
[[[lightning_strike_count]]]
name = Lightning
[[[lightning_distance]]]
name = Min Distance
aggregate_type = min
yAxis = 1

On Monday, March 7, 2022 at 11:22:11 AM UTC-5 Kingsclear Studios wrote:

> Thank you Doug, this is more or less the roadblock(s) I've come against 
> too, I've tried this fruitlessly since 2019 with no luck so I figured I 
> would finally post about it to see if anyone has had any concrete luck. 
> Thanks for the recommendation of the AS3925, I believe that is the same 
> core-sensor on the 06045M with a different wrapper on the SDR, so that is 
> probably challenging. I just liked it due to the audio/visual warnings it 
> produces in use at home, as well as the added value of extra 
> temperature/humidity readings, which albeit work fine.
>
> Thanks again,
> Mike.
>
> On Monday, March 7, 2022 at 11:59:36 AM UTC-4 do...@dougjenkins.com wrote:
>
>> I have tried my hand in this device last year with SDR and MQTT. What I 
>> found is that the device's counter counts up to 127 (or 255 depending on 
>> the SDR release) then essentially resets back to zero. I did not see any 
>> code that would compare the incoming value (eg strike count is now 100) to 
>> the loop value (eg 99) and update the strike count by 1. 
>>
>> My best guess is that Acurite's base station is doing this math 
>> difference and showing you the total strikes for the day with the distance 
>> of the last strike.
>>
>> What needs to be done here is have a driver/service that will take the 
>> raw SDR value for lightning strike count and distance, compare it to the 
>> last reported value, then create a record recording the strike count and 
>> distance as a separate row in a table (eg lighting_raw_data). Once the 
>> archive generation starts, you take the sum of the strikes between archive 
>> periods and average the strike distance. I believe that is what the 
>> accumulator will do for you.
>>
>> This is where I gave up on the device. I have it in my "nice to have" 
>> notes to write this component one day.
>>
>> An alternative is to look at the AS3925 lightning sensor. You can attach 
>> that to a Raspberry PI and use Matthew Wall's driver 
>> (matthewwall/weewx-as3935: 
>> weewx service that collects data from as3935 lightning detector (github.com) 
>> <https://github.com/matthewwall/weewx-as3935>) in a separate weewx 
>> instance reporting to a separate db. From there you can bind both databases 
>> in your main weewx install and report the lightning data in your skin. Look 
>> up multiple database bindings in the docs side of the the weewx 
>> documentation.
>>
>> Hope that helps!
>>
>> Doug Jenkins
>> www.largoweather.com
>>
>>
>>
>> On Monday, March 7, 2022 at 8:42:46 AM UTC-5 Kingsclear Studios wrote:
>>
>>> Thanks Troy, can confirm it's in place, makes no difference:
>>>
>>> [Accumulator]
>>> [[lightning_strike_count]]
>>> extractor = sum
>>> [[lightning_distance]]
>>> extractor = min
>>> merger = minmax
>>>
>>> Lightning Distance is working perfectly, after each artificial strike 
>>> test (power drill + brushless motor = fake lightning) I get the distance 
>>> updated properly, with units, my total_strikes count goes up, and I see odd 
>>> entries like: strike_count: 0.0 - but no delta value(s), I've been trying 
>>> for ages, it seems to elude me :)
>>>
>>> Sample MQTT data flowing to the station as of now:
>>>
>>> { "inHumidity": "31.0", "inTemp_C": "23.775", 
>>> "strikes_total": "244.0", "lightning_distance_km": "6.437376", "dateTime": 
>>> "1646660541.0", "inDewpoint_C": "5.625713349750434", "maxSolarRad_Wpm2": 
>>> "362.7045034071919", "rainRate_cm_per_hour": "0.0", "strikes_count": "0.0", 
>>> "rain_total": "1.59", "windSpeed_kph": "4.310998666280064", "outTemp_C": 
>>> "5.889", "outHumidity": "86.0", "appTemp_C&quo

[weewx-user] Re: Hi All, I am running weewx-sdr/MQTT loop packets with Belchertown skin. I have an Acurite 0645M lightning detector, and I've been having major trouble getting it to display the "delta

[tarob...@gmail.com]

cumulator]
>>> [[lightning_strike_count]]
>>> extractor = sum
>>> [[lightning_distance]]
>>> extractor = min
>>> merger = minmax
>>>
>>> Lightning Distance is working perfectly, after each artificial strike 
>>> test (power drill + brushless motor = fake lightning) I get the distance 
>>> updated properly, with units, my total_strikes count goes up, and I see odd 
>>> entries like: strike_count: 0.0 - but no delta value(s), I've been trying 
>>> for ages, it seems to elude me :)
>>>
>>> Sample MQTT data flowing to the station as of now:
>>>
>>> { "inHumidity": "31.0", "inTemp_C": "23.775", 
>>> "strikes_total": "244.0", "lightning_distance_km": "6.437376", "dateTime": 
>>> "1646660541.0", "inDewpoint_C": "5.625713349750434", "maxSolarRad_Wpm2": 
>>> "362.7045034071919", "rainRate_cm_per_hour": "0.0", "strikes_count": "0.0", 
>>> "rain_total": "1.59", "windSpeed_kph": "4.310998666280064", "outTemp_C": 
>>> "5.889", "outHumidity": "86.0", "appTemp_C": 
>>> "3.6810358576208713", "cloudbase_meter": "326.41695917564834", 
>>> "dewpoint_C": "3.7282050766260766", "heatindex_C": "4.7788891", 
>>> "humidex_C": "5.889", "windchill_C": "5.889", 
>>> "extraTemp1_C": "5.3995", "extraHumid1": "53.0", "windDir": 
>>> "225.0", "hourRain_cm": "0.025423", "rain24_cm": 
>>> "1.98120007", "dayRain_cm": "0.7112", "usUnits": "16.0" }
>>> On Monday, March 7, 2022 at 9:02:11 AM UTC-4 tarob...@gmail.com wrote:
>>>
>>>> The only thing I see missing from your weewx.conf would be the 
>>>> Accumulator section:
>>>>
>>>> [Accumulator]
>>>> [[lightning_strike_count]]
>>>> extractor = sum
>>>> [[lightning_distance]]
>>>> extractor = min
>>>>
>>>> See if adding the Accumulator section in your weewx.conf fixes your 
>>>> issue.
>>>>
>>>> -Troy
>>>>
>>>> On Sunday, March 6, 2022 at 7:40:30 AM UTC-5 Kingsclear Studios wrote:
>>>>
>>>>> Weewx Conf:
>>>>>
>>>>> [SDR]
>>>>> # This section is for the software-defined radio driver.
>>>>>
>>>>> # The driver to use
>>>>> driver = user.sdr
>>>>> path = /usr/local/bin
>>>>> log_unknown_sensors = True
>>>>> log_unmapped_sensors = True
>>>>> [[sensor_map]]
>>>>> extraTemp1 = temperature.1720.AcuriteTowerPacketV2# 
>>>>> basement
>>>>> extraHumid1 = humidity.1720.AcuriteTowerPacketV2
>>>>> outTemp = temperature.041D.Acurite5n1PacketV2
>>>>> outHumidity = humidity.041D.Acurite5n1PacketV2
>>>>> rain_total = rain_total.041D.Acurite5n1PacketV2
>>>>> windDir = wind_dir.041D.Acurite5n1PacketV2
>>>>> windSpeed = wind_speed.041D.Acurite5n1PacketV2
>>>>> inHumidity = humidity.009B.AcuriteLightningPacket#upstairs 
>>>>> Humidity
>>>>> inTemp = temperature.009B.AcuriteLightningPacket#upstairs 
>>>>> Temperature
>>>>> strikes_total = strikes_total.009B.AcuriteLightningPacket   
>>>>>  #Total Lightning Strike Count
>>>>> lightning_distance = distance.009B.AcuriteLightningPacket   
>>>>>  #Storm Distance KM
>>>>> [[sensor_type]]
>>>>> strikes_total = counter
>>>>> [[data_type]]
>>>>> strikes_total = delta
>>>>> [[Deltas]]
>>>>> lightning_strike_count = strikes_total
>>>>>
>>>>>
>>>>> Belchertown Display Settings:
>>>>>
>>>>> station_observations = outTemp, outHumidity, heatindex, dewpoint, 
>>>>> rainRate, windSpeed, windDir, windGust, lightning_strike_count, 
>>>>> lightning_distance, inTemp, inHumidity, extraTemp1
>>>>>
>>>>> Which results in display of "N/A" for lightning strikes.
>>>>>
>>>>> I can trigger an artificial strike to get a count, and I do see 
>>>>> "strikes_total" climbing during this time, so it's recording the event 
>>>>> itself in the DB/MQTT and sending it, but I cannot seem to get it to 
>>>>> display in the skin as a "daily" count = or a count based on the 
>>>>> established reporting period. The 06045M is a counter, it wraps at 255 
>>>>> now, 
>>>>> so I do understand how it works more or less, just not how to get it to 
>>>>> display properly in the skin and for charting in the near future.
>>>>>
>>>>> I've read dozens of threads, and I can't seem to find a conclusive 
>>>>> solution - help!!
>>>>>
>>>>> Most recently added to [StdCalibrate]: lightning_distance = 
>>>>> lightning_distance if lightning_strike_count > 0 else None
>>>>>
>>>>>
>>>>> [image: Capture.PNG]
>>>>>
>>>>

-- 
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/b567562e-e274-4dc4-8566-2c903b28204cn%40googlegroups.com.

[weewx-user] Re: Hi All, I am running weewx-sdr/MQTT loop packets with Belchertown skin. I have an Acurite 0645M lightning detector, and I've been having major trouble getting it to display the "delta

[tarob...@gmail.com]

The only thing I see missing from your weewx.conf would be the Accumulator 
section:

[Accumulator]
[[lightning_strike_count]]
extractor = sum
[[lightning_distance]]
extractor = min

See if adding the Accumulator section in your weewx.conf fixes your issue.

-Troy

On Sunday, March 6, 2022 at 7:40:30 AM UTC-5 Kingsclear Studios wrote:

> Weewx Conf:
>
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
> path = /usr/local/bin
> log_unknown_sensors = True
> log_unmapped_sensors = True
> [[sensor_map]]
> extraTemp1 = temperature.1720.AcuriteTowerPacketV2# basement
> extraHumid1 = humidity.1720.AcuriteTowerPacketV2
> outTemp = temperature.041D.Acurite5n1PacketV2
> outHumidity = humidity.041D.Acurite5n1PacketV2
> rain_total = rain_total.041D.Acurite5n1PacketV2
> windDir = wind_dir.041D.Acurite5n1PacketV2
> windSpeed = wind_speed.041D.Acurite5n1PacketV2
> inHumidity = humidity.009B.AcuriteLightningPacket#upstairs 
> Humidity
> inTemp = temperature.009B.AcuriteLightningPacket#upstairs 
> Temperature
> strikes_total = strikes_total.009B.AcuriteLightningPacket   
>  #Total Lightning Strike Count
> lightning_distance = distance.009B.AcuriteLightningPacket   
>  #Storm Distance KM
> [[sensor_type]]
> strikes_total = counter
> [[data_type]]
> strikes_total = delta
> [[Deltas]]
> lightning_strike_count = strikes_total
>
>
> Belchertown Display Settings:
>
> station_observations = outTemp, outHumidity, heatindex, dewpoint, 
> rainRate, windSpeed, windDir, windGust, lightning_strike_count, 
> lightning_distance, inTemp, inHumidity, extraTemp1
>
> Which results in display of "N/A" for lightning strikes.
>
> I can trigger an artificial strike to get a count, and I do see 
> "strikes_total" climbing during this time, so it's recording the event 
> itself in the DB/MQTT and sending it, but I cannot seem to get it to 
> display in the skin as a "daily" count = or a count based on the 
> established reporting period. The 06045M is a counter, it wraps at 255 now, 
> so I do understand how it works more or less, just not how to get it to 
> display properly in the skin and for charting in the near future.
>
> I've read dozens of threads, and I can't seem to find a conclusive 
> solution - help!!
>
> Most recently added to [StdCalibrate]: lightning_distance = 
> lightning_distance if lightning_strike_count > 0 else None
>
>
> [image: Capture.PNG]
>

-- 
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/cd9878b4-00fb-4834-9fc3-ad78ee041dean%40googlegroups.com.

[weewx-user] Re: Poll rtl-sdr and I2C together

[tarob...@gmail.com]

Here's the guide I followed when adding the pressure/temp sensor to my 
Raspberry Pi: https://github.com/bdwilson/acurite/blob/master/Pressure.md


On Tuesday, December 7, 2021 at 3:17:49 AM UTC-5 udo.kl...@gmail.com wrote:

> Hello everyone, I have successfully set up my Bresser weather station 
> using rtl_433 and rtl-sdr on a Raspberry Pi with WeeWX. So far everything 
> works as desired. However, my weather station does not provide air 
> pressure. 
>
> To collect this value and other data I bought a BMP280 sensor, which I 
> want to query via I2C bus and WeeWX. Unfortunately, I lack the 
> understanding of how I can integrate additional sensors in addition to my 
> weather station, e.g. via I2C.
>
> It would be nice if someone could give me a hint. Thanks a lot
>

-- 
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/28b6f95e-efcb-49ef-aceb-78da64d23e6en%40googlegroups.com.

[weewx-user] Re: Acurite Atlas (status?)

[tarob...@gmail.com]

I've been running an Acurite Atlas and Acurite 5n1 for over a year using 
raspberry Pi 3B and weewx with the SDR driver. The guide I followed is here 
(https://github.com/bdwilson/acurite). Adding the pressure was the hardest 
but got it working with BME280 temp/pressure/humidity sensor and this guide 
(https://github.com/bdwilson/acurite/blob/master/Pressure.md). Adding the 
lightning data wasn't difficult and I can post my config if needed. I can 
post you the links of the USB antenna used and the BME sensor. It might 
take a bit of effort to setup up, but in the long run IMO this is a great 
setup as it allows you to add just about any RTL sensors from many brands 
to the setup. 

BME 
Sensor: 
https://www.amazon.com/gp/product/B01LETIESU/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
RTL-SDR 
Antenna: 
https://www.amazon.com/gp/product/B009U7WZCA/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1



On Tuesday, November 16, 2021 at 9:00:57 PM UTC-5 storm...@gmail.com wrote:

> By "stable" I mean the oscillator frequency does not drift over time.  
> That will be fine for what you want to do.
>
> On Tuesday, November 16, 2021 at 8:13:08 PM UTC-5 kkru...@gmail.com wrote:
>
>> By "stable" do you mean signal strength / quality / SNR, lapses in 
>> connection, availability to the OS, or something else? 
>> I'm not too concerned about interference as the location for this is 
>> quite rural, in the woods. 
>>
>> Unfortunately, I ordered the NESDR Mini 2 before reading your comment. 
>> Yet I'm wondering if it it'll be "good enough" for what I'm trying to 
>> accomplish. 
>>
>> On Monday, November 15, 2021 at 8:02:31 PM UTC-8 storm...@gmail.com 
>> wrote:
>>
>>> In my opinion, I would look at something like this:
>>>
>>>
>>> https://www.amazon.com/NooElec-NESDR-Smart-Bundle-R820T2-Based/dp/B01GDN1T4S/ref=sr_1_4?keywords=rtl-sdr=1637035059=8-4
>>>
>>> The V3/V4 versions are much more stable then the originals.
>>>
>>>
>>> On Monday, November 15, 2021 at 10:07:38 PM UTC-5 kkru...@gmail.com 
>>> wrote:
>>>
 Thanks so much for the responses so far. Stephen... I think I've seen 
 some of your posts re: Atlas. I may just give this another chance with the 
 SDR. Can you (or anyone) tell me if one or both of these works out of the 
 box:

 https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini.html
 https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-2.html

 And thanks Vince for informing me about the Ecowitt products. I haven't 
 looked at those until now. Very interesting! 

 On Monday, November 15, 2021 at 3:59:29 PM UTC-8 vince wrote:

> You can get into ecowitt 'very' inexpensively especially if you don't 
> need a display.  Gary's weewx driver is very solid.
>
> Disclaimer - the gateway module requires internet connectivity or 
> it'll reboot very often due to its watchdog timers.  If that's ok for 
> your 
> site, you might want to give them a look.
>
> Poke around https://www.amazon.com/ecowitt/s?k=ecowitt for 
> possibilities.   You can do it ala-carte piece by piece or they have more 
> integrated solutions with/without a console.
>
>
>

-- 
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/1bcb202c-5442-4be0-8baa-d528da296f4fn%40googlegroups.com.

[weewx-user] Re: Belchertown new install

[tarob...@gmail.com]

I have both Seasons Skin and Belchertown. I like having both, up to you if 
you want to disable the Seasons Skin. However, you can keep everything the 
same, just add /belchertown to the end of your url. So instead of 
http://your_ip/weewx it will be http://your_ip/weewx/belchertown

-Troy

On Monday, September 27, 2021 at 1:58:31 AM UTC-4 zman_...@yahoo.com wrote:

> I am doing a brand new install of the Belchertown skin so here is a noob 
> question for the group.  How do I actually get weewx to start using the 
> Belchertown skin and start uploading it to my webhost?  Do I need to set 
> enable = true in the weewx.conf file?
>
> It seems to still constantly upload the Seasons skin to my web host.  
> Where is the switch to start using the new Belchertown skin?  
>
> Here is the weewx.conf file.
>
> [[Belchertown]]
> skin = Belchertown
> enable=true
> HTML_ROOT = /var/www/html/weewx/belchertown
>
> Is this the old Seasons skin?  This is what it constantly uploads.  I'm 
> not seeing Belchertown at all and I'm pulling my hair out trying to 
> understand what is wrong.  
>
> Thanks for the help.
> Chris 
> [image: Capture.JPG]
>
>

-- 
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/9c3830c8-64d8-473f-98b6-c4e243e68b4dn%40googlegroups.com.

[weewx-user] Re: AcuRite 06045M lightning detector shows constant 12 miles distance when no detected lightning

[tarob...@gmail.com]

I think going back to your original issue something seems to be off. Can 
you post you weewx.conf for lightning data? If you're using sdr, should 
contain the following in each section:

[SDR]
[[sensor_map]]
..
lightning_distance = distance..AcuriteLightningPacket
strikes_total = strikes_total..AcuriteLightningPacket
[[deltas]]
rain = rain_total
lightning_strike_count = strikes_total

[StdCalibrate]

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

[Accumulator]
[[lightning_strike_count]]
extractor = sum
[[lightning_distance]]
extractor = min

On Tuesday, August 10, 2021 at 2:46:44 PM UTC-4 gle...@gmail.com wrote:

> Initially I thought Rich's solution was going to work, adding his 
> suggested correction  'lightning_strike_count'in locals() and lightning_strike_count> 0 else 
> None>  eliminated my fixed lightning_distance data in the absence of 
> lightning_counts, but it created a new problem, now I don't get 
> lightning_distance values with a lightning strike.  I triggered the 
> lightning detector with a spark by transiently shorting a battery charger 
> at time 14:22:16 , which produced 2 detected lightnings and 14:22:24 which 
> produced one, but the lightning_distance remains at None.  My mqtt explorer 
> reports the lightning detector is sending a constant 12-mile lightning 
> distant 
>
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.82, 
> lightning_distance: None, maxSolarRad: None, outHumidity: 73.0, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.81, 
> lightning_strike_count: 2.0, maxSolarRad: None, rainRate: 0.32, usUnits: 1  
>   <
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.82, 
> lightning_distance: None, lightning_strike_count: 0.0, maxSolarRad: None, 
> rainRate: 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.83, 
> lightning_distance: None, lightning_strike_count: 0.0, maxSolarRad: None, 
> rainRate: 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.81, 
> lightning_distance: None, maxSolarRad: None, rainRate: 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.82, 
> lightning_distance: None, maxSolarRad: None, rainRate: 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:16 EDT (1628619736) dateTime: 1628619736.83, 
> lightning_distance: None, maxSolarRad: None, rainRate: 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.67, 
> lightning_distance: None, maxSolarRad: None, outTemp: 82.04, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.68, 
> lightning_distance: None, maxSolarRad: None, outTemp: 82.04, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.69, 
> lightning_distance: None, maxSolarRad: None, outTemp: 82.04, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.67, 
> lightning_distance: None, maxSolarRad: None, outHumidity: 73.0, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.68, 
> lightning_distance: None, maxSolarRad: None, outHumidity: 73.0, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.69, 
> lightning_distance: None, maxSolarRad: None, outHumidity: 73.0, rainRate: 
> 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.68, 
> lightning_strike_count: 1.0, maxSolarRad: None, rainRate: 0.32, usUnits: 1  
>   <---
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.69, 
> lightning_distance: None, lightning_strike_count: 0.0, maxSolarRad: None, 
> rainRate: 0.32, usUnits: 1
> LOOP:   2021-08-10 14:22:24 EDT (1628619744) dateTime: 1628619744.69, 
> lightning_distance: None, lightning_strike_count: 0.0, maxSolarRad: None, 
> rainRate: 0.32, usUnits: 1
>
>
> On Tuesday, August 10, 2021 at 9:20:17 AM UTC-4 bell...@gmail.com wrote:
>
>> I'm no python expert (probably know just enough to be dangerous), but 
>> something like this might get you want you want. 
>>
>> # ligtning_strike_count must exist and have a count > 0 for 
>> lightning_distance to have a valid value
>> lightning_distance = lightning_distance if 'lightning_strike_count'in 
>> locals() and lightning_strike_count> 0 else None
>>
>> rich
>> On Tuesday, 10 August 2021 at 03:03:01 UTC-4 gjr80 wrote:
>>
>>> On Tuesday, 10 August 2021 at 08:37:42 UTC+10 gle...@gmail.com wrote:
>>>
 Here is my output running weewxd directly, I see three lines which show 
 lightning_distance to be None, which is expected from 

[weewx-user] Re: Graphing Lightning Strikes/Distance With Belchertown Sking & Ecowitt WH57

[tarob...@gmail.com]

>From my understanding, when graphs are being generated they are read from 
the weewx database (weewx.sdb if SQlite). The issue you are describing 
sounds like an issue with how the data is stored in the database and not 
with how Belchertown is graphing. I had similar issue when I first started 
collecting lightning data using an acurite lightning sensor. 
See: https://groups.google.com/g/weewx-user/c/xBihBm0jVls/m/J06dlCjlAAAJ 
for more info. This might help you.

On Friday, April 23, 2021 at 4:00:38 PM UTC-4 Alan Bryant wrote:

> Forgot to add the graph code so that you guys don't have to go look it up.
>
> title = Lightning
>   [[[lightning_strike_count]]]
>  name = Number of strikes
>  color = "#ffc83f"
>   [[[lightning_distance]]]
>   name = Distance to Strike
>   color = "#f7f2b4"
>   y_label = "km" 
>
> On Friday, April 23, 2021 at 2:59:48 PM UTC-5 Alan Bryant wrote:
>
>>
>> Hello Everyone,
>>
>> I am a very amateur weather enthusiast, so all of this amazing software 
>> that you guys have put together is phenomenal. Thank all of you so much for 
>> the time that you have put in to these products and the support!
>>
>> I think that I have everything set up mostly how I want it, except for 
>> the Lightning Graph on the main page.
>>
>> I used the code from a previous thread (
>> https://groups.google.com/g/weewx-user/c/tunBoIOIXtI/m/dBchokefCgAJ) 
>> that seems to work, but since the GW1000 driver enters the  
>> lightning_distance into the DB whether there are any new strikes or not, 
>> the distance gets graphed constantly.
>>
>> Is there a way with HighCharts to tell it not to graph the distance 
>> unless there is a number of strikes > 0?
>>
>> Specs:
>> Site: https://weather.bryantgeeks.com
>> Weewx: 4.5.1
>> Belchertown 1.3b1
>> GW1000 Driver: 0.3.1
>> Ecowitt GW1000
>> WH31
>> WS68
>> WH57
>> WH40
>>
>

-- 
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/eb38c5b1-85fe-4520-9428-7275668a913an%40googlegroups.com.

Re: [weewx-user] Re: Version 4.5.0 released

[tarob...@gmail.com]

Upgraded from 4.4 to 4.5.1 via sudo apt without stopping weewx and had no 
issues. Running on Raspberry Pi 4, Raspbian buster.

On Saturday, April 3, 2021 at 2:47:20 PM UTC-4 PJO wrote:

> I updated (via sudo apt upgrade, after stopping weewx) from 4.4 to 4.5.1 
> on Ubuntu 20.04 Core opting to get an updated weewx.conf
>
> Configuration file '/etc/weewx/weewx.conf'
>  ==> Modified (by you or by a script) since installation.
>  ==> Package distributor has shipped an updated version.
>What would you like to do about it ?  Your options are:
> Y or I  : install the package maintainer's version
> N or O  : keep your currently-installed version
>   D : show the differences between the versions
>   Z : start a shell to examine the situation
>  The default action is to keep your current version.
> *** weewx.conf (Y/I/N/O/D/Z) [default=N] ? Y
> Installing new version of config file /etc/weewx/weewx.conf ...
> Installing new version of config file /etc/weewx/weewx.conf.dist ...
> using debconf configuration values from previous install
> update-rc.d: error: unable to read /etc/init.d/weewx
> dpkg: error processing package weewx (--configure):
>  installed weewx package post-installation script subprocess returned 
> error exit status 1
> Processing triggers for systemd (245.4-4ubuntu3.5) ...
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> I ended up with a bad weewx.conf and had to restore weewx.conf.dpkg-old
> On Saturday, April 3, 2021 at 1:24:52 PM UTC+1 tke...@gmail.com wrote:
>
>> Yes, it's possible to extend the V4 schema. That's what is documented in 
>> the section *Modifying a starting schema 
>> . *
>>
>> But, let's keep the wview schema at V3. 
>>
>> On Sat, Apr 3, 2021 at 1:21 AM Gérard P  wrote:
>>
>>> It is possible to stay with 4.5.0 by changing the syntax of code using 
>>> the "+" operator, for instance :
>>> schema_extended = schemas.wview.schema + [('lightning_strikes', 
>>> 'REAL'), ('avg_distance', 'REAL')]
>>> become
>>> schema_extended = schemas.wview.schema.copy()
>>> schema_extended.update([('lightning_strikes', 'REAL'), 
>>> ('avg_distance', 'REAL')])
>>>
>>> Le vendredi 2 avril 2021 à 21:14:27 UTC+2, mksm...@gmail.com a écrit :
>>>
 the upgrade to 4.5 from 4.4 failed and weewx is broken please advice
 used these commands for upgrade
 sudo apt update
 apt list --upgradable  (4.5 was showing)
 sudo apt full-upgrade
 then I answered "N" to the upgrade select to keep my old files

 Apr  2 21:31:49 raspberrypi systemd[1]: Starting LSB: weewx weather 
 system...
 Apr  2 21:31:49 raspberrypi weewx[1049]: Starting weewx weather system: 
 weewxTraceback (most recent call last):
 Apr  2 21:31:49 raspberrypi weewx[1049]:   File 
 "/usr/share/weewx/weewxd", line 29, in 
 Apr  2 21:31:49 raspberrypi weewx[1049]: import user.extensions
 Apr  2 21:31:49 raspberrypi weewx[1049]:   File 
 "/usr/share/weewx/user/extensions.py", line 20, in 
 Apr  2 21:31:49 raspberrypi weewx[1049]: schema_extended = 
 schemas.wview.schema + [('lightning_strikes', 'REAL'), ('avg_distance', 
 'REAL')]
 Apr  2 21:31:49 raspberrypi weewx[1049]: TypeError: unsupported operand 
 type(s) for +: 'dict' and 'list'
 Apr  2 21:31:49 raspberrypi weewx[1049]:  failed!
 Apr  2 21:31:49 raspberrypi systemd[1]: weewx.service: Control process 
 exited, code=exited, status=1/FAILURE
 Apr  2 21:31:49 raspberrypi systemd[1]: weewx.service: Failed with 
 result 'exit-code'.
 Apr  2 21:31:49 raspberrypi systemd[1]: Failed to start LSB: weewx 
 weather system.

>>>
>>> -- 
>>> 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/a14fa3bd-3a52-4df4-be1b-00936e9f7f67n%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/7aafd4d5-7a6e-4656-9b79-91af5b311604n%40googlegroups.com.

[weewx-user] Re: Raspberry pi with sensor (temperature/humidity) working?

[tarob...@gmail.com]

I am using a BME280 pressure/temp/humidity sensor added to my RPi using 
this: https://github.com/parautenbach/WeeWX-BME280


On Thursday, March 4, 2021 at 5:34:07 AM UTC-5 giulianodir...@gmail.com 
wrote:

> Hey
>
> I'm quite new to the field with the Raspberry Pi. Now to my question.. We 
> got a job at school to implement a scientific project with the help of a 
> Raspberry Pie. Since I am very interested in the weather and climatology, I 
> thought that I would build a climate logger/weather staion with the help of 
> a Raspberry Pie. Now before I buy the components, I wanted to let someone 
> look over them again. My idea is using sensors (air 
> pressure/temperature/humidity /CO2 content). 
> display. After a few hours of research I came across the program "Weewx". 
> Now my question is whether it would be possible to implement this project 
> using sensors that I connect to a Raspberry Pi. Since I also met suitable 
> hardware in the documentation on very expensive "finished" weather station 
> modules, I got a bit stupid.
>
> I would be pleased to receive an answer ^^
>
> Hardware:
> -Raspberry Pi Zero
>
> -Air pressure/humidity and temperature sensor  
>
> Would this work with the Weewx program? 
>

-- 
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/b8d9cd29-6204-48e8-801f-f6ccf8a5a1b7n%40googlegroups.com.

Re: [weewx-user] NWS Radar Changes

[tarob...@gmail.com]

I ended up embedding an iframe (windy) in the radar.inc file and commenting 
out the lines that were no longer needed. This has worked great.

On Monday, January 11, 2021 at 11:07:55 PM UTC-5 ral...@gmail.com wrote:

> Anybody able to make the new and improved NWS radar work?  Has anyone 
> written code to build a dynamic link for the aviation weather radar? It 
> appears to me that we need to enter date and time into the url for the 
> radar. I copied the aviation radar link into my skin.conf and it appeared 
> to work, then after a week I noticed that its showing Dec 31 data.   
> https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif
>
> On Friday, January 1, 2021 at 5:28:07 AM UTC-8 messyp...@gmail.com wrote:
>
>> I just found out why my "
>> http://radar.weather.gov/ridge/lite/N0R/HTX_loop.gif; is broke, and, why 
>> I can't find the replacement. They redesigned the entire system (from 
>> something that was working fine) to what could be described as "the new 
>> Coke" of NWS radar services. This article explains it succinctly:
>>
>> https://www.washingtonpost.com/weather/2020/12/21/nws-new-radar-website-slow/
>> Really disappointing. 
>> --MP
>>
>> On Thursday, December 31, 2020 at 9:44:39 PM UTC+1 tke...@gmail.com 
>> wrote:
>>
>>> Here's another option: NOAA's aviation radar. 
>>> https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif
>>>
>>> The images load fast and cover the entire USA.
>>>
>>> [image: image.png]
>>>
>>> On Wed, Dec 30, 2020 at 9:52 AM John Mora  wrote:
>>>
 I have been using these links:
 https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=ILN;
 brand=wui=18=15=N0R=0=1.000=0
 wstorms=1=1=1=1=1=1 

 https://www.wunderground.com/radar/us/oh/cincinnati/iln

 Just replace the station with the one you desire.

 To me they are an adequate replacement until a better one is found

 Cheers!

 On Wednesday, December 30, 2020 at 12:40:17 PM UTC-5 
 jo...@johnkline.com wrote:

> >  I haven't see this link listed anywhere yet.
> It’s listed in this thread.
>
> On Dec 30, 2020, at 8:35 AM, Mark Jenks  wrote:
>
> Finally got an answer back from NOAA.  I haven't see this link listed 
> anywhere yet.   Images aren't the best, but it's something better than 
> the 
> .gz's and straight .gif files
>
>
>
> https://radar.weather.gov/ridge/lite/
>
>
> On Wednesday, December 23, 2020 at 7:12:15 AM UTC-6 Mark Jenks wrote:
>
>> Email contact information here:
>> https://www.weather.gov/radarfaq
>>
>> On Wednesday, December 23, 2020 at 7:10:50 AM UTC-6 Mark Jenks wrote:
>>
>>> I just sent an email to NWS.  I'll let you know the response if I 
>>> get one..
>>>
>>> 
>>>
>>> Good Morning!
>>>
>>> For years, there have been many many people who have linked your 
>>> radar images and loops to their PWS (Personal weather station) 
>>> websites.  I 
>>> currently use weewx @ http://weather.mjenks.net
>>> With the new radar, this is no longer possible, and the .gz versions 
>>> just aren't good enough quality.  So I have to use someone else's radar 
>>> now.
>>>
>>> It sure would be nice if you could provide an iframe code snipped 
>>> that we could embed into our webpages.Or at least recreate the 
>>> images 
>>> and loops.
>>>
>>> This is what I have been using that no longer works.
>>>
>>> radar_img = http://radar.weather.gov/ridge/lite/N0R/GRB_loop.gif
>>> radar_url = 
>>> http://radar.weather.gov/ridge/radar.php?product=NCR=GRB=yes
>>>
>>> Thank you!
>>>
>>> Mark Jenks
>>> Station ID - DW7584
>>>
>>> On Tuesday, December 22, 2020 at 4:20:17 PM UTC-6 chri...@gmail.com 
>>> wrote:
>>>
 Thank you for looking into this folks. It sounds as though they 
 have gone the same route as Environment Canada did a long time ago 
 now.  No 
 more animated gifs available, instead they build the animations on the 
 fly 
 with overlays and a repository of images. The best I could do for 
 Environment Canada radars was to create a shell script that runs on 
 the web 
 server cron that guesses at the current time stamp for the latest 
 image and 
 saves it to my webserver.

 Less than great.

 It sure would be nice if they could just provide an iframe code 
 snipped that we could embed into our webpages.
 Alas.
 Cheers
 Chris
 On Saturday, December 19, 2020 at 9:59:31 AM UTC-8 
 peterq...@gmail.com wrote:

> I hooked up the NWS gif and it's worse than useless. It's hours 
> old and shows nothing, flashes clutter, and repeats. Now, it should 

Re: [weewx-user] Updating Debian Jessie to Buster

[tarob...@gmail.com]

So I've finally got around to getting a new Pi loaded with Buster and 
installed Weewx using python3, all the extensions, and skins. The final 
part is moving my weewx.sdb and I want to ensure I do this properly. Would 
I just be able to stop weewx, copy over weewx.sbd (all historical data), 
and move it to the new Pi? Then start weewx on the new Pi? Or is there 
something else I'll need to do? Thanks.

On Tuesday, November 10, 2020 at 7:58:06 AM UTC-5 tarob...@gmail.com wrote:

> Thanks for the advice. I am running weewx with SDR, so no console to store 
> data. Although I have an acurite access which is still collecting data so I 
> can use that data to fill in any gaps I have while transitioning. I think 
> if I just back up my weewx.conf, my skins, and weewx.sdb I should have 
> everything I need. Plus getting the BME280 pressure/temp running on the new 
> pi and all the weewx extensions I have (BME280, forecast, and SDR).
>
> On Mon, Nov 9, 2020, 5:18 PM Ian Prescott  wrote:
>
>> HI Troy
>> I did something very similar awhile ago and didn't have any issues.
>> As Vince said "use a new sd card to build the new system"
>> What made my transition easy was the weather console has a memory that 
>> holds approx several days of data.
>> If I stop weewx for some reason and for some hours, then restart it, 
>> weewx appears to retrieve the missing time interval.
>> This helped by keeping the original database intact.
>> The new sd build database would be discarded when the new sd card was 
>> finished.
>> So over a few days I just swapped between old and new until I was happy 
>> with the new setup.
>> Then just copied over the files I wanted ...just mounted the old sd 
>> card on another pi and copied the files over.
>>
>> regards ian p
>>
>> On Tue, 10 Nov 2020 at 02:14, tarob...@gmail.com  
>> wrote:
>>
>>> Hello,
>>> When I initially setup weewx, I was very new to raspberry pi OS and so I 
>>> used what I had currently had on hand, a RPi I got a couple years ago which 
>>> was running Jessie. Recently, I've realized there are some issues, mainly 
>>> Python2.7 and Python3.8, that basically boiled down to running Jessie vice 
>>> the new Buster. If anyone is wondering, the SSL module was having issues 
>>> installing updates via pip command and it came down to the OS.
>>>
>>> Anyway, I plan to create a new SD card with Debian 10 (Buster) and then 
>>> install weewx. I've read upgrading OS from Jessie to Stretch to Buster 
>>> could take quite a bit of time and there is a risk to losing data. My 
>>> question comes, what's the quickest way to get weewx running, as it is 
>>> configured now, on the new OS? Ensure I backup my weewx.conf, weewx.sdb, 
>>> and skins? Is there anything else I should be conscience of when moving? Is 
>>> there an "easier" way to do this? Just worried I'll be down for a while 
>>> trying to configure and get everything up and running as it is now.
>>>
>>> Thanks,
>>> Troy
>>>
>>> -- 
>>> 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/4d20cad3-5af5-4ea3-996b-620e2c91a181n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/4d20cad3-5af5-4ea3-996b-620e2c91a181n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> -- 
>>
> 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/ICkSU9ivYL8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAN84nRuvmrym1_9OKLnjhmiAXLZhu_fuPSLJC%3D003FuMJg0D%2BA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/CAN84nRuvmrym1_9OKLnjhmiAXLZhu_fuPSLJC%3D003FuMJg0D%2BA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/d0773616-ca59-422e-8f2a-0324ac33b51dn%40googlegroups.com.

Re: [weewx-user] Re: How to properly record Lightning Data

[tarob...@gmail.com]

Not sure if this would help you Earl but I've set up to capture lightning 
as follows :

weewx.conf 

[SDR]
[[sensor_map]]
lightning_distance = distance.xxx.AcuriteLightningPacket
strikes_total = strikes_total.xxx.AcuriteLightningPacket
lightning_disturber_count = rfi.xxx.AcuriteLightningPacket
lightning_noise_count = active.xxx.AcuriteLightningPacket
lightning_energy = exception.xxx.AcuriteLightningPacket
[[deltas]]
rain = rain_total
lightning_strike_count = strikes_total

[Accumulator]
[[lightning_strike_count]]
extractor = sum
[[lightning_distance]]
extractor = min
[[lightning_noise_count]]
extractor = sum

I don't exactly know what rfi, active, and exception are in the data 
packets but decided to capture them anyways using existing DB schema titles.

I use the Seasons Skin and added lightning data to Current Conditions as 
"Strikes Today" (total strikes for the current day with the timestamp of 
the last strike) and "Closest Strike" (closest strike in miles with 
timestamp of when it occurred). I also have a bar chart that works very 
similar to rain accumulation (hourly total for day, etc).

On Thursday, November 12, 2020 at 6:21:43 PM UTC-5 tke...@gmail.com wrote:

> Frankly, there is no formal semantics for what any of the lightning 
> quantities mean. They have appeared in various sensors that we have seen 
> through the years (more precisely, that Matthew has seen), so we included 
> them in the extended schema. But, their definition varies from sensor to 
> sensor (much like 'radiation' or 'luminance'). 
>
> So, it's up to you to supply meaning. Maybe your definition will 
> eventually catch on! :-)
>
> On Thu, Nov 12, 2020 at 12:40 PM Earl Baugh  wrote:
>
>> Ok, so that's where I'm confused.  (yes I know the packets have to match 
>> exactly, have already had some earlier bugs because of that)
>>
>> The DB schema has :
>>
>>  'lightning_distance','REAL' 
>>  'lightning_disturber_count', 'REAL' 
>>  'lightning_energy',  'REAL' 
>>  'lightning_noise_count', 'REAL' 
>>  'lightning_strike_count','REAL' 
>>
>> So, when a strike occurs, I should generate  a record (as an example) 
>> with : 
>>
>> {"dateTime":1605212295, "lightning_distance":3.5, "lightning_energy: 
>> "46.3", "lightning_strike_count": "1.0"} 
>>
>> I was assuming I didn't supply lightning_strike_count and a 
>> lightning_distance record would be counted,
>> more like this:
>>
>> {"dateTime":1605212295, "lightning_distance":3.5, "lightning_energy: 
>> "46.3"} 
>>
>> I guess there are a number of use cases here.  If 
>> "lightning_strike_count" was ever, say 2.0, then should 
>> "lightning_distance" be the average distance?  Or is the system just trying 
>> to be flexible for all users (and you just wouldn't provide 
>> lightning_distance in this case)
>>
>> I was leaning towards the 2nd case, so I was confused as to what would be 
>> summed up for noise and disturber. 
>> But if the first is the use, then I need to adjust my code already to 
>> provide the count..
>>
>> Earl
>>
>> p.s. I've not looked at the API enough to know how the accumulated value 
>> is retrieved... so that's another place that may provide clarity for me... 
>> maybe my assumption that "count" would be the value over a time window (not 
>> that it would be "accumulated" across a number of count records...) is 
>> incorrect, that also would be clarifying.
>>
>> On Thu, Nov 12, 2020 at 3:13 PM Tom Keffer  wrote:
>>
>>> There's no magic here. If the record has a type 'lightning_noise_count', 
>>> and the database schema has a matching entry, then it will be put in the 
>>> database. But, the names have to match precisely, including case. 
>>>
>>> The wview_extended schema has 'lightning_noise_count'. A record with 
>>> "Lightning_Count" is not going to cut it.
>>>
>>> On Thu, Nov 12, 2020 at 12:04 PM Earl Baugh  wrote:
>>>
 So, how would a "Lighting_Noise" value be saved in the DB?
 Anywhere?   Or would it just go into the "Lightning_Nose_Count"?  

 (that's where I'm confused)

 Earl

 P.S. Thanks for the info where to suggest changes.I'll submit an 
 Enhancement Request for the other data fields that I'm now capturing.

 On Thu, Nov 12, 2020 at 2:46 PM Tom Keffer  wrote:

> If a new type appears in the data stream, a new "scalar" accumulator 
> will automatically be created for it. When it comes time to extract a 
> datum 
> for a new record, the average will be used by default. If you don't like 
> that, then you can specify a different "extractor."
>
> You can suggest some changes here (or, better, in weewx-development), 
> or submit a PR on GitHub.
>
> -tk
>
> On Thu, Nov 12, 2020 at 11:21 AM Earl Baugh  wrote:
>
>> Tom & Vince,
>>
>> All very helpful info!  It aligns with what I was thinking so far.  
>> This wiki 

[weewx-user] Updating Debian Jessie to Buster

[tarob...@gmail.com]

Hello,
When I initially setup weewx, I was very new to raspberry pi OS and so I 
used what I had currently had on hand, a RPi I got a couple years ago which 
was running Jessie. Recently, I've realized there are some issues, mainly 
Python2.7 and Python3.8, that basically boiled down to running Jessie vice 
the new Buster. If anyone is wondering, the SSL module was having issues 
installing updates via pip command and it came down to the OS.

Anyway, I plan to create a new SD card with Debian 10 (Buster) and then 
install weewx. I've read upgrading OS from Jessie to Stretch to Buster 
could take quite a bit of time and there is a risk to losing data. My 
question comes, what's the quickest way to get weewx running, as it is 
configured now, on the new OS? Ensure I backup my weewx.conf, weewx.sdb, 
and skins? Is there anything else I should be conscience of when moving? Is 
there an "easier" way to do this? Just worried I'll be down for a while 
trying to configure and get everything up and running as it is now.

Thanks,
Troy

-- 
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/4d20cad3-5af5-4ea3-996b-620e2c91a181n%40googlegroups.com.

[weewx-user] Re: Basic weather station (temp/humidity) with a large display

[tarob...@gmail.com]

If all you want is temperature/humidity then just get an outdoor 
temp/humidity sensor that is wireless (I have four acurite temp/humidity 
sensors) and use the SDR driver to capture the data. You'll also need to 
get an antenna to capture that data. Here are some good instructions 
(https://github.com/bdwilson/acurite) on everything needed.

On Sunday, November 1, 2020 at 5:13:40 PM UTC-5 danod...@gmail.com wrote:

> I have what seems to be a dumb question but I keep coming up empty. I want 
> a screen with a USB interface for WeeWX that simply needs indoor/outdoor 
> temp and humidity. I don't need a full-blown weather station with all the 
> bells and whistles, just temperature and humidity. Does anyone have a good 
> suggestion? TIA!
>

-- 
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/33300879-0c38-4248-8cb4-df507fd5628en%40googlegroups.com.

Re: [weewx-user] Version 4.2.0 ready

[tarob...@gmail.com]

Upgraded from 4.1.1 to 4.2.0 with no issues at all using DEB package. 
During install, my *current.inc* was different along with *weewx.conf* 
(which of course I expected since I've modified both of those files). I 
choose the default of "N" to keep my modified version but if I would've 
selected "Y" for both of those files would my modification to those files 
carry over to the new ones? Or does it override with the new files and my 
modifications are lost?

On Friday, October 30, 2020 at 6:36:01 AM UTC-4 graha...@gmail.com wrote:

> cut over weewx 4.1.1 (on RPi 4, with custom skin and extensions) → 4.2.0 
> successfully: clean, no issues. well done again, tom
>
> On 27 Oct 2020, at 11:13 pm, Tom Keffer  wrote:
>
> Some new features, fixes some bugs.
>
>
>

-- 
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/f832133a-ca85-4e49-b8cf-8ffdaa319c3bn%40googlegroups.com.

[weewx-user] Re: alarm module - multiple alarms

[tarob...@gmail.com]

Got a post of the logs? I have alarm.py working on 4.1.1. When I initially 
set it up, I wasn't getting emails due to an error on the email side. Once 
I resolved that, it's worked great.

On Saturday, September 19, 2020 at 3:57:45 AM UTC-4 pligg...@gmail.com 
wrote:

>
> Tried this again today but it doesn't send email. I see the expression 
> true in the logs. Has anyone got some idea why the old alarm.py works fine 
> but not the "new" alarm_multi.py?
> First tried on weewx 3.9.1 and now on 4.0.0 but still the same result.
> //Mikael
> tisdag 12 mars 2019 kl. 09:06:50 UTC+1 skrev pligg...@gmail.com:
>
>> Hi!
>>
>> Does anyone got this to work on weewx 3.9.1?
>>
>> I had the original alarm.py working, but this one doesn't send email. I 
>> get the alarm expression true in the log but it never sends an email.
>> I double checked the credentials and the smtp settings.
>>
>> /Mikael
>>
>>
>> Den onsdag 1 maj 2013 kl. 19:06:00 UTC+2 skrev William Phelps:
>>>
>>> I modified the example "alarm.py" to support multiple alarms.  The 
>>> entries in weewx.conf now look like this:
>>>
>>> [Alarm]
>>>   time_wait = 3600
>>>   smtp_host = smtp.mymailserver.com
>>>   smtp_user = myusername
>>>   smtp_password = mypassword
>>>   mailto = au...@adomain.com, anoth...@someplace.com
>>>   from = m...@mydomain.com
>>>
>>>   count = 2
>>>   expression.0 = "outTemp < 40.0"
>>>   subject.0 = "Alarm message from weewx - Low temperature!"
>>>   expression.1 = "outTemp > 90.0"
>>>   subject.1 = "Alarm message from weewx- High temperature!"
>>>
>>> I've attached a zip of alarm.py
>>>
>>> It's still "static" - to change the alarms, you have to restart weewx 
>>> after editing weewx.conf.  I thought about having alarm.py re-fetch the 
>>> config data but that seems like it might be a performance hit since the 
>>> code is attached to the NEW_ARCHIVE_RECORD event.  Maybe attach another 
>>> event to re-read the config data?
>>>
>>> William
>>>
>>

-- 
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/9ad8bb01-ea19-47ca-9216-6838e4bcf271n%40googlegroups.com.

[weewx-user] Re: Acurite Atlas SDR Sensor Mapping and Pressure Readings

[tarob...@gmail.com]

I'm not well versed on getting other pressure readings into weewx. I'm sure 
there is a way but might be more work for just a temp situation.

I think the distance packets should always show up, it would just show the 
last storm distance in the packets. Although I have a standalone lightning 
tower, not an atlas, so maybe the behavior is different. This site 
<https://www.wxforum.net/index.php?topic=30139.0> has some information on 
that discussion.

Assigning battery to outTempBatteryStatus should work but I haven't done 
this. From my understanding, acurite signal for battery is either 1 or 0.

On Thursday, September 17, 2020 at 1:51:19 PM UTC-4 wxwatching wrote:

> I have ordered a pressure sensor, but delivery looks like it will take a 
> month. Meanwhile, I thought I could just use my own console from my AcuRite 
> 5-n-1 (Model 1036), but haven't figured out how to just use the pressure 
> readings from it and combine with my Atlas readings.
>
> So, I assume the distance..AcuriteLightningPacket packets will not 
> show in the SDR output until an actual storm is taking place?
>
> In reference to the battery, is that to mapped then as:
>
> outTempBatteryStatus = battery..0222.AcuriteAtlasPacket 
>
> On Thursday, September 17, 2020 at 8:58:53 AM UTC-4 tarob...@gmail.com 
> wrote:
>
>> The lightning data is handled a bit differently and from searching the 
>> user group I was able to get it working with the following sensor map:
>>
>> [[sensor_map]]
>> ...
>> lightning_distance = distance..AcuriteLightningPacket
>> strikes_total = strikes_total..AcuriteLightningPacket
>> [[deltas]]
>> rain = rain_total
>> lightning_strike_count = strikes_total
>>
>> and then in the calibration section in the weewx.conf file I added the 
>> following:
>>
>> [StdCalibrate]
>> 
>> [[Corrections]]
>> # For each type, an arbitrary calibration expression can be given.
>> # It should be in the units defined in the StdConvert section.
>> # Example:
>> foo = foo + 0.2
>> lightning_distance = lightning_distance if lightning_strike_count 
>> > 0 else None
>>
>> More info here 
>> <https://groups.google.com/g/weewx-user/c/VBHMkb04kEk/m/_XLIZbIBBgAJ>
>>
>> I haven't been able to determine how to capture signal strength from 
>> Acurite via SDR. The battery status as I understand it is either "1" which 
>> is good or "0" which is bad.
>>
>> Depending on your setup, there are a couple ways to get pressure. I am 
>> using a raspberry pi 3 and added a pressure sensor to it using these 
>> instructions 
>> <https://github.com/bdwilson/acurite/blob/master/Pressure.md>.
>>
>

-- 
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/c6521fe7-adf1-44d4-9e4f-331c017d4cdbn%40googlegroups.com.

[weewx-user] Re: Acurite Atlas SDR Sensor Mapping and Pressure Readings

[tarob...@gmail.com]

The lightning data is handled a bit differently and from searching the user 
group I was able to get it working with the following sensor map:

[[sensor_map]]
...
lightning_distance = distance..AcuriteLightningPacket
strikes_total = strikes_total..AcuriteLightningPacket
[[deltas]]
rain = rain_total
lightning_strike_count = strikes_total

and then in the calibration section in the weewx.conf file I added the 
following:

[StdCalibrate]

[[Corrections]]
# For each type, an arbitrary calibration expression can be given.
# It should be in the units defined in the StdConvert section.
# Example:
foo = foo + 0.2
lightning_distance = lightning_distance if lightning_strike_count > 
0 else None

More info here 


I haven't been able to determine how to capture signal strength from 
Acurite via SDR. The battery status as I understand it is either "1" which 
is good or "0" which is bad.

Depending on your setup, there are a couple ways to get pressure. I am 
using a raspberry pi 3 and added a pressure sensor to it using these 
instructions .

-- 
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/fbc52421-617a-4def-8306-e92f618edee6n%40googlegroups.com.

[weewx-user] Re: Acurite Atlas Using sdr.py - No Output

[tarob...@gmail.com]

Also, I'm not sure what you followed to use sdr but the following has good 
write up on getting everything working 
correctly: https://github.com/bdwilson/acurite


On Friday, September 11, 2020 at 1:38:11 PM UTC-4 tarob...@gmail.com wrote:

> Take a look at the GitHub page for rtl_433 (
> https://github.com/merbanan/rtl_433) and ensure you've installed 
> everything correctly. When you run sudo rtl_433, the output in the syslog 
> would be different that what you've posted.
>
> On Friday, September 11, 2020 at 12:44:48 PM UTC-4 wxwatching wrote:
>
>> When I run sudo PYTHONPATH=/usr/share/weewx python 
>> /usr/share/weewx/user/sdr.py --cmd="rtl_433 -M utc -F json" , I get this 
>> in the syslog output:
>>
>> Sep 11 12:38:12 raspberrypi kernel: [403487.365965] r820t 12-001a: 
>> destroying instance
>> Sep 11 12:38:12 raspberrypi kernel: [403487.366736] dvb_usb_v2: 'Realtek 
>> RTL2832U reference design:1-1.3' successfully deinitialized and disconnected
>> Sep 11 12:38:51 raspberrypi kernel: [403527.148526] usb 1-1.3: 
>> dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
>> Sep 11 12:38:51 raspberrypi kernel: [403527.203791] usb 1-1.3: 
>> dvb_usb_v2: will pass the complete MPEG2 transport stream to the software 
>> demuxer
>> Sep 11 12:38:51 raspberrypi kernel: [403527.203850] dvbdev: DVB: 
>> registering new adapter (Realtek RTL2832U reference design)
>> Sep 11 12:38:51 raspberrypi kernel: [403527.203880] usb 1-1.3: media 
>> controller created
>> Sep 11 12:38:51 raspberrypi kernel: [403527.206660] dvbdev: 
>> dvb_create_media_entity: media entity 'dvb-demux' registered.
>> Sep 11 12:38:51 raspberrypi kernel: [403527.272975] i2c i2c-11: Added 
>> multiplexed i2c bus 12
>> Sep 11 12:38:51 raspberrypi kernel: [403527.272992] rtl2832 11-0010: 
>> Realtek RTL2832 successfully attached
>> Sep 11 12:38:51 raspberrypi kernel: [403527.273066] usb 1-1.3: DVB: 
>> registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
>> Sep 11 12:38:51 raspberrypi kernel: [403527.273098] dvbdev: 
>> dvb_create_media_entity: media entity 'Realtek RTL2832 (DVB-T)' registered.
>> Sep 11 12:38:51 raspberrypi kernel: [403527.273282] r820t 12-001a: 
>> creating new instance
>> Sep 11 12:38:51 raspberrypi kernel: [403527.281551] r820t 12-001a: Rafael 
>> Micro r820t successfully identified
>> Sep 11 12:38:52 raspberrypi kernel: [403527.320620] Registered IR keymap 
>> rc-empty
>> Sep 11 12:38:52 raspberrypi kernel: [403527.320755] rc rc0: Realtek 
>> RTL2832U reference design as 
>> /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0
>> Sep 11 12:38:52 raspberrypi kernel: [403527.320908] rc rc0: lirc_dev: 
>> driver dvb_usb_rtl28xxu registered at minor = 0, raw IR receiver, no 
>> transmitter
>> Sep 11 12:38:52 raspberrypi kernel: [403527.321020] input: Realtek 
>> RTL2832U reference design as 
>> /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0/input18
>> Sep 11 12:38:52 raspberrypi kernel: [403527.325735] usb 1-1.3: 
>> dvb_usb_v2: schedule remote query interval to 200 msecs
>> Sep 11 12:38:52 raspberrypi kernel: [403527.335267] usb 1-1.3: 
>> dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized 
>> and connected
>>
>>
>> When I run sudo rtl_433, I get this in the syslog output:
>>
>> Sep 11 12:40:23 raspberrypi kernel: [403618.966282] r820t 12-001a: 
>> destroying instance
>> Sep 11 12:40:23 raspberrypi kernel: [403618.967039] dvb_usb_v2: 'Realtek 
>> RTL2832U reference design:1-1.3' successfully deinitialized and disconnected
>> Sep 11 12:40:40 raspberrypi kernel: [403636.244235] usb 1-1.3: 
>> dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
>> Sep 11 12:40:41 raspberrypi kernel: [403636.301825] usb 1-1.3: 
>> dvb_usb_v2: will pass the complete MPEG2 transport stream to the software 
>> demuxer
>> Sep 11 12:40:41 raspberrypi kernel: [403636.301876] dvbdev: DVB: 
>> registering new adapter (Realtek RTL2832U reference design)
>> Sep 11 12:40:41 raspberrypi kernel: [403636.301895] usb 1-1.3: media 
>> controller created
>> Sep 11 12:40:41 raspberrypi kernel: [403636.304526] dvbdev: 
>> dvb_create_media_entity: media entity 'dvb-demux' registered.
>> Sep 11 12:40:41 raspberrypi kernel: [403636.340845] i2c i2c-11: Added 
>> multiplexed i2c bus 12
>> Sep 11 12:40:41 raspberrypi kernel: [403636.340868] rtl2832 11-0010: 
>> Realtek RTL2832 successfully attached
>> Sep 11 12:40:41 raspberrypi kernel: [403636.340968] usb 1-1.3: DVB: 
>> registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...

[weewx-user] Re: Acurite Atlas Using sdr.py - No Output

[tarob...@gmail.com]

evices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0
> Sep 11 12:40:41 raspberrypi kernel: [403636.401295] rc rc0: lirc_dev: 
> driver dvb_usb_rtl28xxu registered at minor = 0, raw IR receiver, no 
> transmitter
> Sep 11 12:40:41 raspberrypi kernel: [403636.401502] input: Realtek 
> RTL2832U reference design as 
> /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0/input19
> Sep 11 12:40:41 raspberrypi kernel: [403636.407757] usb 1-1.3: dvb_usb_v2: 
> schedule remote query interval to 200 msecs
> Sep 11 12:40:41 raspberrypi kernel: [403636.419188] usb 1-1.3: dvb_usb_v2: 
> 'Realtek RTL2832U reference design' successfully initialized and connected
>
>
> On Friday, September 11, 2020 at 8:45:46 AM UTC-4 tarob...@gmail.com 
> wrote:
>
>> What do you see when you run the following:
>>
>> sudo tail -f /var/log/syslog  
>>
>> On Thursday, September 10, 2020 at 6:01:03 PM UTC-4 wxwatching wrote:
>>
>>> I have the RTL-SDR Blog R820T2 RTL2832U 1PPM TCXO SMA Software Defined 
>>> Radio that was purchased from Amazon:
>>>
>>>
>>> https://www.amazon.com/gp/product/B0129EBDS2/ref=ppx_yo_dt_b_asin_title_o01_s00
>>>
>>

-- 
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/fbaedd15-5476-4143-a19d-12d8359fa1e8n%40googlegroups.com.

[weewx-user] Re: Acurite Atlas Using sdr.py - No Output

[tarob...@gmail.com]

What do you see when you run the following:

sudo tail -f /var/log/syslog  

On Thursday, September 10, 2020 at 6:01:03 PM UTC-4 wxwatching wrote:

> I have the RTL-SDR Blog R820T2 RTL2832U 1PPM TCXO SMA Software Defined 
> Radio that was purchased from Amazon:
>
>
> https://www.amazon.com/gp/product/B0129EBDS2/ref=ppx_yo_dt_b_asin_title_o01_s00
>

-- 
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/236b7354-e0b0-4fb4-beb7-99be0eb32edbn%40googlegroups.com.

[weewx-user] Re: Added second sensor to AcuRite weather station - can I add data to reports

[tarob...@gmail.com]

What is your current setup with getting Acurite data into weewx? If it is 
via the SDR driver, then it is really simple:  
https://github.com/bdwilson/acurite 
If USB than I'm not quite sure.

-Troy 

On Friday, August 28, 2020 at 7:25:19 AM UTC-4 ke...@lakeman.org wrote:

> I have added a second temperature/humidity sensor to my AcuRite weather 
> station.  I would like to see the data from that sensor added to the web 
> reports.   How do I find this data and get it added?
>
> thanks,
>
> -Keith
>

-- 
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/129694b9-38b9-4893-9838-ae7da03ce932n%40googlegroups.com.

[weewx-user] Re: Use weewx without weather station?

[tarob...@gmail.com]

You don't need a weather station. I currently have 4 different 
temp/humidity sensors and a weather station all feeding into raspberry pi 
with SDR antenna. One raspberry pi can handle a lot of sensors at once.

On Friday, August 21, 2020 at 7:16:14 AM UTC-4 pligg...@gmail.com wrote:

> Can weewx run without a weather station? I plan to use several raspberry 
> pi's with temp sensors. 
> /Mikael

-- 
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/6586a0c4-b07d-463b-9ed7-86d116a4b5a8n%40googlegroups.com.

Re: [weewx-user] Re: weather forecast inside the weewx standard skin seasons

[tarob...@gmail.com]

The latest release, v3.4.0b6 has resolved my issue above. Forecasts are now 
being generated along with tides. Thank you for updating!

-Troy

-- 
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/d37fd531-edbc-4a17-bfbf-a44f538453d2n%40googlegroups.com.

Re: [weewx-user] weather forecast inside the weewx standard skin seasons

[tarob...@gmail.com]

Just installed the latest forecast extension and I'm still getting the same 
error as above. I don't know if this is related to the forecast extension 
or an issue with the RPi. It looks like I don't have any issue getting the 
forecast from OWM but the issue arrives when trying to save the forecast:
Aug 18 07:35:24 raspberrypi weewxd: forecast: OWMThread: OWM: saving 40 
forecast records
Aug 18 07:35:24 raspberrypi weewxd: forecast: OWMThread: OWM: forecast 
failure: addRecord() got an unexpected keyword argument 'log_level'
Aug 18 07:35:24 raspberrypi weewxd: forecast: OWMThread: OWM: terminating 
thread

I've search the user group for "log_level" but haven't been able to come 
across the topic that has my issue. I will continue my search!

Thanks,
Troy

-- 
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/d1591cdb-f100-46e5-a10e-5c84bdc43062n%40googlegroups.com.

Re: [weewx-user] Re: weather forecast inside the weewx standard skin seasons

[tarob...@gmail.com]

I am also trying to get forecast with tides into the Seasons Skin but it 
looks like I'm getting some errors trying to pull this data from the 
different sources. Here are the errors I'm seeing in my syslog:

Aug 14 07:15:22 raspberrypi weewxd: forecast: OWMThread: OWM: got 40 
forecast records
Aug 14 07:15:22 raspberrypi weewxd: forecast: OWMThread: OWM: saving 40 
forecast records
Aug 14 07:15:22 raspberrypi weewxd: forecast: OWMThread: OWM: forecast 
failure: addRecord() got an unexpected keyword argument 'log_level'
Aug 14 07:15:22 raspberrypi weewxd: forecast: OWMThread: OWM: terminating 
thread

Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
units=1 winddir=119.225591908 pressure=29.9887493475 first_p=29.985739413 
last_p=29.9854614785
Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
pressure=1015.53545688 month=7 winddir=5 trend=-0.00313731418123 north=True
Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
code is E
Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
generated 1 forecast record
Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
saving 1 forecast records
Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
forecast failure: addRecord() got an unexpected keyword argument 'log_level'
Aug 14 07:15:22 raspberrypi weewxd: forecast: ZambrettiThread: Zambretti: 
terminating thread

Aug 14 07:15:22 raspberrypi weewxd: forecast: XTideThread: XTide: got 222 
lines of output
Aug 14 07:15:22 raspberrypi weewxd: forecast: XTideThread: XTide: forecast 
failure: invalid literal for int() with base 10: 'XXX' 
Aug 14 07:15:22 raspberrypi weewxd: forecast: XTideThread: XTide: 
terminating thread

Any ideas on the unexpected keyword argument 'log_level' ?

Thanks,
Troy

-- 
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/cfc1593c-cc6d-4e2e-b8cb-a5a9532acda3n%40googlegroups.com.