[weewx-user] Re: trouble getting weewx to listen for ws-1001-wifi

[Bill Volz]

Seems to have fixed itself. I guess time heals all wounds?

But now getting this message:
Aug 28 00:44:40 raspberrypi weewx[4022]: interceptor: MainThread: 
unrecognized parameter absbaromin=26.82


On Sunday, August 27, 2017 at 10:21:54 PM UTC-4, mwall wrote:
>
> On Sunday, August 27, 2017 at 10:01:28 PM UTC-4, Bill Volz wrote:
>>
>> I'm having trouble getting the weewx to listen for the incoming info from 
>> a ws-1001-wifi. Here's what in syslog:
>>
>> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is 
>> listen
>> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is 
>> listen
>> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen 
>> on 192.168.0.196:8081
>> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen 
>> on 192.168.0.196:8081
>> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 
>> 99] Cannot assign requested address ()
>> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 
>> 99] Cannot assign requested address ()
>> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: 
>> [Errno 99] Cannot assign requested address
>> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: 
>> [Errno 99] Cannot assign requested address
>> Aug 27 21:43:26 raspberrypi weewx[2809]:   Exiting...
>> Aug 27 21:43:26 raspberrypi weewx[2809]:   Exiting...
>>
>>
> has the network been initialized by the time that weewx starts?  
>
> syslog will tell you
>
> you can also test: for example, does weewx work when you start it 
> manually, but not when started by the system at system startup?
>
> m
>
>

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

[weewx-user] Re: trouble getting weewx to listen for ws-1001-wifi

[mwall]

On Sunday, August 27, 2017 at 10:01:28 PM UTC-4, Bill Volz wrote:
>
> I'm having trouble getting the weewx to listen for the incoming info from 
> a ws-1001-wifi. Here's what in syslog:
>
> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is 
> listen
> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is 
> listen
> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen 
> on 192.168.0.196:8081
> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen 
> on 192.168.0.196:8081
> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 
> 99] Cannot assign requested address ()
> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 
> 99] Cannot assign requested address ()
> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: 
> [Errno 99] Cannot assign requested address
> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: 
> [Errno 99] Cannot assign requested address
> Aug 27 21:43:26 raspberrypi weewx[2809]:   Exiting...
> Aug 27 21:43:26 raspberrypi weewx[2809]:   Exiting...
>
>
has the network been initialized by the time that weewx starts?  

syslog will tell you

you can also test: for example, does weewx work when you start it manually, 
but not when started by the system at system startup?

m

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

[weewx-user] trouble getting weewx to listen for ws-1001-wifi

[Bill Volz]

I'm having trouble getting the weewx to listen for the incoming info from a 
ws-1001-wifi. Here's what in syslog:

Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is 
listen
Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is 
listen
Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen on 
192.168.0.196:8081
Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen on 
192.168.0.196:8081
Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 
99] Cannot assign requested address ()
Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 
99] Cannot assign requested address ()
Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: 
[Errno 99] Cannot assign requested address
Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: 
[Errno 99] Cannot assign requested address
Aug 27 21:43:26 raspberrypi weewx[2809]:   Exiting...
Aug 27 21:43:26 raspberrypi weewx[2809]:   Exiting...

Not sure why everything is repeated but that's the least of the issues.

I;d rather not specify the ip address to listen on since the ws-1001 uses 
DHCP and the address might change. I set a port to one that's not being 
used and should be able to listen for anything on that port.

Here's the weewx.conf 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.7.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Black Mountain, NC"

# Latitude and longitude in decimal degrees
latitude = 35.6671
longitude = -82.36

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

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

# 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

##

[Simulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for 
testing).
#mode = generator

# The start time. If not specified, the default is to use the present 
time.
#start = 2011-01-01 00:00

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

##

#   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.
enable = false
username = replace_me
# To guard against parsing errors, put your password in quotes:
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.
enable = false
station = replace_me
# To guard 

[weewx-user] Re: catching up on Weather Underground after internet outage

[Craig Thom]

Well, never mind.  It was showing data for yesterday, but now there's a 
gap.  So I guess it doesn't automatically update, and I should run 
wunderfixer.

On Sunday, August 27, 2017 at 12:35:42 PM UTC-4, Craig Thom wrote:
>
> It works.  I didn't even know this was a feature.  The only reference I 
> can find to it in the documentation is the "stale" setting for CWOP to 
> prevent catching up, since CWOP apparently only handles real time data.
>
> My internet service at home was down for a few hours yesterday, and today 
> I discovered that Weather Underground wasn't missing any data.  CWOP is, 
> and WOW is, but WU isn't, and it gave me my gold star back.
>
> I looked at the log at the default level, and I can see where the uploads 
> failed and when they started again, but there's no reference to catching up.
>
> I think this automatic catch up for Weather Underground is worth 
> mentioning as a feature in the documentation.  Or, if it's there, maybe a 
> mention in a more obvious place.  It's a selling point, especially to users 
> of Acurite sensors, who are accustomed to WU being their only archive.  We 
> weewx users have our own databases, so Weather Underground isn't as 
> important, but it's still a nice feature.
>

-- 
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] Ambient 2095 (FOUSB) weewx not updating (KPAYORK45)

[Ralph Brandt]

With this situation configuration I get some instances where it looks like 
the station has gone off line see 8/23/2017 for an example.  At this point 
I am pretty sure it is one of two things, I would be interested in the 
experience of others.

My first thought it was the high humidity, you will see that the temp and 
dew point converge before the outage and diverge after.  Ambient tells me 
that cannot be the case, the barometric pressure sensor is in the 
controller, not the outside sensor and it would not die if it was a failure 
of the radio link from the ourside unit.  Although I see the wisdom in 
that, I am not sure and have not been able to confirm that if the RF shuts 
down, the barometer still continues to record.  I think it is possible that 
if weewx does not get valid temp, wind, and rain it dies not record.  I 
would be interested in whether anyone else has seen whether the RF fail 
stops barometer recording.

I did find somewhere a note by a user of another Ambient that they had a 
problem if the interval was dropped to 5 minutes but did not comment if it 
was solid or intermittent failure.  This started after I replaced batteries 
and the interval reset to 1 hour from the 10 minutes i liked.  When i set 
it i set the interval to 5 minutes, not the previous 10 minutes and the 
problem seems to have started about that time.  . It may be that the 
shorter interval and the polling interval conflict at 5 minutes.

Anyone have any thoughts?

I have not had a failure since i reset the interval to 10 but i also have 
not had the terribly high humidity either. I will post if I get a failure.

  

-- 
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] catching up on Weather Underground after internet outage

[Craig Thom]

It works.  I didn't even know this was a feature.  The only reference I can 
find to it in the documentation is the "stale" setting for CWOP to prevent 
catching up, since CWOP apparently only handles real time data.

My internet service at home was down for a few hours yesterday, and today I 
discovered that Weather Underground wasn't missing any data.  CWOP is, and 
WOW is, but WU isn't, and it gave me my gold star back.

I looked at the log at the default level, and I can see where the uploads 
failed and when they started again, but there's no reference to catching up.

I think this automatic catch up for Weather Underground is worth mentioning 
as a feature in the documentation.  Or, if it's there, maybe a mention in a 
more obvious place.  It's a selling point, especially to users of Acurite 
sensors, who are accustomed to WU being their only archive.  We weewx users 
have our own databases, so Weather Underground isn't as important, but it's 
still a nice feature.

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

[Robert Schneider]

Hello all 
look for some help geting the steelseries working with WeeWX 3.7.1
I get the page to up But no data is gowing to the page . 

here is the weewx.config StdReport

#   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
 
[[SteelSeries]]
skin = ss
HTML_ROOT = public_html/ss


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

-- 
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] WeeWX Not updating

[Thomas Keffer]

Hard to say without knowing the type of weather station and without seeing
the log.

-tk

Fat-fingered from my Android

On Aug 27, 2017 5:01 AM, "Den S"  wrote:

> A power failure shut down my Pi WeeWx server when it restarted it is stuck
> on 8/25/17. The /var/www/html/weather files are all being updated but the
> WeeWx data and date are stuck on the day of the outage.
> Any help would be greatly appreciated.
> Den
>
> --
> 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] WeeWX Not updating

[Den S]

A power failure shut down my Pi WeeWx server when it restarted it is stuck 
on 8/25/17. The /var/www/html/weather files are all being updated but the 
WeeWx data and date are stuck on the day of the outage.
Any help would be greatly appreciated.
Den

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