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

2019-08-26 Thread rstetson1
Thanks, that's the piece I couldn't find rslOn the Road... maybe. Sent from my 
T-Mobile 4G LTE Device
 Original message From: gjr80  Date: 
8/26/19  7:28 PM  (GMT-05:00) To: weewx-user  
Subject: Re: [weewx-user] Re: No Updates on new system The preferred method to 
change the archive interval is to use the wee_device utility with the 
—set-interval action 
(http://www.weewx.com/docs/hardware.htm#vantage_archive_interval46). Make sure 
you stop WeeWX before using wee_device.Gary-- 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/8572586f-4b87-487e-82d7-d03be029df0e%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/5d647252.1c69fb81.1430c.bc3e%40mx.google.com.


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

2019-08-26 Thread gjr80
The preferred method to change the archive interval is to use the wee_device 
utility with the —set-interval action 
(http://www.weewx.com/docs/hardware.htm#vantage_archive_interval46). Make sure 
you stop WeeWX before using wee_device.

Gary

-- 
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/8572586f-4b87-487e-82d7-d03be029df0e%40googlegroups.com.


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

2019-08-26 Thread rstetson1
There is the issue. The archive interval as set to 30 minutes but I can't find 
out how to change that.rslOn the Road... maybe. Sent from my T-Mobile 4G LTE 
Device
 Original message From: gjr80  Date: 
8/26/19  5:43 PM  (GMT-05:00) To: weewx-user  
Subject: Re: [weewx-user] Re: No Updates on new system A default install will 
see CWOP posts made every archive interval or 600 seconds, whichever is the 
greater. This period can be changed using the post_interval config option under 
[StdRESTful] [[CWOP]] in weewx.conf but it cannot be reduced to a value less 
than your archive interval. Chances are your archive interval is set to 
something greater than 300 seconds. It is impossible to offer more assistance 
until you post the debug=1 startup log extract asked for by Tom.GaryOn Tuesday, 
27 August 2019 06:35:01 UTC+10, rstetson1  wrote:Ok, I have CWOP interval set 
to 300 or everj 5 minutes, but it actually only updates CEOP  every 30 
minutes.Where and how do you change that interval?rslOn the Road... maybe. Sent 
from my T-Mobile 4G LTE Device Original message From: Thomas 
Keffer  Date: 8/25/19  7:41 PM  (GMT-05:00) To: weewx-user 
 Subject: Re: [weewx-user] Re: No Updates on new 
system I'm not sure what you're referring to. If you mean "debug", it's at the 
top of your weewx.conf file.-tkOn Sun, Aug 25, 2019 at 4:36 PM rstetson1 
 wrote: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 

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

2019-08-26 Thread gjr80
A default install will see CWOP posts made every archive interval or 600 
seconds, whichever is the greater. This period can be changed using the 
post_interval config option under [StdRESTful] [[CWOP]] in weewx.conf but 
it cannot be reduced to a value less than your archive interval. Chances 
are your archive interval is set to something greater than 300 seconds. It 
is impossible to offer more assistance until you post the debug=1 startup 
log extract asked for by Tom.

Gary

On Tuesday, 27 August 2019 06:35:01 UTC+10, rstetson1 wrote:
>
> Ok, I have CWOP interval set to 300 or everj 5 minutes, but it actually 
> only updates CEOP  every 30 minutes.
>
> Where and how do you change that interval?
>
> rsl
>
>
>
> On the Road... maybe. Sent from my T-Mobile 4G LTE Device
>
>  Original message 
> From: Thomas Keffer > 
> Date: 8/25/19 7:41 PM (GMT-05:00) 
> To: weewx-user > 
> Subject: Re: [weewx-user] Re: No Updates on new system 
>
> I'm not sure what you're referring to. If you mean "debug", it's at the 
> top of your weewx.conf file.
>
> -tk
>
> On Sun, Aug 25, 2019 at 4:36 PM rstetson1 > 
> wrote:
>
>> Will look for that variable. It's not in the doc that I have.
>>
>> thanks
>>
>> rsl
>>
>>
>>
>> On 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/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]: wlan

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

2019-08-26 Thread rstetson1
Ok, I have CWOP interval set to 300 or everj 5 minutes, but it actually only 
updates CEOP  every 30 minutes.Where and how do you change that interval?rslOn 
the Road... maybe. Sent from my T-Mobile 4G LTE Device
 Original message From: Thomas Keffer  Date: 
8/25/19  7:41 PM  (GMT-05:00) To: weewx-user  
Subject: Re: [weewx-user] Re: No Updates on new system I'm not sure what you're 
referring to. If you mean "debug", it's at the top of your weewx.conf 
file.-tkOn Sun, Aug 25, 2019 at 4:36 PM rstetson1  
wrote: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:

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

2019-08-26 Thread Thomas Keffer
Again, set debug=1, restart weewx, then send the log through the first
archive record generation.

On Mon, Aug 26, 2019 at 5:39 AM Roy Lamberton  wrote:

> Here's the status of the WeeWx experiment with DW8780
>
> 1. I had to switch back to the Win10-Cumulus setup because of the
> reporting interval issue. I need to spend a little more time reading the
> documentation to see if I can figure it out. Right now the weewx.conf file
> for CWOP is set to pull data every 5 minutes (300 seconds). But, the
> Program uploads data to CWOP, PWS, and Wunderground every 30 minutes, and
> there is no clear description in the doc about what to change to make it
> happen on a different schedule.
>
> 2. My Linux computer, the host for WeeWx, still has some issues when it
> boots up. These issues have to do with the unit updating, and its insane
> desire to get every password known to man to operate cleanly Needless to
> say, it is not presently a walk away system like my Win 10 PC.
>
> It might help if I was more experienced with Python - any positive
> comments would be appreciated. Thank you
> rsl
>
> .
>
> On Sun, Aug 25, 2019 at 11:42 PM rstetson1  wrote:
>
>> Ok, I have CWOP interval set to 300 or everj 5 minutes, but it actually
>> only updates CEOP  every 30 minutes.
>>
>> Where and how do you change that interval?
>>
>> rsl
>>
>>
>>
>> On the Road... maybe. Sent from my T-Mobile 4G LTE Device
>>
>> -------- Original message ----
>> From: Thomas Keffer 
>> Date: 8/25/19 7:41 PM (GMT-05:00)
>> To: weewx-user 
>> Subject: Re: [weewx-user] Re: No Updates on new system
>>
>> I'm not sure what you're referring to. If you mean "debug", it's at the
>> top of your weewx.conf file.
>>
>> -tk
>>
>> On Sun, Aug 25, 2019 at 4:36 PM rstetson1  wrote:
>>
>>> Will look for that variable. It's not in the doc that I have.
>>>
>>> thanks
>>>
>>> rsl
>>>
>>>
>>>
>>> On 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/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]:

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

2019-08-26 Thread Roy Lamberton
Here's the status of the WeeWx experiment with DW8780

1. I had to switch back to the Win10-Cumulus setup because of the reporting
interval issue. I need to spend a little more time reading the
documentation to see if I can figure it out. Right now the weewx.conf file
for CWOP is set to pull data every 5 minutes (300 seconds). But, the
Program uploads data to CWOP, PWS, and Wunderground every 30 minutes, and
there is no clear description in the doc about what to change to make it
happen on a different schedule.

2. My Linux computer, the host for WeeWx, still has some issues when it
boots up. These issues have to do with the unit updating, and its insane
desire to get every password known to man to operate cleanly Needless to
say, it is not presently a walk away system like my Win 10 PC.

It might help if I was more experienced with Python - any positive comments
would be appreciated. Thank you
rsl

.

On Sun, Aug 25, 2019 at 11:42 PM rstetson1  wrote:

> Ok, I have CWOP interval set to 300 or everj 5 minutes, but it actually
> only updates CEOP  every 30 minutes.
>
> Where and how do you change that interval?
>
> rsl
>
>
>
> On the Road... maybe. Sent from my T-Mobile 4G LTE Device
>
>  Original message 
> From: Thomas Keffer 
> Date: 8/25/19 7:41 PM (GMT-05:00)
> To: weewx-user 
> Subject: Re: [weewx-user] Re: No Updates on new system
>
> I'm not sure what you're referring to. If you mean "debug", it's at the
> top of your weewx.conf file.
>
> -tk
>
> On Sun, Aug 25, 2019 at 4:36 PM rstetson1  wrote:
>
>> Will look for that variable. It's not in the doc that I have.
>>
>> thanks
>>
>> rsl
>>
>>
>>
>> On 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/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-STCK1A

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

2019-08-25 Thread 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]: vantag

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

2019-08-25 Thread 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

2019-08-25 Thread 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

2019-08-25 Thread 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

2019-08-25 Thread 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

2019-08-25 Thread 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.