[weewx-user] Re: Belchertown skin 1.0 released!

[rich T]

Pat ..Will give it a try. Here is my first attempt at using data labels.  
It is a work in progress.


On Sunday, August 25, 2019 at 9:44:47 PM UTC-4, Pat wrote:
>
> I added minorTicks to the 1.1 development version in a commit a couple of 
> weeks ago 
> .
>   
> Use yAxis_minorTicks if you want to try it. I don't think it's documented 
> yet in my wiki though (but it follows the same rules as the official 
> highcharts 
> yaxis minorticks )
>
> I am also working on a chart type called weatherRadial in the development 
> version. I commited it as a basic feature today but has a bit of work to go 
> before it's done. 
>
> Details are here 
> ,
>  
> and if anyone's interested install the 1.1b5 development version to try it 
> out. (Since this is development version, please note I may rename it (to 
> something like outTempRadial or outTempRanges) in future release).
>
>
> On Saturday, August 24, 2019 at 10:56:12 PM UTC-4, rich T wrote:
>>
>> Pat...Here are the latest graphs. I'm using Y axis 0 and Y axis 1 now.  
>> Is there a way to add minor grid lines and zones?
>>
>> [[Rain_Thunder_Day]]  
>>   
>>title = Past 24 Hr Rain / Lightning
>>time_length = 86400
>>aggregate_type = sum
>>aggregate_interval = 900
>>gapsize = 90
>>
>>[[[rainRate]]]
>> name = Rain Rate
>> yAxis = 1
>> zIndex = 0
>> color = Orange
>> dashStyle = DashDot
>>
>>[[[rainTotal]]]
>> name = Rain Total
>> yAxis = 1
>> zIndex = 1
>> color = Yellow
>> dashStyle = ShortDash
>> 
>> [[[outTemp]]]
>> name = Temperature
>> aggregate_type = max
>> yAxis = 1
>> zIndex = 2
>> color = Cyan
>> 
>>  [[[dewpoint]]]
>> name = Dewpoint
>> aggregate_type = max
>> yAxis = 1
>> zIndex = 3
>> color = Purple 
>> dashStyle = Dash
>> 
>>  [[[lightning_strikes]]]
>> name = Lightning Count
>> aggregate_type = sum
>> yAxis = 0
>> yAxisLabel = AS3935 Lightning Strikes
>> zIndex = 1
>> color = Red
>> type = column 
>>  
>>  
>>  [[Rain_Thunder_Week]]
>>  
>> title = Weekly Rain / Lightning
>> time_length = 604800
>> aggregate_type = sum
>> aggregate_interval = 900
>> gapsize = 90
>> 
>>[[[rainRate]]]
>> name = Rain Rate
>> yAxis = 1
>> zIndex = 0
>> color = Orange
>> dashStyle = DashDot
>>
>>[[[rainTotal]]]
>> name = Rain Total
>> yAxis = 1
>> zIndex = 1
>> color = Yellow
>> dashStyle = ShortDash
>> 
>> [[[outTemp]]]
>> name = Temperature
>> aggregate_type = max
>> yAxis = 1
>> zIndex = 2
>> color = Cyan
>> 
>>  [[[dewpoint]]]
>> name = Dewpoint
>> aggregate_type = max
>> yAxis = 1
>> zIndex = 3
>> color = Purple 
>> dashStyle = Dash
>> 
>>  [[[lightning_strikes]]]
>> name = Lightning Count
>> aggregate_type = sum
>> yAxis = 0
>> yAxisLabel = AS3935 Lightning Strikes
>> zIndex = 1
>> color = Red
>> type = column
>>
>> 
>>   [[Rain_Thunder_Month]]  
>>   
>>title = Monthly Rain / Lightning
>>time_length = 2592000 # Last 30 days
>>tooltip_date_format = " LL"
>>aggregate_type = sum
>>aggregate_interval = 86400 # 1 day
>>gapsize = 8640 # 1 day in milliseconds
>> 
>> [[[rainRate]]]
>> name = Rain Rate
>> yAxis = 1
>> zIndex = 0
>> color = Orange
>> dashStyle = DashDot
>>
>>[[[rainTotal]]]
>> name = Rain Total
>> yAxis = 1
>> zIndex = 1
>> color = Yellow
>> dashStyle = ShortDash
>> 
>> [[[outTemp]]]
>> name = Temperature
>> aggregate_type = max
>> yAxis = 1
>> zIndex = 2
>> color = Cyan
>> 
>>  [[[dewpoint]]]
>> name = Dewpoint
>> aggregate_type = max
>> yAxis = 1
>>  

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

I added minorTicks to the 1.1 development version in a commit a couple of 
weeks ago 
.
  
Use yAxis_minorTicks if you want to try it. I don't think it's documented 
yet in my wiki though (but it follows the same rules as the official highcharts 
yaxis minorticks )

I am also working on a chart type called weatherRadial in the development 
version. I commited it as a basic feature today but has a bit of work to go 
before it's done. 

Details are here 
,
 
and if anyone's interested install the 1.1b5 development version to try it 
out. (Since this is development version, please note I may rename it (to 
something like outTempRadial or outTempRanges) in future release).


On Saturday, August 24, 2019 at 10:56:12 PM UTC-4, rich T wrote:
>
> Pat...Here are the latest graphs. I'm using Y axis 0 and Y axis 1 now.  Is 
> there a way to add minor grid lines and zones?
>
> [[Rain_Thunder_Day]]  
>   
>title = Past 24 Hr Rain / Lightning
>time_length = 86400
>aggregate_type = sum
>aggregate_interval = 900
>gapsize = 90
>
>[[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 0
> color = Orange
> dashStyle = DashDot
>
>[[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> color = Yellow
> dashStyle = ShortDash
> 
> [[[outTemp]]]
> name = Temperature
> aggregate_type = max
> yAxis = 1
> zIndex = 2
> color = Cyan
> 
>  [[[dewpoint]]]
> name = Dewpoint
> aggregate_type = max
> yAxis = 1
> zIndex = 3
> color = Purple 
> dashStyle = Dash
> 
>  [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> yAxisLabel = AS3935 Lightning Strikes
> zIndex = 1
> color = Red
> type = column 
>  
>  
>  [[Rain_Thunder_Week]]
>  
> title = Weekly Rain / Lightning
> time_length = 604800
> aggregate_type = sum
> aggregate_interval = 900
> gapsize = 90
> 
>[[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 0
> color = Orange
> dashStyle = DashDot
>
>[[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> color = Yellow
> dashStyle = ShortDash
> 
> [[[outTemp]]]
> name = Temperature
> aggregate_type = max
> yAxis = 1
> zIndex = 2
> color = Cyan
> 
>  [[[dewpoint]]]
> name = Dewpoint
> aggregate_type = max
> yAxis = 1
> zIndex = 3
> color = Purple 
> dashStyle = Dash
> 
>  [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> yAxisLabel = AS3935 Lightning Strikes
> zIndex = 1
> color = Red
> type = column
>
> 
>   [[Rain_Thunder_Month]]  
>   
>title = Monthly Rain / Lightning
>time_length = 2592000 # Last 30 days
>tooltip_date_format = " LL"
>aggregate_type = sum
>aggregate_interval = 86400 # 1 day
>gapsize = 8640 # 1 day in milliseconds
> 
> [[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 0
> color = Orange
> dashStyle = DashDot
>
>[[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> color = Yellow
> dashStyle = ShortDash
> 
> [[[outTemp]]]
> name = Temperature
> aggregate_type = max
> yAxis = 1
> zIndex = 2
> color = Cyan
> 
>  [[[dewpoint]]]
> name = Dewpoint
> aggregate_type = max
> yAxis = 1
> zIndex = 3
> color = Purple 
> dashStyle = Dash
> 
>  [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> yAxisLabel = AS3935 Lightning Strikes
> zIndex = 1
> color = Red
> 

[weewx-user] Re: Interceptor working standalone but not with Weewx

[mwall]

On Sunday, August 25, 2019 at 11:01:08 AM UTC-4, Jos Bredek wrote:
>
>
> It looks like weeewx starts the Interceptor listening server on 8000 but 
> within the same second it shuts the serverport again. Weewx keeps doing 
> this every 300 seconds (probably since that is the archive interval). 
>
> Here's my output from the log (debug set to 1):
>
> Aug 25 16:48:54 weerstation weewx[9422]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Aug 25 16:48:54 weerstation weewx[9422]: engine: Loading station type 
> Interceptor (user.interceptor)
> Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: driver 
> version is 0.46
> Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: device 
> type: wu-client
> Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: sensor 
> map: None
> Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: mode is 
> listen
> Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: listen 
> on :8000
> Aug 25 16:48:54 weerstation weewx[9422]: engine: StdConvert target unit is 
> 0x1
> Aug 25 16:48:54 weerstation weewx[9422]: wxcalculate: The following values 
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
> Aug 25 16:48:54 weerstation weewx[9422]: wxcalculate: The following 
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Aug 25 16:48:54 weerstation weewx[9422]: engine: Archive will use data 
> binding wx_binding
> Aug 25 16:48:54 weerstation weewx[9422]: engine: Record generation will be 
> attempted in 'software'
> Aug 25 16:48:54 weerstation weewx[9422]: engine: Using archive interval of 
> 300 seconds (software record generation)
> Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: shutting 
> down server thread
>
> Is there something (simple) i've been missing? The server should keep 
> listening on port 8000 all the time not just a the every 3 minutes for just 
> a second
>

it would help to see more of the log, not just one cycle.  and it would 
help if you set debug=1

however, this smells like an unreported exception - the listening thread is 
probably raising an exception, but that is getting swallowed.

try running weewx directly - that will show us whether there are any 
exceptions in the listening (or other) thread.

also, you are probably testing two different things - your weewx.conf uses 
wu-client as device_type, but since you did not specify a mode in the 
direct invocation of interceptor.py, the device_type is acurite-bridge.

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/cdbab26e-77d3-4297-aa5a-1ae684d25ed5%40googlegroups.com.

Re: [weewx-user] Re: No Updates on new system

[rstetson1]

Will look for that variable. It's not in the doc that I have.thanksrslOn the 
Road... maybe. Sent from my T-Mobile 4G LTE Device
 Original message From: Andrew Milner 
 Date: 8/25/19  1:35 PM  (GMT-05:00) To: 
weewx-user  Subject: [weewx-user] Re: No Updates 
on new system Well you did not actually post for two archive intervals.  Weewx 
usually reads vantage loop data every few seconds and rec data according to the 
archive interval specified in the console.  this can be adjusted using 
wee_device.  the start up sequence usually gives the archive interval which 
weewx will use (ie the console or as specified in weewx.conf) - but your log 
file does not start from the beginning of the start up sequence.  Data is 
usually output once every archive interval to reports and/or WU, CWOP etc.  The 
fact that your CWOP is at 30 minute intervals makes me think that the console 
is probably set taking records at 30 minute intervals.  If you want 5 minute 
intervals then you will need to idealy set console = weewx.conf = 5 minute (300 
seconds) interval.On Sunday, 25 August 2019 20:22:21 UTC+3, Roy Lamberton  
wrote:The CWOP and PWS updated at 1200, 1230, & 1300, regardless of the time of 
the setting under CWOP in the .conf file. I'm not sure where you tell the 
system to generate the transmissions, but that is happening every 30 minutes at 
the top and bottom of the hour.Here is the log:roy@roy-STCK1A8LFC:/etc/weewx$ 
tail -f /var/log/syslogAug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: manager: 
Daily summary version is 2.0Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: message 
repeated 2 times: [ manager: Daily summary version is 2.0]Aug 25 13:06:21 
roy-STCK1A8LFC weewx[8075]: engine: Clock error is -1.20 seconds (positive is 
fast)Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Getting archive 
packets since 2019-08-25 13:00:00 EDT (1566752400)Aug 25 13:06:21 
roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of console successfulAug 25 
13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Retrieving 0 page(s); starting 
index= 0Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Starting main 
packet loop.Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up 
of console successfulAug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: 
Requesting 200 LOOP packets.Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: 
vantage: Gentle wake up of console successfulAug 25 13:07:30 roy-STCK1A8LFC 
wpa_supplicant[1179]: wlan1: CTRL-EVENT-SCAN-STARTED Aug 25 13:11:30 
roy-STCK1A8LFC wpa_supplicant[1179]: message repeated 2 times: [ wlan1: 
CTRL-EVENT-SCAN-STARTED ]Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: 
Requesting 200 LOOP packets.Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: 
vantage: Gentle wake up of console successfulAug 25 13:13:30 roy-STCK1A8LFC 
wpa_supplicant[1179]: wlan1: CTRL-EVENT-SCAN-STARTED Aug 25 13:15:30 
roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: CTRL-EVENT-SCAN-STARTED Aug 25 
13:17:01 roy-STCK1A8LFC CRON[8141]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)Aug 25 13:17:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
CTRL-EVENT-SCAN-STARTED It appears that WeeWx is asking the console for an 
update every 5 minutes, but then sits on the data until the top and bottom of 
the hour. Because of my location, CWOP always wanted a 5 minute reporting 
interval. So did Wunderground.I can't find anything that changes the time 
between reports that I haven't changed.On Sunday, August 25, 2019 at 1:05:35 PM 
UTC-4, Andrew Milner wrote:Posting the log from startup until two archive 
intervals have passed would help analysing your problem.On Sunday, 25 August 
2019 19:49:48 UTC+3, Roy Lamberton  wrote:Update - it is posting the latest 
information every time I restart WeeWx, but then it asks for the LOOP Packets 
every 5 minutes, but doesn't process them.It almost seems like the software is 
getting the data but doesn't know what to do with it. I can't find anything in 
the Doc about the conf file that talks about timing of upload, except the 
Wunderground flash, which I turned off temporarily. But I need to talk with 
someone fast, or I'm going badcfk to my old Cumulus setup and putting WeeWx on 
hold.rslOn Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton 
wrote:OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
appears to be working, but it isn't updating CWOP or any of the other weather 
systems:Here's the syslog"roy@roy-STCK1A8LFC:/etc/weewx$ tail -f 
/var/log/syslogAug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily 
summary version is 2.0Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message 
repeated 2 times: [ manager: Daily summary version is 2.0]Aug 25 12:05:20 
roy-STCK1A8LFC weewx[7510]: engine: Clock error is -0.45 seconds (positive is 
fast)Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive 
packets since 2019-08-25 12:00:00 EDT (1566748800)Aug 25 12:05:20 
roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up 

Re: [weewx-user] Enabling Windrun

[Thomas Keffer]

If you set windrun=software in [StdWXCalculate], windrun will be
calculated, but it will only be the run over the archive interval. To get
the run over longer periods you need, of course, the database.

So, yes, you will have to add windrun to the database schema. See the
section *Adding a new type to the database
* for how to do
this.

On Sun, Aug 25, 2019 at 1:34 PM Steve Schindler  wrote:

> I am trying to display windrun using WeeWX ver. 3.9.2 and a Davis VP2
> station. Currently on my web page, I'm seeing the literal tag
> "$day.windrun.sum" vice a value.
>
> I did some digging around and discovered in Issue #250 that "
> StdWXCalculate can optionally (it is disabled by default) augment each
> archive record with a calculated windrun field." So I added windrun to
> StdWXCalculate (although I'm not sure that this is still required):
>
> [StdWXCalculate]
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible
> values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
>
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = prefer_hardware
> windchill = prefer_hardware
> heatindex = prefer_hardware
> dewpoint = prefer_hardware
> inDewpoint = prefer_hardware
> rainRate = prefer_hardware
> # Added windrun 8-24-2019
> windrun = software
>
> Also in that Issue, Tom mentioned "It should be possible to sum the
> archive records and get the total for the day. However, this is only
> possible if windrun appears in the database."
>
> This make me think that I need to add a new observation type (windrun) to
> the WeeWx database.
>
> Am I on the right track here?
>
> Log file is attached.
>
> --
> 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/08c01789-84e6-49cb-959c-042ac08293a5%40googlegroups.com
> 
> .
>

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

Re: [weewx-user] No Updates on new system

[Thomas Keffer]

Odds are this is a simple case of corruption of the logger memory. See the
section *WeeWX generates HTML pages, but it does not update them
* in
the User's Guide.

If that doesn't help, set debug=1, restart weewx, then send the log through
the first archive record generation.

-tk


On Sun, Aug 25, 2019 at 9:19 AM Roy Lamberton  wrote:

> OK, I have WeeWx running on an Ubuntu desktop PC and its connected and
> appears to be working, but it isn't updating CWOP or any of the other
> weather systems:
>
> Here's the syslog"
> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary version
> is 2.0
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [
> manager: Daily summary version is 2.0]
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is -0.45
> seconds (positive is fast)
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive
> packets since 2019-08-25 12:00:00 EDT (1566748800)
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of
> console successful
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Retrieving 0 page(s);
> starting index= 0
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Starting main packet
> loop.
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of
> console successful
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Requesting 200 LOOP
> packets.
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of
> console successful
> Aug 25 12:05:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1:
> CTRL-EVENT-SCAN-STARTED
>
> When I first ran it, the woftware download 2 months of data from the
> console, and it did update one time when I restarted the software, but now
> it doesn't seem to be updating CWOP or the web page on the PC.
>
> ???
>
> rsl
>
> --
> 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/f46f7b9c-2829-40ba-a8e1-7653e5b57825%40googlegroups.com
> 
> .
>

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

[weewx-user] Enabling Windrun

[Steve Schindler]

I am trying to display windrun using WeeWX ver. 3.9.2 and a Davis VP2 
station. Currently on my web page, I'm seeing the literal tag 
"$day.windrun.sum" vice a value.

I did some digging around and discovered in Issue #250 that "StdWXCalculate 
can optionally (it is disabled by default) augment each archive record with 
a calculated windrun field." So I added windrun to StdWXCalculate (although 
I'm not sure that this is still required):

[StdWXCalculate]

[[Calculations]]
# Derived quantities are calculated by this service. Possible 
values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = prefer_hardware
windchill = prefer_hardware
heatindex = prefer_hardware
dewpoint = prefer_hardware
inDewpoint = prefer_hardware
rainRate = prefer_hardware
# Added windrun 8-24-2019
windrun = software

Also in that Issue, Tom mentioned "It should be possible to sum the archive 
records and get the total for the day. However, this is only possible if 
windrun appears in the database."

This make me think that I need to add a new observation type (windrun) to 
the WeeWx database.

Am I on the right track here?

Log file is attached.

-- 
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/08c01789-84e6-49cb-959c-042ac08293a5%40googlegroups.com.
Aug 25 15:31:44 watson weewx[2423]:   for _loop_packet in 
self.genDavisLoopPackets(200):
Aug 25 15:31:44 watson weewx[2423]: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 535, in genDavisLoopPackets
Aug 25 15:31:44 watson weewx[2423]:   _buffer = self.port.read(99)
Aug 25 15:31:44 watson weewx[2423]: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 256, in read
Aug 25 15:31:44 watson weewx[2423]:   _buffer = 
self.serial_port.read(chars)
Aug 25 15:31:44 watson weewx[2423]: File 
"/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 442, in read
Aug 25 15:31:44 watson weewx[2423]:   ready,_,_ = 
select.select([self.fd],[],[], self._timeout)
Aug 25 15:31:44 watson weewx[2423]: File 
"/home/weewx/bin/weewx/engine.py", line 812, in sigTERMhandler
Aug 25 15:31:44 watson weewx[2423]:   raise Terminate
Aug 25 15:31:44 watson weewx[2423]:   Terminate
Aug 25 15:32:37 watson weewx[2470]: engine: Initializing weewx version 3.9.2
Aug 25 15:32:37 watson weewx[2470]: engine: Using Python 2.7.3 (default, Nov 24 
2017, 21:13:24) #012[GCC 4.6.3]
Aug 25 15:32:37 watson weewx[2470]: engine: Platform 
Linux-4.1.19+-armv6l-with-debian-7.11
Aug 25 15:32:37 watson weewx[2470]: engine: Locale is 'en_US.UTF-8'
Aug 25 15:32:37 watson weewx[2470]: engine: pid file is /var/run/weewx.pid
Aug 25 15:32:37 watson weewx[2474]: engine: Using configuration file 
/home/weewx/weewx.conf
Aug 25 15:32:37 watson weewx[2474]: engine: Debug is 1
Aug 25 15:32:37 watson weewx[2474]: engine: Initializing engine
Aug 25 15:32:37 watson weewx[2474]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Aug 25 15:32:37 watson weewx[2474]: vantage: Driver version is 3.1.1
Aug 25 15:32:37 watson weewx[2474]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 5.00
Aug 25 15:32:37 watson weewx[2474]: vantage: Gentle wake up of console 
successful
Aug 25 15:32:37 watson weewx[2474]: vantage: Hardware type is 16
Aug 25 15:32:37 watson weewx[2474]: vantage: ISS ID is 1
Aug 25 15:32:37 watson weewx[2474]: vantage: Hardware name: Vantage Pro2
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.engine.StdTimeSynch
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.engine.StdConvert
Aug 25 15:32:37 watson weewx[2474]: engine: StdConvert target unit is 0x1
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdConvert
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.engine.StdCalibrate
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdCalibrate
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service weewx.engine.StdQC
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdQC
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Aug 25 15:32:37 watson 

[weewx-user] Re: No Updates on new system

[Roy Lamberton]

Where is the "set Console" variable?

On Sunday, August 25, 2019 at 1:35:50 PM UTC-4, Andrew Milner wrote:
>
> Well you did not actually post for two archive intervals.  Weewx usually 
> reads vantage loop data every few seconds and rec data according to the 
> archive interval specified in the console.  this can be adjusted using 
> wee_device.  the start up sequence usually gives the archive interval which 
> weewx will use (ie the console or as specified in weewx.conf) - but your 
> log file does not start from the beginning of the start up sequence.  Data 
> is usually output once every archive interval to reports and/or WU, CWOP 
> etc.  The fact that your CWOP is at 30 minute intervals makes me think that 
> the console is probably set taking records at 30 minute intervals.  If you 
> want 5 minute intervals then you will need to idealy set console = 
> weewx.conf = 5 minute (300 seconds) interval.
>
>
>
>
> On Sunday, 25 August 2019 20:22:21 UTC+3, Roy Lamberton wrote:
>>
>> The CWOP and PWS updated at 1200, 1230, & 1300, regardless of the time of 
>> the setting under CWOP in the .conf file. 
>>
>> I'm not sure where you tell the system to generate the transmissions, but 
>> that is happening every 30 minutes at the top and bottom of the hour.
>>
>> Here is the log:
>> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: manager: Daily summary 
>> version is 2.0
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: message repeated 2 times: [ 
>> manager: Daily summary version is 2.0]
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Clock error is -1.20 
>> seconds (positive is fast)
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Getting archive 
>> packets since 2019-08-25 13:00:00 EDT (1566752400)
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Retrieving 0 
>> page(s); starting index= 0
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Starting main packet 
>> loop.
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP 
>> packets.
>> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 13:07:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
>> CTRL-EVENT-SCAN-STARTED 
>> Aug 25 13:11:30 roy-STCK1A8LFC wpa_supplicant[1179]: message repeated 2 
>> times: [ wlan1: CTRL-EVENT-SCAN-STARTED ]
>> Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP 
>> packets.
>> Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 13:13:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
>> CTRL-EVENT-SCAN-STARTED 
>> Aug 25 13:15:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
>> CTRL-EVENT-SCAN-STARTED 
>> Aug 25 13:17:01 roy-STCK1A8LFC CRON[8141]: (root) CMD (   cd / && 
>> run-parts --report /etc/cron.hourly)
>> Aug 25 13:17:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
>> CTRL-EVENT-SCAN-STARTED 
>>
>> It appears that WeeWx is asking the console for an update every 5 
>> minutes, but then sits on the data until the top and bottom of the hour. 
>> Because of my location, CWOP always wanted a 5 minute reporting interval. 
>> So did Wunderground.
>>
>> I can't find anything that changes the time between reports that I 
>> haven't changed.
>>
>>
>> On Sunday, August 25, 2019 at 1:05:35 PM UTC-4, Andrew Milner wrote:
>>>
>>> Posting the log from startup until two archive intervals have passed 
>>> would help analysing your problem.
>>>
>>>
>>>
>>> On Sunday, 25 August 2019 19:49:48 UTC+3, Roy Lamberton wrote:

 Update - it is posting the latest information every time I restart 
 WeeWx, but then it asks for the LOOP Packets every 5 minutes, but doesn't 
 process them.

 It almost seems like the software is getting the data but doesn't know 
 what to do with it. 

 I can't find anything in the Doc about the conf file that talks about 
 timing of upload, except the Wunderground flash, which I turned off 
 temporarily. 

 But I need to talk with someone fast, or I'm going badcfk to my old 
 Cumulus setup and putting WeeWx on hold.


 rsl
 On Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton wrote:
>
> OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
> appears to be working, but it isn't updating CWOP or any of the other 
> weather systems:
>
> Here's the syslog"
> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary 
> version is 2.0
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: 
> [ manager: Daily summary version is 2.0]
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: 

[weewx-user] Re: No Updates on new system

[Andrew Milner]

Well you did not actually post for two archive intervals.  Weewx usually 
reads vantage loop data every few seconds and rec data according to the 
archive interval specified in the console.  this can be adjusted using 
wee_device.  the start up sequence usually gives the archive interval which 
weewx will use (ie the console or as specified in weewx.conf) - but your 
log file does not start from the beginning of the start up sequence.  Data 
is usually output once every archive interval to reports and/or WU, CWOP 
etc.  The fact that your CWOP is at 30 minute intervals makes me think that 
the console is probably set taking records at 30 minute intervals.  If you 
want 5 minute intervals then you will need to idealy set console = 
weewx.conf = 5 minute (300 seconds) interval.




On Sunday, 25 August 2019 20:22:21 UTC+3, Roy Lamberton wrote:
>
> The CWOP and PWS updated at 1200, 1230, & 1300, regardless of the time of 
> the setting under CWOP in the .conf file. 
>
> I'm not sure where you tell the system to generate the transmissions, but 
> that is happening every 30 minutes at the top and bottom of the hour.
>
> Here is the log:
> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: manager: Daily summary version 
> is 2.0
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: message repeated 2 times: [ 
> manager: Daily summary version is 2.0]
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Clock error is -1.20 
> seconds (positive is fast)
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Getting archive 
> packets since 2019-08-25 13:00:00 EDT (1566752400)
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
> console successful
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Retrieving 0 page(s); 
> starting index= 0
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Starting main packet 
> loop.
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
> console successful
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP 
> packets.
> Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
> console successful
> Aug 25 13:07:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
> CTRL-EVENT-SCAN-STARTED 
> Aug 25 13:11:30 roy-STCK1A8LFC wpa_supplicant[1179]: message repeated 2 
> times: [ wlan1: CTRL-EVENT-SCAN-STARTED ]
> Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP 
> packets.
> Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
> console successful
> Aug 25 13:13:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
> CTRL-EVENT-SCAN-STARTED 
> Aug 25 13:15:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
> CTRL-EVENT-SCAN-STARTED 
> Aug 25 13:17:01 roy-STCK1A8LFC CRON[8141]: (root) CMD (   cd / && 
> run-parts --report /etc/cron.hourly)
> Aug 25 13:17:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
> CTRL-EVENT-SCAN-STARTED 
>
> It appears that WeeWx is asking the console for an update every 5 minutes, 
> but then sits on the data until the top and bottom of the hour. Because of 
> my location, CWOP always wanted a 5 minute reporting interval. So did 
> Wunderground.
>
> I can't find anything that changes the time between reports that I haven't 
> changed.
>
>
> On Sunday, August 25, 2019 at 1:05:35 PM UTC-4, Andrew Milner wrote:
>>
>> Posting the log from startup until two archive intervals have passed 
>> would help analysing your problem.
>>
>>
>>
>> On Sunday, 25 August 2019 19:49:48 UTC+3, Roy Lamberton wrote:
>>>
>>> Update - it is posting the latest information every time I restart 
>>> WeeWx, but then it asks for the LOOP Packets every 5 minutes, but doesn't 
>>> process them.
>>>
>>> It almost seems like the software is getting the data but doesn't know 
>>> what to do with it. 
>>>
>>> I can't find anything in the Doc about the conf file that talks about 
>>> timing of upload, except the Wunderground flash, which I turned off 
>>> temporarily. 
>>>
>>> But I need to talk with someone fast, or I'm going badcfk to my old 
>>> Cumulus setup and putting WeeWx on hold.
>>>
>>>
>>> rsl
>>> On Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton wrote:

 OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
 appears to be working, but it isn't updating CWOP or any of the other 
 weather systems:

 Here's the syslog"
 roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
 Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary 
 version is 2.0
 Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [ 
 manager: Daily summary version is 2.0]
 Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is 
 -0.45 seconds (positive is fast)
 Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive 
 packets since 2019-08-25 12:00:00 EDT (1566748800)
 Aug 25 12:05:20 roy-STCK1A8LFC 

[weewx-user] Re: No Updates on new system

[Roy Lamberton]

The CWOP and PWS updated at 1200, 1230, & 1300, regardless of the time of 
the setting under CWOP in the .conf file. 

I'm not sure where you tell the system to generate the transmissions, but 
that is happening every 30 minutes at the top and bottom of the hour.

Here is the log:
roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: manager: Daily summary version 
is 2.0
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: message repeated 2 times: [ 
manager: Daily summary version is 2.0]
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Clock error is -1.20 
seconds (positive is fast)
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Getting archive 
packets since 2019-08-25 13:00:00 EDT (1566752400)
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
console successful
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Retrieving 0 page(s); 
starting index= 0
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Starting main packet 
loop.
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
console successful
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP 
packets.
Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
console successful
Aug 25 13:07:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
CTRL-EVENT-SCAN-STARTED 
Aug 25 13:11:30 roy-STCK1A8LFC wpa_supplicant[1179]: message repeated 2 
times: [ wlan1: CTRL-EVENT-SCAN-STARTED ]
Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP 
packets.
Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of 
console successful
Aug 25 13:13:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
CTRL-EVENT-SCAN-STARTED 
Aug 25 13:15:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
CTRL-EVENT-SCAN-STARTED 
Aug 25 13:17:01 roy-STCK1A8LFC CRON[8141]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Aug 25 13:17:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
CTRL-EVENT-SCAN-STARTED 

It appears that WeeWx is asking the console for an update every 5 minutes, 
but then sits on the data until the top and bottom of the hour. Because of 
my location, CWOP always wanted a 5 minute reporting interval. So did 
Wunderground.

I can't find anything that changes the time between reports that I haven't 
changed.


On Sunday, August 25, 2019 at 1:05:35 PM UTC-4, Andrew Milner wrote:
>
> Posting the log from startup until two archive intervals have passed would 
> help analysing your problem.
>
>
>
> On Sunday, 25 August 2019 19:49:48 UTC+3, Roy Lamberton wrote:
>>
>> Update - it is posting the latest information every time I restart WeeWx, 
>> but then it asks for the LOOP Packets every 5 minutes, but doesn't process 
>> them.
>>
>> It almost seems like the software is getting the data but doesn't know 
>> what to do with it. 
>>
>> I can't find anything in the Doc about the conf file that talks about 
>> timing of upload, except the Wunderground flash, which I turned off 
>> temporarily. 
>>
>> But I need to talk with someone fast, or I'm going badcfk to my old 
>> Cumulus setup and putting WeeWx on hold.
>>
>>
>> rsl
>> On Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton wrote:
>>>
>>> OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
>>> appears to be working, but it isn't updating CWOP or any of the other 
>>> weather systems:
>>>
>>> Here's the syslog"
>>> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary 
>>> version is 2.0
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [ 
>>> manager: Daily summary version is 2.0]
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is -0.45 
>>> seconds (positive is fast)
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive 
>>> packets since 2019-08-25 12:00:00 EDT (1566748800)
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
>>> console successful
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Retrieving 0 
>>> page(s); starting index= 0
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Starting main packet 
>>> loop.
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
>>> console successful
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Requesting 200 LOOP 
>>> packets.
>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
>>> console successful
>>> Aug 25 12:05:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
>>> CTRL-EVENT-SCAN-STARTED 
>>>
>>> When I first ran it, the woftware download 2 months of data from the 
>>> console, and it did update one time when I restarted the software, but now 
>>> it doesn't seem to be updating CWOP or the web page on the PC.
>>>
>>> ???
>>>
>>> rsl
>>>
>>>

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

[weewx-user] Re: No Updates on new system

[Andrew Milner]

Posting the log from startup until two archive intervals have passed would 
help analysing your problem.



On Sunday, 25 August 2019 19:49:48 UTC+3, Roy Lamberton wrote:
>
> Update - it is posting the latest information every time I restart WeeWx, 
> but then it asks for the LOOP Packets every 5 minutes, but doesn't process 
> them.
>
> It almost seems like the software is getting the data but doesn't know 
> what to do with it. 
>
> I can't find anything in the Doc about the conf file that talks about 
> timing of upload, except the Wunderground flash, which I turned off 
> temporarily. 
>
> But I need to talk with someone fast, or I'm going badcfk to my old 
> Cumulus setup and putting WeeWx on hold.
>
>
> rsl
> On Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton wrote:
>>
>> OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
>> appears to be working, but it isn't updating CWOP or any of the other 
>> weather systems:
>>
>> Here's the syslog"
>> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary 
>> version is 2.0
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [ 
>> manager: Daily summary version is 2.0]
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is -0.45 
>> seconds (positive is fast)
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive 
>> packets since 2019-08-25 12:00:00 EDT (1566748800)
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Retrieving 0 
>> page(s); starting index= 0
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Starting main packet 
>> loop.
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Requesting 200 LOOP 
>> packets.
>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
>> console successful
>> Aug 25 12:05:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
>> CTRL-EVENT-SCAN-STARTED 
>>
>> When I first ran it, the woftware download 2 months of data from the 
>> console, and it did update one time when I restarted the software, but now 
>> it doesn't seem to be updating CWOP or the web page on the PC.
>>
>> ???
>>
>> rsl
>>
>>

-- 
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/06ea355b-dd19-4b05-b4ae-57a7cfc9e86c%40googlegroups.com.

[weewx-user] Re: No Updates on new system

[Roy Lamberton]

Update - it is posting the latest information every time I restart WeeWx, 
but then it asks for the LOOP Packets every 5 minutes, but doesn't process 
them.

It almost seems like the software is getting the data but doesn't know what 
to do with it. 

I can't find anything in the Doc about the conf file that talks about 
timing of upload, except the Wunderground flash, which I turned off 
temporarily. 

But I need to talk with someone fast, or I'm going badcfk to my old Cumulus 
setup and putting WeeWx on hold.


rsl
On Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton wrote:
>
> OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
> appears to be working, but it isn't updating CWOP or any of the other 
> weather systems:
>
> Here's the syslog"
> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary version 
> is 2.0
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [ 
> manager: Daily summary version is 2.0]
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is -0.45 
> seconds (positive is fast)
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive 
> packets since 2019-08-25 12:00:00 EDT (1566748800)
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
> console successful
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Retrieving 0 page(s); 
> starting index= 0
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Starting main packet 
> loop.
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
> console successful
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Requesting 200 LOOP 
> packets.
> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
> console successful
> Aug 25 12:05:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
> CTRL-EVENT-SCAN-STARTED 
>
> When I first ran it, the woftware download 2 months of data from the 
> console, and it did update one time when I restarted the software, but now 
> it doesn't seem to be updating CWOP or the web page on the PC.
>
> ???
>
> rsl
>
>

-- 
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/05e32223-5ad0-4fbe-886e-c7be94877d93%40googlegroups.com.

[weewx-user] No Updates on new system

[Roy Lamberton]

OK, I have WeeWx running on an Ubuntu desktop PC and its connected and 
appears to be working, but it isn't updating CWOP or any of the other 
weather systems:

Here's the syslog"
roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary version 
is 2.0
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [ 
manager: Daily summary version is 2.0]
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is -0.45 
seconds (positive is fast)
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive 
packets since 2019-08-25 12:00:00 EDT (1566748800)
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
console successful
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Retrieving 0 page(s); 
starting index= 0
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Starting main packet 
loop.
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
console successful
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Requesting 200 LOOP 
packets.
Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of 
console successful
Aug 25 12:05:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: 
CTRL-EVENT-SCAN-STARTED 

When I first ran it, the woftware download 2 months of data from the 
console, and it did update one time when I restarted the software, but now 
it doesn't seem to be updating CWOP or the web page on the PC.

???

rsl

-- 
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/f46f7b9c-2829-40ba-a8e1-7653e5b57825%40googlegroups.com.

[weewx-user] Interceptor working standalone but not with Weewx

[Jos Bredek]

Hi everyone,

i'm new into the world weewx. Looking for some help

My setup is:
- ambient ws2902 CLONE
- interceptor driver in listen mode, port 8000
- weather station is set to send data to my server, on port 8000

My first step looked good! The command:
python interceptor.py --mode=listen --port=8000 --debug

worked excellent, although it did report in the logs that 4 parameters were 
not being recognized (no big deal).
Here is the output
identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None} 
raw data: 
ID=xxx==77.4=88.9=59.4=88.9=58=37=0.9=1.1=138=30.107=30.071=0.000=0.000=0.000=0.020=332.63=3=2019-08-25%2014:57:04=EasyWeatherV1.4.0=updateraw=1=5
 
raw packet: {'temperature_in..': 77.4, 'winddir..': 138.0, 'dateTime': 
1566745024, 'usUnits..': 1, 'pressure..': 30.071, 'humidity_in..': 58.0, 
'temperature..': 88.9, 'dateTime..': 1566745024, 'windspeed..': 0.9, 
'rainfall..': None, 'usUnits': 1, 'humidity..': 37.0} mapped packet: 
{'pressure': 30.071, 'inHumidity': 58.0, 'inTemp': 77.4, 'usUnits': 1, 
'dateTime': 1566745024}

Then.. i tried to run weewx (from commandline) with the interceptor-driver. 
My config for the interceptor is like this:
[Interceptor] # This section is for the network traffic interceptor driver. 
# The driver to use: driver = user.interceptor # Specify the hardware 
device to capture. Options include: # acurite-bridge - acurite internet 
bridge, smarthub, or access # observer - fine offset WH2600/HP1000/HP1003, 
ambient WS2902 # lw30x - oregon scientific LW301/LW302 # lacrosse-bridge - 
lacrosse GW1000U/C84612 internet bridge # wu-client - any hardware that 
uses the weather underground protocol device_type = wu-client port = 8000 
## 

It looks like weeewx starts the Interceptor listening server on 8000 but 
within the same second it shuts the serverport again. Weewx keeps doing 
this every 300 seconds (probably since that is the archive interval). 

Here's my output from the log (debug set to 1):

Aug 25 16:48:54 weerstation weewx[9422]: engine: Using configuration file 
/etc/weewx/weewx.conf
Aug 25 16:48:54 weerstation weewx[9422]: engine: Loading station type 
Interceptor (user.interceptor)
Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: driver 
version is 0.46
Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: device 
type: wu-client
Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: sensor 
map: None
Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: mode is 
listen
Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: listen on 
:8000
Aug 25 16:48:54 weerstation weewx[9422]: engine: StdConvert target unit is 
0x1
Aug 25 16:48:54 weerstation weewx[9422]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Aug 25 16:48:54 weerstation weewx[9422]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Aug 25 16:48:54 weerstation weewx[9422]: engine: Archive will use data 
binding wx_binding
Aug 25 16:48:54 weerstation weewx[9422]: engine: Record generation will be 
attempted in 'software'
Aug 25 16:48:54 weerstation weewx[9422]: engine: Using archive interval of 
300 seconds (software record generation)
Aug 25 16:48:54 weerstation weewx[9422]: interceptor: MainThread: shutting 
down server thread

Is there something (simple) i've been missing? The server should keep 
listening on port 8000 all the time not just a the every 3 minutes for just 
a second

My database is on a different server. So far there is no data at all pushed 
into the db 

I've read the documentation on both weewx and the interceptor driver, but i 
can't find anything wrong

Any hints/tips?

CIao,
Jos

-- 
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/57bc7f59-288b-4443-8657-5c00921ccc00%40googlegroups.com.

[weewx-user] Re: French translation

[herve FRELAT]

Salut
J'utilise weewx et j'ai un probleme pour uploader en ftp sur ma page perso 
orange.visiblement il faut mettre dans weewx.conf en mode ftp secure =enable 
mais je me retrouve avec un message "pb ssl dh key too small". Tu as modifie 
des choses ?.merci pour ton retour

-- 
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/9aee0d6d-ea15-4550-a881-fc0453f3c954%40googlegroups.com.