Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-16 Thread Tim Phillips 
I put the original engine.py on my desktop, so the process of getting that
back to the location would be?:

sudo /etc/init.d/weewx stop
​sudo cd /usr/share/weewx​/weewx
sudo mv engine.py engine.py.orig
sudo cp ~/Desktop/engine.py engine.py
sudo /etc/init.d/weewx start

Drag/drop using the UI doesn't work due to permissions. I added sudo to the
commands earlier since I got denied with permission errors there earlier as
well. Assuming that IS the way it's supposed to be?


On Sun, Oct 16, 2016 at 1:29 PM, Thomas Keffer <tkef...@gmail.com> wrote:

> Put the original engine back. They are the same, but the modified version
> will put a lot of entries into your log.
>
> -tk
>
> On Sun, Oct 16, 2016 at 1:07 PM, Tim Phillips <timaphill...@gmail.com>
> wrote:
>
>> Do I need to put the original engine.py back into the folder or do I
>> leave what you gave me in there?
>>
>>
>>
>> On Sun, Oct 16, 2016 at 11:29 AM, Thomas Keffer <tkef...@gmail.com>
>> wrote:
>>
>>> Your value of archive_delay is set to 300 seconds. Change it to 15
>>> seconds and all your problems will go away.
>>>
>>> archive_delay = 15
>>>
>>> -tk
>>>
>>> On Sun, Oct 16, 2016 at 11:18 AM, Tim Phillips <timaphill...@gmail.com>
>>> wrote:
>>>
>>>> New log attached after replacing the engine.py per instructions. Lots
>>>> of "syslog" files attached in this thread, so I've renamed this log with
>>>> appropriate changes- "new engine.py" in the file name
>>>>
>>>> Tim.
>>>>
>>>>
>>>> On Sunday, October 16, 2016 at 9:58:18 AM UTC-7, Tim Phillips wrote:
>>>>>
>>>>> Just followed your instructions and will post the new log file
>>>>> after it's had a chance to run a while as suggested.
>>>>>
>>>>> On Sunday, October 16, 2016 at 6:59:57 AM UTC-7, Tom Keffer wrote:
>>>>>>
>>>>>> On Sun, Oct 16, 2016 at 6:18 AM, mwall <mw...@users.sourceforge.net>
>>>>>> wrote:
>>>>>>
>>>>>>> On Sunday, October 16, 2016 at 8:19:38 AM UTC-4, Tom Keffer wrote:
>>>>>>>>
>>>>>>>> ​Me too.​ What do you think of my theory that the console is
>>>>>>>> (occasionally) waiting more than 5 minutes to emit a LOOP packet?
>>>>>>>>
>>>>>>>
>>>>>>> the log indicates that the driver is getting data regularly.  take a
>>>>>>> look at the entries between some of the 10 minute add records.
>>>>>>>
>>>>>>> there is a yield just before each "next read in X second".  when the
>>>>>>> data are stale, the yielded packet contains only dateTime, usUnits,
>>>>>>> channel, sensor_id, rssi, sensor_battery, but no weather data.
>>>>>>>
>>>>>>
>>>>>> ​That should be enough to give the engine a chance to break the loop.
>>>>>>
>>>>>> Tim: I have attached an instrumented version of
>>>>>> engine.py
>>>>>>  that should shed some light on this mystery. Please set your old
>>>>>> version of
>>>>>> engine.py
>>>>>> aside, and replace it with this one. Assuming you download this
>>>>>> version into
>>>>>> ~/Downloads
>>>>>> , the process would be:
>>>>>>
>>>>>> ​cd /usr/share/weewx​/weewx
>>>>>> mv engine.py engine.py.orig
>>>>>> cp ~/Downloads/engine.py engine.py
>>>>>>
>>>>>>
>>>>>> Make sure debug=1, then restart weewx, then send the log from the
>>>>>> restart, through the first couple of reports (should take about 20
>>>>>> minutes). The log will be big, so just attach it as a file.
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>>
>>>>>>
>>>>>> ​
>>>>>>
>>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx-user+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>&

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-16 Thread Tim Phillips 
Do I need to put the original engine.py back into the folder or do I leave
what you gave me in there?



On Sun, Oct 16, 2016 at 11:29 AM, Thomas Keffer <tkef...@gmail.com> wrote:

> Your value of archive_delay is set to 300 seconds. Change it to 15 seconds
> and all your problems will go away.
>
> archive_delay = 15
>
> -tk
>
> On Sun, Oct 16, 2016 at 11:18 AM, Tim Phillips <timaphill...@gmail.com>
> wrote:
>
>> New log attached after replacing the engine.py per instructions. Lots of
>> "syslog" files attached in this thread, so I've renamed this log with
>> appropriate changes- "new engine.py" in the file name
>>
>> Tim.
>>
>>
>> On Sunday, October 16, 2016 at 9:58:18 AM UTC-7, Tim Phillips wrote:
>>>
>>> Just followed your instructions and will post the new log file
>>> after it's had a chance to run a while as suggested.
>>>
>>> On Sunday, October 16, 2016 at 6:59:57 AM UTC-7, Tom Keffer wrote:
>>>>
>>>> On Sun, Oct 16, 2016 at 6:18 AM, mwall <mw...@users.sourceforge.net>
>>>> wrote:
>>>>
>>>>> On Sunday, October 16, 2016 at 8:19:38 AM UTC-4, Tom Keffer wrote:
>>>>>>
>>>>>> ​Me too.​ What do you think of my theory that the console is
>>>>>> (occasionally) waiting more than 5 minutes to emit a LOOP packet?
>>>>>>
>>>>>
>>>>> the log indicates that the driver is getting data regularly.  take a
>>>>> look at the entries between some of the 10 minute add records.
>>>>>
>>>>> there is a yield just before each "next read in X second".  when the
>>>>> data are stale, the yielded packet contains only dateTime, usUnits,
>>>>> channel, sensor_id, rssi, sensor_battery, but no weather data.
>>>>>
>>>>
>>>> ​That should be enough to give the engine a chance to break the loop.
>>>>
>>>> Tim: I have attached an instrumented version of
>>>> engine.py
>>>>  that should shed some light on this mystery. Please set your old
>>>> version of
>>>> engine.py
>>>> aside, and replace it with this one. Assuming you download this version
>>>> into
>>>> ~/Downloads
>>>> , the process would be:
>>>>
>>>> ​cd /usr/share/weewx​/weewx
>>>> mv engine.py engine.py.orig
>>>> cp ~/Downloads/engine.py engine.py
>>>>
>>>>
>>>> Make sure debug=1, then restart weewx, then send the log from the
>>>> restart, through the first couple of reports (should take about 20
>>>> minutes). The log will be big, so just attach it as a file.
>>>>
>>>> -tk
>>>>
>>>>
>>>>
>>>> ​
>>>>
>>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/W8C-1CuFsik/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-16 Thread Tim Phillips 
New log attached after replacing the engine.py per instructions. Lots of 
"syslog" files attached in this thread, so I've renamed this log with 
appropriate changes- "new engine.py" in the file name

Tim. 

On Sunday, October 16, 2016 at 9:58:18 AM UTC-7, Tim Phillips wrote:
>
> Just followed your instructions and will post the new log file after it's 
> had a chance to run a while as suggested. 
>
> On Sunday, October 16, 2016 at 6:59:57 AM UTC-7, Tom Keffer wrote:
>>
>> On Sun, Oct 16, 2016 at 6:18 AM, mwall <mw...@users.sourceforge.net> 
>> wrote:
>>
>>> On Sunday, October 16, 2016 at 8:19:38 AM UTC-4, Tom Keffer wrote:
>>>>
>>>> ​Me too.​ What do you think of my theory that the console is 
>>>> (occasionally) waiting more than 5 minutes to emit a LOOP packet?
>>>>
>>>
>>> the log indicates that the driver is getting data regularly.  take a 
>>> look at the entries between some of the 10 minute add records.
>>>
>>> there is a yield just before each "next read in X second".  when the 
>>> data are stale, the yielded packet contains only dateTime, usUnits, 
>>> channel, sensor_id, rssi, sensor_battery, but no weather data.
>>>
>>
>> ​That should be enough to give the engine a chance to break the loop.
>>
>> Tim: I have attached an instrumented version of 
>> engine.py
>>  that should shed some light on this mystery. Please set your old version 
>> of 
>> engine.py
>> aside, and replace it with this one. Assuming you download this version 
>> into 
>> ~/Downloads
>> , the process would be:
>>
>> ​cd /usr/share/weewx​/weewx
>> mv engine.py engine.py.orig
>> cp ~/Downloads/engine.py engine.py
>>
>>
>> Make sure debug=1, then restart weewx, then send the log from the 
>> restart, through the first couple of reports (should take about 20 
>> minutes). The log will be big, so just attach it as a file.
>>
>> -tk
>>
>>
>>
>> ​
>>  
>>
>

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


syslog (new engine.py)
Description: Binary data

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-16 Thread Tim Phillips 
Just followed your instructions and will post the new log file after it's 
had a chance to run a while as suggested. 

On Sunday, October 16, 2016 at 6:59:57 AM UTC-7, Tom Keffer wrote:
>
> On Sun, Oct 16, 2016 at 6:18 AM, mwall  > wrote:
>
>> On Sunday, October 16, 2016 at 8:19:38 AM UTC-4, Tom Keffer wrote:
>>>
>>> ​Me too.​ What do you think of my theory that the console is 
>>> (occasionally) waiting more than 5 minutes to emit a LOOP packet?
>>>
>>
>> the log indicates that the driver is getting data regularly.  take a look 
>> at the entries between some of the 10 minute add records.
>>
>> there is a yield just before each "next read in X second".  when the data 
>> are stale, the yielded packet contains only dateTime, usUnits, channel, 
>> sensor_id, rssi, sensor_battery, but no weather data.
>>
>
> ​That should be enough to give the engine a chance to break the loop.
>
> Tim: I have attached an instrumented version of 
> engine.py
>  that should shed some light on this mystery. Please set your old version 
> of 
> engine.py
> aside, and replace it with this one. Assuming you download this version 
> into 
> ~/Downloads
> , the process would be:
>
> ​cd /usr/share/weewx​/weewx
> mv engine.py engine.py.orig
> cp ~/Downloads/engine.py engine.py
>
>
> Make sure debug=1, then restart weewx, then send the log from the restart, 
> through the first couple of reports (should take about 20 minutes). The log 
> will be big, so just attach it as a file.
>
> -tk
>
>
>
> ​
>  
>

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

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-15 Thread Tim Phillips 
No, I had turned debug back to 0 a while ago. I'll turn it back to 1 and
repost later.

​Tim​

​

On Sat, Oct 15, 2016 at 9:37 PM, gjr80  wrote:

> Was debug=1? If debug=1we should see what messages if any are coming in
> from the station. There are a lot of stale data entries but they seem to
> disappear in time.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/W8C-1CuFsik/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-15 Thread Tim Phillips 
Maybe I put it at ad oddball interval like 8 minutes and see what it does?

​Tim​



​
On Sat, Oct 15, 2016 at 7:38 PM, mwall <mw...@users.sourceforge.net> wrote:

> On Saturday, October 15, 2016 at 9:58:28 PM UTC-4, Tim Phillips wrote:
>>
>> So what do you guys think? Are the external sites just reporting a little
>> flakey or is weewx skipping uploads?  Check the PWS link and notice that is
>> takes either a 5 or 10 minute interval with seemingly no pattern.
>>
>
> tim,
>
> i'm still stumped.  your archive interval is 300s, and since there is no
> hardware logger, weewx will use record_generation=software.
>
> these are the 'add record' entries from your log posting for the pid 3225
> run.
>
> Oct 15 09:55:01 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 09:55:00 PDT (1476550500) to database 'weewx.sdb'
> Oct 15 09:55:01 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 09:55:00 PDT (1476550500) to daily summary in 'weewx.sdb'
> Oct 15 10:05:09 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:05:00 PDT (1476551100) to database 'weewx.sdb'
> Oct 15 10:05:09 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:05:00 PDT (1476551100) to daily summary in 'weewx.sdb'
> Oct 15 10:15:10 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:15:00 PDT (1476551700) to database 'weewx.sdb'
> Oct 15 10:15:10 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:15:00 PDT (1476551700) to daily summary in 'weewx.sdb'
> Oct 15 10:25:05 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:25:00 PDT (1476552300) to database 'weewx.sdb'
> Oct 15 10:25:05 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:25:00 PDT (1476552300) to daily summary in 'weewx.sdb'
> Oct 15 10:35:00 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:30:00 PDT (1476552600) to database 'weewx.sdb'
> Oct 15 10:35:00 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:30:00 PDT (1476552600) to daily summary in 'weewx.sdb'
> Oct 15 10:40:07 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:40:00 PDT (1476553200) to database 'weewx.sdb'
> Oct 15 10:40:07 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:40:00 PDT (1476553200) to daily summary in 'weewx.sdb'
> Oct 15 10:50:02 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:50:00 PDT (1476553800) to database 'weewx.sdb'
> Oct 15 10:50:02 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 10:50:00 PDT (1476553800) to daily summary in 'weewx.sdb'
> Oct 15 11:00:15 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:00:00 PDT (1476554400) to database 'weewx.sdb'
> Oct 15 11:00:15 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:00:00 PDT (1476554400) to daily summary in 'weewx.sdb'
> Oct 15 11:10:10 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:10:00 PDT (1476555000) to database 'weewx.sdb'
> Oct 15 11:10:10 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:10:00 PDT (1476555000) to daily summary in 'weewx.sdb'
> Oct 15 11:20:05 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:20:00 PDT (1476555600) to database 'weewx.sdb'
> Oct 15 11:20:05 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:20:00 PDT (1476555600) to daily summary in 'weewx.sdb'
> Oct 15 11:30:00 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:30:00 PDT (1476556200) to database 'weewx.sdb'
> Oct 15 11:30:00 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:30:00 PDT (1476556200) to daily summary in 'weewx.sdb'
> Oct 15 11:40:13 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:40:00 PDT (1476556800) to database 'weewx.sdb'
> Oct 15 11:40:13 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:40:00 PDT (1476556800) to daily summary in 'weewx.sdb'
> Oct 15 11:50:08 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:50:00 PDT (1476557400) to database 'weewx.sdb'
> Oct 15 11:50:08 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 11:50:00 PDT (1476557400) to daily summary in 'weewx.sdb'
> Oct 15 12:00:03 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 12:00:00 PDT (1476558000) to database 'weewx.sdb'
> Oct 15 12:00:03 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 12:00:00 PDT (1476558000) to daily summary in 'weewx.sdb'
> Oct 15 12:10:16 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 12:10:00 PDT (1476558600) to database 'weewx.sdb'
> Oct 15 12:10:16 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 12:10:00 PDT (1476558600) to daily summary in 'weewx.sdb'
> Oct 15 12:20:11 raspberrypi weewx[3225]: manager: added record 2016-10-15
> 12:

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-15 Thread Tim Phillips 
So what do you guys think? Are the external sites just reporting a little
flakey or is weewx skipping uploads?  Check the PWS link and notice that is
takes either a 5 or 10 minute interval with seemingly no pattern.

Tim

On Oct 15, 2016 6:36 PM, "vince" <vinceska...@gmail.com> wrote:

On Saturday, October 15, 2016 at 4:25:10 PM UTC-7, mwall wrote:
>
> On Saturday, October 15, 2016 at 4:27:47 PM UTC-4, Tim Phillips wrote:
>>
>> Attached the new (longer) log that's been going all day. I took a glance
>> at it and saw a few things that kept popping up and look out of the
>> ordinary:
>>
>> 1) "Oct 15 12:46:38 raspberrypi rsyslogd-2007: action 'action 17'
>> suspended, next retry is Sat Oct 15 12:48:08 2016 [try
>> http://www.rsyslog.com/e/2007 ]"
>>
>
> this is a bug (or misbehavior - depends who you ask) in debian on rpi if
> there is no /dev/xconsole
>
>
This is fixed in recent Raspbian, anything since may-2016 if I remember
correctly.
It's just an annoyance anyway, doesn't hurt anything.

-- 
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/weewx-user/W8C-1CuFsik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: [weewx-user] Re: External site reporting irregular timing schedule

2016-10-15 Thread Tim Phillips 
Just set record_generation=hardware to record_generation=software. We'll
see how that goes.

I have the interval set to (300) 5 minutes, but as you are seeing it
doesn't seem to be sticking to that.
​
Tim

On Sat, Oct 15, 2016 at 2:56 PM, Thomas Keffer  wrote:

> Good suggestion, and I'll be interested to see what happens once
> record_generation is set to software, but I don't think things are that
> simple. Sometimes the driver saves to the database every 5 minutes, and
> sometimes only every 10 minutes. If the issue was that the archive interval
> is wrong, it might not be the right interval, but it would be consistent.
>
> I'm thinking that there may be very long waits between LOOP packets
> occasionally, so the weewx engine does not get a chance to see if the
> archive interval has passed.
>
> I'm not familiar with the Acurite. What sort of interval should we
> expected between LOOP packets?
>
> -tk
>
> On Sat, Oct 15, 2016 at 1:47 PM, gjr80  wrote:
>
>> You have record_generation=hardware under [StdArchive] in weewx.conf but
>> I don't believe your weather station actually produces archive records.
>> Stop weewx, edit weewx.conf and set record_generation=software then start
>> weewx. See how that goes.
>>
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/W8C-1CuFsik/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: External site reporting irregular timing schedule

2016-10-15 Thread Tim Phillips 
Here's what looks like an issue for the standard report:

"Oct 15 09:40:06 raspberrypi weewx[754]: acurite: Found station at bus=001 
device=004
Oct 15 09:40:06 raspberrypi weewx[754]: manager: added record 2016-10-15 
09:40:00 PDT (1476549600) to database 'weewx.sdb'
Oct 15 09:40:06 raspberrypi weewx[754]: manager: added record 2016-10-15 
09:40:00 PDT (1476549600) to daily summary in 'weewx.sdb'
Oct 15 09:40:06 raspberrypi weewx[754]: reportengine: Running reports for 
latest time in the database.
Oct 15 09:40:06 raspberrypi weewx[754]: acurite: Found station at bus=001 
device=004
Oct 15 09:40:06 raspberrypi weewx[754]: reportengine: Running report 
StandardReport
Oct 15 09:40:06 raspberrypi weewx[754]: reportengine: Failed to read skin 
configuration file /etc/weewx/skins/Standard/skin.conf for report 
StandardReport: Invalid line ('[Extras') (matched as neither section nor 
keyword) at line 6.
Oct 15 09:40:06 raspberrypi weewx[754]:   Report ignored"

So, an issue with my skins. Bet it's the radar website. Must have formatted 
something wrong...

But that doesn't explain why external site reporting isn't happening on the 
5 min schedule. Unless the external sites (WU and PWS) servers aren't 
logging the data when it's being received?

Syslog is attached. Let me know if it should posted as text here in the 
thread. 

On Friday, October 14, 2016 at 9:57:44 PM UTC-7, gjr80 wrote:
>
> > Suggestions?
>
> Yes, show us the logs, that is where the answers will be. Stop weewx, make 
> whatever rapid fire changes you mentioned, set debug=1 in weewx.conf then 
> start weewx. Copy the log here from when weewx starts until at least 1 or 2 
> report cycles have completed. Only then will you get any meaningful 
> feedback as to what is (maybe) wrong.
>
> 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.
For more options, visit https://groups.google.com/d/optout.


syslog
Description: Binary data

[weewx-user] Re: External site reporting irregular timing schedule

2016-10-14 Thread Tim Phillips 
I'll turn off rapid fire and see what the deal is. The WU uploads before 
adding PWS today seemed intermittent, so maybe it was rapid fire causing 
that. I'm also not getting any updated info on my local LAN http page. I've 
donesomething...lol. This is what happens when I fix what ain't broken! 
I think I somehow moved the output file somewhere that was not the default 
location in the setup guide.

We've got a decent set of storms happening here in the NW and I was trying 
to get WU to upload data at quicker intervals. Suggestions?


On Friday, October 14, 2016 at 9:37:05 PM UTC-7, Andrew Milner wrote:
>
> Check your weewx log to see how often it is uploading to PWS.  Quite often 
> PWS and WU do not report in their tables all the uploads which they receive 
> - for reasons known only to them!
> PWS and WU are entwined in some way as far as I recall.  WU seek either 
> rapidfire OR archive records according to their website, but not both.  
> Weewx can only supply rapidfire for weatherstations that provide full data 
> in all LOOP records (eg Davis), and is not suitable for weather stations 
> which emit partial packets at the present time.
>
>
>
> On Saturday, 15 October 2016 06:38:07 UTC+3, Tim Phillips wrote:
>
>> Weewx is reporting to PWS every 10 minutes, where when I first set it up 
>> a few hours ago it was every 5 minutes. Any ideas what's going on here? I 
>> should note I also have it set to report to WUnderground and is set to 
>> Rapid Fire, in case that's an issue. 
>>
>>
>> <https://lh3.googleusercontent.com/-1wNzUSx3F9M/WAGkSSIStfI/ZZc/7e_UcoJhq9UuywafO2OfLuteA0Z3l2aaQCLcB/s1600/Clipboard01.jpg>
>>
>>

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

[weewx-user] External site reporting irregular timing schedule

2016-10-14 Thread Tim Phillips 


Weewx is reporting to PWS every 10 minutes, where when I first set it up a 
few hours ago it was every 5 minutes. Any ideas what's going on here? I 
should note I also have it set to report to WUnderground and is set to 
Rapid Fire, in case that's an issue. 



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

Re: [weewx-user] Re: Changing Apache WAN port- HTTP security?

2016-10-10 Thread Tim Phillips 
I'm OK with opening a port for FTP or a webcam but I try my best to make
sure it's a secure connection. Strong passwords, HTTPS if possible, using a
brand that's not off the Walmart discount shelf and MAC filtering if
possible.

I still won't put a webcam inside my house though. So that says something...

I just like the ability to control my security and know what's happening vs
blindly trusting some brand's server. There was a recent webcam breach
where the company inadvertently allowed access to ALL users video somehow.
Things like that are what keeps me tinkering on my own like this. Leaving
it up to someone else at some unknown "server" doesn't make me comfortable.
So, yeah, it goes beyond people simply not changing the default password.
Anyway, I'm just taking this as an opportunity to learn more.
​
​
T​im​

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

Re: [weewx-user] Re: Changing Apache WAN port- HTTP security?

2016-10-09 Thread Tim Phillips 
An excellent read. I wish they would market the device better to people
like me (us?) that require web security. I might have bought their product.
Might still, in fact, after reading that.

It's important to take some caution to adding and trusting IoT devices.

On Oct 9, 2016 6:42 PM, "Andrew Milner" <andrew.s.r.mil...@gmail.com> wrote:

> This tells you how the bridge works:
> http://moderntoil.com/?p=794
>
> It would appear to me that the bridge has no real need for security as
> such since it only transmits data to acurite web site from your weather
> station using POST commands.  It's security is controlled by your own
> router, and it would only respond to incoming data when it switched to
> update mode to update its firmware.
>
>
>
> On Monday, 10 October 2016 02:28:39 UTC+3, Tim Phillips wrote:
>
>> So I've totally misinterpreted what Apache does for the weewx
>> serviceI'm super new to this so I'm sorry you need to explain these
>> things like this. My WAN/IP education is limited to setting up a handful of
>> foscam's on WAN manually as well as doing a RPi webcam project
>> (RPi-Cam-Interface) which worked well.
>>
>> I ALWAYS set a custom password on my stuff and change the username if
>> possible. Actually, I decided to use my RPi as a weather station server
>> because the Acurite "bridge" accessory gave no indication of how their
>> security works, which I disliked. So I took it as an opportunity to learn
>> all about it, hopefully via this project as a starting point. I was not
>> keen on just plugging in their bridge accessory to my router and thinking
>> that's A-OK.
>>
>>
>> I appreciate the clarification!
>>
>>
>>
>> On Sunday, October 9, 2016 at 12:28:56 PM UTC-7, vince wrote:
>>>
>>> On Sunday, October 9, 2016 at 10:10:00 AM UTC-7, Tim Phillips wrote:
>>>>
>>>> My understanding of how my Weewx on my Pi is:
>>>>
>>>> Weewx running as a daemon (service/background process).
>>>>
>>>
>>> almost certainly yes
>>>
>>>
>>>> Apache2 is the web server so a user can access the Weewx service
>>>> (daemon) from a browser on LAN/WAN (if port forwarded).
>>>>
>>>
>>> no.  Apache does not talk to the weewx daemon at all.
>>>
>>> It listens on the port(s) you have it configured to listen on, commonly
>>> http (tcp/80), and makes available whatever data or programs apache is
>>> configured to permit (typically, just a document tree).  Sometimes your web
>>> pages are executable (php typically) but most times not. Initially it's set
>>> up to just return data.
>>>
>>> The default weewx output from the default skins is just datahtml
>>> files and image files.  Other skins might have executable php content
>>> (saratoga templates to name one).  Again, the apache configuration must be
>>> set up to permit php files to execute, and there is additional software
>>> you'd install to do that.  There are a lot of apache-related packages.
>>>
>>>
>>>  - Apache2 runs in the background and is the "gatekeeper" to the
>>>> services that request a browser-based information request.
>>>>
>>>
>>> not really.   It's a daemon that listens on the port(s) it is configured
>>> for, and does what it's configured to do based on the apache config
>>> file(s).   Again, usually it just provides a way to read files using a
>>> remote web browser kind of interface, from a well-defined directory on the
>>> filesystem.
>>>
>>>   - Services get access *through *the Apache server to the
>>>> destination port it's assigned to. In Weewx's case it's "/weewx".
>>>>
>>>>
>>> no.   Apache makes some files (in locations defined by the apache config
>>> files) on the pi accessible via http or https, assuming those files are
>>> accessible by the non-privileged account the apache daemon runs as.
>>>
>>>
>>>> BUT, if the port to Apache is 80, and that directs to Weewx, then how
>>>> would I set up multiple WAN access, say if I had a webcam service running
>>>> on the same Pi?
>>>>
>>>>
>>> Again, apache doesn't really 'direct' to weewx, it can make
>>> weewx-generated output files available, if weewx puts it in a place apache
>>> is configured to know about, and if the files are set with the right
>>> permissions so the apache daemon can read the

[weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips 
Looks like it's all working now. Thanks!

On Saturday, October 8, 2016 at 9:47:07 PM UTC-7, Tim Phillips wrote:
>
> I actually had a fun time learning by "doing," as it's the way that I 
> learn things the best, for better or worse. This is a good project for me 
> as I know what "sudo" does and knew enough to be able to get leafpad (text 
> editor) to edit the config file as an admin. I thought I was doing 
> something wrong by having to do it this way. I didn't see it anywhere in 
> the Wiki that this was the only way to edit the config file. The command in 
> the wiki only would edit the first few generic items like elevation and 
> model/brand. In fact, the default package installed in the GUI for the 
> latest Raspbian Jessie never asked me to configure anything like I expected 
> from reading the Wiki. It just installed and didn't ask me a thing. This 
> entire time, I thought I installed it in the wrong place. Will I need to 
> whitelist anything?
>
> Still not showing up, though...
> Added my WU URL to the [StdRESTful] [[Station Registry]] section and it is 
> set to "true"
> Added my LAN IP 192.168.x.x:weewx to the Station_url in [Station]
>
>
>
> On Saturday, October 8, 2016 at 9:27:29 PM UTC-7, mwall wrote:
>>
>> On Sunday, October 9, 2016 at 12:18:29 AM UTC-4, Tim Phillips wrote:
>>>
>>> I spent the day trying to get this to work at all am quite proud of it 
>>> "just" working with WU's site.
>>>
>>
>> nice!  hopefully most of that time was general learning about pi and 
>> linux rather than fighting weewx.  if you were battling weewx, please let 
>> us know so we can fix the sharp edges so the next person does not get as 
>> many scars.
>>  
>>
>>> So what you're saying is that I should set the "Station" for my personal 
>>> use, using my WU site and I can use the "StdRESTful" for my private use, 
>>> using my WAN IP address?
>>>
>>
>> make the Station.station_url your lan-accessible url, and make 
>> StdRESTful.StationRegistry.station_url your publicly-accessible WU url.
>>  
>>
>>> **I had a hard enough time trying to edit the conf. file since the 
>>> package got installed to my "etc" folder on my RPi3 and I ended up using 
>>> "sudo leafpad /etc/weewx/weewx.conf" to edit my config file. I'm sure I 
>>> went wrong somewhere but that's the workaround I eventually found. Does 
>>> that seem right?
>>>
>>
>> you got it.
>>
>> there are many editors, including nano, vim, vi, emacs, or even ed.  none 
>> of them can edit the system configuration files (the files in /etc) unless 
>> you run them as root.  and as you figured out, that is what sudo does.
>>
>> m 
>>
>

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

Re: [weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips 
Looks like it's working now. Thanks for the help! Really had a fun time
doing this today!

- - - - - - - - - -
*Tim Phillips*
*Cell: 425-765-1631*

On Sat, Oct 8, 2016 at 9:27 PM, mwall <mw...@users.sourceforge.net> wrote:

> On Sunday, October 9, 2016 at 12:18:29 AM UTC-4, Tim Phillips wrote:
>>
>> I spent the day trying to get this to work at all am quite proud of it
>> "just" working with WU's site.
>>
>
> nice!  hopefully most of that time was general learning about pi and linux
> rather than fighting weewx.  if you were battling weewx, please let us know
> so we can fix the sharp edges so the next person does not get as many scars.
>
>
>> So what you're saying is that I should set the "Station" for my personal
>> use, using my WU site and I can use the "StdRESTful" for my private use,
>> using my WAN IP address?
>>
>
> make the Station.station_url your lan-accessible url, and make
> StdRESTful.StationRegistry.station_url your publicly-accessible WU url.
>
>
>> **I had a hard enough time trying to edit the conf. file since the
>> package got installed to my "etc" folder on my RPi3 and I ended up using
>> "sudo leafpad /etc/weewx/weewx.conf" to edit my config file. I'm sure I
>> went wrong somewhere but that's the workaround I eventually found. Does
>> that seem right?
>>
>
> you got it.
>
> there are many editors, including nano, vim, vi, emacs, or even ed.  none
> of them can edit the system configuration files (the files in /etc) unless
> you run them as root.  and as you figured out, that is what sudo does.
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/os70a52yDPc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips 
I actually had a fun time learning by "doing," as it's the way that I learn 
things the best, for better or worse. This is a good project for me as I 
know what "sudo" does and knew enough to be able to get leafpad (text 
editor) to edit the config file as an admin. I thought I was doing 
something wrong by having to do it this way. I didn't see it anywhere in 
the Wiki that this was the only way to edit the config file. The command in 
the wiki only would edit the first few generic items like elevation and 
model/brand. In fact, the default package installed in the GUI for the 
latest Raspbian Jessie never asked me to configure anything like I expected 
from reading the Wiki. It just installed and didn't ask me a thing. This 
entire time, I thought I installed it in the wrong place. Will I need to 
whitelist anything?

Still not showing up, though...
Added my WU URL to the [StdRESTful] [[Station Registry]] section and it is 
set to "true"
Added my LAN IP 192.168.x.x:weewx to the Station_url in [Station]



On Saturday, October 8, 2016 at 9:27:29 PM UTC-7, mwall wrote:
>
> On Sunday, October 9, 2016 at 12:18:29 AM UTC-4, Tim Phillips wrote:
>>
>> I spent the day trying to get this to work at all am quite proud of it 
>> "just" working with WU's site.
>>
>
> nice!  hopefully most of that time was general learning about pi and linux 
> rather than fighting weewx.  if you were battling weewx, please let us know 
> so we can fix the sharp edges so the next person does not get as many scars.
>  
>
>> So what you're saying is that I should set the "Station" for my personal 
>> use, using my WU site and I can use the "StdRESTful" for my private use, 
>> using my WAN IP address?
>>
>
> make the Station.station_url your lan-accessible url, and make 
> StdRESTful.StationRegistry.station_url your publicly-accessible WU url.
>  
>
>> **I had a hard enough time trying to edit the conf. file since the 
>> package got installed to my "etc" folder on my RPi3 and I ended up using 
>> "sudo leafpad /etc/weewx/weewx.conf" to edit my config file. I'm sure I 
>> went wrong somewhere but that's the workaround I eventually found. Does 
>> that seem right?
>>
>
> you got it.
>
> there are many editors, including nano, vim, vi, emacs, or even ed.  none 
> of them can edit the system configuration files (the files in /etc) unless 
> you run them as root.  and as you figured out, that is what sudo does.
>
> m 
>

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

[weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips 
That's a really good point. I never thought of just using the weather 
underground URL. I'll give that a shot and see if it works. 

I spent the day trying to get this to work at all am quite proud of it 
"just" working with WU's site. I'm super new to RPi and Linux so I 
appreciate the help. 

So what you're saying is that I should set the "Station" for my personal 
use, using my WU site and I can use the "StdRESTful" for my private use, 
using my WAN IP address?

**I had a hard enough time trying to edit the conf. file since the package 
got installed to my "etc" folder on my RPi3 and I ended up using "sudo 
leafpad /etc/weewx/weewx.conf" to edit my config file. I'm sure I went 
wrong somewhere but that's the workaround I eventually found. Does that 
seem right?



On Saturday, October 8, 2016 at 9:02:01 PM UTC-7, mwall wrote:
>
> hi tim,
>
> the log should tell you what is happening.  most likely the registration 
> is failing because there is no server_url
>
> why not use your wundergound url?  then change to the station's public web 
> page when (if) you want to publish that one.
>
> btw, you can set the root level server_url to your station's local web 
> page, and the registration url to whatever you want the public to see.  for 
> example:
>
> [Station]
> ...
> station_url = http://private.lan/weewx
>
> [StdRESTful]
> [[StationRegistry]]
> register_this_station = True
> station_url = http://public.com/weewx
>
> m
>

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