RE: [weewx-user] Noisy logging, log_success = False not followed

[nineback]

Thanks Tom.  Working fine now.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Monday, May 25, 2020 6:13 PM
To: weewx-user 
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

 

My apologies. The layout of the configuration dictionary changed, and I have 
not had a chance to update the Wiki. The change makes it more consistent with 
the Python docs. You want:

 

[Logging]
# Root logger
[[root]]
   handlers = rotate,   
[[loggers]]
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG  
formatter = verbose   
class = logging.handlers.RotatingFileHandler  
filename = /var/log/weewx.log

 

The difference is that the root logger, [[root]], is now a peer, instead of a 
child, of [[loggers]].

 

V4.1.0 can now handle the integer options maxBytes and backupCount, if you want 
to put them back in.

 

-tk

 

 

 

On Mon, May 25, 2020 at 3:55 PM mailto:nineb...@gmail.com> 
> wrote:

Following these instructions I had logging to weewx.log working.  I upgraded to 
4.1.0 and am now logging to syslog and not weewx.log.  I tied Logging with and 
without the integers in my config file as below.

 

#[Logging]

#[[loggers]]

## Root logger

#[[[root]]]

#handlers = rotate,

#[[handlers]]

## Log to a set of rotating files

#[[[rotate]]]

#level = DEBUG   

#formatter = verbose

#class = logging.handlers.RotatingFileHandler   

#filename = /var/log/weewx.log

#maxBytes = 1000

#backupCount = 4   

 

[Logging]

[[loggers]]

# Root logger

[[[root]]]

handlers = rotate,

[[handlers]]

# Log to a set of rotating files

[[[rotate]]]

level = DEBUG   

formatter = verbose

class = logging.handlers.RotatingFileHandler   

filename = /var/log/weewx.log

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Tom Keffer
Sent: Friday, May 15, 2020 7:09 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

Sorry, Tom. This is due to a bug in how weewx configures the logger. The 
problem is that weewx does not convert strings to int when configuring.  It was 
fixed a couple weeks ago (commit  

 6348741), but I totally forgot about it.

 

You have two choices: 

1.   Replace your copy of weeutil/logger.py with the one in the repository 
 , 
or 

2.   remove the integers from the configuration stanza. It becomes

[Logging]
[[loggers]]
# Root logger
[[[root]]]
  handlers = rotate,# 1
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG   # 2
formatter = standard# 3
class = logging.handlers.RotatingFileHandler  # 4
filename = /var/log/weewx.log   # 5

-tk

 

On Fri, May 15, 2020 at 3:58 PM Chris Nelson mailto:cjncj...@gmail.com> > wrote:

Thinking out loud here...  Running as the Pi user?  Have write access to 
/var/log?

-- 
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/8fb4e590-c1f8-4220-beef-ab6e6baba964%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/CAPq0zEAkF8DDP%3D5ahXooNr2KiSFzQbcLWKo2tU4Y4RQMb7f8yw%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 

RE: [weewx-user] Noisy logging, log_success = False not followed

[nineback]

Following these instructions I had logging to weewx.log working.  I upgraded to 
4.1.0 and am now logging to syslog and not weewx.log.  I tied Logging with and 
without the integers in my config file as below.

 

#[Logging]

#[[loggers]]

## Root logger

#[[[root]]]

#handlers = rotate,

#[[handlers]]

## Log to a set of rotating files

#[[[rotate]]]

#level = DEBUG   

#formatter = verbose

#class = logging.handlers.RotatingFileHandler   

#filename = /var/log/weewx.log

#maxBytes = 1000

#backupCount = 4   

 

[Logging]

[[loggers]]

# Root logger

[[[root]]]

handlers = rotate,

[[handlers]]

# Log to a set of rotating files

[[[rotate]]]

level = DEBUG   

formatter = verbose

class = logging.handlers.RotatingFileHandler   

filename = /var/log/weewx.log

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Friday, May 15, 2020 7:09 PM
To: weewx-user 
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

Sorry, Tom. This is due to a bug in how weewx configures the logger. The 
problem is that weewx does not convert strings to int when configuring.  It was 
fixed a couple weeks ago (commit  

 6348741), but I totally forgot about it.

 

You have two choices: 

1.   Replace your copy of weeutil/logger.py with the one in the repository 
 , 
or 

2.   remove the integers from the configuration stanza. It becomes

[Logging]
[[loggers]]
# Root logger
[[[root]]]
  handlers = rotate,# 1
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG   # 2
formatter = standard# 3
class = logging.handlers.RotatingFileHandler  # 4
filename = /var/log/weewx.log   # 5

-tk

 

On Fri, May 15, 2020 at 3:58 PM Chris Nelson mailto:cjncj...@gmail.com> > wrote:

Thinking out loud here...  Running as the Pi user?  Have write access to 
/var/log?

-- 
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/8fb4e590-c1f8-4220-beef-ab6e6baba964%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/CAPq0zEAkF8DDP%3D5ahXooNr2KiSFzQbcLWKo2tU4Y4RQMb7f8yw%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/08c501d632e7%24a27a3340%24e76e99c0%24%40gmail.com.

RE: [weewx-user] Noisy logging, log_success = False not followed

[nineback]

Thanks Tom.  I updated the logger.py file and all is well.  I also changed the 
formatter to verbose so I could get date/time stamps.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Friday, May 15, 2020 7:09 PM
To: weewx-user 
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

Sorry, Tom. This is due to a bug in how weewx configures the logger. The 
problem is that weewx does not convert strings to int when configuring.  It was 
fixed a couple weeks ago (commit  

 6348741), but I totally forgot about it.

 

You have two choices: 

1.   Replace your copy of weeutil/logger.py with the one in the repository 
 , 
or 

2.   remove the integers from the configuration stanza. It becomes

[Logging]
[[loggers]]
# Root logger
[[[root]]]
  handlers = rotate,# 1
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG   # 2
formatter = standard# 3
class = logging.handlers.RotatingFileHandler  # 4
filename = /var/log/weewx.log   # 5

-tk

 

On Fri, May 15, 2020 at 3:58 PM Chris Nelson mailto:cjncj...@gmail.com> > wrote:

Thinking out loud here...  Running as the Pi user?  Have write access to 
/var/log?

-- 
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/8fb4e590-c1f8-4220-beef-ab6e6baba964%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/CAPq0zEAkF8DDP%3D5ahXooNr2KiSFzQbcLWKo2tU4Y4RQMb7f8yw%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/026901d62b1e%24a66839f0%24f338add0%24%40gmail.com.

RE: [weewx-user] Noisy logging, log_success = False not followed

[nineback]

I tried to follow the instructions in the v4 logging wiki, 
https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging.  I added this to my 
weewx.conf file:

 

[Logging]

[[loggers]]

# Root logger

[[[root]]]

  handlers = rotate,# 1

[[handlers]]

# Log to a set of rotating files

[[[rotate]]]

level = DEBUG   # 2

formatter = standard# 3

class = logging.handlers.RotatingFileHandler  # 4

filename = /var/log/weewx.log   # 5

maxBytes = 1000 # 6

backupCount = 4 # 7

 

Nothing is being logged to the weewx.log file and weewx is not updating the 
archive file or reports.  It appears weewx has crashed but syslog is not 
showing anything which I’m assuming indicates the program is trying to write to 
the weewx.log file but cannot hence it isn’t recording any error messages.

 

I tried top add syslog to the handlers thinking something might show up in 
syslog.

 

handlers = rotate, syslog   

 

This is what I get in the syslog file:

 

May 15 14:20:21 raspberrypi systemd[1]: Starting LSB: weewx weather system...

May 15 14:20:21 raspberrypi weewx[2183] INFO __main__: Initializing weewx 
version 4.0.0

May 15 14:20:21 raspberrypi weewx[2183] INFO __main__: Using Python 3.7.3 
(default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]

May 15 14:20:21 raspberrypi weewx[2183] INFO __main__: Platform 
Linux-4.19.97-v7+-armv7l-with-debian-10.4

May 15 14:20:21 raspberrypi weewx[2183] INFO __main__: Locale is 'en_US.UTF-8'

May 15 14:20:21 raspberrypi weewx[2183] INFO __main__: PID file is 
/var/run/weewx.pid

 

This is a new install.  Everything works fine until I try to add [Logging} to 
the weewx.conf file.

 

Tom

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Friday, May 15, 2020 6:55 AM
To: weewx-user 
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

Version 4.0 allows much more control over what gets logged 
 . To suppress 
everything below log level WARN, put this at the bottom of weewx.conf:

 

[Logging]
  [[loggers]]
[[[weewx.manager]]]
  level = WARN

 

-tk

 

On Thu, May 14, 2020 at 9:53 PM Chris Nelson mailto:cjncj...@gmail.com> > wrote:

These two log.info   lines in manager.py do not use the config 
file log_success switch, resulting in entries every five minutes.  Adding the 
log_success switch test within _addSingleRecord instances is not trivial since 
the config is not passed to the object.

 

May 12 18:55:15 shop2 journal: weewx[7760] INFO weewx.manager: Added record 
2020-05-12 18:55:00 MST (1589334900) to database 'weewx.sdb'

May 12 18:55:15 shop2 journal: weewx[7760] INFO weewx.manager: Added record 
2020-05-12 18:55:00 MST (1589334900) to daily summary in 'weewx.sdb'

 

This was noted back in 2017 also by Daniel Jönsson in this thread 
  - not a new 
issue.  I just commented out the two calls to log.info  ().  
I'm just working to clean up noise in my system log.

-- 
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/11778f1a-f56b-4753-97e9-4bc53c9a03e3%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/CAPq0zEDmQAMGzTFNDmhsXBupmo9e65%2B2CPEDDGiEuinW%2BYXXfg%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/00b201d62aef%24c7b1d8c0%2457158a40%24%40gmail.com.

[weewx-user] Re: Beta testers for v3.9.0 needed

[nineback]

>
> Just updated to 3.9.0b1 and am getting the following error.  I guess Gary 
> needs to look at the WD script.


Jan 23 11:13:24 raspberrypi weewx[11023]: cheetahgenerator: Generate failed 
with exception ''
Jan 23 11:13:24 raspberrypi weewx[11023]: cheetahgenerator:  Ignoring 
template /home/weewx/skins/Clientraw/clientrawdaily.txt.tmpl
Jan 23 11:13:24 raspberrypi weewx[11023]: cheetahgenerator:  Reason: 
toString() got an unexpected keyword argument 'NONE_string'
Jan 23 11:13:24 raspberrypi weewx[11023]:   Traceback (most recent call 
last):
Jan 23 11:13:24 raspberrypi weewx[11023]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in generate
Jan 23 11:13:24 raspberrypi weewx[11023]:   
fd.write(str(compiled_template))
Jan 23 11:13:24 raspberrypi weewx[11023]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Jan 23 11:13:24 raspberrypi weewx[11023]:   rc = getattr(self, 
mainMethName)()
Jan 23 11:13:24 raspberrypi weewx[11023]: File 
"_home_weewx_skins_Clientraw_clientrawdaily_txt_tmpl.py", line 138, in 
respond
Jan 23 11:13:24 raspberrypi weewx[11023]:   TypeError: toString() got 
an unexpected keyword argument 'NONE_string'
Jan 23 11:13:24 raspberrypi weewx[11023]: cheetahgenerator: Generate failed 
with exception ''
Jan 23 11:13:24 raspberrypi weewx[11023]: cheetahgenerator:  Ignoring 
template /home/weewx/skins/Clientraw/clientraw.txt.tmpl
Jan 23 11:13:24 raspberrypi weewx[11023]: cheetahgenerator:  Reason: 
toString() got an unexpected keyword argument 'NONE_string'
Jan 23 11:13:24 raspberrypi weewx[11023]:   Traceback (most recent call 
last):
Jan 23 11:13:24 raspberrypi weewx[11023]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in generate
Jan 23 11:13:24 raspberrypi weewx[11023]:   
fd.write(str(compiled_template))
Jan 23 11:13:24 raspberrypi weewx[11023]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Jan 23 11:13:24 raspberrypi weewx[11023]:   rc = getattr(self, 
mainMethName)()
Jan 23 11:13:24 raspberrypi weewx[11023]: File 
"_home_weewx_skins_Clientraw_clientraw_txt_tmpl.py", line 194, in respond
Jan 23 11:13:24 raspberrypi weewx[11023]:   TypeError: toString() got 
an unexpected keyword argument 'NONE_string'

Tom
 

-- 
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] Real Time Gauges (RTGD) for Steel Series

[nineback]

I'm a little confused which is nothing new.  I have RTGD configured as

[RealtimeGaugeData]
date_format = %Y.%m.%d %H:%M
rtgd_path = /home/weewx/public_html
scroller_source = WU
remote_server_url = http://www.XXX.com/weewx/ss/post_gauge-data.php
rtgd_file_name = gauge-data.txt

In my skin.com for ss is have

[CheetahGenerator]
   # search_list_extensions = user.forecast.ForecastVariables
encoding = html_entities
[[ToDate]]
[[[index]]]
template = index.html.tmpl
  #  [[[data]]]
   # template = gauge-data.txt.tmpl

I am getting the gauge-data.txt file created in the weewx/ss folder on my 
web site every loop but I am also getting the gauge-data.txt file upload to 
my weex folder at each archive interval.  I thought by commenting out the 
two lines in the ss skin that would prevent one file from being created.  I 
thought the loop file, created by RTGD, would go in the weex directory but 
it seems as though it is in my ss directory since the ss directory is being 
updated every loop.

When I look at my public_html folder on my Raspi I see the gauge-data.txt 
file in the root (weewx/public_html) but do not see the file in the 
weewx/public_html/ss folder.

So why am I getting two files and why is the loop going into the ss folder?

Tom




-- 
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] RPI and Saving Files to NAS

[nineback]

I have my laptop running Linux and weewx set up to store the archive folder 
and the public_html folder on my Synology NAS.  I have entered the lines 
into the fstab to have the NAS mounted when the laptop boots up.

I have tried different combinations of fstab with my RPI and the RPI will 
not boot.  I can mount the NAS folders from the command line once the RPI 
boots.

I've tried googling without success.  

I thought it would be as easy as transferring my Ubuntu fstab to the RPI.  
Boy was I mistaken.

Anyone had success putting your files on a nas using an RPI?

Thanks.

Tom

-- 
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] Re: Getting the RPi 3 with Davis Vantage up and running

[nineback]

Look towards the bottom of the index.html.temp file in the skins/standard 
directory.  You  will see .  Comment 
out this line.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
monmul
Sent: Sunday, January 13, 2019 2:48 PM
To: weewx-user 
Subject: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

 

I am searching for how to turn off showing the "internal temperature" graph but 
cannot see a anything in skin.conf or in weewx.conf.what am I missing?

On Sunday, 13 January 2019 17:15:11 UTC+13, monmul wrote:

WOW! thank you so much, Gary, for the pointers.I will get on to that in the 
next few days!

On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:

Hi,

 

There are a few steps involved in achieving what you want to do. First the 
historical max/min - by this I presume you mean all time statistics - those 
that cover all of your weeWX data and not just the last day, month or year. 

 

If I have this right you need to extend weeWX so that you can access stats from 
all of your data, this is most easily achieved by installing the xstats example 
extension. You will find the xstats files are in the 
/usr/share/doc/weewx/examples directory. I would install manually and just 
follow step 1 in the readme.txt remembering later that you will need to enable 
the alltime stats for your templates/reports by following step 2. You can 
install xstats using wee_extension but that will also install the example web 
page which you probably do not want.

 

Now that you have xstats installed you can use tags like $alltime.outTemp.max 
in report templates to display the maximum outside temperature. The time it 
occurred will be $alltime.outTemp.maxtime. Just like $day, $month and $year 
tags but you use $alltime. If you are not familiar with weeWX tags it is worth 
reading the Tags section 

  of the Customization Guide.

 

To use the $alltime tags you will probably want to create a new page or modify 
an existing one. It is really up to you want you want to do. To modify an 
existing page have a look at the .tmpl files in you Standard skin directory 
/etc/weewx/skins/Standard. These are the files weeWX uses to generate a 
corresponding .html page. You will see how tags are used in a template, in a 
nutshell where you place a tag weeWX will replace that with the relevant data 
when the reports are generated. The process is a little more involved if you 
want to create a new page as not only do you need to modify/create a page but 
you also need to modify skin.conf to have weeWX generate the new page. You may 
also need to modify other pages to include a link to your new page. A good 
starting point may be to take a copy of 
/etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl and 
start modifying. Have a good poke around the templates and skin.conf (and 
[StdReport] in weewx.conf) to see how it comes together. 

 

Including an image in a weeWX generated page can be relatively straightforward. 
If you have a look in index.html.tmpl you will see lines such as:

 



 

This line creates a HTML img tag that displays the daily temperature and 
dewpoint plot. If whatever you use to generate your webcam image can create a 
file named, say, webcam.jpg then that keeps it easy, you may be able to create 
a new img tag but using webcam.jpg (rather than daytempdew.png), you may need 
to add a path in front of the file name. If your webcam image is timestamped 
like webcam201901131345.jpg then that gets a little more complicated. If you 
can drop your webcam image into the weeWX directory structure under 
/var/www/html/weewx then you can very easily use weeWX to upload your webcam 
image to your web server if you wish. There are many different ways to achieve 
this, I have outlined one and I am sure other will have other ways. At the end 
of the day it will likely depend on your setup.

 

You have started on the slippery slope of customising your weeWX install, the 
process can appear daunting but do persist and feel free to continue to ask if 
not sure.

 

Gary

 

On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote:

I have managed to get the Standard skin loaded on my weather website 
www.wilsonbayweather.com...2   
small adjustments I would like to make..how do I show the historical max 
and min for temp, wind, rain etcand how might I include a jpeg photo from 
webcam showing a picture every hour or so? Thanks in advance.you guys have 
been fabulous in helping a newbie!

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails 

RE: [weewx-user] Real Time Gauges (RTGD) for Steel Series

[nineback]

OK.  I see more detailed instructions in the rtgd.py file.  I’ll give it a go 
though I may wait until tomorrow morning when I am fresh.  The steps seem 
pretty involved for us novices.  It does appear as though the gauge-data.txt 
file generated by SS is placed in the public_html/ss directory and the RTGD 
will place it in the public_html do it should not be an issue.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
nineb...@gmail.com
Sent: Saturday, January 12, 2019 7:55 PM
To: weewx-user@googlegroups.com
Subject: [weewx-user] Real Time Gauges (RTGD) for Steel Series

 

I am just starting to attempt to set these up.  I intend to use the 
post_gauge-data.php to get the files on my off-site server.  The instructions 
say:

 

Note: If the SteelSeries weeWX skin is installed either disable the skin or 
ensure that the Realtime gauge-data extension generated gauge-data.txt file is 
saved to a different location to that generated by the SteelSeries weeWX skin.

 

Doesn’t the SS skin generate the index.html file and the graphs.  I might have 
read somewhere that the graphs do not work with the RTGD extension but I would 
think you need the index.html?  So do go into the weex.conf file and but 
##skin=ss and that is all other than modifying the rtgd.py file?

 

Tom

-- 
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 

 .

-- 
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] Real Time Gauges (RTGD) for Steel Series

[nineback]

I am just starting to attempt to set these up.  I intend to use the
post_gauge-data.php to get the files on my off-site server.  The
instructions say:

 

Note: If the SteelSeries weeWX skin is installed either disable the skin or
ensure that the Realtime gauge-data extension generated gauge-data.txt file
is saved to a different location to that generated by the SteelSeries weeWX
skin.

 

Doesn't the SS skin generate the index.html file and the graphs.  I might
have read somewhere that the graphs do not work with the RTGD extension but
I would think you need the index.html?  So do go into the weex.conf file and
but ##skin=ss and that is all other than modifying the rtgd.py file?

 

Tom

-- 
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] Re: #IF #ELSE in Index.html.tmpl

[nineback]

Perfect!  I saw the .raw in the customizing reports but never thought to try it.

 

Thanks Andy.

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Andrew Milner
Sent: Monday, January 7, 2019 12:31 PM
To: weewx-user 
Subject: [weewx-user] Re: #IF #ELSE in Index.html.tmpl

 

try 

 

if $current.rainRate.raw == 0.00


On Monday, 7 January 2019 20:07:47 UTC+2, nine...@gmail.com 
  wrote:

No laughing please.  I’m trying to learn.

 

I want to make the value for Rain Rate RED when it is raining.  For some reason 
my code always default to the ELSE statement.  I have spent way too much time 
trying different options and internet searches so it is time to ask for help.  
My basic code:

 

#if $current.rainRate == 0.00

  

Rain Rate

$current.rainRate

  

#else



Rain Rate

 $current.rainRate 

  

  #end if

 

Since it is not raining current.rain.Rate = 0 but my display is showing in red 
which is the ELSE statement.

 

I’m sure it is something very basic.

 

Tom

-- 
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 

 .

-- 
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] #IF #ELSE in Index.html.tmpl

[nineback]

No laughing please.  I'm trying to learn.

 

I want to make the value for Rain Rate RED when it is raining.  For some
reason my code always default to the ELSE statement.  I have spent way too
much time trying different options and internet searches so it is time to
ask for help.  My basic code:

 

#if $current.rainRate == 0.00

  

Rain Rate

$current.rainRate

  

#else



Rain Rate

 $current.rainRate 

  

  #end if

 

Since it is not raining current.rain.Rate = 0 but my display is showing in
red which is the ELSE statement.

 

I'm sure it is something very basic.

 

Tom

-- 
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] Re: Getting the RPi 3 with Davis Vantage up and running

[nineback]

Curious why you are using a Wi-Fi dongle?  RPI 3 has Wi-Fi built in.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
monmul
Sent: Monday, January 7, 2019 12:18 AM
To: weewx-user 
Subject: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

 

Yes, thank you Gary for your help..it is very much my problem and not 
yours! I have a new power supply and wifi dongle on order...that might help!

 

Thanks for the digging on the WD data - will have a look at that in the next 
day or so!

On Monday, 7 January 2019 19:00:56 UTC+13, gjr80 wrote:

Ok, so on the face of it weeWX appears to be running fine. Not sure what 
problem we are solving now? My post of about 2 hours ago was in an attempt to 
work out if your headless RPi was running weeWX but it seems that is down to a 
wifi/dongle issue. If weeWX is running OK then WU should be fine as should your 
generated pages - checking syslog will show you what weeWX is/is not doing.

 

As an aside, I did a bit of digging on importing historical WD data. Should be 
relatively straightforward, have started adding to wee_import. Will let you 
know how it goes.

 

Gary


On Monday, 7 January 2019 15:54:22 UTC+10, monmul wrote:

This is what I get headless and with the LAN as opposed to the wifi dongle!

 

pi@Weatherpi:~ $ sudo systemctl status weewx 

● weewx.service - LSB: weewx weather system

   Loaded: loaded (/etc/init.d/weewx)

   Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago

  Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)

   CGroup: /system.slice/weewx.service

   └─786 python /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid...

 

Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled.

Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version 3.8.2

Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 seconds ...t)

Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 18:5...0)

Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 18:5...b'

Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 18:5...b'

Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop.

Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published re...0)

Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: Expected...ad

Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: Expected...ad

Hint: Some lines were ellipsized, use -l to show in full.

pi@Weatherpi:~ $ 

 


On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:

I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
Vantage weather station. I have a serial Envoy data logger attaced to my Rpi 
with a serial/usb converter. In following the set up instructions, I get these 
errors!

 

sudo weewxd weewx.conf

Traceback (most recent call last):

  File "/usr/bin/weewxd", line 64, in 

weewx.engine.main(options, args)

  File "/usr/share/weewx/weewx/engine.py", line 835, in main

sane = os.stat(config_path).st_ctime

OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'

pi@Weatherpi:~ $ tail -f /var/log/syslog

Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: sender=:1.16 
path=/MediaEndpoint/A2DPSink

Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available

Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available

Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed

Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed

Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, next 
retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007 

  ]

Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 3.8.2

Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 (default, Sep 
26 2018, 05:58:52) #012[GCC 4.9.2]

Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0

Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'

Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
Directories...

Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, next 
retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007 

  ]

Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary Directories.

Jan  6 13:55:28 Weatherpi 

RE: [weewx-user] Re: Alarm.py Help

[nineback]

Thanks for the heads up. I hardly ever use this email account (non-SSL) so was 
not aware of the problem. I updated the MX record and then tested it using the 
alarm.py file in the example directory.  Worked fine.

 

Again thanks for the help and sorry for the confusion.

 

Tom

 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, January 6, 2019 10:01 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

It looks like the problem is that there is no DNS entry for your hostname. This 
was causing a socket.gaierror exception to be raised, which quietly terminated 
the thread. I've changed the code to catch such an exception and log it.

 

-tk

 

On Sun, Jan 6, 2019 at 7:38 AM mailto:nineb...@gmail.com> 
> wrote:

Sent.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Sunday, January 6, 2019 9:33 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Possibly, but I don't think so. The library smtplib uses a default of 465 for 
attempting SSL connections. Also, even if one attempted to connect using the 
wrong port, it should still time out. Which it didn't.

 

Can you send the host name of the non-SSL server by private email? I don't need 
the user name and password. 

 

tkeffer at gmail.com 

 

 

-tk

 

On Sun, Jan 6, 2019 at 7:27 AM mailto:nineb...@gmail.com> 
> wrote:

It is the mail server provided by my ISP, inmotionhosting.com 

 .  No exception was raised.  Could it be something to do with the port?  I 
noticed in the setup that there was no way to designate a port.

 

SSL:

Outgoing Server:  secure246.inmotionhosting.com 

SMTP Port: 465

 

Non-SSL:

Outgoing Server:  mail.XXX.com 

  SMTP Port: 587

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Sunday, January 6, 2019 6:51 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

OK, but I wish we knew what the trouble was.

 

The last version had a 20 second 'timeout': if the server didn't respond, an 
exception should have been raised. Sounds like that didn't happen.

 

What was the non-SSL server you were using?

 

-tk

 

On Sat, Jan 5, 2019 at 6:59 PM mailto:nineb...@gmail.com> 
> wrote:

OK.  I got it working by changing my server to one requiring SSL.  I was using 
a non-SSL server and the latest version you sent still would not work.  I also 
tried Gmail SMTP and it works.  The “issue” seems to be with non-SSL servers.  
I usually find it the other way around.

 

I tried the original example alarm.py using an SSL server and it works so I 
think this confirms my ”issue” is with non-SSL servers.

 

Sorry for all the trouble.  I am happy to use the SSL server.

 

Many thanks.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 8:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Looks like your smtp server hangs if you try to connect to it using SSL. Try 
this version. 

 

-tk

 

On Sat, Jan 5, 2019 at 5:23 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I 

RE: [weewx-user] Re: Alarm.py Help

[nineback]

Sent.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, January 6, 2019 9:33 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Possibly, but I don't think so. The library smtplib uses a default of 465 for 
attempting SSL connections. Also, even if one attempted to connect using the 
wrong port, it should still time out. Which it didn't.

 

Can you send the host name of the non-SSL server by private email? I don't need 
the user name and password. 

 

tkeffer at gmail.com 

 

 

-tk

 

On Sun, Jan 6, 2019 at 7:27 AM mailto:nineb...@gmail.com> 
> wrote:

It is the mail server provided by my ISP, inmotionhosting.com 

 .  No exception was raised.  Could it be something to do with the port?  I 
noticed in the setup that there was no way to designate a port.

 

SSL:

Outgoing Server:  secure246.inmotionhosting.com 

SMTP Port: 465

 

Non-SSL:

Outgoing Server:  mail.XXX.com 

  SMTP Port: 587

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Sunday, January 6, 2019 6:51 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

OK, but I wish we knew what the trouble was.

 

The last version had a 20 second 'timeout': if the server didn't respond, an 
exception should have been raised. Sounds like that didn't happen.

 

What was the non-SSL server you were using?

 

-tk

 

On Sat, Jan 5, 2019 at 6:59 PM mailto:nineb...@gmail.com> 
> wrote:

OK.  I got it working by changing my server to one requiring SSL.  I was using 
a non-SSL server and the latest version you sent still would not work.  I also 
tried Gmail SMTP and it works.  The “issue” seems to be with non-SSL servers.  
I usually find it the other way around.

 

I tried the original example alarm.py using an SSL server and it works so I 
think this confirms my ”issue” is with non-SSL servers.

 

Sorry for all the trouble.  I am happy to use the SSL server.

 

Many thanks.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 8:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Looks like your smtp server hangs if you try to connect to it using SSL. Try 
this version. 

 

-tk

 

On Sat, Jan 5, 2019 at 5:23 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I attached it along 
with the syslog.  I am not using an SSL connection.  Still nothing.  I  did 
notice an error when I quit weewx this time.


On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com 
  wrote:

I set up alarm.py per the instructions (I think).  I wanted to test an alarm so 
I set it for expression= "outTemp > 40".  When I run weewx I get

 

alarm: Alarm set for expression: 'outTemp > 40.0'

 

alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 11:15:00 
CST (1546708500)

 

This is what I would expect however nothing else happens.  I looked in the 
syslog file and there is no mention of the mail being sent or an smtp error.   
Also there were no other entries stating the expression was true.

 

I waited one hour and again got this but no other entries in syslog.

 

Jan  5 12:16:16 raspberrypi 

RE: [weewx-user] Re: Alarm.py Help

[nineback]

It is the mail server provided by my ISP, inmotionhosting.com.  No exception 
was raised.  Could it be something to do with the port?  I noticed in the setup 
that there was no way to designate a port.

 

SSL:

Outgoing Server:  secure246.inmotionhosting.com   SMTP Port: 465

 

Non-SSL:

Outgoing Server:  mail.XXX.com SMTP Port: 587

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, January 6, 2019 6:51 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

OK, but I wish we knew what the trouble was.

 

The last version had a 20 second 'timeout': if the server didn't respond, an 
exception should have been raised. Sounds like that didn't happen.

 

What was the non-SSL server you were using?

 

-tk

 

On Sat, Jan 5, 2019 at 6:59 PM mailto:nineb...@gmail.com> 
> wrote:

OK.  I got it working by changing my server to one requiring SSL.  I was using 
a non-SSL server and the latest version you sent still would not work.  I also 
tried Gmail SMTP and it works.  The “issue” seems to be with non-SSL servers.  
I usually find it the other way around.

 

I tried the original example alarm.py using an SSL server and it works so I 
think this confirms my ”issue” is with non-SSL servers.

 

Sorry for all the trouble.  I am happy to use the SSL server.

 

Many thanks.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 8:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Looks like your smtp server hangs if you try to connect to it using SSL. Try 
this version. 

 

-tk

 

On Sat, Jan 5, 2019 at 5:23 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I attached it along 
with the syslog.  I am not using an SSL connection.  Still nothing.  I  did 
notice an error when I quit weewx this time.


On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com 
  wrote:

I set up alarm.py per the instructions (I think).  I wanted to test an alarm so 
I set it for expression= "outTemp > 40".  When I run weewx I get

 

alarm: Alarm set for expression: 'outTemp > 40.0'

 

alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 11:15:00 
CST (1546708500)

 

This is what I would expect however nothing else happens.  I looked in the 
syslog file and there is no mention of the mail being sent or an smtp error.   
Also there were no other entries stating the expression was true.

 

I waited one hour and again got this but no other entries in syslog.

 

Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp > 
40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)

 

 

I am using a Raspberry Pi.

 

Thanks,

 

Tom

 

 

-- 
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 

 .

-- 
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 

 .

-- 
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] Re: Alarm.py Help

[nineback]

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I attached it along 
with the syslog.  I am not using an SSL connection.  Still nothing.  I  did 
notice an error when I quit weewx this time.


On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com 
  wrote:

I set up alarm.py per the instructions (I think).  I wanted to test an alarm so 
I set it for expression= "outTemp > 40".  When I run weewx I get

 

alarm: Alarm set for expression: 'outTemp > 40.0'

 

alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 11:15:00 
CST (1546708500)

 

This is what I would expect however nothing else happens.  I looked in the 
syslog file and there is no mention of the mail being sent or an smtp error.   
Also there were no other entries stating the expression was true.

 

I waited one hour and again got this but no other entries in syslog.

 

Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp > 
40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)

 

 

I am using a Raspberry Pi.

 

Thanks,

 

Tom

 

 

-- 
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 

 .

-- 
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 

 .

-- 
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.
Jan  5 19:11:05 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
Jan  5 19:11:45 raspberrypi systemd[1]: Starting LSB: weewx weather system...
Jan  5 19:11:45 raspberrypi weewx[8566]: engine: Initializing weewx version 
3.8.2
Jan  5 19:11:45 raspberrypi weewx[8566]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan  5 19:11:45 raspberrypi weewx[8566]: engine: Platform 
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Jan  5 19:11:45 raspberrypi weewx[8566]: engine: Locale is 'en_US.UTF-8'
Jan  5 19:11:45 raspberrypi weewx[8566]: engine: pid file is /var/run/weewx.pid
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Using configuration file 
/home/weewx/weewx.conf
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Debug is 1
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Initializing engine
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Jan  5 19:11:45 raspberrypi weewx[8555]: Starting weewx weather system: weewx.
Jan  5 19:11:45 raspberrypi systemd[1]: Started LSB: weewx weather system.
Jan  5 19:11:45 raspberrypi weewx[8570]: vantage: Driver version is 3.0.11
Jan  5 19:11:45 raspberrypi weewx[8570]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
Jan  5 19:11:45 raspberrypi weewx[8570]: vantage: Gentle wake up of console 
successful
Jan  5 19:11:45 raspberrypi weewx[8570]: vantage: Hardware type is 16
Jan  5 19:11:45 raspberrypi weewx[8570]: vantage: ISS ID is 1
Jan  5 19:11:45 raspberrypi weewx[8570]: vantage: Hardware name: Vantage Pro2
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Loading service 
weewx.engine.StdTimeSynch
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: Loading service 
weewx.engine.StdConvert
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: StdConvert target unit is 0x1
Jan  5 19:11:45 raspberrypi weewx[8570]: engine: 

[weewx-user] Re: Alarm.py Help

[nineback]

I used the alarm.py version that you sent the link to.  I attached it along 
with the syslog.  I am not using an SSL connection.  Still nothing.  I  did 
notice an error when I quit weewx this time.

On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com wrote:
>
> I set up alarm.py per the instructions (I think).  I wanted to test an 
> alarm so I set it for expression= "outTemp > 40".  When I run weewx I get
>
> alarm: Alarm set for expression: 'outTemp > 40.0'
>
> alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 
> 11:15:00 CST (1546708500)
>
> This is what I would expect however nothing else happens.  I looked in the 
> syslog file and there is no mention of the mail being sent or an smtp 
> error.   Also there were no other entries stating the expression was true.
>
> I waited one hour and again got this but no other entries in syslog.
>
> Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp 
> > 40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)
>
>
> I am using a Raspberry Pi.
>
> Thanks,
>
> Tom
>
>
>

-- 
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.
Jan  5 18:19:18 raspberrypi weewx[7759]: engine: Initializing weewx version 
3.8.2
Jan  5 18:19:18 raspberrypi weewx[7759]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan  5 18:19:18 raspberrypi weewx[7759]: engine: Platform 
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Jan  5 18:19:18 raspberrypi weewx[7759]: engine: Locale is 'en_US.UTF-8'
Jan  5 18:19:18 raspberrypi weewx[7759]: engine: pid file is /var/run/weewx.pid
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Using configuration file 
/home/weewx/weewx.conf
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Debug is 1
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Initializing engine
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Jan  5 18:19:18 raspberrypi weewx[7748]: Starting weewx weather system: weewx.
Jan  5 18:19:18 raspberrypi systemd[1]: Started LSB: weewx weather system.
Jan  5 18:19:18 raspberrypi weewx[7763]: vantage: Driver version is 3.0.11
Jan  5 18:19:18 raspberrypi weewx[7763]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
Jan  5 18:19:18 raspberrypi weewx[7763]: vantage: Gentle wake up of console 
successful
Jan  5 18:19:18 raspberrypi weewx[7763]: vantage: Hardware type is 16
Jan  5 18:19:18 raspberrypi weewx[7763]: vantage: ISS ID is 1
Jan  5 18:19:18 raspberrypi weewx[7763]: vantage: Hardware name: Vantage Pro2
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading service 
weewx.engine.StdTimeSynch
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading service 
weewx.engine.StdConvert
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: StdConvert target unit is 0x1
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Finished loading service 
weewx.engine.StdConvert
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading service 
weewx.engine.StdCalibrate
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Finished loading service 
weewx.engine.StdCalibrate
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading service 
weewx.engine.StdQC
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Finished loading service 
weewx.engine.StdQC
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Jan  5 18:19:18 raspberrypi weewx[7763]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jan  5 18:19:18 raspberrypi weewx[7763]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Loading service 
weewx.engine.StdArchive
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Archive will use data binding 
wx_binding
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Record generation will be 
attempted in 'hardware'
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Using archive interval of 60 
seconds (specified by hardware)
Jan  5 18:19:18 raspberrypi weewx[7763]: engine: Use LOOP data in hi/low 
calculations: 1
Jan  5 18:19:18 raspberrypi weewx[7763]: manager: Daily 

[weewx-user] Alarm.py Help

[nineback]

I set up alarm.py per the instructions (I think).  I wanted to test an 
alarm so I set it for expression= "outTemp > 40".  When I run weewx I get

alarm: Alarm set for expression: 'outTemp > 40.0'

alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 
11:15:00 CST (1546708500)

This is what I would expect however nothing else happens.  I looked in the 
syslog file and there is no mention of the mail being sent or an smtp 
error.   Also there were no other entries stating the expression was true.

I waited one hour and again got this but no other entries in syslog.

Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp > 
40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)


I am using a Raspberry Pi.

Thanks,

Tom


-- 
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] Re: All Time Records

[nineback]

Thanks Pat!  I tried different variable but not sure why I did not try this one.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of Pat
Sent: Friday, January 4, 2019 2:30 PM
To: weewx-user 
Subject: [weewx-user] Re: All Time Records

 

$alltime.outTemp.mintime

On Friday, January 4, 2019 at 2:49:32 PM UTC-5, nine...@gmail.com 
  wrote:

I installed the xstats extension from the examples directory and it is 
producing the sample html file. I want to be able to show the max/min values 
and the time they occurred? Is there a variable I can use with say 
$alltime.outTemp.min to give me the time it occurred?

 

All Time Low: $alltime.outTemp.min at $xx.

 

Thanks,

Tom

-- 
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 

 .

-- 
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] All Time Records

[nineback]

I installed the xstats extension from the examples directory and it is 
producing the sample html file. I want to be able to show the max/min 
values and the time they occurred? Is there a variable I can use with say 
$alltime.outTemp.min to give me the time it occurred?

All Time Low: $alltime.outTemp.min at $xx.

Thanks,
Tom

-- 
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] Zambretti Forecast Showing "The forecast is Fine weather" When it is Raining

[nineback]

I have set up up the forecast add-in and have it set up to produce NWS and 
Weather Underground forecast which it is doing.  It is also producing a 
Zambretti Forecast but it ais showing "The forecast is Fine weather" for 
the past couple of days I have had forecast running.   The weather has not 
been fine.  It has been raining for the past couple of days.  Pressure had 
been up and down between 30.23 to 30.06 inHG.  This is the latest 
output from the zambretti.html file:

The forecast is Fine weather
Issued at 03-Jan-2019 10:55

Any ideas why I am not getting an accurate forecast?


Tom

-- 
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: Steel Series Gauges

[nineback]

I was testing the files on my local Window's Machine and getting the 
message.  Once I tested them on my off-site server all is well.

Tom

On Tuesday, January 1, 2019 at 10:30:52 AM UTC-6, nine...@gmail.com wrote:
>
> I installed the gauges uses the weex install script.  Files are being 
> produced in my var/www/html/weewx/ss directory.  When I run the index.html 
> file the gauges show up just fine except I get an error: in the led display 
> and no data is shown on the gauges.  I suspect it s something to do with 
> the location of the gauge-data.txt file but not sure?  The gauge-data.txt 
> file in the html/ss directory.
>
> Tom
>

-- 
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] Steel Series Gauges

[nineback]

I installed the gauges uses the weex install script.  Files are being 
produced in my var/www/html/weewx/ss directory.  When I run the index.html 
file the gauges show up just fine except I get an error: in the led display 
and no data is shown on the gauges.  I suspect it s something to do with 
the location of the gauge-data.txt file but not sure?  The gauge-data.txt 
file in the html/ss directory.

Tom

-- 
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] ExtraTemp1

[nineback]

Thanks again for the help and a great program.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, December 30, 2018 9:16 AM
To: weewx-user 
Subject: Re: [weewx-user] ExtraTemp1

 

Glad to hear all is well.

 

-tk

 

On Sun, Dec 30, 2018 at 4:59 AM Tom mailto:nineb...@gmail.com> > wrote:

Thanks.  I just copied the indoor temp graphs (day, week, month, year) in 
skin.conf to new sections and renamed to extraTemp1 and added the png files to 
the a new src line in the various html templates.

 

The more I use this program the more I am appreciating its flexibility and I am 
far from being a programmer. 

 

Linux from the command line, like reading the database file, is one of the 
hardest challenges for me.

 

It is interesting that I used two different Sqlite programs, one on Windows and 
one on Mac, and they both showed missing data where the Linux command line 
query showed the data.  I thought it would be easier to just copy the database 
file to Windows or Mac and use a GUI program to look at the database instead of 
figuring out the Linux commands. 

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Andrew Milner
Sent: Sunday, December 30, 2018 3:02 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] ExtraTemp1

 

just include extratemp1 to either an existing graph or to a new one.

 

change generic labels to add extratmp1 = my new label for the label on the graph

 

 


On Sunday, 30 December 2018 05:21:58 UTC+2, nine...@gmail.com 
  wrote:

Here is what sqlite3 shows.

 

sqlite> select datetime(dateTime, 'unixepoch', 'localtime'), inTemp, 
inHumidity, extraTemp1, windSpeed, windGust from archive order by dateTime desc 
limit 10;

2018-12-29 20:13:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:12:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:11:00|75.3|47.0|53.0|1.0|2.0

2018-12-29 20:10:00|75.3|47.0|53.0|1.0|2.0

2018-12-29 20:09:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:08:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:07:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:06:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:05:00|75.3|47.0|53.0|0.0|0.0

2018-12-29 20:04:00|75.3|47.0|53.0|0.0|0.0

 

So if I’m reading this right the data is being recorded. Interesting I also 
used a program on my Mac and got the same results of the data not showing.

 

I modified the standard html templates and have the extraTemp1 data showing in 
the reports.  Now I need to figure out how to modify skin.conf to get the 
extraTemp1 data to show up on the graphs produced by weewx.

 

Thanks a lot for all the help.

 

Tom

 

 

From: weewx...@googlegroups.com   
mailto:weewx...@googlegroups.com> > On Behalf Of 
Thomas Keffer
Sent: Saturday, December 29, 2018 8:12 PM
To: weewx-user mailto:weewx...@googlegroups.com> >
Subject: Re: [weewx-user] ExtraTemp1

 

That all looks normal.

 

Is there any reason you can't check the database on the machine which is 
running WeeWX? I would not trust a file transfer to Windows. Use the utility 
sqlite3:

 

You may need to install it first:

 

sudo apt-get install sqlite3

 

Then do

 

sqlite3 /var/lib/weewx/weewx.sdb

select datetime(dateTime, 'unixepoch', 'localtime'), inTemp, inHumidity, 
extraTemp1, windSpeed, windGust from archive order by dateTime desc limit 10;

 

 

-tk

 

On Sat, Dec 29, 2018 at 5:53 PM mailto:nine...@gmail.com> > 
wrote:

As requested.  Looking at the database I also see that windGustDir, inTemp, and 
inHumidity are NULL.



 

Tom

 

From: weewx...@googlegroups.com   
mailto:weewx...@googlegroups.com> > On Behalf Of 
Thomas Keffer
Sent: Saturday, December 29, 2018 7:22 PM
To: weewx-user mailto:weewx...@googlegroups.com> >
Subject: Re: [weewx-user] ExtraTemp1

 

So, the value is not making it to the database. 

 

At this point, we need to see the log. See the Wiki entry  

 Help! Posting to weewx-user for how to get a good log.

 

-tk

 

On Sat, Dec 29, 2018 at 5:17 PM Tom Robertson mailto:nine...@gmail.com> > wrote:

Thanks for the fast reply.  I downloaded the database to my windows machine and 
then used SQLiteStudio to look at it.  extraTemp1 shows null. Other fields are 
populated except for inTemp and inHumidity.  I must have turned them off 
somewhere?

 

I ran the –info and got this:

 

CONSOLE TYPE:   Vantage Pro2



CONSOLE FIRMWARE:

  Date: May  8 2012

  Version:  3.00



CONSOLE SETTINGS:

  

RE: [weewx-user] ExtraTemp1

[nineback]

Here is what sqlite3 shows.

 

sqlite> select datetime(dateTime, 'unixepoch', 'localtime'), inTemp, 
inHumidity, extraTemp1, windSpeed, windGust from archive order by dateTime desc 
limit 10;

2018-12-29 20:13:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:12:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:11:00|75.3|47.0|53.0|1.0|2.0

2018-12-29 20:10:00|75.3|47.0|53.0|1.0|2.0

2018-12-29 20:09:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:08:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:07:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:06:00|75.3|47.0|53.0|0.0|1.0

2018-12-29 20:05:00|75.3|47.0|53.0|0.0|0.0

2018-12-29 20:04:00|75.3|47.0|53.0|0.0|0.0

 

So if I’m reading this right the data is being recorded. Interesting I also 
used a program on my Mac and got the same results of the data not showing.

 

I modified the standard html templates and have the extraTemp1 data showing in 
the reports.  Now I need to figure out how to modify skin.conf to get the 
extraTemp1 data to show up on the graphs produced by weewx.

 

Thanks a lot for all the help.

 

Tom

 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Saturday, December 29, 2018 8:12 PM
To: weewx-user 
Subject: Re: [weewx-user] ExtraTemp1

 

That all looks normal.

 

Is there any reason you can't check the database on the machine which is 
running WeeWX? I would not trust a file transfer to Windows. Use the utility 
sqlite3:

 

You may need to install it first:

 

sudo apt-get install sqlite3

 

Then do

 

sqlite3 /var/lib/weewx/weewx.sdb

select datetime(dateTime, 'unixepoch', 'localtime'), inTemp, inHumidity, 
extraTemp1, windSpeed, windGust from archive order by dateTime desc limit 10;

 

 

-tk

 

On Sat, Dec 29, 2018 at 5:53 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.  Looking at the database I also see that windGustDir, inTemp, and 
inHumidity are NULL.



 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, December 29, 2018 7:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] ExtraTemp1

 

So, the value is not making it to the database. 

 

At this point, we need to see the log. See the Wiki entry Help! Posting to 
weewx-user 

  for how to get a good log.

 

-tk

 

On Sat, Dec 29, 2018 at 5:17 PM Tom Robertson mailto:nineb...@gmail.com> > wrote:

Thanks for the fast reply.  I downloaded the database to my windows machine and 
then used SQLiteStudio to look at it.  extraTemp1 shows null. Other fields are 
populated except for inTemp and inHumidity.  I must have turned them off 
somewhere?

 

I ran the –info and got this:

 

CONSOLE TYPE:   Vantage Pro2



CONSOLE FIRMWARE:

  Date: May  8 2012

  Version:  3.00



CONSOLE SETTINGS:

  Archive interval: 60 (seconds)

  Altitude: 1089 (foot)

  Wind cup type:large

  Rain bucket type: 0.01 inches

  Rain year start:  1

  Onboard time: 2018-12-29 18:55:44

  

CONSOLE DISPLAY UNITS:

  Barometer:inHg

  Temperature:  degree_F

  Rain: inch

  Wind: mile_per_hour

  

CONSOLE STATION INFO:

  Latitude (onboard):   +34.2°

  Longitude (onboard):  -86.2°

  Use manual or auto DST?   AUTO

  DST setting:  N/A

  Use GMT offset or zone code?  ZONE_CODE

  Time zone code:   6

  GMT offset:   N/A

  Temperature logging:  LAST

  Retransmit channel:   ON (255)



TRANSMITTERS: 

  Channel   Receive   Repeater  Type

 1  active  noneiss 

 2  active  nonetemp (as extra temperature 1)

 3  active  nonewind 

 4  inactivenone(N/A) 

 5  inactivenone(N/A) 

 6  inactivenone(N/A) 

 7  inactivenone(N/A) 

 8  inactivenone(N/A) 

 

RECEPTION STATS:

  Total packets received:   25957

  Total packets missed: 636

  Number of resynchronizations: 0

  Longest good stretch: 327

  Number of CRC errors: 98

  

BAROMETER CALIBRATION DATA:

  Current barometer reading:30.295 inHg

  Altitude: 1089 feet

  Dew point:

RE: [weewx-user] ExtraTemp1

[nineback]

As requested.  Looking at the database I also see that windGustDir, inTemp, and 
inHumidity are NULL.



 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Saturday, December 29, 2018 7:22 PM
To: weewx-user 
Subject: Re: [weewx-user] ExtraTemp1

 

So, the value is not making it to the database. 

 

At this point, we need to see the log. See the Wiki entry Help! Posting to 
weewx-user 

  for how to get a good log.

 

-tk

 

On Sat, Dec 29, 2018 at 5:17 PM Tom Robertson mailto:nineb...@gmail.com> > wrote:

Thanks for the fast reply.  I downloaded the database to my windows machine and 
then used SQLiteStudio to look at it.  extraTemp1 shows null. Other fields are 
populated except for inTemp and inHumidity.  I must have turned them off 
somewhere?

 

I ran the –info and got this:

 

CONSOLE TYPE:   Vantage Pro2



CONSOLE FIRMWARE:

  Date: May  8 2012

  Version:  3.00



CONSOLE SETTINGS:

  Archive interval: 60 (seconds)

  Altitude: 1089 (foot)

  Wind cup type:large

  Rain bucket type: 0.01 inches

  Rain year start:  1

  Onboard time: 2018-12-29 18:55:44

  

CONSOLE DISPLAY UNITS:

  Barometer:inHg

  Temperature:  degree_F

  Rain: inch

  Wind: mile_per_hour

  

CONSOLE STATION INFO:

  Latitude (onboard):   +34.2°

  Longitude (onboard):  -86.2°

  Use manual or auto DST?   AUTO

  DST setting:  N/A

  Use GMT offset or zone code?  ZONE_CODE

  Time zone code:   6

  GMT offset:   N/A

  Temperature logging:  LAST

  Retransmit channel:   ON (255)



TRANSMITTERS: 

  Channel   Receive   Repeater  Type

 1  active  noneiss 

 2  active  nonetemp (as extra temperature 1)

 3  active  nonewind 

 4  inactivenone(N/A) 

 5  inactivenone(N/A) 

 6  inactivenone(N/A) 

 7  inactivenone(N/A) 

 8  inactivenone(N/A) 

 

RECEPTION STATS:

  Total packets received:   25957

  Total packets missed: 636

  Number of resynchronizations: 0

  Longest good stretch: 327

  Number of CRC errors: 98

  

BAROMETER CALIBRATION DATA:

  Current barometer reading:30.295 inHg

  Altitude: 1089 feet

  Dew point:44 F

  Virtual temperature:  46 F

  Humidity correction factor:   2.0

  Correction ratio: 1.041

  Correction constant:  +0.000 inHg

  Gain: 0.000

  Offset:   -50.000

  

OFFSETS:

  Wind direction:   +0 deg

  Inside Temperature:   +0.0 F

  Inside Humidity:  +0 %

  Outside Temperature:  +0.0 F

  Outside Humidity: +0 %

  Extra Temperature 1:  +0.0 F

 

I ran the program direct and it showed extraTemp1: 54.0.

 

Tom

 

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, December 29, 2018 6:52 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] ExtraTemp1

 

Hello, Tom

 

How did you check for values in the database? Could you be more specific?

 

Couple things to try:

 

1. Try using the wee_device command with the --info option 

 . You will have to stop WeeWX first. This will confirm whether the console is 
aware of the extra sensor.

 

2. Try running WeeWX directly from the command line 

  and watch what it prints out. What values do you see for 

[weewx-user] Re: Unrecoverable Error

[nineback]

Replaced with older conf.  Now working.

Tom

On Wednesday, December 19, 2018 at 12:18:15 PM UTC-6, nine...@gmail.com 
wrote:
>
> Well I have somehow managed to change something that is causing my system 
> not to work.  It was working fine.  I imported several years worth of 
> record from Weather Underground. 
>
> I get this message:
>
> weewx[481]: engine: Caught unrecoverable exception in engine:
> Dec 19 11:50:37 weewx weewx[481]:   'windSpeed'
> Dec 19 11:50:37 weewx weewx[481]:   Traceback (most recent call 
> last):
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 877, in main
> Dec 19 11:50:37 weewx weewx[481]:   engine.run()
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 160, in run
> Dec 19 11:50:37 weewx weewx[481]:   
> self.dispatchEvent(weewx.Event(weewx.STARTUP))
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Dec 19 11:50:37 weewx weewx[481]:   callback(event)
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 509, in startup
> Dec 19 11:50:37 weewx weewx[481]:   
> self._catchup(self.engine.console.genStartupRecords)
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 623, in _catchup
> Dec 19 11:50:37 weewx weewx[481]:   origin='hardware'))
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Dec 19 11:50:37 weewx weewx[481]:   callback(event)
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/user/weewxwd3.py", line 177, in new_archive_record
> Dec 19 11:50:37 weewx weewx[481]:   data_metricwx['windSpeed'])
> Dec 19 11:50:37 weewx weewx[481]:   KeyError: 'windSpeed'
>
> Here is my config file:
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 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 = /
>
> # 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 = 3.8.2
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
> 
> # Description of the station location
> location = "Albertville, AL"
> 
> # Latitude and longitude in decimal degrees
> latitude = 34.244
> longitude = -86.235
> 
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 322, meter
> 
> # 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/ttyUSB0
> 
> # If the connection type is ethernet, an IP Address/hostname is 
> required:
> host = 1.2.3.4
> 
> ##
> # The rest of this section rarely needs any attention. 
> # You can safely leave it "as is."
> ##
> 
> # Serial baud rate (usually 19200)
> baudrate = 19200
> 
> # TCP port (when using the WeatherLinkIP)
> tcp_port = 2
> 
> # TCP send delay (when using the WeatherLinkIP):
> tcp_send_delay = 0.5
> 
> # The id of your ISS station 

[weewx-user] Re: Unrecoverable Error

[nineback]

I went back to a previous conf file and loaded it and things are now 
working again.  It is interesting that I tried this before with no luck.  I 
found out, for some reason, I needed to reboot weewx vs just restarting 
after replacing the conf file, for it to work.

Tom

On Wednesday, December 19, 2018 at 12:18:15 PM UTC-6, nine...@gmail.com 
wrote:
>
> Well I have somehow managed to change something that is causing my system 
> not to work.  It was working fine.  I imported several years worth of 
> record from Weather Underground. 
>
> I get this message:
>
> weewx[481]: engine: Caught unrecoverable exception in engine:
> Dec 19 11:50:37 weewx weewx[481]:   'windSpeed'
> Dec 19 11:50:37 weewx weewx[481]:   Traceback (most recent call 
> last):
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 877, in main
> Dec 19 11:50:37 weewx weewx[481]:   engine.run()
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 160, in run
> Dec 19 11:50:37 weewx weewx[481]:   
> self.dispatchEvent(weewx.Event(weewx.STARTUP))
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Dec 19 11:50:37 weewx weewx[481]:   callback(event)
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 509, in startup
> Dec 19 11:50:37 weewx weewx[481]:   
> self._catchup(self.engine.console.genStartupRecords)
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 623, in _catchup
> Dec 19 11:50:37 weewx weewx[481]:   origin='hardware'))
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Dec 19 11:50:37 weewx weewx[481]:   callback(event)
> Dec 19 11:50:37 weewx weewx[481]: File 
> "/usr/share/weewx/user/weewxwd3.py", line 177, in new_archive_record
> Dec 19 11:50:37 weewx weewx[481]:   data_metricwx['windSpeed'])
> Dec 19 11:50:37 weewx weewx[481]:   KeyError: 'windSpeed'
>
> Here is my config file:
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 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 = /
>
> # 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 = 3.8.2
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
> 
> # Description of the station location
> location = "Albertville, AL"
> 
> # Latitude and longitude in decimal degrees
> latitude = 34.244
> longitude = -86.235
> 
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 322, meter
> 
> # 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/ttyUSB0
> 
> # If the connection type is ethernet, an IP Address/hostname is 
> required:
> host = 1.2.3.4
> 
> ##
> # The rest of this section rarely needs any attention. 
> # You can safely leave it "as is."
> ##
> 
> # Serial baud rate (usually 19200)
> 

[weewx-user] Unrecoverable Error

[nineback]

Well I have somehow managed to change something that is causing my system 
not to work.  It was working fine.  I imported several years worth of 
record from Weather Underground. 

I get this message:

weewx[481]: engine: Caught unrecoverable exception in engine:
Dec 19 11:50:37 weewx weewx[481]:   'windSpeed'
Dec 19 11:50:37 weewx weewx[481]:   Traceback (most recent call 
last):
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/weewx/engine.py", line 877, in main
Dec 19 11:50:37 weewx weewx[481]:   engine.run()
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/weewx/engine.py", line 160, in run
Dec 19 11:50:37 weewx weewx[481]:   
self.dispatchEvent(weewx.Event(weewx.STARTUP))
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Dec 19 11:50:37 weewx weewx[481]:   callback(event)
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/weewx/engine.py", line 509, in startup
Dec 19 11:50:37 weewx weewx[481]:   
self._catchup(self.engine.console.genStartupRecords)
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/weewx/engine.py", line 623, in _catchup
Dec 19 11:50:37 weewx weewx[481]:   origin='hardware'))
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Dec 19 11:50:37 weewx weewx[481]:   callback(event)
Dec 19 11:50:37 weewx weewx[481]: File 
"/usr/share/weewx/user/weewxwd3.py", line 177, in new_archive_record
Dec 19 11:50:37 weewx weewx[481]:   data_metricwx['windSpeed'])
Dec 19 11:50:37 weewx weewx[481]:   KeyError: 'windSpeed'

Here is my config file:
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 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 = /

# 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 = 3.8.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Albertville, AL"

# Latitude and longitude in decimal degrees
latitude = 34.244
longitude = -86.235

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

# 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/ttyUSB0

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

##
# The rest of this section rarely needs any attention. 
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5

# The id of your ISS station (usually 1). If you use a wind meter 
connected
# to a anemometer transmitter kit, use its id
iss_id = 1

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
timeout = 4

# How long to wait before trying again (in seconds)
wait_before_retry = 1.2

# How many times to try before 

[weewx-user] Re: weewx-WD Upload Directory

[nineback]

Thanks Gary.  I commented out the various sections that had WD and the site 
is updating.  While using Weather Display software I had made some custom 
changes that I need to deal with.  I am using the alternate Saratoga script 
as well so need to do some fine tuning.

Tom

On Tuesday, December 18, 2018 at 10:28:16 PM UTC-6, gjr80 wrote:
>
> Hi,
>
> If you have a look in weewx.conf you will probably see something like:
>
> [StdReport]
> ...
> [[wdClientraw]]
> HTML_ROOT = WD
> skin = Clientraw
> 
>
> Commenting out the HTML_ROOT = WD line should do what you want though 
> this will depend on other config items in weewx.conf, alternatively you 
> can change that line to HTML_ROOT = public_html/wd.
>
> Save weewx.conf and then do a config reload or restart weeWX.
>
> Gary
>
> On Wednesday, 19 December 2018 13:08:24 UTC+10, nine...@gmail.com wrote:
>
>> New user of the raspberry pi and weewx.  I got weewx uploading fine to my 
>> Meteotemplate site.  I installed weewx-wd and am having problems with the 
>> FTP upload directory.  The html, png, etc files are going into my 
>> public_html/wd directory which is my main directory for wd.  The client* 
>> files are going into public_html/wd/WD.  WD is looking for the files in 
>> public_html/wd.  How do I get the client* files into the public_html/wd 
>> folder.
>>
>> Thanks,
>> Tom
>>
>

-- 
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] weewx-WD Upload Directory

[nineback]

New user of the raspberry pi and weewx.  I got weewx uploading fine to my 
Meteotemplate site.  I installed weewx-wd and am having problems with the 
FTP upload directory.  The html, png, etc files are going into my 
public_html/wd directory which is my main directory for wd.  The client* 
files are going into public_html/wd/WD.  WD is looking for the files in 
public_html/wd.  How do I get the client* files into the public_html/wd 
folder.

Thanks,
Tom

-- 
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.