Re: [weewx-user] WeeWx and time

[Steve Sykes]

The procedures worked to clear the bad data. Thank you Tom.

Steve

On Monday, February 15, 2021 at 4:06:27 PM UTC tke...@gmail.com wrote:

> You didn't post a log, but I'm guessing that jumping around in time 
> corrupted the logger's memory. See the section *WeeWX generates HTML 
> pages, but it does not update them 
> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them>*
>  
> in the Wiki.
>
> On Mon, Feb 15, 2021 at 6:43 AM Steve Sykes  wrote:
>
>> I have had to change the server I am using for WeeWx 4.2.0 to GMT. I have 
>> checked the Vantage Pro2 weather station and it is also set to GMT. As soon 
>> as I changed the time the WeeWx web page stopped updating. I have tried 
>> restarting WeeWx and running it via command line. It is running normally 
>> but still no webpage updates. Wunderground is also not getting updated so 
>> it is not just the local page. If I set the server back to EST, everything 
>> works fine.
>> Anyone have an idea to fix this?
>>
>> 73
>> Steve KD2OM
>>
>> -- 
>> 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/80a46d95-cefc-4247-8c8a-67799386b7d0n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/80a46d95-cefc-4247-8c8a-67799386b7d0n%40googlegroups.com?utm_medium=email&utm_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/2350238c-de48-42e7-bff4-ead70e11bf57n%40googlegroups.com.

[weewx-user] WeeWx and time

[Steve Sykes]

I have had to change the server I am using for WeeWx 4.2.0 to GMT. I have 
checked the Vantage Pro2 weather station and it is also set to GMT. As soon 
as I changed the time the WeeWx web page stopped updating. I have tried 
restarting WeeWx and running it via command line. It is running normally 
but still no webpage updates. Wunderground is also not getting updated so 
it is not just the local page. If I set the server back to EST, everything 
works fine.
Anyone have an idea to fix this?

73
Steve KD2OM

-- 
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/80a46d95-cefc-4247-8c8a-67799386b7d0n%40googlegroups.com.

[weewx-user] Re: 0 files copied to /home/weewx/public_html

[Steve Sykes]

Thank you Gary, I just wondered if it was a problem, I don't usually look 
at the log file but I had a problem where WeeWx wasn't starting reliably. I 
will just ignore the line.

Steve

On Tuesday, October 27, 2020 at 11:56:46 AM UTC gjr80 wrote:

> Hi,
>
> I presume the message you refer to is:
>
> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
> files to /home/weewx/public_html
>
> This is normal and is not necessarily a sign that anything is amiss. The 
> line concerned is the from the CopyGenerator and is quite correct, it did 
> not copy any files. The CheetahGenerator is creating files from your 
> cheetah templates and the ImageGenerator is creating image files for your 
> plots. These generators place the generated files in the correct 
> destination directory not the CopyGenerator.
>
> The CopyGenerator <http://weewx.com/docs/customizing.htm#[CopyGenerator]> 
> is used to copy static files from a skin directory to somewhere else on the 
> system. It is typically used to copy static css or javascript files for use 
> by a web server. The CopyGenerator has two modes of operation; copy once 
> where it copies files on the first report cycle after WeeWX has started or 
> copy always where it copies the specified files on every report cycle. The 
> WeeWX Seasons and Standard skins (by default) run the CopyGenerator (along 
> with the CheetahGenerator and ImageGenerator) on each report cycle but 
> the CopyGenerator is not used to copy any files.
>
> If the line is annoying you can do one of two things. You can prevent the 
> Seasons skin from invoking the CopyGenerator by removing it from the 
> generator_list config setting at the bottom of the Seasons skin config file 
> (skins/Seasons/skin.conf). You could also set log_success = false under 
> [StdReport] in weewx.conf, but this will also have the effect of silencing 
> all log entries for all generators not just the CopyGenerator.
>
> Gary
>
>
> On Tuesday, 27 October 2020 20:34:59 UTC+10, Steve Sykes wrote:
>>
>> I am getting this message in my log file, but the weewx wepbage is 
>> updating as it should. I have also looked in the  public_html directory and 
>> see files of the latest update interval so files are being copied in spite 
>> of the log file data.
>> Can anyone explain this?
>>
>> Steve KD2OM
>>
>>
>>
>> TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 
>> LEN=329 
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
>> 2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
>> 2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 0.32 seconds
>> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 0.18 seconds
>> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
>> files to /home/weewx/public_html
>>
>>

-- 
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/5a4428f5-b90f-44ab-bdb0-cbb5b6e57f9en%40googlegroups.com.

[weewx-user] 0 files copied to /home/weewx/public_html

[Steve Sykes]

I am getting this message in my log file, but the weewx wepbage is updating 
as it should. I have also looked in the  public_html directory and see 
files of the latest update interval so files are being copied in spite of 
the log file data.
Can anyone explain this?

Steve KD2OM



TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 LEN=329 
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 0.32 seconds
Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 0.18 seconds
Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
files to /home/weewx/public_html

-- 
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/cdde9f00-3350-427a-927e-8785d0b9a297n%40googlegroups.com.

Re: [weewx-user] New installation on Ubuntu 18.04

[Steve Sykes]

I tried to upload the log file but for some reason it wouldn't upload. 

I believe the problem with the webpage was that python-cheetah didn't 
install.  During the original install  apt install phonython3-cheetah 
didn't work so I used the other method shown on the installation page. 
Apparently that didn't work either but I didn't realize it. After more 
research I got pip3 install cheetah3 to work.
Now the webpage shows up. I believe it is working correctly now.

I have tried to upload the log but I keep getting an error.

Steve


-- 
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/1d544226-9f70-4cf2-a5ff-b7c83abc7dd9n%40googlegroups.com.

Re: [weewx-user] New installation on Ubuntu 18.04

[Steve Sykes]

Tom,
Here is the log file. 


-- 
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/77ba3ec0-7fa9-4214-a8dc-0bdc90b10c9dn%40googlegroups.com.

[weewx-user] New installation on Ubuntu 18.04

[Steve Sykes]

I have installed weewx using setup.py. It seems to run, my weather station 
is a Davis Vantage Pro2 and the ip data logger.  This is the dump when 
using weewx status -l.

I believe the issue is that there is no index.html in either 
/home/weewx/public_html or /var/www/html

additionally I don't know why  the line in the status dump says 0 files 
copied and also that 'StandardReport' not is enabled.

● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (running) since Thu 2020-10-08 11:56:39 EDT; 1h 34min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 21471 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 22114 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
Tasks: 2 (limit: 4915)
   CGroup: /system.slice/weewx.service
   └─22132 /usr/bin/python3 /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG weewx.restx: 
CWOP: Connected to server cwop.aprs.net:14580
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] INFO 
weewx.imagegenerator: Generated 15 images for report Season… seconds
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] INFO 
weewx.reportengine: Copied 0 files to /home/weewx/public_html
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'SmartphoneReport' not enabled.…kipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'FTP' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'RSYNC' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] INFO weewx.restx: 
CWOP: Published record 2020-10-08 13:30:00 EDT…2178200)
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.drivers.vantage: Gentle wake up of console successful
Hint: Some lines were ellipsized, use -l to show in full.


Steve

-- 
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/0a571137-49a6-4e33-9870-eae065ad2b2bn%40googlegroups.com.

Re: [weewx-user] OWFS Weather station Humidity Sensor

[Steve Sykes]

Thanks Glen, I have placed the order. Waterproofing was the problem. Hobby 
Boards must have been a bit light on the coating. Traces and thru holes are 
corroded. When I get time I will try to repair it. I hope Sheepwalk has a 
better coating for waterproofing. I don't really know how to protect it 
without causing the readings to be affected. 

On Monday, July 17, 2017 at 7:06:57 PM UTC-4, Glenn McKechnie wrote:
>
> Sheepwalk Electronics sell an equivalent to the hobby-boards version
>
>
> http://www.sheepwalkelectronics.co.uk/product_info.php?products_id=55&osCsid=2308a9eb63d5662838e334279a35f3e9
>
> Do you supply 5v to the existing sensor? I found they behaved better with 
> it jumpered on. 
>
> I've swapped out the actual sensor (Honeywell HIH module) before with 
> success. If you do that just make sure you re-waterproof the board again, 
> in particular the re-soldered joints.
>
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi + weewx: now with scripts 
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> On 18 July 2017 at 06:12, Steve Sykes > 
> wrote:
>
>> I have been running my homebrew weather station using a Hobby Boards 
>> humidity sensor. This sensor has been intermittant for the past few months 
>> and I would like to replace it. Hobby boards is no longer in business so I 
>> am wondering what other options are available. What sensor are other OWFS 
>> weather stations using?
>>
>> Anyone have a recommendation?
>>
>> Regards,
>> Steve Sykes 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] OWFS Weather station Humidity Sensor

[Steve Sykes]

I have been running my homebrew weather station using a Hobby Boards 
humidity sensor. This sensor has been intermittant for the past few months 
and I would like to replace it. Hobby boards is no longer in business so I 
am wondering what other options are available. What sensor are other OWFS 
weather stations using?

Anyone have a recommendation?

Regards,
Steve Sykes 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AS3935 and weewx.sdb

[Steve Sykes]

I agree, although yesterday we really did have lightning and I was home to 
see it. Both modules did actually detect lightning and weewx generated the 
alarm email. I even got warnings from the BlitzortungLive app about the 
same time.

Steve KD2OM 

On Saturday, October 1, 2016 at 10:41:47 PM UTC-4, Steve2Q wrote:
>
> Steve..your inability to correlate readings between two sensors leads me 
> to believe that (unfortunately) they may be unreliable. Maybe the best test 
> would be two pi's running identical software and check the results.
>
> Steve (N2QLQ)
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AS3935 and weewx.sdb

[Steve Sykes]

Steve
I have twp sensors working, one with weewx and one with RPi-AS3935-Web. 
They are both configured the same and in close proximity to each other.  
The one running the web code tags "disturbers", as well tagged lightning. 
However so far I haven't been able to correlate between the two modules. 
Nor have I been able to confirm that it detected actual lightning. I wonder 
if weewx is showing lightning which is really "disturbers". My graph always 
shows many spikes which are not reported. You can see the graphs at 
http://www.ecsykes.com

There is a tuning procedure using an oscilloscope or frequency country but 
I haven't done it yet. 

Steve 

On Thursday, September 29, 2016 at 4:12:45 PM UTC-4, Steve2Q wrote:
>
> Matthew. .thank you. I am doing the changes under weewx.conf. As far as 
> the indoor v outdoor parameters, I assume that indoor = true would increase 
> the sensitivity  (my senor is indoors), but I wonder if this would lead to 
> false positives.
>
> Steve 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AS3935 and weewx.sdb

[Steve Sykes]

matt,

I understand the service a bit better. I tried setting weewx.conf to make 
the separate database, which worked. I have reset it to save to the weewx 
database now. I checked the lightning database and saw a couple "strikes", 
but they didn't show up in the weewx database. I am pretty sure they 
weren't real strikes anyway. I have increased the noise floor to hopefully 
eliminate these false hits. I am also comparing it to the Hobby boards 
detector. So far there isn't much correlation. The purpose for both 
detectors is so I know when to disconnect my HF antennas. I can't 
understand why I get the (errno5) when testing with a lighter. Perhaps I 
need to find a better way to test it. It may just overwhelm the chip, 
lightning wouldn't emit energy so close.  We haven't had much lightning 
here this year, I may have to wait until next year to verify correct 
operation.

I still would like to know why the values in the database and webpage don't 
agree, for instance the web page reports 1 mile and the database .62 for 
the same sample. I think weewx is saying 1 mile but means 1 km, even though 
it is set to US units.


Steve 
On Sunday, September 25, 2016 at 1:29:40 PM UTC-4, mwall wrote:
>
>
>
> On Saturday, September 24, 2016 at 10:07:39 PM UTC-4, Steve Sykes wrote:
>>
>> I am still getting this in the log.  I am running as3935.py v0.5rc1. 
>>
>
> steve,
>
> i have release v0.5
>
> no changes to the code, but i updated the comments and the wiki to show 
> how data_binding is used
>
> sorry for the confusion - the old comments still had weewx 2.x syntax
>
> the first step is to verify that lightning data are being saved to the 
> weewx database (run weewxd directly to validate this, and check the 
> contents of your weewx database).  in your case, based on the sql query, it 
> seems to be working just fine.
>
> do not specify data_binding unless you intend to save data to a separate 
> database in addition to saving data to the weewx database.  the lightning 
> database will be a simple table of dateTime and distance, so you can see 
> the time of each strike and how far away it happened.  from that you can 
> plot circles, or if you have weewx running in two locations, you can 
> overlap circles to infer the strike location on a map.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] AS3935 and weewx.sdb

[Steve Sykes]

I have moved it as suggested.  When using the piezo lighter to test it I 
get this. The [Errno 5] errors occur when using the piezo tester much of 
the time. The placement of the driver line doesn't seem to make a 
difference.

Sep 25 12:43:19 raspberrypi weewx[16068]: as3935: callback failed: [Errno 
5] Input/output error
Sep 25 12:43:19 raspberrypi weewx[16068]: as3935: callback failed: [Errno 
5] Input/output error
Sep 25 12:43:20 raspberrypi weewx[16068]: as3935: callback failed: [Errno 
5] Input/output error
Sep 25 12:43:20 raspberrypi weewx[16068]: as3935: callback failed: [Errno 
5] Input/output error
Sep 25 12:43:21 raspberrypi weewx[16068]: as3935: callback failed: [Errno 
5] Input/output error
Sep 25 12:43:21 raspberrypi weewx[16068]: as3935: strike at 8.0 km
Sep 25 12:43:21 raspberrypi weewx[16068]: as3935: callback failed: Unit 
system of incoming record (0x10) differs from 'archive' table in 
'weewx.sdb' database (0x01)
Sep 25 12:43:21 raspberrypi weewx[16068]: as3935: callback failed: [Errno 
5] Input/output error
Sep 25 12:43:44 raspberrypi weewx[16068]: as3935: strike at 8.0 km
Sep 25 12:43:44 raspberrypi weewx[16068]: as3935: callback failed: Unit 
system of incoming record (0x10) differs from 'archive' table in 
'weewx.sdb' database (0x01)
Sep 25 12:43:45 raspberrypi weewx[16068]: as3935: strike at 8.0 km
Sep 25 12:43:45 raspberrypi weewx[16068]: as3935: callback failed: Unit 
system of incoming record (0x10) differs from 'archive' table in 
'weewx.sdb' database (0x01)


On Sunday, September 25, 2016 at 11:01:59 AM UTC-4, Tom Keffer wrote:
>
> Just realized that you're using the as3935 service. In your weewx.conf, 
> make sure that it is included *before* StdConvert. So, your [Engine] 
> section should look something like this (NOT TESTED):
>
> [Engine]
> 
> [[Services]]
> # This section specifies the services that should be run. They are
> # grouped by type, and the order of services within each group
> # determines the order in which the services will be run.
> prep_services = weewx.engine.StdTimeSynch
> data_services = user.as3935.AS3935
> process_services = weewx.engine.StdConvert, 
> weewx.engine.StdCalibrate, weewx.engine.StdQC, 
> weewx.wxservices.StdWXCalculate
> archive_services = weewx.engine.StdArchive
> restful_services = weewx.restx.StdStationRegistry, 
> weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
> weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>
> -tk
>
>
> On Sun, Sep 25, 2016 at 6:50 AM, Steve Sykes  > wrote:
>
>> Hi Tom,
>>
>> I have not modified [StdConvert]. Another interesting thing is that I 
>> don't believe that my extensions.py is getting read. I had to modify 
>> wview.py to get the database to include the lightning_strikes and 
>> avg_distance.
>>
>>
>> [StdConvert]
>> 
>> # The target_unit affects only the unit system in the database. Once
>> # chosen it cannot be changed without converting the entire database.
>> # Modification of target_unit after starting weewx will result in
>> # corrupt data - the database will contain a mix of US and METRIC 
>> data.
>> #
>> # The value of target_unit does not affect the unit system for
>> # reporting - reports can display US, Metric, or any combination of 
>> units.
>> #
>> # In most cases, target_unit should be left as the default: US
>> #
>> # In particular, those migrating from a standard wview installation
>> # should use US since that is what the wview database contains.
>> 
>> # DO NOT MODIFY THIS VALUE UNLESS YOU KNOW WHAT YOU ARE DOING!
>> target_unit = US# Options are 'US', 'METRICWX', or 'METRIC'
>>
>>
>> ##
>>
>>
>> On Saturday, September 24, 2016 at 10:18:47 PM UTC-4, Tom Keffer wrote:
>>>
>>> Your database is set up with US units, but you are trying to put  METRIC 
>>> into it. 
>>>
>>> What does your section [StdConvert] look like in weewx.conf? Did you 
>>> change it?
>>>
>>> What the driver sends out does not matter (so long as it is correct!). 
>>> It is the job of the StdConvert service to convert it into the unit system 
>>> used by the database.
>>>
>>> -tk
>>>
>>> On Sat, Sep 24, 2016 at 7:07 PM, Steve Sykes  wrote:
>>>
>>>> I am still getting 

Re: [weewx-user] AS3935 and weewx.sdb

[Steve Sykes]

Hi Tom,

I have not modified [StdConvert]. Another interesting thing is that I don't 
believe that my extensions.py is getting read. I had to modify wview.py to 
get the database to include the lightning_strikes and avg_distance.


[StdConvert]

# The target_unit affects only the unit system in the database. Once
# chosen it cannot be changed without converting the entire database.
# Modification of target_unit after starting weewx will result in
# corrupt data - the database will contain a mix of US and METRIC data.
#
# The value of target_unit does not affect the unit system for
# reporting - reports can display US, Metric, or any combination of 
units.
#
# In most cases, target_unit should be left as the default: US
#
# In particular, those migrating from a standard wview installation
# should use US since that is what the wview database contains.

# DO NOT MODIFY THIS VALUE UNLESS YOU KNOW WHAT YOU ARE DOING!
target_unit = US# Options are 'US', 'METRICWX', or 'METRIC'

##


On Saturday, September 24, 2016 at 10:18:47 PM UTC-4, Tom Keffer wrote:
>
> Your database is set up with US units, but you are trying to put  METRIC 
> into it. 
>
> What does your section [StdConvert] look like in weewx.conf? Did you 
> change it?
>
> What the driver sends out does not matter (so long as it is correct!). It 
> is the job of the StdConvert service to convert it into the unit system 
> used by the database.
>
> -tk
>
> On Sat, Sep 24, 2016 at 7:07 PM, Steve Sykes  > wrote:
>
>> I am still getting this in the log.  I am running as3935.py v0.5rc1. 
>>
>> Sep 24 21:32:55 raspberrypi weewx[9576]: as3935: strike at 1.0 km
>> Sep 24 21:32:55 raspberrypi weewx[9576]: as3935: callback failed: Unit 
>> system of incoming record (0x10) differs from 'archive' table in 
>> 'weewx.sdb' database (0x01)
>>
>>
>> Checking the database shows that the column and data are in the 
>> database.  I see that the distance units are shown in miles and the as3935 
>> sends distance in km.
>>
>> sqlite3> select avg_distance, lightning_strikes from archive;
>>
>> 3.10685596|2.0
>> 3.10685596|3.0
>> 1.864113576|2.0
>> 0.621371192|1.0
>> 0.621371192|1.0
>> 0.621371192|2.0
>> 0.621371192|1.0
>> 0.621371192|1.0
>>
>>
>> I am sure the strike at 1 km is just noise but it is helpful as a 
>> diagnostic.  Should just ignore the log?
>>
>> Steve
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] AS3935 and weewx.sdb

[Steve Sykes]

I am still getting this in the log.  I am running as3935.py v0.5rc1. 

Sep 24 21:32:55 raspberrypi weewx[9576]: as3935: strike at 1.0 km
Sep 24 21:32:55 raspberrypi weewx[9576]: as3935: callback failed: Unit 
system of incoming record (0x10) differs from 'archive' table in 
'weewx.sdb' database (0x01)


Checking the database shows that the column and data are in the database.  
I see that the distance units are shown in miles and the as3935 sends 
distance in km.

sqlite3> select avg_distance, lightning_strikes from archive;

3.10685596|2.0
3.10685596|3.0
1.864113576|2.0
0.621371192|1.0
0.621371192|1.0
0.621371192|2.0
0.621371192|1.0
0.621371192|1.0


I am sure the strike at 1 km is just noise but it is helpful as a 
diagnostic.  Should just ignore the log?

Steve

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AS3935 Lightning detector and database creation not working

[Steve Sykes]

Still I have not been able to get lightning and lightning_strikes into the 
database.  I have added the units to extensions.py per the customization 
manual, reconfigured the database several times but still no luck. 
When I run weewx manually with the as3925 configuration I see those units 
in the loop so I know the module and driver are working. 
Modifying wview.py will probably work but I would rather fix it the correct 
way and I just don't understand why the items from extensions.py are not 
being read into the database.

Steve



On Thursday, September 8, 2016 at 7:29:33 PM UTC-4, Steve Sykes wrote:
>
> I have installed the AS3935 service, configured the extensions.py and the 
> wview.py schema. I found that I needed to modify wview.py in order to get 
> the extensions to work for some reason. 
>
> At this time I have the lightning archive configured as a separate 
> archive. 
>
> So far there has been no archive created so I must have something wrong. 
>
> For a time I had it archiving to weewx.sdb but was getting an error about 
> units. At some point I would like to just have one database.
>
> The log file, even with debug on shows nothing untoward. I have attached 
> my weewx.conf, extensions.py and wview.py. Hopefully someone can see what 
> is wrong. 
>
> Lightning detection doesn't seem to work properly yet but if a database 
> isn't created I will never see it.
>
> Steve
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AS3935 Lightning detector and database creation not working

[Steve Sykes]

Matthew,
Thanks, I thought that the database section was different than the others, 
I copied it from the as3935 driver. I have changed it and now the database 
is being created. I assume I need to move the call to as3935 in the engine 
section to "process" instead of "data" as well. 

Ultimately since lightning doesn't occur very much where I live, I would 
like to have it displayed in a separate page like cmon. I also have the 
hobbyboards lightning detector which is why I have lightning as well as 
lightning_strikes. 

As Steve2Q suggested I need to get the extended schema working instead of 
modifying the wview schema. cmon refers to its schema in the driver where 
as3935 doesn't. I have added the schema information to extensions.py but 
since it is not using the additional info, I must have something wrong. 
Since I want to use two databases, should the "schema = 
user.extensions.extended_schema" statement be in the [[lightning_binding]] 
instead of the [[wx_binding]]?

[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.wxmanager.WXDaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = user.extensions.extended_schema
[[lightning_binding]]
database = lightning_sqlite
[[cmon_binding]]
manager = weewx.manager.DaySummaryManager
schema = user.cmon.schema
table_name = archive
database = cmon_sqlite
import locale
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, '')
# extend the default schema to include lightning
import weewx.units
weewx.units.USUnits['group_distance'] = 'mile'
weewx.units.MetricUnits['group_distance'] = 'kilometer'
weewx.units.MetricWXUnits['group_distance'] = 'kilometer'

weewx.units.obs_group_dict['lightning_strikes'] = 'group_count'
weewx.units.obs_group_dict['avg_distance'] = 'group_distance'

import schemas.wview
extended_schema = schemas.wview.schema + [('lightning', 'REAL')]
extended_schema = schemas.wview.schema + [('lightning_strikes', 'REAL')]
extended_schema = schemas.wview.schema + [('avg_distance', 'REAL')]
# ensure that lightning uses the right units
from weewx.units import obs_group_dict 
obs_group_dict['lightning'] = 'group_count'
from weewx.units import obs_group_dict
obs_group_dict['lightning_strikes'] = 'group_count'




On Friday, September 9, 2016 at 8:46:24 PM UTC-4, mwall wrote:
>
>
>
> On Thursday, September 8, 2016 at 7:29:33 PM UTC-4, Steve Sykes wrote:
>>
>> Lightning detection doesn't seem to work properly yet but if a database 
>> isn't created I will never see it.
>>
>>
> steve,
>
> you don't need a second database - that is an optional feature of the 
> as3935 extension.
>
> the reason your second database is not working is because of how you 
> defined it. in your weewx.conf, this:
>
> [[lightning_sqlite]]
> root = %(WEEWX_ROOT)s
> database_name = archive/lightning.sdb
> driver = weedb.sqlite
>
> is incorrect - that is how databases were specified in weewx 2.  you want 
> this:
>
> [[lightning_sqlite]]
> database_type = SQLite
> database_name = lightning.sdb
>
> but you should walk before you run.  
>
> remove the data_binding = lightning_binding from the [AS3935] section so 
> that lightning data are saved only to the wx database.
>
> run weewx directly to be sure that lightning data are actually being 
> captured.
>
> sudo weewxd /etc/weewx/weewx.conf
>
> you should see LOOP data with the lightning fields.
>
> then make sure the data are getting into your wx database:
>
> sqlite3 /var/lib/weewx.sdb
> sqlite> select dateTime, avg_distance, lightning_strikes from archive;
>
> note that the two fields are avg_distance and lightning_strikes.  you 
> need to modify your schema, since you are using lightning and 
> lightning_strikes.  you can also eliminate the lightning references in 
> your extensions.py.
>
> after all of that is working properly, add the lightning data 
> (avg_distance and lightning_strikes) to your reports.
>
> the separate lightning database records the distance to and time of each 
> strike.  it has its own schema and is completely independent of the weewx 
> wx database.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] AS3935 Lightning detector and database creation not working

[Steve Sykes]

I have installed the AS3935 service, configured the extensions.py and the 
wview.py schema. I found that I needed to modify wview.py in order to get 
the extensions to work for some reason. 

At this time I have the lightning archive configured as a separate archive. 

So far there has been no archive created so I must have something wrong. 

For a time I had it archiving to weewx.sdb but was getting an error about 
units. At some point I would like to just have one database.

The log file, even with debug on shows nothing untoward. I have attached my 
weewx.conf, extensions.py and wview.py. Hopefully someone can see what is 
wrong. 

Lightning detection doesn't seem to work properly yet but if a database 
isn't created I will never see it.

Steve

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
#
#Copyright (c) 2009-2015 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#
"""The wview schema, which is also used by weewx."""

# =
# This is a list containing the default schema of the archive database.  It is
# identical to what is used by wview. It is only used for initialization ---
# afterwards, the schema is obtained dynamically from the database.  Although a
# type may be listed here, it may not necessarily be supported by your weather
# station hardware.
#
# You may trim this list of any unused types if you wish, but it will not
# result in saving as much space as you may think --- most of the space is
# taken up by the primary key indexes (type "dateTime").
# =
schema = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
  ('usUnits',  'INTEGER NOT NULL'),
  ('interval', 'INTEGER NOT NULL'),
  ('barometer','REAL'),
  ('pressure', 'REAL'),
  ('altimeter','REAL'),
  ('inTemp',   'REAL'),
  ('outTemp',  'REAL'),
  ('inHumidity',   'REAL'),
  ('outHumidity',  'REAL'),
  ('windSpeed','REAL'),
  ('windDir',  'REAL'),
  ('windGust', 'REAL'),
  ('windGustDir',  'REAL'),
  ('rainRate', 'REAL'),
  ('rain', 'REAL'),
  ('dewpoint', 'REAL'),
  ('windchill','REAL'),
  ('heatindex','REAL'),
  ('ET',   'REAL'),
  ('radiation','REAL'),
  ('UV',   'REAL'),
  ('extraTemp1',   'REAL'),
  ('extraTemp2',   'REAL'),
  ('extraTemp3',   'REAL'),
  ('soilTemp1','REAL'),
  ('soilTemp2','REAL'),
  ('soilTemp3','REAL'),
  ('soilTemp4','REAL'),
  ('leafTemp1','REAL'),
  ('leafTemp2','REAL'),
  ('extraHumid1',  'REAL'),
  ('extraHumid2',  'REAL'),
  ('soilMoist1',   'REAL'),
  ('soilMoist2',   'REAL'),
  ('soilMoist3',   'REAL'),
  ('soilMoist4',   'REAL'),
  ('leafWet1', 'REAL'),
  ('leafWet2', 'REAL'),
  ('rxCheckPercent',   'REAL'),
  ('txBatteryStatus',  'REAL'),
  ('consBatteryVoltage',   'REAL'),
  ('hail', 'REAL'),
  ('hailRate', 'REAL'),
  ('heatingTemp',  'REAL'),
  ('heatingVoltage',   'REAL'),
  ('supplyVoltage','REAL'),
  ('referenceVoltage', 'REAL'),
  ('windBatteryStatus','REAL'),
  ('rainBatteryStatus','REAL'),
  ('outTempBatteryStatus', 'REAL'),
  ('inTempBatteryStatus',  'REAL'),
  ('lightning_strikes','REAL'),
  ('lightning','REAL')]
#
#Copyright (c) 2009-2015 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#

"""User extensions module

This module is imported from the main executable, so anything put here will be
executed before anything else happens. This makes it a good place to put user
extensions.
"""

import locale
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, '')
# extend the default schema to include lightning
import weewx.units
weewx.units.USUnits['group_distance'] = 'mile'
weewx.units.MetricUnits['group_d

[weewx-user] Re: Distance Units

[Steve Sykes]

I have this in the log. I am running as3935.py v0.5rc1

Sep  1 14:52:30 raspberrypi weewx[25166]: as3935: strike at 6.0 km
Sep  1 14:52:30 raspberrypi weewx[25166]: as3935: callback failed: Unit 
system of incoming record (0x10) differs from 'archive' table in 
'weewx.sdb' database (0x01)

I must have something configured incorrectly but where?

Steve

On Friday, July 31, 2015 at 12:03:05 PM UTC-4, mwall wrote:
>
> On Friday, July 31, 2015 at 11:50:21 AM UTC-4, Robin wrote:
>>
>> Could I also ask if it is possible to put the Calibration (TUNE_CAP bits) 
>> in weewx.conf as each board is likely to be different? Mine is 4 so I need 
>> to change the value with each update.
>>
>
> support for the calibration (tune_cap) is already there.  just do this in 
> weewx.conf:
>
> [AS3935]
> calibration = 4
>
> if you want to specify everything, it looks like this:
>
> [AS3935]   
>  
> address = 3   
>   
> bus = 1   
>   
> noise_floor = 0   
>   
> calibration = 6   
>   
> indoors = True 
>  
> pin = 17   
>  
> data_binding = lightning_binding   
>  
>
> anything you do not specify gets a (hopefully sane) default value.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Instromet Sunshine Sensor

[Steve Sykes]

Robin

Looking on the sun sensor webpage, I see that they have a davis interface 
using an additional rain sensor input. Perhaps that is the easier way to 
go. You would only have to change the labels then.

Steve



On Wednesday, July 27, 2016 at 6:11:05 AM UTC-4, Robin wrote:
>
> Thank you Susan, the voltage divider I understand.
>
> Now I get into territory that I have not a clue about! I can manage 
> English (most of the time) and a little Greek (some of the time) but code 
> comes in at none of the time!!!
>
> Can anyone help me here.
>
>
>- I need to record (at short intervals) if there is a voltage present 
>via GPIO (the sun is casting a shadow).
>- at each archive interval I need to write the data to the database 
>and reset the record to zero, then start over again.
>
> I hope that there is some kind soul out there with the time, skill and 
> interest to help me. If I can get this sorted with a dummy sensor I will 
> buy the Instromet Sunshine Sensor and report back.
>
> Measuring the hours of sunshine has been a 'bee in my bonnet' for a while 
> and I currently estimate this from solar radiation. The Instromat sensor 
> seems to be a much more precise tool. I would love to have this working and 
> compare it to my estimated method.
>
> Thanks for reading this far.
> Regards
> Robin
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: wee_device usb error

[Steve Sykes]

You can add the user running weewx to the dialout group in /etc/groups. I have 
weewx owned by root to avoid these issues.

Steve

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx, Acurite, and Chip Computer

[Steve Sykes]

Andy,
I have one of these boards as well. I have thought to install weewx on it. 
It is an amazing little board for $5. I wonder, did you install it from a 
.deb or with setup.py? Perhaps it needs to be compiled for the Chip.

Steve

On Thursday, August 25, 2016 at 11:23:49 PM UTC-4, Andy wrote:
>
> Installed weewx on the Chip Computer  
> connected 
> to my Acurite 2032c  which can be viewed here 
> .  Seems to be working ok for the 
> last couple hours.  The backup battery connector is a nice feature.  Wonder 
> how long the permanently attached storage will hold up.  
>
> cmon is not happy with the new hardware
> Aug 25 19:42:16 chip weewx[17756]:  
>  self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD, 
> record=record, origin='software'))
> Aug 25 19:42:16 chip weewx[17756]: File 
> "/home/weewx/bin/weewx/engine.py", line 218, in dispatchEvent
> Aug 25 19:42:16 chip weewx[17756]:   callback(event)
> Aug 25 19:42:16 chip weewx[17756]: File 
> "/home/weewx/bin/user/cmon.py", line 581, in new_archive_record
> Aug 25 19:42:16 chip weewx[17756]:  
>  self.save_data(self.get_data(now, self.last_ts))
> Aug 25 19:42:16 chip weewx[17756]: File 
> "/home/weewx/bin/user/cmon.py", line 601, in get_data
> Aug 25 19:42:16 chip weewx[17756]:   record = 
> self.collector.get_data(now_ts)
> Aug 25 19:42:16 chip weewx[17756]: File 
> "/home/weewx/bin/user/cmon.py", line 474, in get_data
> Aug 25 19:42:16 chip weewx[17756]:   s = 
> self._readproc_line(tfile)
> Aug 25 19:42:16 chip weewx[17756]: File 
> "/home/weewx/bin/user/cmon.py", line 371, in _readproc_line
> Aug 25 19:42:16 chip weewx[17756]:   info = fp.read()
> Aug 25 19:42:16 chip weewx[17756]:   IOError: [Errno 22] Invalid 
> argument
> Aug 25 19:42:16 chip weewx[17756]:   Exiting.
>
> root@chip:/home/weewx# cat /proc/cpuinfo 
> processor : 0
> model name : ARMv7 Processor rev 2 (v7l)
> BogoMIPS : 1001.88
> Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant : 0x3
> CPU part : 0xc08
> CPU revision : 2
>
> Hardware : Allwinner sun4i/sun5i Families
> Revision : 
> Serial : 162542940781d366
>
> The Chip Computer has a connection for a 3.6v battery and a script which 
> pulls the stats.  If the Chip proves to be stable, on the to do list is get 
> the battery into cmon or adapt the APC UPS monitor in cmon.
> root@chip:/home/weewx# battery.sh 
> BAT_STATUS=0
> CHARG_IND=0
> BAT_EXIST=1
> CHARGE_CTL=0xc9
> CHARGE_CTL2=0x45
> Battery voltage = 4115.1mV
> Battery discharge current = .5mA
> Battery charge current = 0mA
>
>
>
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: MOD1016 Lightning Sensor

[Steve Sykes]

I did as well. For some reason it wouldn't take the change when I added it 
to extensions.py but did when I added it to the schema directly.
When I direct the archive to the loop, (I am using driver 0.5rc1) I see 
both units and when I dump the schema in sqlite3 I see them.  

What I am wondering is how to get them to show up on the webpage.

Steve
On Friday, August 26, 2016 at 11:48:51 AM UTC-4, meltz...@gmail.com wrote:
>
> Steve..when I followed the install instructions in the wiki, it added 2 
> columns to the .sdb file: 1 for strikes and 1 for distance. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Lightning detector units

[Steve Sykes]

I found this in the log this morning. I doubt that it is real lightning but 
at least it is detecting something.

Aug 26 11:06:47 raspberrypi weewx[4650]: as3935: strike at 5.0 km
Aug 26 11:06:47 raspberrypi weewx[4650]: as3935: callback failed: Unit 
system of incoming record (0x10) differs from 'archive' table in 
'weewx.sdb' database (0x01)

I looked in the weewx driver and see that it is supposed to convert the 
value to US units. group_distance in weewx.conf is set to mile so I don't 
quite know what is happening.

Anyone have similar results?

Steve

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] MOD1016 Lightning Sensor

[Steve Sykes]

Has anyone figured a way to show both the strikes and distance for the 
Lightning detector. I may have mine showing the strikes but can't figure out 
how to show how far away they are.

Steve

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] AS3935 Lightning sensor.

[Steve Sykes]

I recently upgraded to weewx 3.5.0 and just added the AS3935 Lightning 
sensor. I also have the Hobby boards lightning module running as well. I 
installed the weewx extension for the board. It shows up with i2cdetect at 
address 03. As far as I can tell it is running as weewx doesn't crash and 
the demo.py from github runs too.

When I run weewx from the command line I don't see new sensor show up. I 
tried disabling the HB sensor, but that didn't make a difference.

Since it is running and so is weewx, I don't where to start with the issue. 
Does anyone have a suggestion?

Steve

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.