Re: [weewx-user] Questions about weewx-loopdata

[geoffs...@gmail.com]

Hi John,

This is a great extension. I'm wondering if there is a way to be able to 
include sending data that is null  or none for a particular key? I'm using 
a davis vantage pro2, weewx 4.2. I'd like to use this to make a JSON output 
that can be ingested into a home automation system. So far it works great 
as long as the data is available to be sent, but I have not figured out how 
to send a key with a Null or none value. It looks like a key with a null or 
none value gets cleaved off the JSON output. If a battery dies on a sensor 
and it just disappears from the JSON output, that is much harder for the HA 
system to handle than a null, none or zero value. 

On Monday, November 16, 2020 at 2:57:13 PM UTC-8 jo...@johnkline.com wrote:

> A fix is released (v2.7.2).  There is no hurry to install the new release; 
> but once you’ve installed it, you can remove the field I asked you to add 
> to weewx.conf.
>
> On Nov 16, 2020, at 9:04 AM, Geni  wrote:
>
> Ok, works
>
>
> Thank you
>
> jo...@johnkline.com schrieb am Montag, 16. November 2020 um 16:05:21 
> UTC+1:
>
>> I can duplicate this problem and will issue a fix.
>>
>> In the meantime, you can add:
>> rainyear.outTemp.max
>> to the fields clause in the LoopData section of weewx.conf?
>>
>> That will stop this problem.  If you get similar errors for other periods 
>> where you have no fields listed, you’ll have to temporarily add a field for 
>> those periods also.
>>
>> I should have a fix shortly.  I don’t know that this is related to WeeWX 
>> 4.2, not that that really matters. 
>>
>> On Nov 16, 2020, at 2:45 AM, Geni  wrote:
>>
>> 
>>
>>
>> Hi john
>> since weewx 4.2.0 the loop-data.txt is no longer generated?
>> regards Geni
>>
>>
>> -- 
>> 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/3f89791f-c06b-43d1-beac-0afa58df59d6n%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+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/0f6cb227-1cdd-4fbb-9cf9-6f4c59521262n%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/0611c189-0c9f-4ab6-b6be-4d797e80bb96n%40googlegroups.com.

Re: [weewx-user] VantagePro 2 No longer connecting after S/W Update

[Chip Towner]

Hi,
Thanks for the quick reply!
You must see the code and/or these log messages in your sleep, I didn't see 
anything that even mentioned WRD.  I confirmed with minicom that I am not 
getting a response when I send out a WRD.  

I appreciate the work around, but before I use it I need to understand why 
the WRD is not working otherwise I have no idea what else is going wrong 
and my brain will start to itch.  

FYI, the serial connection is three wires connected from the serial port on 
the PI to the serial port on the VP2.  The cable ends do not appear to have 
been moved but it is certainly not robust. I had to move my hardware to 
perform the upgrade and if things were not shut down properly I suppose I 
could have damaged something.  Not sure why the WRD was impacted put the 
TEST, LAMP, VER, NVER commands were not impacted.  Of course different 
parts of the underlying circuits could have been damaged.

Again thanks very much.

Cheers! 



On Tuesday, November 24, 2020 at 5:32:11 PM UTC-7 tke...@gmail.com wrote:

> You didn't say much about your direct serial connection to the console, 
> but it is not properly emulating the Davis WRD command. This command 
> returns the hardware type (VantageVue, VantagePro, etc.)
>
> If all else fails, you can hard set it in the driver. At line 494 (or 
> thereabouts), change this
>
> self.hardware_type = None
>
>
> to this
>
> self.hardware_type = 16
>
>
> That may fix things, but there are likely to be other problems. You'll 
> have to do this every time you upgrade. Or, get the serial connection fixed!
>
>
>
> On Tue, Nov 24, 2020 at 4:20 PM Chip Towner  wrote:
>
>> Hi,
>> I have been using Weewx since 2014 on a RaspberryPi 2.  My weather 
>> station is a VantagePro2 and the connection is a straight serial connection 
>> (no data logger).  Weewx has worked well for this entire time.
>>
>> This year after a failed update (mirror sites no longer exist),  I 
>> decided I would take a chance and upgrade to the latest version of the 
>> Raspbian OS (Buster I beleive).  I backed up my Weewx data as directed 
>> prior to the update.  Then I updated the OS and took the opportunity to 
>> also update Weewx to the latest/greatest.
>>
>> Unfortunately Weewx is now unable to connect to the VP2.  
>>
>> Since I originally configured this connection in 2014 it is possible 
>> (perhpas eve likely) that I have missed something or even damaged the VP2 
>> (hope not).  
>>
>>- I have dug into the User Guide and believe I have things configured 
>>properly.
>>- I have used minicom and screen to confirm that my RPi can in fact 
>>talk to the VP2.   
>>- Used TEST and received the expected reply
>>   - Used LAMP 1 and turned the display light on
>>- I attempted to use wee_device to turn on the VP2 lamp. It did not 
>>work. 
>>   - I copied the results into the file weeDeviceLog.txt in case it 
>>   might be helpful 
>>- I edited the weewx.conf that was installed and did my best to 
>>configure things as they were previously (attached is weewxCurrent.conf, 
>> a 
>>renamed version of this document with some passwords removed)
>>   - I have updated the weewx.conf file to use software based record 
>>   generation.
>>   - The port settings appear to be correct - even when comparing to 
>>   my previous weewx.conf file.
>>
>> I am attaching a portion of the tail of the syslog file. I stopped weewx 
>> and then started it to show what happens. 
>>
>> Because it appears that I can communicate with the VP2 using minicom and 
>> screen I am hoping this means my RPI & VP2 are healthy and that this is 
>> some weewx configuration issue I have missed.
>>
>> Any help is appreciated!
>>
>> -- 
>> 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/e9bf7d61-7762-4853-b8be-4805299e7536n%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/2f58831b-1187-4379-a551-d3b32981869bn%40googlegroups.com.

Re: [weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

[vince]

We can't help much without an exact transcript of what you're seeing...your 
descriptions aren't quite enough for us.

It is likely you have quotes in there, or you're missing quotes, based on a 
google search for ":schema missing wget" and poking around the first few 
links.

Try putting quotes around the URL.  The question mark character in there 
can throw bash off.  You probably want a space after -O as well.

   wget --user=user --password=user  "
http://192.168.254.33/jpg/image.jpg?size=3;  -O /home/pi/Pictures/image.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/80fc3493-915a-4d25-93eb-c5a1071c59d5n%40googlegroups.com.

Re: [weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

[Rich Strle]

Thank you for all the suggestions. I need to take my linux-fu a lot.

Before I can move forward, I have a problem on my weather station Pi. On my 
'dev' Pi this wget command works as expected wget --user=user 
--password=user  http://192.168.254.33/jpg/image.jpg?size=3 
-O/home/pi/Pictures/image.jpg works as expected

When I run the same wget command on my weather station Pi I get an error 
message :schema Missing from wget. it makes the file but there isn't any 
data in the file. if I put the URL into a browser window I get the image I 
expect. 

if it matters, I am running WeeWX directly. I believe both Pi's have the 
same version of the operating system and I didn't change any permissions.

I'm out of ideas...

On Monday, November 23, 2020 at 10:03:46 AM UTC-6 sali...@gmail.com wrote:

> hello,
>
> here, what I did to capture a video image and put it on the RPi server 
> with the belchertown skin. I used an intermediate server, here a NAS. 
> (freeNas).
> 1- Samsung Camera > FTP > Freenas.
> 2 - SCP transfer from RPi (weewx) ---> FreeNas -> / home / pi / 
> transfer-images / "capture name"
> 3 - script to rename "capture name" ---> new name.jpg
> 4- cp "new name.jpg" ---> / var / www / html / weewx / belchertown / 
> images /
> 5- to automate everything, this I created a batch that I put in crontab.
>
> Patrick
> Le 23/11/2020 à 15:35, Greg Sinclair a écrit :
>
> I do this by doing all the processing on the Pi capturing the image and 
> then doing a sftp to place the image where weewx can find it. 
>
> Greg
>
> On Sunday, November 22, 2020 at 1:47:33 PM UTC-6 Rich Strle wrote:
>
>> Thanks very much Vince. 
>>
>> I appreciate your advice on the Linux Fundamentals course. 
>>
>> Rich Strle 
>> 309-824-9213 <(309)%20824-9213> 
>>
>> On Sun, Nov 22, 2020 at 12:34 PM vince  wrote: 
>> > 
>> > On Sunday, November 22, 2020 at 8:44:01 AM UTC-8 Rich Strle wrote: 
>> >> 
>> >> Looking at my passwrd file I see: 
>> www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin 
>> >> Would I remove the /nologin? 
>> >> 
>> > 
>> > Please don't do that. 
>> > 
>> > www-data is the owner of the web 'data' and your webserver process 
>> likely runs as that user. 
>> > The nologin there ensures that if anybody/anything breaks security on 
>> your webserver running process, then they still wouldn't be able to get a 
>> shell and install/run malware etc. 
>> > 
>> > What you want to do is: 
>> > 
>> > put all your processing in a script 
>> > run that script as the non-privileged user 'pi' and write to scratch 
>> directories that pi can write to (/tmp or /var/tmp are likely places) 
>> > in your script, do the 'privileged' copy of the output file to the 
>> /var/www/html directory by prefacing your 'cp' command ala 'sudo cp' 
>> > and you'll likely want to set the permissions on the file in 
>> /var/www/html also with 'sudo chmod' 
>> > 
>> > (standard suggestion - if you're asking this you need to up your 
>> linux-fu a little - I always suggest looking at the free edx.org Linux 
>> Fundamentals course that literally a million folks have taken) 
>> > 
>> > A simple script that grabs Google's logo image as an example would look 
>> something like: 
>> > 
>> > #!/bin/bash 
>> > UPSTREAM_URL="
>> https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png;
>>  
>>
>> > SCRATCH_FILE="/tmp/image.jpg" 
>> > FINAL_OUTPUT="/var/www/html/image.jpg" 
>> > 
>> > # wget the file in quiet mode to a temporary location 
>> > wget -q "${URL}" "${SCRATCH_FILE}" 
>> > 
>> > # copy it into place and fix up permissions via sudo 
>> > sudo cp "${SCRATCH_FILE}" "${FINAL_OUTPUT}" 
>> > sudo chown www-data "${FINAL_OUTPUT}" 
>> > sudo chmod 644 "${FINAL_OUTPUT}" 
>> > 
>> > This script did the right thing for me, FWIW. You'll of course have to 
>> put in the right wget switches to grab your image from the camera, as well 
>> as doing any processing with ImageMagick etc. before you copy your image 
>> into the web tree, but this should give you a skeleton to start with that 
>> does the permission stuff... 
>> > 
>> > 
>> > -- 
>> > 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/979HfPDddwc/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/ca47e7f4-cdd5-4989-92f1-6af8d1a154dan%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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6b532573-933d-4e1b-b010-c54f4b8ee483n%40googlegroups.com
>  
> 

Re: [weewx-user] VantagePro 2 No longer connecting after S/W Update

[Tom Keffer]

You didn't say much about your direct serial connection to the console, but
it is not properly emulating the Davis WRD command. This command returns
the hardware type (VantageVue, VantagePro, etc.)

If all else fails, you can hard set it in the driver. At line 494 (or
thereabouts), change this

self.hardware_type = None


to this

self.hardware_type = 16


That may fix things, but there are likely to be other problems. You'll have
to do this every time you upgrade. Or, get the serial connection fixed!



On Tue, Nov 24, 2020 at 4:20 PM Chip Towner  wrote:

> Hi,
> I have been using Weewx since 2014 on a RaspberryPi 2.  My weather station
> is a VantagePro2 and the connection is a straight serial connection (no
> data logger).  Weewx has worked well for this entire time.
>
> This year after a failed update (mirror sites no longer exist),  I decided
> I would take a chance and upgrade to the latest version of the Raspbian OS
> (Buster I beleive).  I backed up my Weewx data as directed prior to the
> update.  Then I updated the OS and took the opportunity to also update
> Weewx to the latest/greatest.
>
> Unfortunately Weewx is now unable to connect to the VP2.
>
> Since I originally configured this connection in 2014 it is possible
> (perhpas eve likely) that I have missed something or even damaged the VP2
> (hope not).
>
>- I have dug into the User Guide and believe I have things configured
>properly.
>- I have used minicom and screen to confirm that my RPi can in fact
>talk to the VP2.
>- Used TEST and received the expected reply
>   - Used LAMP 1 and turned the display light on
>- I attempted to use wee_device to turn on the VP2 lamp. It did not
>work.
>   - I copied the results into the file weeDeviceLog.txt in case it
>   might be helpful
>- I edited the weewx.conf that was installed and did my best to
>configure things as they were previously (attached is weewxCurrent.conf, a
>renamed version of this document with some passwords removed)
>   - I have updated the weewx.conf file to use software based record
>   generation.
>   - The port settings appear to be correct - even when comparing to
>   my previous weewx.conf file.
>
> I am attaching a portion of the tail of the syslog file. I stopped weewx
> and then started it to show what happens.
>
> Because it appears that I can communicate with the VP2 using minicom and
> screen I am hoping this means my RPI & VP2 are healthy and that this is
> some weewx configuration issue I have missed.
>
> Any help is appreciated!
>
> --
> 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/e9bf7d61-7762-4853-b8be-4805299e7536n%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/CAPq0zED1pTFO6fERkOFtF6ZLqoLgAbxt_%3DCfN2_esA7HxeEp3g%40mail.gmail.com.

[weewx-user] VantagePro 2 No longer connecting after S/W Update

[Chip Towner]

Hi,
I have been using Weewx since 2014 on a RaspberryPi 2.  My weather station 
is a VantagePro2 and the connection is a straight serial connection (no 
data logger).  Weewx has worked well for this entire time.

This year after a failed update (mirror sites no longer exist),  I decided 
I would take a chance and upgrade to the latest version of the Raspbian OS 
(Buster I beleive).  I backed up my Weewx data as directed prior to the 
update.  Then I updated the OS and took the opportunity to also update 
Weewx to the latest/greatest.

Unfortunately Weewx is now unable to connect to the VP2.  

Since I originally configured this connection in 2014 it is possible 
(perhpas eve likely) that I have missed something or even damaged the VP2 
(hope not).  

   - I have dug into the User Guide and believe I have things configured 
   properly.
   - I have used minicom and screen to confirm that my RPi can in fact talk 
   to the VP2.   
   - Used TEST and received the expected reply
  - Used LAMP 1 and turned the display light on
   - I attempted to use wee_device to turn on the VP2 lamp. It did not 
   work. 
  - I copied the results into the file weeDeviceLog.txt in case it 
  might be helpful 
   - I edited the weewx.conf that was installed and did my best to 
   configure things as they were previously (attached is weewxCurrent.conf, a 
   renamed version of this document with some passwords removed)
  - I have updated the weewx.conf file to use software based record 
  generation.
  - The port settings appear to be correct - even when comparing to my 
  previous weewx.conf file.
   
I am attaching a portion of the tail of the syslog file. I stopped weewx 
and then started it to show what happens. 

Because it appears that I can communicate with the VP2 using minicom and 
screen I am hoping this means my RPI & VP2 are healthy and that this is 
some weewx configuration issue I have missed.

Any help is appreciated!

-- 
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/e9bf7d61-7762-4853-b8be-4805299e7536n%40googlegroups.com.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2020 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.2.0

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Littleton, Colorado"

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = 37.574
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = -105.010

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 5650, foot

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = Vantage

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet 
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
   type = serial

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
   port = /dev/ttyAMA0

# If the connection type is ethernet, an IP Address/hostname is required:
#host = 1.2.3.4

##
# The rest of this section rarely 

Re: [weewx-user] Max tries exceeded while getting LOOP data

[Tom Keffer]

I stand corrected!

On Tue, Nov 24, 2020 at 1:20 PM DaveStLou  wrote:

> Clearing the logger memory is what got mine back on track after recent
> extended power outage caused the same error.
> On Monday, November 23, 2020 at 5:07:30 PM UTC-6 tke...@gmail.com wrote:
>
>> You could try clearing the memory. It's hard to imagine how that would
>> cause an unresponsive logger, but it wouldn't cost you anything to try.
>>
>> On Mon, Nov 23, 2020 at 3:05 PM ccroom  wrote:
>>
>>> Yes, it was on a UPS.  The computer ran for about 4 hours following the
>>> power outage.  I'm a bit puzzled about how this could happen as well.  I'm
>>> not throwing it in the trash.  Maybe some sort of corruption??
>>>
>>> On Monday, November 23, 2020 at 5:58:26 PM UTC-5 tke...@gmail.com wrote:
>>>
 Seems that way. Perhaps a power surge? Do you have the unit on a UPS
 or, at least, a surge suppressor?

 Logger failures are rare. This is maybe the  4th or 5th I've heard of.

 On Mon, Nov 23, 2020 at 2:54 PM ccroom  wrote:

> Thanks for your suggestions.  I removed and reset the logger, removed
> batteries from the console, etc but still no data from the logger.  I did
> have a brand new logger as a backup and installed the new logger.  After
> doing so everything works and it is operating normally.  I suppose
> "something"  during or after the storm caused a failure to the data
> logger.
>
> On Monday, November 23, 2020 at 10:28:37 AM UTC-5 tke...@gmail.com
> wrote:
>
>> He had a multi-hour outage. It's not surprising the Vantage clock
>> would be way behind.
>>
>> On Mon, Nov 23, 2020 at 6:19 AM Graham Eddy 
>> wrote:
>>
>>> also this does not look good
>>>
>>> On 24 Nov 2020, at 12:38 am, Tom Keffer  wrote:
>>>
>>> Nov 23 07:38:07 wxfitpc weewx[1201] INFO weewx.engine: Clock error
>>> is -1755.28 seconds (positive is fast)
>>>
>>>
>>> --
>>> 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/DE89371B-36A0-4A3B-918E-790F870667D0%40gmail.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+...@googlegroups.com.
>
 To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9f53e40e-780a-475c-8a7e-c413682a58ean%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/b6c5956d-f4bc-4b1e-b91c-65ba53f97d77n%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/0e34c519-f04d-46f3-8320-cb9f3b357692n%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/CAPq0zEAcJkb%3D%2BD0STbvc2AP6SVAgav4Xi4fy--Ra41i23vxWFg%40mail.gmail.com.

Re: [weewx-user] Max tries exceeded while getting LOOP data

[DaveStLou]

Clearing the logger memory is what got mine back on track after recent 
extended power outage caused the same error.
On Monday, November 23, 2020 at 5:07:30 PM UTC-6 tke...@gmail.com wrote:

> You could try clearing the memory. It's hard to imagine how that would 
> cause an unresponsive logger, but it wouldn't cost you anything to try.
>
> On Mon, Nov 23, 2020 at 3:05 PM ccroom  wrote:
>
>> Yes, it was on a UPS.  The computer ran for about 4 hours following the 
>> power outage.  I'm a bit puzzled about how this could happen as well.  I'm 
>> not throwing it in the trash.  Maybe some sort of corruption??  
>>
>> On Monday, November 23, 2020 at 5:58:26 PM UTC-5 tke...@gmail.com wrote:
>>
>>> Seems that way. Perhaps a power surge? Do you have the unit on a UPS or, 
>>> at least, a surge suppressor?
>>>
>>> Logger failures are rare. This is maybe the  4th or 5th I've heard of.
>>>
>>> On Mon, Nov 23, 2020 at 2:54 PM ccroom  wrote:
>>>
 Thanks for your suggestions.  I removed and reset the logger, removed 
 batteries from the console, etc but still no data from the logger.  I did 
 have a brand new logger as a backup and installed the new logger.  After 
 doing so everything works and it is operating normally.  I suppose 
 "something"  during or after the storm caused a failure to the data 
 logger.  

 On Monday, November 23, 2020 at 10:28:37 AM UTC-5 tke...@gmail.com 
 wrote:

> He had a multi-hour outage. It's not surprising the Vantage clock 
> would be way behind. 
>
> On Mon, Nov 23, 2020 at 6:19 AM Graham Eddy  
> wrote:
>
>> also this does not look good
>>
>> On 24 Nov 2020, at 12:38 am, Tom Keffer  wrote:
>>
>> Nov 23 07:38:07 wxfitpc weewx[1201] INFO weewx.engine: Clock error is 
>> -1755.28 seconds (positive is fast)
>>
>>
>> -- 
>> 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/DE89371B-36A0-4A3B-918E-790F870667D0%40gmail.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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/9f53e40e-780a-475c-8a7e-c413682a58ean%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b6c5956d-f4bc-4b1e-b91c-65ba53f97d77n%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/0e34c519-f04d-46f3-8320-cb9f3b357692n%40googlegroups.com.

[weewx-user] Re: Bresser 6in1

[Paul Eaton]

Many thanks Bob, that did the trick.

Just set up on Weathercloud. ID = d0878973678 if you're interested.

Have a nice evening.

Regards, Paul

On Tuesday, 24 November 2020 at 17:23:59 UTC Bob Atchley wrote:

> Hi Paul,
>
> Within the weewx.conf file In the WS6in1 driver section simply add "model 
> = abc" as an additional parameter, replacing abc with whatever you want to 
> call it.
> So mine reads:
> [WS6in1]
> # This section is for the 6in1 series of weather stations.
> # model - this is optional
> model = Youshiko YC9388 (WS6in1)
> 
> # The driver to use:
> driver = user.ws6in1
>
> Hope this helps
>
> Regards
>
> Bob
>

-- 
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/46a4dc7e-e676-4bd0-a404-33a196db8e56n%40googlegroups.com.

[weewx-user] weewx.conf with forecast aeris

[sali...@gmail.com]

hello,
why, when I put this conf "forecats", in  my file weewx.conf, weewx doesn't 
work ?

# General Forecast translations 
forecast_header = 7 Day Forecast 
daily_forecast = Daily Forecast 
alert_in_effect = in effect until forecast_last_updated = Last Updated on 

thanks

Patrick;

-- 
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/de200062-cb24-4493-b709-097acf7deb66n%40googlegroups.com.

[weewx-user] Re: Bresser 6in1

[Bob Atchley]

Hi Paul,

Within the weewx.conf file In the WS6in1 driver section simply add "model = 
abc" as an additional parameter, replacing abc with whatever you want to 
call it.
So mine reads:
[WS6in1]
# This section is for the 6in1 series of weather stations.
# model - this is optional
model = Youshiko YC9388 (WS6in1)

# The driver to use:
driver = user.ws6in1

Hope this helps

Regards

Bob

-- 
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/3ca7974d-956b-4470-b831-de5e3491351an%40googlegroups.com.

[weewx-user] Re: Belchertown Graphs, Reports, Records only show Index with parent directory in text.

[lecoqacr...@gmail.com]

Is there no answer to this issue? Pretty sure that it should be a simple 
fix if someone can point me in the right direction.
the seasons skin shows all graphs but the belchertown only has the output 
above of the " Parent directory etc." for graphs, records, reports.
Tried on weewx 3.9 with same results using debian install.
On Saturday, November 21, 2020 at 12:10:58 AM UTC-6 lecoqacr...@gmail.com 
wrote:

> Have weewx installed on Raspberry pi as a new install using the setup.py 
> method.
> Was trying to test the Belchertown skin after an install according to 
> instructions.
> The home screen of Belchertown looks normal but the Reports, Graphs and 
> Records tabs only bring up the following :
> Index of /home/weewx/public_html/graphs/
> NameSizeDate Modified
> index.html 
> 13.5 kB
> 11/20/20, 10:45:19 PM
>
> Weewx.conf is as follows for the StdReport section
> [StdReport]
> 
> # Where the skins reside, relative to WEEWX_ROOT
> SKIN_ROOT = /home/weewx/skins/
> 
> # Where the generated reports should go, relative to WEEWX_ROOT
> HTML_ROOT = /home/weewx/public_html/
> 
> # The database binding indicates which data should be used in reports.
> data_binding = wx_binding
> 
> # Whether to log a successful operation
> log_success = True
> 
> # Whether to log an unsuccessful operation
> log_failure = False
> 
> # Each of the following subsections defines a report that will be run.
> # See the customizing guide to change the units, plot types and line
> # colors, modify the fonts, display additional sensor data, and other
> # customizations. Many of those changes can be made here by overriding
> # parameters, or by modifying templates within the skin itself.
> 
> [[SeasonsReport]]
> # The SeasonsReport uses the 'Seasons' skin, which contains the
> # images, templates and plots for the report.
> skin = Seasons
> enable = false
> 
> [[SmartphoneReport]]
> # The SmartphoneReport uses the 'Smartphone' skin, and the images 
> and
> # files are placed in a dedicated subdirectory.
> skin = Smartphone
> enable = false
> HTML_ROOT = public_html/smartphone
> 
> [[MobileReport]]
> # The MobileReport uses the 'Mobile' skin, and the images and files
> # are placed in a dedicated subdirectory.
> skin = Mobile
> enable = false
> HTML_ROOT = public_html/mobile
> 
> [[StandardReport]]
> # This is the old "Standard" skin. By default, it is not enabled.
> skin = Standard
> enable = false
> [[Belchertown]]
> skin = Belchertown
> HTML_ROOT = /home/weewx/public_html/Belchertown
> enable = true
> 
> [[FTP]]
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> skin = Ftp
> 
> # If you wish to use FTP, set "enable" to "true", then
> # fill out the next four lines.
> # Use quotes around passwords to guard against parsing errors.
> enable = false
> user = replace_me
> password = replace_me
> server = replace_me# The ftp server name, e.g, 
> www.myserver.org
> path = replace_me# The destination directory, e.g., /weather
> 
> # Set to True for an FTP over TLS (FTPS) connection. Not all 
> servers
> # support this.
> secure_ftp = False
> 
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> #HTML_ROOT = public_html
> 
> # Most FTP servers use port 21
> port = 21
> 
> # Set to 1 to use passive mode, zero for active mode
> passive = 1
> 
> [[RSYNC]]
> # rsync'ing to a webserver is treated as just another report
> skin = Rsync
> 
> # If you wish to use rsync, you must configure passwordless ssh 
> using
> # public/private key authentication from the user account that 
> weewx
> # runs to the user account on the remote machine where the files
> # will be copied.
> #
> # If you wish to use rsync, set "enable" to "true", then
> # fill out server, user, and path.
> # The server should appear in your .ssh/config file.
> # The user is the username used in the identity file.
> # The path is the destination directory, such as 
> /var/www/html/weather.
> # Be sure that the user has write permissions on the destination!
> enable = false
> server = replace_me
> user = replace_me
> path = replace_me
> 
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a 

[weewx-user] Re: wxnow.txt does not contain precipitation totals

[tbu...@gmail.com]

I do like the idea of using CWOP for the reasons you mentioned.  I'm 
comfortable around the Weewx ecosystem, Python, etc.  If you don't mind, 
send it along and I'll have a look.

No rush.  I still don't have a dedicated antenna for a packet station like 
I used to.  (Although I have a few things in mind)

Thanks.


On Monday, November 23, 2020 at 9:43:31 PM UTC-5 ls1b...@gmail.com wrote:

> After spending some time fixing cwxn to address the issues I found, I took 
> a brief look at weewx-aprx.  I forget exactly why I decided not to go that 
> route, I think it pertained to the way it was generating the packet which 
> didn't entirely mesh with how I wanted it for direwolf.  So then I decided 
> to leverage the CWOP support since it's basically the same format.  I 
> enabled the CWOP support (so that it's sending directly to aprs-is) and I 
> made a couple minor edits in restx.py to output the relevant bits of the 
> packet to a wxnow.txt which direwolf can use.  Unfortunately I just did 
> them as local edits - I didn't pull the weewx branch and make the changes 
> via git.  And I basically just hard-coded the changes in.  What I should've 
> done was add an option in the weewx.conf to write it out and then maybe 
> submit a pull request to get that included in the weewx sources.  
>
> Depending on your comfort level dealing with source code, if you want, I 
> can send you my restx.py with my changes, but you'll want to compare with 
> your restx.py in case it's not based on the same version.  
>
> -Dave
>
> On Monday, November 23, 2020 at 5:28:26 PM UTC-8 tbu...@gmail.com wrote:
>
>> Hello - 
>>
>> Longtime Weewx user trying to get his station on APRS (RF).
>>
>> I'm using Direwolf and, ideally, would just like to get a wxnow.txt file 
>> that it can pick up.  However, it appears that the original author of the 
>> cxwn extension may have pulled it down.
>>
>> I see a reference to another plugin -  weewx-aprx  - but I'm unable to 
>> locate that as well.
>>
>> Any assistance would be great!  Thanks!
>>
>>  
>>
>> On Thursday, September 17, 2020 at 12:09:12 PM UTC-4 ls1b...@gmail.com 
>> wrote:
>>
>>> Gary,
>>>
>>> Thanks!  I just took a look at the weewx-aprx extension.  FWIW, in 
>>> addition to fixing the humidity, I also added solar radiation 
>>> (luminosity).  One other thing to note which I'm likely going to try and 
>>> fix shortly, and you might consider fixing in weewx-aprx, is that the 
>>> nullproof probably shouldn't turn those values into 0.  To indicate "no 
>>> value", I believe periods should be used - otherwise it's interpreted as a 
>>> real value of 0. 
>>>
>>> Here's the code I added for radiation:
>>>
>>> # DWC adding solar radiation. If it's below 1000, use 'L' 
>>> # if it's above 1000, use 'l' and provide the value above 1000 
>>> if data['radiation'] < 1000: 
>>> fields.append("L%03d" % int(data['radiation'])) 
>>> elif data['radiation'] < 2000: 
>>> fields.apped("l%03d" % (int(data['radiation'])-1000)) 
>>> else: 
>>> loginf("radiation looks bad: %d" % int(data['radiation']))
>>>
>>> -Dave
>>>
>>> On Thursday, September 17, 2020 at 3:16:12 AM UTC-7 gjr80 wrote:
>>>
 Thanks, subsequent to the above thread and in concert with Bill I created 
 the weewx-aprx extension  which 
 does include the correct humidity behaviour.

 Gary

 On Thursday, 17 September 2020 at 11:16:08 UTC+10 ls1b...@gmail.com 
 wrote:

> Sorry for bringing an old thread up here.  I just posted this to the 
> related wxforum post:  https://www.wxforum.net/index.php?topic=38877
>
> I'll copy-paste my post here:
>
> Following this thread and some threads and references elsewhere, I 
> just got my WX station working with direwolf and weewx running on an rpi, 
> and I wanted to point out that there's a small issue with the cwxn.py 
> implementation, at least for APRS use.   
>
> At first I thought everything was going great - I was beaconing out 
> the wxnow.txt info and looking at aprs.fi everything looked good.  
> But then I looked at the info in findu and noticed the dew point seemed 
> to 
> be messed up.  Looking at it more closely, that was because the humidity 
> was wrong.  Instead of, for example, 92%, it was showing up as 9%.  So I 
> took a closer look at the format of the data.  The humidity is being 
> formatted as a 3 digit number by cwxn.  But the APRS spec and CWOP spec 
> indicate it should be 2 digits, and 00 should be interpreted as 100%.  
> Apparently aprs.fi is being tolerant of the 3-digit number, but findu 
> is not. 
>
> I made a small change to cwxn.py to convert 100 to 0 and to format as 
> %02d instead of %03d.  All looks good in both aprs.fi and findu now. 
>
> BTW, in case it's relevant, I'm using the cwxn.py that was posted 
> earlier in this thread by gjr80.  
>
> My station:
> 

[weewx-user] Re: Bresser 6in1

[Paul Eaton]

Hi Bob,

Thanks for the reply regarding the "model" parameter but it's got me a bit 
confused (easily done!) I've been trying to edit the weewx.conf file where 
there is a line "station_type = WS6in1" but as I said that doesn't seem to 
work. You have referred to "model = " as the line to edit to but I can't 
see that in weewx.conf so I'm assuming it's in a different file but I'm not 
sure where to look.

Regards, Paul

On Monday, 23 November 2020 at 17:37:45 UTC Bob Atchley wrote:

> Hi Paul,
>
> Yes, I wish I had known about CCL Electronics before, almost definitely 
> the manufacturer.  I'll stick with the current name but update the Readme.
>
> As for 'About this weather station', the 'model' parameter is optionally 
> supported, I have mine set to "model = Youshiko YC9388 (WS6in1)"
>
> Regards
>
> Bob
>
>

-- 
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/07a51e51-9eb0-4121-bc23-d2eba13bcd3dn%40googlegroups.com.