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

Yes, although it's not necessary to do the first 'mv.' If the version on your desktop is truly the original engine, then sudo /etc/init.d/weewx stop cd /usr/share/weewx/weewx sudo cp ~/Desktop/engine.py engine.py sudo /etc/init.d/weewx start If you're not sure, you can download the v3.6.0

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

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

[weewx-user] Chilling hours

Hello, I use the NOAA reports as a summary for my stations and now I would like to add an extra column called "Chilling hours". ( https://en.wikipedia.org/wiki/Chilling_requirement) Is it possible to create this new "tag"? Anyone done this before? Should I follow the same idea as in the

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

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 wrote: > Do I need to put the original engine.py back into the folder or do I leave > what you gave me in

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

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 wrote: > Your value of archive_delay is set to 300 seconds. Change it to 15 seconds > and all your problems will go away. >

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

Indeed. I've removed it from weewx.conf, and included a check in engine.py for sane values. -tk On Sun, Oct 16, 2016 at 11:57 AM, mwall wrote: > On Sunday, October 16, 2016 at 2:30:00 PM UTC-4, Tom Keffer wrote: >> >> Your value of archive_delay is set to 300

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

On Sunday, October 16, 2016 at 2:30:00 PM UTC-4, Tom Keffer wrote: > > Your value of archive_delay is set to 300 seconds. Change it to 15 seconds > and all your problems will go away. > doh! occam's razor cuts again -- You received this message because you are subscribed to the Google

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

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 wrote: > New log attached after replacing the engine.py per instructions. Lots of >

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

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

Re: [weewx-user] Re: Errors during the report generation

Pier sent his configuration file, weewx.conf to me. As suspected, it includes a BOM ("byte order marker") at the beginning, which signaled to the configuration parser that the file was encoded in utf-8. So, when the parser read it, it automatically converted it to Unicode. Hence, when

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

can you post the section of log from the restart until the first archive record is created - the log you provided does not run from the start of weewx .. On Sunday, 16 October 2016 19:43:38 UTC+3, Tim Phillips wrote: > Debug set to =1 last night around the time you posted this response.

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

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,

Re: [weewx-user] Re: Errors during the report generation

Thanks, Pier. The Unicode seems to be coming from weewx.conf. In particular, HTML_ROOT, SKIN_ROOT, and skin all seem to be in unicode, which would suggest that they are encoded as utf-8 within your copy of weewx.conf. Could you please send weewx.conf to me privately? While you could edit it to

Re: [weewx-user] Rebuild stats database

Thanks again for your kind support. I'm trying a totally fresh install of weewx (3.x) on a totally fresh raspbian in a raspberry pi. And include all possible old data in new weewx.sdb in order to weewx can rebuild personalized yearly NOAA reports. Default temperature ranges are pretty useless

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

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

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

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

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

On Sat, Oct 15, 2016 at 7:38 PM, mwall wrote: > > i'm stumped. > > ​Me too.​ What do you think of my theory that the console is (occasionally) waiting more than 5 minutes to emit a LOOP packet? -tk -- You received this message because you are subscribed to the

Re: [weewx-user] Rebuild stats database

The NOAA data is a small subset of the data in the daily summaries. It contains only temperature, rain, and wind. It does not include other observation types. Furthermore, you would still be missing the archive data, which are used for some calculations. What are you trying to do? You could write

[weewx-user] There is a report on temperature-time to be used for agricultural pest and disease control?

Dear colleagues, I was wondering if somebody has prepared a report, similar to the HEAT/COOL DEG DAYS in NOAA files, to show the degrees x time above/below a customizable threshold temperature. The main idea is to use that information for agricultural pest and disease control, since there

Re: [weewx-user] Re: Version 3.6.1

On Fri, 14 Oct 2016 04:51:37 -0700 (PDT) mwall wrote: > On Friday, October 14, 2016 at 6:36:25 AM UTC-4, Liz wrote: > > > > Just trying the upgrade through this system. I have got to diff the > > files and find the essential parts of the weewx.conf that I have to >

[weewx-user] Re: Extract maximum value of an observation from loop packet

Thanks Tom and Matt for your prompt responses. Apologies - I probably didn't quite make my intention clear. I'm reading a sensor via OWFS, and am hoping to get weewx to only use the maximum value measured during any 5-minute archive interval. Going on from Tom's post, I want to make sure the