date:20190523

Hi,
Well got little bit more working. To get around the issue with the 
format(add_label I changed all the "format(add_label" code to 
"toString(addLabel" which is the function in units.py that matched what was 
trying to be done. Not sure why the other format function call is not 
there, maybe a different version of units.py. I am using 3.8.2. I now have 
a number of apache errors with the PHP and some problems with the 
almanac.sun in the tmpl file. But I am getting closer. The weewx docs show 
the add_label with the format show be correct so not sure what is missing. 
Do you have an updated version of units.py?
Thanks Jerry

>
>>

-- 
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/a99f374e-f51b-4101-84eb-011874a92454%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

2019-05-23 Thread Leon Shaner

I am in contact with IBM.  This whole intersection is entirely for THEIR 
benefit.
I am persistent SOB. It'll be fixed.  LOL

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 23, 2019, at 9:22 PM, Jarom Hatch  wrote:
> 
> Even after that none of the backfilled data made it in.  If they are no 
> longer accepting backfilled data then fixing wunderfixer might not be 
> possible.
> 
> -- 
> 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/76f9aa83-37ac-4014-aa04-7f675d63a6e1%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/36EA4E1E-EEAE-4210-A18E-5024653E6F09%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

Even after that none of the backfilled data made it in.  If they are no longer 
accepting backfilled data then fixing wunderfixer might not be possible.

-- 
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/76f9aa83-37ac-4014-aa04-7f675d63a6e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Weather34 Template for WeeWX - New Major Update

Hi,
Here is weewx.conf.# 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 = 1

# 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 = 
# Latitude and longitude in decimal degrees
latitude = xx
longitude =xx

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 1500, 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 = WS23xx

# 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

##

[WS23xx]
# This section is for the La Crosse WS-2300 series of weather stations.

# Serial port such as /dev/ttyS0, /dev/ttyUSB0, or /dev/cuaU0
port = /dev/ttyUSB0

# The station model, e.g., 'LaCrosse WS2317' or 'TFA Primus'
model = LaCrosse WS-2316

# The driver to use:
driver = weewx.drivers.ws23xx

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = false

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against parsing errors, put the password in quotes.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = false
station = replace_me

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = False

##

#   This section specifies what reports, using which skins, to generate.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

report_timing = 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 59 * * * *

# Each of the

Re: [weewx-user] Weather34 Template for WeeWX - New Major Update

2019-05-23 Thread steeple ian

Can you post your weewx.conf and w34skin skin.conf files please (redact any 
passwords, user IDs, keys etc. first)

Thanks

> On 23 May 2019, at 20:15, Jd D  wrote:
> 
> Hi,
> My path looks correct. The following error is in the syslog from the Cheetah 
> Generator.
> 
> May 23 12:00:54 localhost weewx[7901]: cheetahgenerator: Generate failed with 
> exception ''
> May 23 12:00:54 localhost weewx[7901]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/w34skin/w34stats.php.tmpl
> May 23 12:00:54 localhost weewx[7901]: cheetahgenerator:  Reason: 
> format() got an unexpected keyword argument 'add_label'
> May 23 12:00:54 localhost weewx[7901]:   Traceback (most recent call 
> last):
> May 23 12:00:54 localhost weewx[7901]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
> May 23 12:00:54 localhost weewx[7901]:   print >> _file, 
> compiled_template
> May 23 12:00:54 localhost weewx[7901]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in __str__
> May 23 12:00:54 localhost weewx[7901]:   rc = getattr(self, 
> mainMethName)()
> May 23 12:00:54 localhost weewx[7901]: File 
> "_etc_weewx_skins_w34skin_w34stats_php_tmpl.py", line 2656, in respond
> May 23 12:00:54 localhost weewx[7901]: File 
> "_etc_weewx_skins_w34skin_w34stats_php_tmpl.py", line 106, in __errorCatcher6
> May 23 12:00:54 localhost weewx[7901]: File "", line 1, in 
> 
> May 23 12:00:54 localhost weewx[7901]:   TypeError: format() got an 
> unexpected keyword argument 'add_label'
> 
> Looks like I am missing something.
> Thanks Jerry
> 
> On Thursday, May 23, 2019 at 10:28:31 AM UTC-7, steeple ian wrote:
> Hi Jerry,
> 
> I am glad my first instinct was correct.
> 
> The w34stats.php.tmpl file should be generating the w34stats.php file at 
> every archive interval. You to make sure you have the correct path settings 
> in the w34skin skin.conf file.
> 
> I hope that fixes it for you.
> 
> Ian
> 
> On Thu, May 23, 2019 at 6:16 PM Jd D > wrote:
> Hi,
> I am using PHP7 and was using the previous version of template, I just missed 
> that this version is now using php mb functions, so the following two 
> commands fixed this for me.
> 
> sudo apt-get install php7.0-mbstring
> sudo systemctl restart apache2.service
> 
> Also metobridge_lookup.php has the following include
> include('w34stats.php');
> but only file I see in the install package is w34stats.php.tmpl in the skins 
> directory and the apache log has lots of undefineds.
> 
> Thanks Jerry
> 
> On Wednesday, May 22, 2019 at 11:30:16 PM UTC-7, steeple ian wrote:
> Hi, 
> It looks like your PHP installation is missing some modules. Please look at 
> the important information regarding installing PHP in the installation guide. 
> 
> I also recommend that you upgrade to PHP7 or later. 
> 
> Ian 
> 
> Sent from my iPad 
> 
> > On 23 May 2019, at 02:35, Jd D > wrote: 
> > 
> > PHP Fatal error:  Uncaught Error: Call to undefined function 
> > mb_internal_encoding() in /var/www/html/pws_new/common.php:5\nStack 
> > trace:\n#0 /var/www/html/pws_new/index.php(59): include_once()\n#1 {main}\n 
> >  thrown in /var/www/html/pws_new/common.php on line 5 
> 
> -- 
> 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...@googlegroups.com <>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/fc6d7fc0-163e-46fa-b695-ade13f743f46%40googlegroups.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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/438b634b-39b6-43f7-b424-963c022c2b7c%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32AD3FC3-472F-4257-A77A-1F30EB0E769A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

Leon and Vince; first thanks for your help and advice. My only experience
in programming was a LONG time ago, so anything I learn is either from
helpful people like you or what I can figure out by searching the web. I
did come to the conclusion that the nesting order of the expressions is
most likely why the email is not being sent properly. My next bit of
research will be in how to properly nest if / then statements. The reason I
picked such low values is I did not want to wait so long for the %mem to
climb to a high value so I could see what is happening. I was careful in
copying the original script that I found, so I can only assume it didn't
run properly as originally written, and no one called the writer out on it.
As for the multitude of braces, parenthesis, and who knows what else, that
is me not knowing proper syntax. Here is where I found the script, (he uses
free -m) if you want to see it:
https://superuser.com/questions/419617/how-to-monitor-memory-usage-for-alarming-purpose

It is answer #3.

Leon, This all started when I noticed my system was crashing after running
for a relatively short time. There are almost 8 pages (!) but back around
Jan 38 I think I posted the results of top.

Steve

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/11131edd-7d7a-423f-b29e-4876b715ee62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

Hi,
My path looks correct. The following error is in the syslog from the 
Cheetah Generator.

May 23 12:00:54 localhost weewx[7901]: cheetahgenerator: Generate failed 
with exception ''
May 23 12:00:54 localhost weewx[7901]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/w34skin/w34stats.php.tmpl
May 23 12:00:54 localhost weewx[7901]: cheetahgenerator:  Reason: 
format() got an unexpected keyword argument 'add_label'
May 23 12:00:54 localhost weewx[7901]:   Traceback (most recent call 
last):
May 23 12:00:54 localhost weewx[7901]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
May 23 12:00:54 localhost weewx[7901]:   print >> _file, 
compiled_template
May 23 12:00:54 localhost weewx[7901]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
May 23 12:00:54 localhost weewx[7901]:   rc = getattr(self, 
mainMethName)()
May 23 12:00:54 localhost weewx[7901]: File 
"_etc_weewx_skins_w34skin_w34stats_php_tmpl.py", line 2656, in respond
May 23 12:00:54 localhost weewx[7901]: File 
"_etc_weewx_skins_w34skin_w34stats_php_tmpl.py", line 106, in 
__errorCatcher6
May 23 12:00:54 localhost weewx[7901]: File "", line 1, in 

May 23 12:00:54 localhost weewx[7901]:   TypeError: format() got an 
unexpected keyword argument 'add_label'

Looks like I am missing something.
Thanks Jerry

On Thursday, May 23, 2019 at 10:28:31 AM UTC-7, steeple ian wrote:
>
> Hi Jerry,
>
> I am glad my first instinct was correct.
>
> The w34stats.php.tmpl file should be generating the w34stats.php file at 
> every archive interval. You to make sure you have the correct path settings 
> in the w34skin skin.conf file.
>
> I hope that fixes it for you.
>
> Ian
>
> On Thu, May 23, 2019 at 6:16 PM Jd D > 
> wrote:
>
>> Hi,
>> I am using PHP7 and was using the previous version of template, I just 
>> missed that this version is now using php mb functions, so the following 
>> two commands fixed this for me.
>>
>> sudo apt-get install php7.0-mbstring
>> sudo systemctl restart apache2.service
>>
>> Also metobridge_lookup.php has the following include
>> include('w34stats.php');
>> but only file I see in the install package is w34stats.php.tmpl in the 
>> skins directory and the apache log has lots of undefineds.
>>
>> Thanks Jerry
>>
>> On Wednesday, May 22, 2019 at 11:30:16 PM UTC-7, steeple ian wrote:
>>>
>>> Hi, 
>>> It looks like your PHP installation is missing some modules. Please look 
>>> at the important information regarding installing PHP in the installation 
>>> guide. 
>>>
>>> I also recommend that you upgrade to PHP7 or later. 
>>>
>>> Ian 
>>>
>>> Sent from my iPad 
>>>
>>> > On 23 May 2019, at 02:35, Jd D  wrote: 
>>> > 
>>> > PHP Fatal error:  Uncaught Error: Call to undefined function 
>>> mb_internal_encoding() in /var/www/html/pws_new/common.php:5\nStack 
>>> trace:\n#0 /var/www/html/pws_new/index.php(59): include_once()\n#1 {main}\n 
>>>  thrown in /var/www/html/pws_new/common.php on line 5 
>>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/fc6d7fc0-163e-46fa-b695-ade13f743f46%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/438b634b-39b6-43f7-b424-963c022c2b7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] NWS Forecast not reading icons in icon folder

2019-05-23 Thread Chris P




Hello, 

 How do you allow access to a folder that's on a secured webserver?  My 
website is working just fine, and the forecast module is working, but its 
not getting the images from the icon folder.  I would assume it has 
something to do with it not having access as noted below.  the icons are on 
my html root server, so I know the icons were copied over during the 
running of weewx. 




[image: Capture.JPG]

[image: Capture.JPG]

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f7226020-b94a-493b-941a-2fcba576bf7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Missing Midnight database update

Hi,
So just to close this off, it looks like the LaCrosse ws2316 has a "out of 
service" time that starts 30 seconds before midnight and continues for 60 
seconds after midnight where it does not respond to any input requests. 
Probably doing some house keeping. So there are no loop packets during this 
time.  Now I know.
Thanks
Jerry

On Sunday, May 19, 2019 at 1:40:58 PM UTC-7, Jd D wrote:
>
> Hi,
>
> station LaCrosse  ws2316
> weewx version 3.8.2
> hardware Raspberry Pi 
> NAME="Raspbian GNU/Linux"
> VERSION_ID="9"
> VERSION="9 (stretch)"
>
> I have noticed that the midnight updates to the database do not happen.  
> My cron entries is 0,5,10,15,20,25,30,35,40,45,50,55,59.  I added the 59 
> entry otherwise my report data stopped at 23:54 now I get report data at 
> 23:59. My station update interval is set for 1 minute which is supported by 
> the wx2316. Not a big deal but wanted to report this in case there is a fix 
> otherwise I will dig into the code myself and see what I can find. Not sure 
> if this is a software problem in weewx or the station itself.
>
> Here are the database timestamps. There is a jump of a 120 seconds instead 
> of 60 seconds. This is the only time in the day that jumps 120 seconds.
> "1558249380"
> *"1558249320"*
> *"1558249200"*
> "1558249140"
>
> Here is a snippet of the log. There is no record created at midnight.
>
> May 18 23:58:17 localhost weewx[1076]: reportengine: Report RSYNC skipped 
> due to report_timing setting
> *May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
> 23:59:00 MST (1558249140) to database 'weewx.sdb'*
> *May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
> 23:59:00 MST (1558249140) to daily summary in 'weewx.sdb'*
> May 18 23:59:25 localhost weewx[1076]: reportengine: Running reports for 
> latest time in the database.
> May 18 23:59:25 localhost weewx[1076]: reportengine: Running report 
> StandardReport
> May 18 23:59:25 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Standard/skin.conf for report StandardReport
> May 18 23:59:25 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> May 18 23:59:25 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:55 localhost weewx[1076]: cheetahgenerator: Generated 18 
> files for report StandardReport in 30.14 seconds
> May 18 23:59:55 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:56 localhost weewx[1076]: imagegenerator: Generated 12 images 
> for StandardReport in 1.39 seconds
> May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
> /var/www/html/weewx
> May 18 23:59:56 localhost weewx[1076]: reportengine: Running report 
> SteelSeries
> May 18 23:59:56 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/ss/skin.conf for report SteelSeries
> May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
> /var/www/html/weewx/ss
> May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: Generated 2 files 
> for report SteelSeries in 0.18 seconds
> May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:58 localhost weewx[1076]: imagegenerator: Generated 11 images 
> for SteelSeries in 1.72 seconds
> May 18 23:59:58 localhost weewx[1076]: reportengine: Running report FTP
> May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Ftp/skin.conf for report FTP
> May 18 23:59:58 localhost weewx[1076]: ftpgenerator: FTP upload not 
> requested. Skipped.
> May 18 23:59:58 localhost weewx[1076]: reportengine: Running report RSYNC
> May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
> May 18 23:59:58 localhost weewx[1076]: rsyncgenerator: rsync upload not 
> requested. Skipped.
> May 19 00:00:01 localhost CRON[25282]: (root) CMD 
> (/usr/local/HomeSeer/register_with_find.sh)
> *May 19 00:01:20 localhost weewx[1076]: manager: Added record 2019-05-19 
> 00:00:00 MST (1558249200) to database 'weewx.sdb'*
> *May 19 00:01:20 localhost weewx[1076]: manager: Added record 2019-05-19 
> 00:00:00 MST (1558249200) to daily summary in 'weewx.sdb'*
> May 19 00:01:21 localhost weewx[1076]: reportengine: Running reports for 
> latest time in the database.
> May 19 00:01:21 localhost weewx[1076]:

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

Yesterday when I was able to download the csv I saved a copy of it.  I put 
it up on a site hosted by me and changed the URL in wunderfixer to point 
there instead.  Now it parses it and starts the backfill.  Still isn't 
showing up on their side though.  I'm going to run it about 10 times over 
the next few hours and see what happens.  Could be that Akamai is blocking 
the backfill.  Or they have totally jacked up their backend.
On Thursday, May 23, 2019 at 10:10:28 AM UTC-6, Leon Shaner wrote:

Yeah, I have found that it is normal for WU to lazily process re-uploaded 
> records, and it seems as if they drop them...as if some backend process is 
> dying.
>
> I found through trial and error that after a weewx "outage" I need to 
> re-upload exactly 10 times, but not back to back.  I do one upload every 20 
> minutes, which means spreading the 10 re-uploads out over a 200 minute 
> period.
> After that wunderfixer reports no missing records.
> Well, at least it used to work before all these 404's and 503's.  :-(
>

-- 
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/dbe70c45-d4dd-4718-b5af-c9b5c1a7de34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

I haven't seen a 403 since you changed the user agent.

On Thursday, May 23, 2019 at 10:10:28 AM UTC-6, Leon Shaner wrote:
>
> Jarom,
>
> So you got 503's with my updated code, but not 403's?
>

-- 
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/c9122812-155c-465a-a003-e45d9dff623b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

I haven't seen a 403 since you changed the user agent.

On Thursday, May 23, 2019 at 10:10:28 AM UTC-6, Leon Shaner wrote:
>
> Jarom,
>
> So you got 503's with my updated code, but not 403's?
>
> Yeah, I have found that it is normal for WU to lazily process re-uploaded 
> records, and it seems as if they drop them...as if some backend process is 
> dying.
>
> I found through trial and error that after a weewx "outage" I need to 
> re-upload exactly 10 times, but not back to back.  I do one upload every 20 
> minutes, which means spreading the 10 re-uploads out over a 200 minute 
> period.
> After that wunderfixer reports no missing records.
> Well, at least it used to work before all these 404's and 503's.  :-(
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 23, 2019, at 11:06 AM, Jarom Hatch > 
> wrote:
>
> Those 503's are coming from Akamai.  When I have used Akamai in the past 
> those errors are because the origin is not responding correctly.
>
> Related sorta, when I took out the code to pull the timestamps and just 
> force-ran all my records as a big backfill I got success messages back 
> however none of the records actually made their way in.
>
> On Thursday, May 23, 2019 at 8:27:37 AM UTC-6, Leon Shaner wrote:
>>
>> Jarom,
>>
>> Thanks so much!  I see what I did wrong and I was able to make a stubbed 
>> down version for basic testing to prove it's at least trying to connect.
>>
>> Same location (for WeeWX 3.9.1):
>>
>>
>> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>>
>> The thing is, I'm still constantly getting 404 (Not Found) even with 
>> CURL, and just a bit ago the site started throwing 503 (Service Not 
>> Available).
>> So...  It's kinda hard to test under these conditions.   But as long as 
>> you don't get a 403, then at least my User-Agent "hack" will be "proven."   
>> :-/
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 23, 2019, at 1:57 AM, Jarom Hatch  wrote:
>>
>> I tried the 3.9.1 version and I get Could not get Weather Underground 
>> data. Exiting.
>>
>> Curl still works, even for yesterday's data.  Tracing the script it 
>> doesn't appear to be actually attempting the download.  
>>
>>
>> On Wednesday, May 22, 2019 at 7:03:49 PM UTC-6, Leon Shaner wrote:
>>>
>>> Say, we need a tester who is still on 3.9.1 or there abouts to try this 
>>> out:
>>>
>>>
>>> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>>>
>>> Can't do anything to workaround WU's sporadic 404 and 503 errors, but at 
>>> least the 403 error should be gone.
>>>
>>> I was able to test the 4.0 / development version myself on both Python2 
>>> and 3, so hopefully Tom will merge that soon.  It's over here if you are 
>>> impatient.  =D
>>>
>>>
>>> https://raw.githubusercontent.com/UberEclectic/weewx/development/bin/wunderfixer
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On May 22, 2019, at 7:24 PM, Leon Shaner  wrote:
>>>
>>> Hey WeeWX'ers!!!  =D
>>>
>>> I have a fix in the hopper.
>>>
>>> There's nothing that can be done for the occasional HTTP 404, or even 
>>> 503's I am now seeing, but the HTTP 403 was due to a change on WU's part 
>>> where they are rejecting certain HTTP User-Agent strings.  The fact that 
>>> they are putting Akamai in the middle is almost certainly a great thing re: 
>>> their scalability issues; however, they probably inherited some default 
>>> settings that filter "bots" and malware and such, which is likely why the 
>>> HTTP User-Agent now matters.
>>>
>>> I have set the User-Agent to "CURL" and it works.
>>> I have set it to "Mozilla" and it works.  I'm going with that one, since 
>>> it means Mosaic Killer, both of which were among the the very first 
>>> User-Agents I ever worked with, circa 1993 back before there was such as 
>>> thing as Netscape.  =D
>>>
>>> /ye-olde-farte mode off  ;-)
>>>
>>> My testing has so far been under Python3, but coincidentally (and not a 
>>> causation), WU started throwing HTTP 503's around the time that I tried 
>>> validating my code also under Python2.
>>>
>>> Everything is working against today's date.
>>> It's when I go after yesterday's date that I get the HTTP server error 
>>> 503.
>>>
>>> I expect the 404's and 503's to go away eventually, but at least for now 
>>> I have a fix for the 403 (forbidden)'s, just based on the User-Agent string.
>>>
>>> I'll submit a change for wunderfixer both to the 3.9.x "master" and 
>>> 4.0.x "development" branches in a moment and reply back with direct links 
>>> for anyone who wants a fix sooner.  =D
>>>
>>> Isn't this fun?  =D
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On May 22, 2019, at 4:20 PM, Leon Shaner  wrote:
>>>
>>> I'm still working on this.
>>> CURL is telling me they are not only using https, but also TLSv1.2.
>>> Here is a transcript, in case one of y'all beats me

[weewx-user] Re: Weewx und Renkforce WH2315

Hast du das mal so gemacht wie in dem Link beschreiben..

Am Donnerstag, 23. Mai 2019 19:08:36 UTC+2 schrieb Günther Wrana:
>
> Ich schaffe es nicht einmal den Treiber zu installieren.
>
> pi@raspberrypi:~/Downloads $ dir
> weewx-3.9.1  weewx-3.9.1.tar.gz  weewx-wh23xx-master  weewx-wh23xx.zip
> pi@raspberrypi:~/Downloads $ sudo wee_extension --install weewx-wh23xx.zip
> sudo: wee_extension: Befehl nicht gefunden
> pi@raspberrypi:~/Downloads $ 
>
>
>
>
>
>
>
>
> Am Donnerstag, 23. Mai 2019 02:49:34 UTC+2 schrieb mwall:
>>
>>
>>
>> On Wednesday, May 22, 2019 at 2:43:09 PM UTC-4, Günther Wrana wrote:
>>>
>>>
>>> Aber auf dem Raspberry konnte ich den Treiber nicht installieren und das 
>>> mit dem
>>>
>>> sudo wee_config --reconfigure
>>>
>>>
>>> funktioniert auch nicht.
>>>
>>> Ist da ein anderer Syntax?
>>>
>>
>> difficult to diagnose without knowing how you installed weewx on the pi 
>> and what response you see when you type the wee_config command.
>>
>> if you installed using setup.py then you will need to full path to 
>> wee_config
>>
>> m
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ce4a5e3e-3e7a-4caf-87c6-6fafc7144720%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx und Renkforce WH2315

Hier haste noch einige Links

https://www.rothlive.de/de/article/raspberry-pi-weewx-installieren-wetterstation-datenlogger-software-wettersoftware

https://www.rothlive.de/de/article/weewx-installieren-neue-installationsmethode-paketmanager

Am Donnerstag, 23. Mai 2019 19:24:10 UTC+2 schrieb Kalli:
>
> Hast du das mal so gemacht wie in dem Link beschreiben..
>
> Am Donnerstag, 23. Mai 2019 19:08:36 UTC+2 schrieb Günther Wrana:
>>
>> Ich schaffe es nicht einmal den Treiber zu installieren.
>>
>> pi@raspberrypi:~/Downloads $ dir
>> weewx-3.9.1  weewx-3.9.1.tar.gz  weewx-wh23xx-master  weewx-wh23xx.zip
>> pi@raspberrypi:~/Downloads $ sudo wee_extension --install weewx-wh23xx.zip
>> sudo: wee_extension: Befehl nicht gefunden
>> pi@raspberrypi:~/Downloads $ 
>>
>>
>>
>>
>>
>>
>>
>>
>> Am Donnerstag, 23. Mai 2019 02:49:34 UTC+2 schrieb mwall:
>>>
>>>
>>>
>>> On Wednesday, May 22, 2019 at 2:43:09 PM UTC-4, Günther Wrana wrote:


 Aber auf dem Raspberry konnte ich den Treiber nicht installieren und 
 das mit dem

 sudo wee_config --reconfigure


 funktioniert auch nicht.

 Ist da ein anderer Syntax?

>>>
>>> difficult to diagnose without knowing how you installed weewx on the pi 
>>> and what response you see when you type the wee_config command.
>>>
>>> if you installed using setup.py then you will need to full path to 
>>> wee_config
>>>
>>> m
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7a975697-503d-4e6d-bbaf-73e95afc95e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

2019-05-23 Thread steeple ian

Hi Jerry,

I am glad my first instinct was correct.

The w34stats.php.tmpl file should be generating the w34stats.php file at
every archive interval. You to make sure you have the correct path settings
in the w34skin skin.conf file.

I hope that fixes it for you.

Ian

On Thu, May 23, 2019 at 6:16 PM Jd D  wrote:

> Hi,
> I am using PHP7 and was using the previous version of template, I just
> missed that this version is now using php mb functions, so the following
> two commands fixed this for me.
>
> sudo apt-get install php7.0-mbstring
> sudo systemctl restart apache2.service
>
> Also metobridge_lookup.php has the following include
> include('w34stats.php');
> but only file I see in the install package is w34stats.php.tmpl in the
> skins directory and the apache log has lots of undefineds.
>
> Thanks Jerry
>
> On Wednesday, May 22, 2019 at 11:30:16 PM UTC-7, steeple ian wrote:
>>
>> Hi,
>> It looks like your PHP installation is missing some modules. Please look
>> at the important information regarding installing PHP in the installation
>> guide.
>>
>> I also recommend that you upgrade to PHP7 or later.
>>
>> Ian
>>
>> Sent from my iPad
>>
>> > On 23 May 2019, at 02:35, Jd D  wrote:
>> >
>> > PHP Fatal error:  Uncaught Error: Call to undefined function
>> mb_internal_encoding() in /var/www/html/pws_new/common.php:5\nStack
>> trace:\n#0 /var/www/html/pws_new/index.php(59): include_once()\n#1 {main}\n
>>  thrown in /var/www/html/pws_new/common.php on line 5
>>
> --
> 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/fc6d7fc0-163e-46fa-b695-ade13f743f46%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaQk%2B1LhvdDno8KYP_qcw6nyoHxC2ZRWAKEOn4AkaHQ5JA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx und Renkforce WH2315

Hast du das mal so gemacht wie in dem Link beschreiben..

Am Donnerstag, 23. Mai 2019 19:08:36 UTC+2 schrieb Günther Wrana:
>
> Ich schaffe es nicht einmal den Treiber zu installieren.
>
> pi@raspberrypi:~/Downloads $ dir
> weewx-3.9.1  weewx-3.9.1.tar.gz  weewx-wh23xx-master  weewx-wh23xx.zip
> pi@raspberrypi:~/Downloads $ sudo wee_extension --install weewx-wh23xx.zip
> sudo: wee_extension: Befehl nicht gefunden
> pi@raspberrypi:~/Downloads $ 
>
>
>
>
>
>
>
>
> Am Donnerstag, 23. Mai 2019 02:49:34 UTC+2 schrieb mwall:
>>
>>
>>
>> On Wednesday, May 22, 2019 at 2:43:09 PM UTC-4, Günther Wrana wrote:
>>>
>>>
>>> Aber auf dem Raspberry konnte ich den Treiber nicht installieren und das 
>>> mit dem
>>>
>>> sudo wee_config --reconfigure
>>>
>>>
>>> funktioniert auch nicht.
>>>
>>> Ist da ein anderer Syntax?
>>>
>>
>> difficult to diagnose without knowing how you installed weewx on the pi 
>> and what response you see when you type the wee_config command.
>>
>> if you installed using setup.py then you will need to full path to 
>> wee_config
>>
>> m
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/da3a53ba-1400-4878-953d-50827b246ae5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

Hi,
I am using PHP7 and was using the previous version of template, I just 
missed that this version is now using php mb functions, so the following 
two commands fixed this for me.

sudo apt-get install php7.0-mbstring
sudo systemctl restart apache2.service

Also metobridge_lookup.php has the following include
include('w34stats.php');
but only file I see in the install package is w34stats.php.tmpl in the 
skins directory and the apache log has lots of undefineds.

Thanks Jerry

On Wednesday, May 22, 2019 at 11:30:16 PM UTC-7, steeple ian wrote:
>
> Hi, 
> It looks like your PHP installation is missing some modules. Please look 
> at the important information regarding installing PHP in the installation 
> guide. 
>
> I also recommend that you upgrade to PHP7 or later. 
>
> Ian 
>
> Sent from my iPad 
>
> > On 23 May 2019, at 02:35, Jd D > 
> wrote: 
> > 
> > PHP Fatal error:  Uncaught Error: Call to undefined function 
> mb_internal_encoding() in /var/www/html/pws_new/common.php:5\nStack 
> trace:\n#0 /var/www/html/pws_new/index.php(59): include_once()\n#1 {main}\n 
>  thrown in /var/www/html/pws_new/common.php on line 5 
>

-- 
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/fc6d7fc0-163e-46fa-b695-ade13f743f46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx und Renkforce WH2315

2019-05-23 Thread Günther Wrana

Ich schaffe es nicht einmal den Treiber zu installieren.

pi@raspberrypi:~/Downloads $ dir
weewx-3.9.1  weewx-3.9.1.tar.gz  weewx-wh23xx-master  weewx-wh23xx.zip
pi@raspberrypi:~/Downloads $ sudo wee_extension --install weewx-wh23xx.zip
sudo: wee_extension: Befehl nicht gefunden
pi@raspberrypi:~/Downloads $ 








Am Donnerstag, 23. Mai 2019 02:49:34 UTC+2 schrieb mwall:
>
>
>
> On Wednesday, May 22, 2019 at 2:43:09 PM UTC-4, Günther Wrana wrote:
>>
>>
>> Aber auf dem Raspberry konnte ich den Treiber nicht installieren und das 
>> mit dem
>>
>> sudo wee_config --reconfigure
>>
>>
>> funktioniert auch nicht.
>>
>> Ist da ein anderer Syntax?
>>
>
> difficult to diagnose without knowing how you installed weewx on the pi 
> and what response you see when you type the wee_config command.
>
> if you installed using setup.py then you will need to full path to 
> wee_config
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dbe29abb-81a1-4618-819c-b33201c03822%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

2019-05-23 Thread Leon Shaner

Jarom,

So you got 503's with my updated code, but not 403's?

Yeah, I have found that it is normal for WU to lazily process re-uploaded 
records, and it seems as if they drop them...as if some backend process is 
dying.

I found through trial and error that after a weewx "outage" I need to re-upload 
exactly 10 times, but not back to back.  I do one upload every 20 minutes, 
which means spreading the 10 re-uploads out over a 200 minute period.
After that wunderfixer reports no missing records.
Well, at least it used to work before all these 404's and 503's.  :-(

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 23, 2019, at 11:06 AM, Jarom Hatch  wrote:
> 
> Those 503's are coming from Akamai.  When I have used Akamai in the past 
> those errors are because the origin is not responding correctly.
> 
> Related sorta, when I took out the code to pull the timestamps and just 
> force-ran all my records as a big backfill I got success messages back 
> however none of the records actually made their way in.
> 
>> On Thursday, May 23, 2019 at 8:27:37 AM UTC-6, Leon Shaner wrote:
>> Jarom,
>> 
>> Thanks so much!  I see what I did wrong and I was able to make a stubbed 
>> down version for basic testing to prove it's at least trying to connect.
>> 
>> Same location (for WeeWX 3.9.1):
>> 
>> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>> 
>> The thing is, I'm still constantly getting 404 (Not Found) even with CURL, 
>> and just a bit ago the site started throwing 503 (Service Not Available).
>> So...  It's kinda hard to test under these conditions.   But as long as you 
>> don't get a 403, then at least my User-Agent "hack" will be "proven."   :-/
>> 
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>> 
>>> On May 23, 2019, at 1:57 AM, Jarom Hatch  wrote:
>>> 
>>> I tried the 3.9.1 version and I get Could not get Weather Underground data. 
>>> Exiting.
>>> 
>>> Curl still works, even for yesterday's data.  Tracing the script it doesn't 
>>> appear to be actually attempting the download.  
>>> 
>>> 
 On Wednesday, May 22, 2019 at 7:03:49 PM UTC-6, Leon Shaner wrote:
 Say, we need a tester who is still on 3.9.1 or there abouts to try this 
 out:
 
 https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
 
 Can't do anything to workaround WU's sporadic 404 and 503 errors, but at 
 least the 403 error should be gone.
 
 I was able to test the 4.0 / development version myself on both Python2 
 and 3, so hopefully Tom will merge that soon.  It's over here if you are 
 impatient.  =D
 
 https://raw.githubusercontent.com/UberEclectic/weewx/development/bin/wunderfixer
 
 Regards,
 \Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPad Pro)
 
> On May 22, 2019, at 7:24 PM, Leon Shaner  wrote:
> 
> Hey WeeWX'ers!!!  =D
> 
> I have a fix in the hopper.
> 
> There's nothing that can be done for the occasional HTTP 404, or even 
> 503's I am now seeing, but the HTTP 403 was due to a change on WU's part 
> where they are rejecting certain HTTP User-Agent strings.  The fact that 
> they are putting Akamai in the middle is almost certainly a great thing 
> re: their scalability issues; however, they probably inherited some 
> default settings that filter "bots" and malware and such, which is likely 
> why the HTTP User-Agent now matters.
> 
> I have set the User-Agent to "CURL" and it works.
> I have set it to "Mozilla" and it works.  I'm going with that one, since 
> it means Mosaic Killer, both of which were among the the very first 
> User-Agents I ever worked with, circa 1993 back before there was such as 
> thing as Netscape.  =D
> 
> /ye-olde-farte mode off  ;-)
> 
> My testing has so far been under Python3, but coincidentally (and not a 
> causation), WU started throwing HTTP 503's around the time that I tried 
> validating my code also under Python2.
> 
> Everything is working against today's date.
> It's when I go after yesterday's date that I get the HTTP server error 
> 503.
> 
> I expect the 404's and 503's to go away eventually, but at least for now 
> I have a fix for the 403 (forbidden)'s, just based on the User-Agent 
> string.
> 
> I'll submit a change for wunderfixer both to the 3.9.x "master" and 4.0.x 
> "development" branches in a moment and reply back with direct links for 
> anyone who wants a fix sooner.  =D
> 
> Isn't this fun?  =D
> 
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
> 
>> On May 22, 2019, at 4:20 PM, Leon Shaner  wrote:
>> 
>> I'm still working on this.
>> CURL is telling me they are not only using https, but also TLSv1.2.
>> Here is a transcript, in case one of y'all beats me to the fix.  =D

[weewx-user] Re: New to weewx need some help

2019-05-23 Thread Joe Santas

Finally sorted this.  
Thanking you both Gábor and Gary for your assistance with this and spending 
time trying to resolve this.
Believe it or not it was something simple in my config.  
After some more reading re the interceptor driver i figured out what was 
going on.
I had my config set to wu-client.  When i changed it to observer everything 
just fell into place.
Looks like my data is getting to the sites i have signed up too and my 
weewx server as well.  
Hopefully it rains tomorrow lol and that will be pretty much it.  Thats the 
only update i am waiting on now to see if it works.
Happy days lol.

Regards

On Tuesday, May 21, 2019 at 3:05:35 AM UTC+10, Joe Santas wrote:
>
> Hi all new here after a week of messing around with this to get it 
> communicating i finally have some progress.
> Managed to setup the basics here.  http://jsantas.com:83/weewx/
> Main issue i have is the rain hourly total and rain rate and rain today.
> These just keep incrementing.
> Im using the Interceptor driver.  Copy of my config and log attached.
> If someone is able to assist to see where its falling over it would be 
> great.
>
> Running all this on a ubuntu OS and the Weather station is an ECOWITT 
> HP2551.
>
> Regards
>
>
>
>

-- 
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/b49f13b4-cbaf-42d7-bcd6-798038a7a65c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

2019-05-23 Thread vince

Your script has a lot of errors in it from a quick look-see, did you have a 
cut+paste massacre perhaps ?


   - if weewxd is not running at all, it'll blow up in your 'if' statement
   - you have braces and parens all messed up in your usage calculation line
   - do you really mean '3' and '4' for your thresholds ?  Guessing not.
   - the if/then flow doesn't make any sense to me

Try to work this one out yourself a little more.


   - rename your 'threshold' and 'threshold2' variables to be able to 
   understand what you wrote 6 months from now (or at least comment the code a 
   bit)
   - Hard-set usage's value to a good value, walk through your logic and 
   see what it will do
   - then hard-set it to a value in between your two thresholds, walk 
   through your logic and see what it'll do
   - then hard-set it to a value over the 'need to restart' threshold, walk 
   through your logic and see what it'll do
   - then hard-set it to a non-numeric value and see if the code breaks (it 
   will)
   - then hard-set it to a null value and see if the code breaks (it will)
   - then try it live in a 'log only, take no action mode' for a bit
   - then try it live for real, taking action as needed
   
If it's me, my flow would be something like:

   - if it's bad, syslog a message (hint - use 'logger') and try to take 
   action to fix it
   - if it's semi-bad, syslog a message saying it's in the not-great middle 
   range
   - if it's ok, 'consider' logging "all is good"
   - in all cases, log the actual data so you have that in the message (ie, 
   "weewx mem usage 23.3 % (ok)" or the like)
   

But you should really do the coding and analysis here so you can 
effectively 'own' your solution long-term.




-- 
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/f7aba085-c3c5-41c0-87a6-319376e4f030%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

Those 503's are coming from Akamai.  When I have used Akamai in the past 
those errors are because the origin is not responding correctly.

Related sorta, when I took out the code to pull the timestamps and just 
force-ran all my records as a big backfill I got success messages back 
however none of the records actually made their way in.

On Thursday, May 23, 2019 at 8:27:37 AM UTC-6, Leon Shaner wrote:
>
> Jarom,
>
> Thanks so much!  I see what I did wrong and I was able to make a stubbed 
> down version for basic testing to prove it's at least trying to connect.
>
> Same location (for WeeWX 3.9.1):
>
> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>
> The thing is, I'm still constantly getting 404 (Not Found) even with CURL, 
> and just a bit ago the site started throwing 503 (Service Not Available).
> So...  It's kinda hard to test under these conditions.   But as long as 
> you don't get a 403, then at least my User-Agent "hack" will be "proven."   
> :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 23, 2019, at 1:57 AM, Jarom Hatch > 
> wrote:
>
> I tried the 3.9.1 version and I get Could not get Weather Underground 
> data. Exiting.
>
> Curl still works, even for yesterday's data.  Tracing the script it 
> doesn't appear to be actually attempting the download.  
>
>
> On Wednesday, May 22, 2019 at 7:03:49 PM UTC-6, Leon Shaner wrote:
>>
>> Say, we need a tester who is still on 3.9.1 or there abouts to try this 
>> out:
>>
>>
>> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>>
>> Can't do anything to workaround WU's sporadic 404 and 503 errors, but at 
>> least the 403 error should be gone.
>>
>> I was able to test the 4.0 / development version myself on both Python2 
>> and 3, so hopefully Tom will merge that soon.  It's over here if you are 
>> impatient.  =D
>>
>>
>> https://raw.githubusercontent.com/UberEclectic/weewx/development/bin/wunderfixer
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 22, 2019, at 7:24 PM, Leon Shaner  wrote:
>>
>> Hey WeeWX'ers!!!  =D
>>
>> I have a fix in the hopper.
>>
>> There's nothing that can be done for the occasional HTTP 404, or even 
>> 503's I am now seeing, but the HTTP 403 was due to a change on WU's part 
>> where they are rejecting certain HTTP User-Agent strings.  The fact that 
>> they are putting Akamai in the middle is almost certainly a great thing re: 
>> their scalability issues; however, they probably inherited some default 
>> settings that filter "bots" and malware and such, which is likely why the 
>> HTTP User-Agent now matters.
>>
>> I have set the User-Agent to "CURL" and it works.
>> I have set it to "Mozilla" and it works.  I'm going with that one, since 
>> it means Mosaic Killer, both of which were among the the very first 
>> User-Agents I ever worked with, circa 1993 back before there was such as 
>> thing as Netscape.  =D
>>
>> /ye-olde-farte mode off  ;-)
>>
>> My testing has so far been under Python3, but coincidentally (and not a 
>> causation), WU started throwing HTTP 503's around the time that I tried 
>> validating my code also under Python2.
>>
>> Everything is working against today's date.
>> It's when I go after yesterday's date that I get the HTTP server error 
>> 503.
>>
>> I expect the 404's and 503's to go away eventually, but at least for now 
>> I have a fix for the 403 (forbidden)'s, just based on the User-Agent string.
>>
>> I'll submit a change for wunderfixer both to the 3.9.x "master" and 4.0.x 
>> "development" branches in a moment and reply back with direct links for 
>> anyone who wants a fix sooner.  =D
>>
>> Isn't this fun?  =D
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 22, 2019, at 4:20 PM, Leon Shaner  wrote:
>>
>> I'm still working on this.
>> CURL is telling me they are not only using https, but also TLSv1.2.
>> Here is a transcript, in case one of y'all beats me to the fix.  =D
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/DA01E425-B99A-4959-8FB2-B564A61B3E77%40isylum.org
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> 
>>
>>
>>
>>
>> Working from here:
>> https://docs.python.org/2/library/ssl.html
>>
>> So far I have tried this, to no avail.
>> Really just doing the "import ssl" and using https in the URL, and adding 
>> context=ssl_context to the urllib.request.
>>
>> A snippet of that looks as follows, but still getting 403 forbidden.  :-(
>>
>> # For new WU interface which uses SSL and

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

Sad, now I'm getting the 503.  I'll keep trying.

On Thursday, May 23, 2019 at 8:27:37 AM UTC-6, Leon Shaner wrote:
>
> Jarom,
>
> Thanks so much!  I see what I did wrong and I was able to make a stubbed 
> down version for basic testing to prove it's at least trying to connect.
>
> Same location (for WeeWX 3.9.1):
>
> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>
> The thing is, I'm still constantly getting 404 (Not Found) even with CURL, 
> and just a bit ago the site started throwing 503 (Service Not Available).
> So...  It's kinda hard to test under these conditions.   But as long as 
> you don't get a 403, then at least my User-Agent "hack" will be "proven."   
> :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 23, 2019, at 1:57 AM, Jarom Hatch > 
> wrote:
>
> I tried the 3.9.1 version and I get Could not get Weather Underground 
> data. Exiting.
>
> Curl still works, even for yesterday's data.  Tracing the script it 
> doesn't appear to be actually attempting the download.  
>
>
> On Wednesday, May 22, 2019 at 7:03:49 PM UTC-6, Leon Shaner wrote:
>>
>> Say, we need a tester who is still on 3.9.1 or there abouts to try this 
>> out:
>>
>>
>> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>>
>> Can't do anything to workaround WU's sporadic 404 and 503 errors, but at 
>> least the 403 error should be gone.
>>
>> I was able to test the 4.0 / development version myself on both Python2 
>> and 3, so hopefully Tom will merge that soon.  It's over here if you are 
>> impatient.  =D
>>
>>
>> https://raw.githubusercontent.com/UberEclectic/weewx/development/bin/wunderfixer
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 22, 2019, at 7:24 PM, Leon Shaner  wrote:
>>
>> Hey WeeWX'ers!!!  =D
>>
>> I have a fix in the hopper.
>>
>> There's nothing that can be done for the occasional HTTP 404, or even 
>> 503's I am now seeing, but the HTTP 403 was due to a change on WU's part 
>> where they are rejecting certain HTTP User-Agent strings.  The fact that 
>> they are putting Akamai in the middle is almost certainly a great thing re: 
>> their scalability issues; however, they probably inherited some default 
>> settings that filter "bots" and malware and such, which is likely why the 
>> HTTP User-Agent now matters.
>>
>> I have set the User-Agent to "CURL" and it works.
>> I have set it to "Mozilla" and it works.  I'm going with that one, since 
>> it means Mosaic Killer, both of which were among the the very first 
>> User-Agents I ever worked with, circa 1993 back before there was such as 
>> thing as Netscape.  =D
>>
>> /ye-olde-farte mode off  ;-)
>>
>> My testing has so far been under Python3, but coincidentally (and not a 
>> causation), WU started throwing HTTP 503's around the time that I tried 
>> validating my code also under Python2.
>>
>> Everything is working against today's date.
>> It's when I go after yesterday's date that I get the HTTP server error 
>> 503.
>>
>> I expect the 404's and 503's to go away eventually, but at least for now 
>> I have a fix for the 403 (forbidden)'s, just based on the User-Agent string.
>>
>> I'll submit a change for wunderfixer both to the 3.9.x "master" and 4.0.x 
>> "development" branches in a moment and reply back with direct links for 
>> anyone who wants a fix sooner.  =D
>>
>> Isn't this fun?  =D
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 22, 2019, at 4:20 PM, Leon Shaner  wrote:
>>
>> I'm still working on this.
>> CURL is telling me they are not only using https, but also TLSv1.2.
>> Here is a transcript, in case one of y'all beats me to the fix.  =D
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/DA01E425-B99A-4959-8FB2-B564A61B3E77%40isylum.org
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> 
>>
>>
>>
>>
>> Working from here:
>> https://docs.python.org/2/library/ssl.html
>>
>> So far I have tried this, to no avail.
>> Really just doing the "import ssl" and using https in the URL, and adding 
>> context=ssl_context to the urllib.request.
>>
>> A snippet of that looks as follows, but still getting 403 forbidden.  :-(
>>
>> # For new WU interface which uses SSL and TLSv1.2
>> import ssl
>>
>> ...
>>
>> _url = "
>> https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=%s; \
>>"=%d=%d=%d=1" % (self.station, 
>> dayRequested_tt[1],
>>   dayRequested_tt[2], 
>>

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

2019-05-23 Thread Leon Shaner

Jarom,

Thanks so much!  I see what I did wrong and I was able to make a stubbed down 
version for basic testing to prove it's at least trying to connect.

Same location (for WeeWX 3.9.1):

https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer

The thing is, I'm still constantly getting 404 (Not Found) even with CURL, and 
just a bit ago the site started throwing 503 (Service Not Available).
So...  It's kinda hard to test under these conditions.   But as long as you 
don't get a 403, then at least my User-Agent "hack" will be "proven."   :-/

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 23, 2019, at 1:57 AM, Jarom Hatch  wrote:
> 
> I tried the 3.9.1 version and I get Could not get Weather Underground data. 
> Exiting.
> 
> Curl still works, even for yesterday's data.  Tracing the script it doesn't 
> appear to be actually attempting the download.  
> 
> 
>> On Wednesday, May 22, 2019 at 7:03:49 PM UTC-6, Leon Shaner wrote:
>> Say, we need a tester who is still on 3.9.1 or there abouts to try this out:
>> 
>> https://raw.githubusercontent.com/UberEclectic/weewx/master/bin/wunderfixer
>> 
>> Can't do anything to workaround WU's sporadic 404 and 503 errors, but at 
>> least the 403 error should be gone.
>> 
>> I was able to test the 4.0 / development version myself on both Python2 and 
>> 3, so hopefully Tom will merge that soon.  It's over here if you are 
>> impatient.  =D
>> 
>> https://raw.githubusercontent.com/UberEclectic/weewx/development/bin/wunderfixer
>> 
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>> 
>>> On May 22, 2019, at 7:24 PM, Leon Shaner  wrote:
>>> 
>>> Hey WeeWX'ers!!!  =D
>>> 
>>> I have a fix in the hopper.
>>> 
>>> There's nothing that can be done for the occasional HTTP 404, or even 503's 
>>> I am now seeing, but the HTTP 403 was due to a change on WU's part where 
>>> they are rejecting certain HTTP User-Agent strings.  The fact that they are 
>>> putting Akamai in the middle is almost certainly a great thing re: their 
>>> scalability issues; however, they probably inherited some default settings 
>>> that filter "bots" and malware and such, which is likely why the HTTP 
>>> User-Agent now matters.
>>> 
>>> I have set the User-Agent to "CURL" and it works.
>>> I have set it to "Mozilla" and it works.  I'm going with that one, since it 
>>> means Mosaic Killer, both of which were among the the very first 
>>> User-Agents I ever worked with, circa 1993 back before there was such as 
>>> thing as Netscape.  =D
>>> 
>>> /ye-olde-farte mode off  ;-)
>>> 
>>> My testing has so far been under Python3, but coincidentally (and not a 
>>> causation), WU started throwing HTTP 503's around the time that I tried 
>>> validating my code also under Python2.
>>> 
>>> Everything is working against today's date.
>>> It's when I go after yesterday's date that I get the HTTP server error 503.
>>> 
>>> I expect the 404's and 503's to go away eventually, but at least for now I 
>>> have a fix for the 403 (forbidden)'s, just based on the User-Agent string.
>>> 
>>> I'll submit a change for wunderfixer both to the 3.9.x "master" and 4.0.x 
>>> "development" branches in a moment and reply back with direct links for 
>>> anyone who wants a fix sooner.  =D
>>> 
>>> Isn't this fun?  =D
>>> 
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>> 
 On May 22, 2019, at 4:20 PM, Leon Shaner  wrote:
 
 I'm still working on this.
 CURL is telling me they are not only using https, but also TLSv1.2.
 Here is a transcript, in case one of y'all beats me to the fix.  =D
 
 -- 
 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...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/DA01E425-B99A-4959-8FB2-B564A61B3E77%40isylum.org.
 For more options, visit https://groups.google.com/d/optout.
 
 
 
 
 Working from here:
 https://docs.python.org/2/library/ssl.html
 
 So far I have tried this, to no avail.
 Really just doing the "import ssl" and using https in the URL, and adding 
 context=ssl_context to the urllib.request.
 
 A snippet of that looks as follows, but still getting 403 forbidden.  :-(
 
 # For new WU interface which uses SSL and TLSv1.2
 import ssl
 
 ...
 
 _url = 
 "https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=%s; \
"=%d=%d=%d=1" % (self.station, 
 dayRequested_tt[1],
   dayRequested_tt[2], 
 dayRequested_tt[0])
 
 # specify TLSv1.2 and SSLv2, but not SSLv3
 ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLSv1_2)

Re: [weewx-user] Re: Second crash after 11 days

Leon: thank you very much for your reply...lots of interesting things 
there. I like the top command rather than free as top would give me the % 
of memory used by weewxd. I took the command ps -C weewxd -o 
comm,size,rss,vsize,%mem (which I never saw before, thank you!) and 
shortened it to ps -C weewxd -o %mem as that is the parameter I am 
interested in tracking. I then made the following script, which has a 
problem: It does not send the email when the first "threshold" is exceeded; 
it sends an email that the second threshold is exceeded and simultaneously 
restarts weewx. Do I have something in the wrong order in the script?


---
#!/bin/bash

threshold=3
threshold2=4

usage=$(($(ps -C weewxd -o %mem |awk 'NR==2 {printf ("%.0f", $1}')))   

if [ "$usage" -gt "$threshold2" ]

then

sudo /etc/init.d/service_name restart

 if [ "$usage" -gt "$threshold" ]

 then

 echo "The memory usage has reached $usage% on $HOSTNAME." | mail -s 
"High Memory Usage Alert" someoneseamailaddress

 fi
fi
---




-- 
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/6b2ec4dd-f453-4a53-9e08-2c8d81e4508f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

Leon: thank you very much for your reply...lots of interesting things 
there. I like the top command rather than free as top would give me the % 
of memory used by weewxd. I took the command ps -C weewxd -o 
comm,size,rss,vsize,%mem (which I never saw before, thank you!) and 
shortened it to ps -C weewxd -o %mem as that is the parameter I am 
interested in tracking. I then made the following script, which has a 
problem: It does not send the email when the first "threshold" is exceeded; 
it sends an email that the second threshold is exceeded and simultaneously 
restarts weewx. Do I have something in the wrong order in the script?


---
#!/bin/bash

threshold=3
threshold2=4

usage=$(($(ps -C weewxd -o %mem |awk 'NR==2 {printf ("%.0f", $1}')))   

if [ "$usage" -gt "$threshold2" ]

then

sudo /etc/init.d/service_name restart

 if [ "$usage" -gt "$threshold" ]

 then

 echo "The memory usage has reached $usage% on $HOSTNAME." | mail -s 
"High Memory Usage Alert" userssemailaddress

 fi
fi
---




-- 
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/722fbf07-c6b1-467b-b5a3-7ef1c9f80d81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days


Leon: thank you very much for your reply...lots of interesting things 
there. I like the top command rather than free as top would show me the % 
of memory used by weewxd. I took the command ps -C weewxd -o 
comm,size,rss,vsize,%mem (which I never saw before, thank you!) and 
shortened it to ps -C weewxd -o %mem as that is the parameter I am 
interested in tracking. I then made the following script, which has a 
problem: It does not send the email when the first "threshold" is exceeded; 
it sends an email that the second threshold is exceeded and simultaneously 
restarts weewx. Do I have something in the wrong order in the script?


---
#!/bin/bash

threshold=3
threshold2=4

usage=$(($(ps -C weewxd -o %mem |awk 'NR==2 {printf ("%.0f", $1}')))   

if [ "$usage" -gt "$threshold2" ]

then

sudo /etc/init.d/service_name restart

 if [ "$usage" -gt "$threshold" ]

 then

 echo "The memory usage has reached $usage% on $HOSTNAME." | mail -s 
"High Memory Usage Alert" x...@mail.com


 fi
fi
---




-- 
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/198a5f4c-b558-4aec-abc7-b61cb2fdb46c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WU forecast API3

2019-05-23 Thread Radoslav Drdla

Trying to edit the WU forecast, I found that the original API call was in 
the form of:
http://api.wunderground.com/api/{interval} {max_age} {api_key} {location}
The new WU API3 works with this URL:
https://api.weather.com/v3/wx/forecast/daily/5day?geocode={lat,long}=json=e=en-US=
How do I edit forecast.py to create the correct URL? I suppose it will be 
lines 2540 to 2630 (approximately), but I don't know how to edit them, I'm 
not a programmer.
Will anyone find me to direct me? What I do not deal with the data yet, I 
have to be able to download them first ...

I found out that only WU has a sufficiently accurate forecast for less 
populated areas and therefore I would like to use it again.

-- 
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/2e70d29a-477d-43e6-8810-e594a189bb2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx und Renkforce WH2315

2019-05-23 Thread Günther Wrana

Hallo danke für die Tipps ich werde das heute noch testen.



Am Donnerstag, 23. Mai 2019 13:58:23 UTC+2 schrieb Kalli:
>
> Du kannst auch mal hier nach sehen und alles Abarbeiten.
>
> http://wetterstation-gellershausen.de/wiki/doku.php?id=wetter:weewx_installation
>
> Am Donnerstag, 23. Mai 2019 13:03:21 UTC+2 schrieb Kalli:
>>
>> Hallo
>> ich betreibe die Selbe Station
>>
>> schau mal in deine weewx.conf   ob das so da drinne steht.
>>
>> [WH23xx]
>> # This section is for Fine Offset WH23xx stations
>> 
>> # The model name such as Tycon, or TP2700
>> model = Tycon TP2700
>> 
>> polling_mode = PERIODIC
>> 
>> polling_interval = 60
>> 
>> 
>> # The driver to use
>> driver = user.wh23xx
>>
>>
>> Am Mittwoch, 22. Mai 2019 12:15:38 UTC+2 schrieb Günther Wrana:
>>>
>>> Hallo
>>>
>>> Ich habe diese Wetterstation Renkforce WH2315
>>>
>>> Wenn jemand weis das diese Wetterstation mit weewx auf Lununtu oder 
>>> Raspberry pi kompatibel ist da soll er mir sagen was ich falsch gemacht 
>>> habe.
>>>
>>>
>>>
>>>
>>> https://www.conrad.at/de/p/renkforce-wh2300-wh2315-funk-wetterstation-vorhersage-fuer-12-bis-24-stunden-1404262.html
>>>
>>> Das Programm weewx habe ich auf einem Laptop mit Lubuntu 16.04 und 
>>> einem raspberry pi 3 v1.2 installiert.
>>>
>>> Ob das richtig installiert ist wies ich nicht aber es lässt sich starten 
>>> und es startet.
>>>
>>> Die Wetterstation wird auch nach Eingabe von lsusb im Terminal angezeigt.
>>>
>>>
>>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ lsusb
>>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 001 Device 004: ID 10c4:8468 Cygnal Integrated Products, Inc. 
>>> Bus 001 Device 002: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 
>>> [Atheros AR9271]
>>> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ 
>>>
>>>
>>> Wenn ich dann weewx starte oder es schon gestartet ist wird folgendes 
>>> angezeigt.
>>>
>>>
>>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ sudo 
>>> /etc/init.d/weewx start
>>> [sudo] password for modelleisenbahn: 
>>>  * Starting weewx weather system weewx  
>>>  [ OK ] 
>>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ sudo tail -f 
>>> /var/log/syslog
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2447]: engine: 
>>> pid file is /var/run/weewx.pid
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: engine: 
>>> Using configuration file /etc/weewx/weewx.conf
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: engine: 
>>> Loading station type FineOffsetUSB (weewx.drivers.fousb)
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>>> driver version is 1.9
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>>> polling mode is PERIODIC
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>>> polling interval is 60
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>>> Cannot find USB device with Vendor=0x1941 ProdID=0x8021 Device=None
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: import of 
>>> driver failed: Unable to find USB device ()
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: engine: 
>>> Unable to load driver: Unable to find USB device
>>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]:   
>>> Exiting...
>>>
>>>
>>>
>>> Nun habe ich in der weewx.conf etwas eingefügt wie in einer anderen 
>>> Zeile beschrieben.
>>>
>>> weewx StdReport exits if USB disconnected
>>>
>>> # Keeping retrying!
>>>
>>> loop_on_init = 1
>>>
>>>
>>> Danach wird im Terminal alle 60 Sekunden folgendes angezeigt.
>>>
>>>
>>> Unable to load driver: Unable to find USB device
>>>
>>>
>>> Zum Abschluss ist diese Wetterstation mit weewx auslesbar oder nicht 
>>> wenn ja was habe ich bei der Installation oder beim einstellen falsch 
>>> gemacht.
>>>
>>>
>>> Grüße Günther
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  
>>>
>>

-- 
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/4824a71d-c4c3-4232-8c39-18a2c3def692%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx und Renkforce WH2315

Du kannst auch mal hier nach sehen und alles Abarbeiten.
http://wetterstation-gellershausen.de/wiki/doku.php?id=wetter:weewx_installation

Am Donnerstag, 23. Mai 2019 13:03:21 UTC+2 schrieb Kalli:
>
> Hallo
> ich betreibe die Selbe Station
>
> schau mal in deine weewx.conf   ob das so da drinne steht.
>
> [WH23xx]
> # This section is for Fine Offset WH23xx stations
> 
> # The model name such as Tycon, or TP2700
> model = Tycon TP2700
> 
> polling_mode = PERIODIC
> 
> polling_interval = 60
> 
> 
> # The driver to use
> driver = user.wh23xx
>
>
> Am Mittwoch, 22. Mai 2019 12:15:38 UTC+2 schrieb Günther Wrana:
>>
>> Hallo
>>
>> Ich habe diese Wetterstation Renkforce WH2315
>>
>> Wenn jemand weis das diese Wetterstation mit weewx auf Lununtu oder 
>> Raspberry pi kompatibel ist da soll er mir sagen was ich falsch gemacht 
>> habe.
>>
>>
>>
>>
>> https://www.conrad.at/de/p/renkforce-wh2300-wh2315-funk-wetterstation-vorhersage-fuer-12-bis-24-stunden-1404262.html
>>
>> Das Programm weewx habe ich auf einem Laptop mit Lubuntu 16.04 und 
>> einem raspberry pi 3 v1.2 installiert.
>>
>> Ob das richtig installiert ist wies ich nicht aber es lässt sich starten 
>> und es startet.
>>
>> Die Wetterstation wird auch nach Eingabe von lsusb im Terminal angezeigt.
>>
>>
>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ lsusb
>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 001 Device 004: ID 10c4:8468 Cygnal Integrated Products, Inc. 
>> Bus 001 Device 002: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 
>> [Atheros AR9271]
>> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ 
>>
>>
>> Wenn ich dann weewx starte oder es schon gestartet ist wird folgendes 
>> angezeigt.
>>
>>
>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ sudo 
>> /etc/init.d/weewx start
>> [sudo] password for modelleisenbahn: 
>>  * Starting weewx weather system weewx  
>>  [ OK ] 
>> modelleisenbahn@modelleisenbahn-LIFEBOOK-E-Series:~$ sudo tail -f 
>> /var/log/syslog
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2447]: engine: 
>> pid file is /var/run/weewx.pid
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: engine: 
>> Using configuration file /etc/weewx/weewx.conf
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: engine: 
>> Loading station type FineOffsetUSB (weewx.drivers.fousb)
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>> driver version is 1.9
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>> polling mode is PERIODIC
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>> polling interval is 60
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: fousb: 
>> Cannot find USB device with Vendor=0x1941 ProdID=0x8021 Device=None
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: import of 
>> driver failed: Unable to find USB device ()
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]: engine: 
>> Unable to load driver: Unable to find USB device
>> May  5 11:24:55 modelleisenbahn-LIFEBOOK-E-Series weewx[2451]:   
>> Exiting...
>>
>>
>>
>> Nun habe ich in der weewx.conf etwas eingefügt wie in einer anderen Zeile 
>> beschrieben.
>>
>> weewx StdReport exits if USB disconnected
>>
>> # Keeping retrying!
>>
>> loop_on_init = 1
>>
>>
>> Danach wird im Terminal alle 60 Sekunden folgendes angezeigt.
>>
>>
>> Unable to load driver: Unable to find USB device
>>
>>
>> Zum Abschluss ist diese Wetterstation mit weewx auslesbar oder nicht wenn 
>> ja was habe ich bei der Installation oder beim einstellen falsch gemacht.
>>
>>
>> Grüße Günther
>>
>>
>>
>>
>>
>>
>>
>>  
>>
>

-- 
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/d87d95c6-1258-4877-a038-c0dfe4f1a8b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx und Renkforce WH2315