[weewx-user] Belchertown added ssl - mqtt stuck "connecting"

[DaveStLou]

I recently added ssl to my website oakvillewx.com. Now my mqtt data feed is 
stuck saying "Connecting to weather station real time data" in all browser 
types. 

I found references on the forum to using debugger in the browser. I can get 
that but I don't know how to use it to figure out what's happening. 

Appreciate help on troubleshooting this. Thanks!

-- 
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/4a1c677e-7d6b-460a-a419-90d12c01b7d6n%40googlegroups.com.

[weewx-user] Re: wee_import from WD logs fails

[Peter Süß]

Hi Gary,

today my Raspberry 4 arrived, which will hopefully be my long-running 
weather computer.
I tried to import all my data on Pi3. It worked back for about 8 years, but 
then the performance crashed into hell.
The import of one year took about 1 week and was getting worse.

Now I'm starting it all over on a fresh install and report, what will be 
the result.

Peter
gjr80 schrieb am Montag, 1. Februar 2021 um 23:28:04 UTC+1:

> Hi Peter,
>
> On Tuesday, 2 February 2021 at 06:03:36 UTC+10 peter.su...@gmail.com 
> wrote:
>
>> Hey Gary,
>> its looking perfect. I just separated the logs for each year and right 
>> now I am testing the 6th year in a row, doing a quick dry-run.
>> The script is finding some duplicates, but it looks like every complete 
>> year from 01/01 to 12/31 should be imported into the database.
>>
>
> That is interesting, the screen output you posted originally clearly 
> showed an error decoding a date-time, I am surprised that re-arranging the 
> log files fixed that. The first person that trialled the WD import module 
> was in a similar boat to you; they had many years of WD data and when they 
> first tried to import the data they did it in one run and not only did it 
> take many hours but wee_import eventually ground to a halt and crashed 
> (the exact details escape me). So importing/processing a year at a time may 
> be more manageable and safer.
>
> The duplicates issue is not uncommon, the few suites of WD logs I have 
> worked on all contained the odd duplicate date-time. wee_import will 
> simply ignore the duplicates, the  only issue is when the data for each 
> duplicate is different. Probably not going to make too much difference over 
> 15 years of data at one minute intervals.
>
> One more question from my side: Would you prefer a MySQL database with all 
>> this mass of data?
>>
>  
> I think the consensus is that unless you have good reason to use 
> MySQL/MariaDB stick with SQLite. SQLite is faster and simpler to 
> backup/restore. SQLite will easy handle all of your 15 years of data.
>  
> 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/d6822694-7e91-42a2-b2d4-b661bf376b49n%40googlegroups.com.

[weewx-user] WeeWx and time

[Steve Sykes]

I have had to change the server I am using for WeeWx 4.2.0 to GMT. I have 
checked the Vantage Pro2 weather station and it is also set to GMT. As soon 
as I changed the time the WeeWx web page stopped updating. I have tried 
restarting WeeWx and running it via command line. It is running normally 
but still no webpage updates. Wunderground is also not getting updated so 
it is not just the local page. If I set the server back to EST, everything 
works fine.
Anyone have an idea to fix this?

73
Steve KD2OM

-- 
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/80a46d95-cefc-4247-8c8a-67799386b7d0n%40googlegroups.com.

[weewx-user] Customising NOAATable

[Auchtermuchty Weather]

I much prefer the output of NOAATable for making the NOAA reports available.

However my template where I want this to appear is creating a Dokuwiki 
Page, so if the name in the link ends with '.txt' it looks for a file 
ending in '.txt.txt'.

I have it working with the drop-downs as per the header in the Standard 
website by not appending the '.txt' in the Javascript that loads the page.

What I'd like to do is customise NOAATable so the link is missing the 
'.txt' - I'd rather not write my own version of it if possible.

But I've searched & searched and can't find where & how it's implemented.  

-- 
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/79992f9a-7079-42bb-bb20-9df8fd088fbdn%40googlegroups.com.

Re: [weewx-user] Customising NOAATable

[Tom Keffer]

I'm not sure what you're asking.

If you're asking how to customize the Javascript, it depends on the skin.
For the "Standard" skin, it's in the template itself, index.html.tmpl. Just
modify the template. For the "Seasons" skin, it's in seasons.js.

If you're asking how the name of the generated file is set, it's the
template name minus the ".tmpl" at the end. So, if you don't want the
".txt" suffix, just rename the NOAA templates.

Does that answer your question?

On Mon, Feb 15, 2021 at 6:45 AM Auchtermuchty Weather 
wrote:

> I much prefer the output of NOAATable for making the NOAA reports
> available.
>
> However my template where I want this to appear is creating a Dokuwiki
> Page, so if the name in the link ends with '.txt' it looks for a file
> ending in '.txt.txt'.
>
> I have it working with the drop-downs as per the header in the Standard
> website by not appending the '.txt' in the Javascript that loads the page.
>
> What I'd like to do is customise NOAATable so the link is missing the
> '.txt' - I'd rather not write my own version of it if possible.
>
> But I've searched & searched and can't find where & how it's implemented.
>
> --
> 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/79992f9a-7079-42bb-bb20-9df8fd088fbdn%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/CAPq0zED6iwNN8ka3vH_oYzWJ2nTYSdK_HQAx%2BeP4WEs2Um_tOw%40mail.gmail.com.

[weewx-user] acurite 02032c station pressure calibration?

[Christopher Maness]

Is station pressure calibration possible with this device?  If not, can 
it be compensated for in the config file?  In other words, having the 
correct BP reading with the correct elevation. I do realize that the 
altitude set in WeeWX affects the BP, and I imagine it is doing a little 
calculation based on a station pressure field polled from the unit.  
Feel free to point out errors in my thinking.


Thank you,

Chris KQ6UP

--
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/194deb50-330b-cd71-7540-a2a949137ffb%40gmail.com.


OpenPGP_0x55BE65AD1B41D696.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [weewx-user] acurite 02032c station pressure calibration?

[p q]

I have an Acurite 5in1 and I haven't found how to calibrate the barometer
in the unit, but I do calibrate it in Weewx. Use the StdCalibrate section
in weewx.conf under where it says foo=foo+0.2

I have pressure = pressure - 0.11
I found this number by trial an error, matching my reading vs what I see on
the nearest reliable source (regional airport) over a few days.

On Mon, Feb 15, 2021 at 7:07 AM Christopher Maness <
christopher.man...@gmail.com> wrote:

> Is station pressure calibration possible with this device?  If not, can
> it be compensated for in the config file?  In other words, having the
> correct BP reading with the correct elevation. I do realize that the
> altitude set in WeeWX affects the BP, and I imagine it is doing a little
> calculation based on a station pressure field polled from the unit.
> Feel free to point out errors in my thinking.
>
> Thank you,
>
> Chris KQ6UP
>
> --
> 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/194deb50-330b-cd71-7540-a2a949137ffb%40gmail.com
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM20_DjcAfxu_ehUF41VhsSUuG1qah4LkKs233LOkXiSKAQ%40mail.gmail.com.

Re: [weewx-user] WeeWx and time

[Tom Keffer]

You didn't post a log, but I'm guessing that jumping around in time
corrupted the logger's memory. See the section *WeeWX generates HTML pages,
but it does not update them
*
in the Wiki.

On Mon, Feb 15, 2021 at 6:43 AM Steve Sykes  wrote:

> I have had to change the server I am using for WeeWx 4.2.0 to GMT. I have
> checked the Vantage Pro2 weather station and it is also set to GMT. As soon
> as I changed the time the WeeWx web page stopped updating. I have tried
> restarting WeeWx and running it via command line. It is running normally
> but still no webpage updates. Wunderground is also not getting updated so
> it is not just the local page. If I set the server back to EST, everything
> works fine.
> Anyone have an idea to fix this?
>
> 73
> Steve KD2OM
>
> --
> 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/80a46d95-cefc-4247-8c8a-67799386b7d0n%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/CAPq0zEAkvZ_%2BfkQkwA47rGAogKSQvFF1J7G5PBuiBmFO1WaVZg%40mail.gmail.com.

[weewx-user] Re: update identifier for HIDEKI-wind and hideki rain to the new style SDR.

[Giuseppe Saia]

good evening michael, sorry if I answer you just now. in the meantime, 
thank you very much for your suggestion.
when i use the suggested option -M oldmodel i don't recognize hidekiTS04 
and acurite 6045M sensors
this is because I have replaced the sdr.py file created by andy to 
recognize the two sensors mentioned above.
could you please work if you can on the sdr.py file that I attach for the 
hideki wind and hideki rain sensors?

Il giorno domenica 7 febbraio 2021 alle 15:54:31 UTC+1 Michael ha scritto:

> Hi Giuseppe,
>
> which cmd are you using in your weewx.config?
> In my case 
> cmd = /usr/local/bin/rtl_433 -f 433.92M -M utc -F json -G -M oldmodel
> works fine. 
>
> Michael
>
>
>>
>> thank you all
>>
>>

-- 
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/5f049eb1-be59-488d-9eef-da70eb1b122cn%40googlegroups.com.
#!/usr/bin/env python
# Copyright 2016-2020 Matthew Wall
# Distributed under the terms of the GNU Public License (GPLv3)
"""
Collect data from stl-sdr.  Run rtl_433 on a thread and push the output onto
a queue.

The SDR detects many different sensors and sensor types, so this driver
includes a mechanism to filter the incoming data, and to map the filtered
data onto the weewx database schema and identify the type of data from each
sensor.

Sensors are filtered based on a tuple that identifies uniquely each sensor.
A tuple consists of the observation name, a unique identifier for the hardware,
and the packet type, separated by periods:

  ..

The filter and data types are specified in a sensor_map stanza in the driver
stanza.  For example:

[SDR]
driver = user.sdr
[[sensor_map]]
inTemp = temperature.25A6.AcuriteTowerPacket
outTemp = temperature.24A4.AcuriteTowerPacket
rain_total = rain_total.A52B.Acurite5n1Packet

If no sensor_map is specified, no data will be collected.

The deltas stanza indicates which observations are cumulative measures and
how they should be split into delta measures.

[SDR]
...
[[deltas]]
rain = rain_total

In this case, the value for rain will be a delta calculated from sequential
rain_total observations.

To identify sensors, run the driver directly.  Alternatively, use the options
log_unknown_sensors and log_unmapped_sensors to see data from the SDR that are
not yet recognized by your configuration.

[SDR]
driver = user.sdr
log_unknown_sensors = True
log_unmapped_sensors = True

The default for each of these is False.

Eventually we would prefer to have all rtl_433 output as json.  Unfortunately,
many of the rtl_433 decoders do not emit this format yet (as of January 2017).
So this driver is designed to look for json first, then fall back to single-
or multi-line plain text format.

WARNING: Handling of units and unit systems in rtl_433 is a mess, but it is
getting better.  Although there is an option to request SI units, there is no
indicate in the decoder output whether that option is respected, nor does
rtl_433 specify exactly which SI units are used for various types of measure.
There seems to be a pattern of appending a unit label to the observation name
in the JSON data, for example 'wind_speed_mph' instead of just 'wind_speed'.
"""

from __future__ import with_statement
from calendar import timegm
try:
# Python 3
import queue
except ImportError:
# Python 2:
import Queue as queue
import fnmatch
import os
import re
import subprocess
import threading
import time

try:
import cjson as json
setattr(json, 'dumps', json.encode)
setattr(json, 'loads', json.decode)
except (ImportError, AttributeError):
try:
import simplejson as json
except ImportError:
import json

import weewx.drivers
import weewx.units
from weeutil.weeutil import tobool

try:
# New-style weewx logging
import weeutil.logger
import logging
log = logging.getLogger(__name__)

def logdbg(msg):
log.debug(msg)

def loginf(msg):
log.info(msg)

def logerr(msg):
log.error(msg)

except ImportError:
# Old-style weewx logging
import syslog

def logmsg(level, msg):
syslog.syslog(level, 'sdr: %s: %s' %
  (threading.currentThread().getName(), msg))

def logdbg(msg):
logmsg(syslog.LOG_DEBUG, msg)

def loginf(msg):
logmsg(syslog.LOG_INFO, msg)

def logerr(msg):
logmsg(syslog.LOG_ERR, msg)

DRIVER_NAME = 'SDR'
DRIVER_VERSION = '0.79'

# The default command requests json output from every decoder
# Use the -R option to indicate specific decoders

# -q  - suppress non-data messages (for older versions of rtl_433)
# -M utc  - print timestamps in UTC (-U for older versions of rtl_433)
# -F json - emit data in json format (not al

[weewx-user] Added time to produce report on Ver 4.3

[philip....@gmail.com]

Hi
I upgraded from v4.1.1 to v4.4 and noticed in the logs that a report took 
36 seconds to generate where it use to be only 1 second.
Starting back from v4.1.1 I found that the extra time started when I 
upgraded  from v4.2 to v4.3.
Im using a Pi4 and on a Pi3 the time was over 70 seconds.
After eliminating various pieces of code I find that the line
#set $min1 = $day.rain.sum.inch.format($WM, add_label=False) was causing 
the extra time.
The following is an extract and not the full code but as the NOOA report 
uses something similar and that works ok Im thinking that the data_binding 
is perhaps the cause or have I got the code wrong and was just lucky in 
older versions.

#for $day in $month($data_binding='sun_binding').days 
=
#set $min1 = $day.rain.sum.inch.format($WM, add_label=False)
===
===
#end for
Just wondered what changed in v4.3 as v4.2 work perfectly

-- 
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/9a1f1311-b9a2-4f09-9349-7eaddc54ca4dn%40googlegroups.com.

Re: [weewx-user] Added time to produce report on Ver 4.3

[Tom Keffer]

Not much information here, but I am not aware of any changes that would
cause this.

What is the nature of the binding 'sun_binding'? Is it a sqlite database?
MySQL on a remote server?

I assume the placeholder $WM is a simple formatting string.

How about a log? Set debug=1, restart weewxd, then post the log through the
first reporting cycle. Or, if it's easier, you can use wee_reports.


On Mon, Feb 15, 2021 at 9:02 AM philip@gmail.com <
philip.c.ow...@gmail.com> wrote:

> Hi
> I upgraded from v4.1.1 to v4.4 and noticed in the logs that a report took
> 36 seconds to generate where it use to be only 1 second.
> Starting back from v4.1.1 I found that the extra time started when I
> upgraded  from v4.2 to v4.3.
> Im using a Pi4 and on a Pi3 the time was over 70 seconds.
> After eliminating various pieces of code I find that the line
> #set $min1 = $day.rain.sum.inch.format($WM, add_label=False) was causing
> the extra time.
> The following is an extract and not the full code but as the NOOA report
> uses something similar and that works ok Im thinking that the data_binding
> is perhaps the cause or have I got the code wrong and was just lucky in
> older versions.
>
> #for $day in $month($data_binding='sun_binding').days
> =
> #set $min1 = $day.rain.sum.inch.format($WM, add_label=False)
> ===
> ===
> #end for
> Just wondered what changed in v4.3 as v4.2 work perfectly
>
> --
> 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/9a1f1311-b9a2-4f09-9349-7eaddc54ca4dn%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/CAPq0zEAe3CvYtqpOYuv1yO6UsmR7WMPBJGREY0EwR%3DC4Eze4kQ%40mail.gmail.com.

RE: [weewx-user] Re: weewx-wd/Saratoga Template - datenotresolving/depicting properly

[Tim Lambert]

Gary,

I un-installed the original install of WeeWX-WD v1.0.3 and installed WeeWX-WD 
v2.1.3 – the date issue has been resolved and is presenting properly on the 
Saratoga template.

Thanks again!

Regards,

Tim

From: Tim Lambert
Sent: Sunday, February 14, 2021 8:51 PM
To: weewx-user@googlegroups.com
Subject: RE: [weewx-user] Re: weewx-wd/Saratoga Template - 
datenotresolving/depicting properly

Many Thanks for the quick response.

If we don’t thaw out here (south of Portland, OR, where we received over 1” of 
ice, which has caused considerable tree damage on my property) I’ll have 
something to play with tomorrow and report back.   Otherwise I’ll circle back 
later in the week.

Thanks again!

Tim

Sent from Mail for Windows 10

From: gjr80
Sent: Sunday, February 14, 2021 7:50 PM
To: weewx-user
Subject: [weewx-user] Re: weewx-wd/Saratoga Template - date 
notresolving/depicting properly

Tim,

Unfortunately the holes in the cheese all lined up for you and resulted in a 
broken clientraw.txt being generated. If no weather service is specified under 
[Weewx-WD] [[Supplementary]] in weewx.conf WeeWX-WD use some default values for 
a number of fields in various templates, including clientraw.txt.tmpl. 
Unfortunately clientraw.txt.tmpl had a bug that formatted one of these defaults 
incorrectly, and as clientraw.txt is a simple space delimited text field this 
threw off all fields after the problem field in clientraw.txt. Consequently on 
your site you would see some values being updated correctly on your site but 
some would be incorrect.

I have fixed the bug and released WeeWX-WD v2.1.3. To upgrade just download the 
v2.1.3 extension package from GitHub, install v2.1.3 with wee_extension and 
restart WeeWX. After the first report cycle things should come good. If not 
please let me know.

Gary
On Monday, 15 February 2021 at 06:55:34 UTC+10 tim lambert wrote:
weeWX v4.4.0 (installed using setup.py method)
Raspberry Pi 4 (32-bit OS)

I recently installed wee-wd (https://github.com/weewx/weewx/wiki/weewx-wd) 
without issue.

When I stand up the Saratoga Template 
(http://www.tslllc.com/korsherw28/weewx/mainconsole/wxindex.php) the date stamp 
on the header is simply showing a numeric value (the time stamp is correct).  
The same is happening with the date directly under the radar.

The value that is being displayed for the date is the same value that is 
showing in the clientraw.txt file generated by the weewx-wd plugin/skin for 
weewx.

Any ideas as to the underlying issue and how to resolve -- noting I'm simply 
looking for the date to be in the format of m/d/Y.

Thanks in advance!

- Tim

-- 
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/0fEg9TuulT4/unsubscribe.
To unsubscribe from this group and all its topics, 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/720b16bd-8b4b-42d7-987c-3d41e5c4d039n%40googlegroups.com.

-- 
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/0fEg9TuulT4/unsubscribe.
To unsubscribe from this group and all its topics, 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/6029fdd4.1c69fb81.bda7f.4318SMTPIN_ADDED_MISSING%40gmr-mx.google.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/602ab751.1c69fb81.ce64b.74c7SMTPIN_ADDED_MISSING%40gmr-mx.google.com.

Re: [weewx-user] Customising NOAATable

[Auchtermuchty Weather]

The output files need to have '.txt' and the end, but the links to them 
mustn't include it so they fit the DokuWiki way of doing things.  By 
default they do and I can't find where that code is generated to amend it.


On Monday, 15 February 2021 at 14:56:10 UTC tke...@gmail.com wrote:

> I'm not sure what you're asking.
>
> If you're asking how to customize the Javascript, it depends on the skin. 
> For the "Standard" skin, it's in the template itself, index.html.tmpl. Just 
> modify the template. For the "Seasons" skin, it's in seasons.js.
>
> If you're asking how the name of the generated file is set, it's the 
> template name minus the ".tmpl" at the end. So, if you don't want the 
> ".txt" suffix, just rename the NOAA templates.
>
> Does that answer your question?
>
> On Mon, Feb 15, 2021 at 6:45 AM Auchtermuchty Weather  
> wrote:
>
>> I much prefer the output of NOAATable for making the NOAA reports 
>> available.
>>
>> However my template where I want this to appear is creating a Dokuwiki 
>> Page, so if the name in the link ends with '.txt' it looks for a file 
>> ending in '.txt.txt'.
>>
>> I have it working with the drop-downs as per the header in the Standard 
>> website by not appending the '.txt' in the Javascript that loads the page.
>>
>> What I'd like to do is customise NOAATable so the link is missing the 
>> '.txt' - I'd rather not write my own version of it if possible.
>>
>> But I've searched & searched and can't find where & how it's 
>> implemented.  
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/79992f9a-7079-42bb-bb20-9df8fd088fbdn%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/8efe627d-02a3-498b-9148-9552721f6127n%40googlegroups.com.

[weewx-user] Cheetah Generator Errors

[Parker Lohrenz]

My charts have stopped updating, though the data still is coming in from 
the weather station, and is getting posted externally and MQTT.  Any wisdom 
on what could be going awry?

Hardware is Acurite 01536 connected USB to Raspberry pi ZeroW

The direct weewx webserver is not public, but pws is 
here: https://www.pwsweather.com/station/pws/KCOCOLOR1160

Here is the syslog:

Feb 15 10:40:24 weatherpi weewx[10493] DEBUG weewx.reportengine: Running 
report 'Belchertown'
Feb 15 10:40:24 weatherpi weewx[10493] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
'Belchertown'
Feb 15 10:40:25 weatherpi weewx[10493] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', u'user.belchertown.getData']
Feb 15 10:40:25 weatherpi weewx[10493] DEBUG weewx.manager: Daily summary 
version is 4.0
Feb 15 10:40:25 weatherpi weewx[10493] INFO user.belchertown: version 1.1
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   Parse error in value at line 570.
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   Traceback (most recent call last):
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   obj.start()
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   self.run()
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 150, in run
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   ngen = self.generate(gen_dict[section_name], self.gen_ts)
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in 
generate
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   ngen += self.generate(section[subsection], gen_ts)
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in 
generate
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   ngen += self.generate(section[subsection], gen_ts)
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in 
generate
Feb 15 10:40:26 weatherpi weewx[10493] ERROR weewx.reportengine:
   default_binding)
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 385, in 
_getSearchList
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
   searchList += obj.get_extension_list(timespan, db_lookup)
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/share/weewx/user/belchertown.py", line 208, in 
get_extension_list
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
   chart_dict = configobj.ConfigObj(chart_config_path, 
file_error=True)
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, 
in __init__
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
   self._load(infile, configspec)
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
 File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, 
in _load
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
   raise error
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
   ParseError: Parse error in value at line 570.
Feb 15 10:40:27 weatherpi weewx[10493] ERROR weewx.reportengine:
   Generator terminated
Feb 15 10:40:27 weatherpi weewx[10493] INFO weewx.reportengine: Copied 31 
files to /var/www/html/weewx/belchertown
Feb 15 10:40:28 weatherpi weewx[10493] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'user.belchertown.HighchartsJsonGenerator'
Feb 15 10:40:28 weatherpi weewx[10493] ERROR weewx.reportengine:
   Parse error in value at line 570.
Feb 15 10:40:28 weatherpi weewx[10493] ERROR weewx.reportengine:
   Traceback (most recent call last):
Feb 15 10:40:

[weewx-user] Re: Cheetah Generator Errors

[vince]

Are you doing anything unusual like running off a weewx tree out on a NAS 
on your LAN or the like ?
Did you change anything ?   

The logs look like it's having issues reading files including perhaps even 
your weewx.conf.   Is your SD card maybe going bad ?

-- 
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/dd856fcc-47fa-4b97-8348-e04f81fca28bn%40googlegroups.com.

[weewx-user] Re: Cheetah Generator Errors

[Parker Lohrenz]

 Thanks for the thoughts.  The whole system is on the raspberry pi, nothing 
on a NAS yet.  I don't recall any specifics what might have triggered it 
since i was slow to realize the problem.  I noticed the last date it was 
working was Jan 5 2021.   The only thing I have been doing with the system 
was trying to apt-get update to keep things current.   I did recently 
notice I was pulling the wrong source list (python3 instead of python2):

For python3 (debian10 and later):
curl -s http://weewx.com/apt/weewx-python3.list | sudo tee 
/etc/apt/sources.list.d/weewx.list
For python2 (debian9 and earlier):
curl -s http://weewx.com/apt/weewx-python2.list | sudo tee 
/etc/apt/sources.list.d/weewx.list

The raspberry pi is still debian 9, and running python2.7.   Once I updated 
this I was able to update from 3.9.2 to 4.4.0, but that hasn't fixed the 
problem.  

I hope the SD card is still good(only a couple years old, and weewx is 
really all this pi is doing).   My best guess is that i did an apt-get 
update that must have broken something last month that I didn't notice 
until recently.  

On Monday, February 15, 2021 at 11:46:30 AM UTC-7 vince wrote:

> Are you doing anything unusual like running off a weewx tree out on a NAS 
> on your LAN or the like ?
> Did you change anything ?   
>
> The logs look like it's having issues reading files including perhaps even 
> your weewx.conf.   Is your SD card maybe going bad ?
>

-- 
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/7e98fa08-a972-4662-9737-92aca81a33f3n%40googlegroups.com.

Re: [weewx-user] Customising NOAATable

[Tom Keffer]

Did you check the locations I mentioned in my post? To repeat:

If you're asking how to customize the Javascript, it depends on the skin.
> For the "Standard" skin, it's in the template itself, index.html.tmpl. Just
> modify the template. For the "Seasons" skin, it's in seasons.js.


On Mon, Feb 15, 2021 at 10:05 AM Auchtermuchty Weather 
wrote:

>
> The output files need to have '.txt' and the end, but the links to them
> mustn't include it so they fit the DokuWiki way of doing things.  By
> default they do and I can't find where that code is generated to amend it.
>
>
> On Monday, 15 February 2021 at 14:56:10 UTC tke...@gmail.com wrote:
>
>> I'm not sure what you're asking.
>>
>> If you're asking how to customize the Javascript, it depends on the skin.
>> For the "Standard" skin, it's in the template itself, index.html.tmpl. Just
>> modify the template. For the "Seasons" skin, it's in seasons.js.
>>
>> If you're asking how the name of the generated file is set, it's the
>> template name minus the ".tmpl" at the end. So, if you don't want the
>> ".txt" suffix, just rename the NOAA templates.
>>
>> Does that answer your question?
>>
>> On Mon, Feb 15, 2021 at 6:45 AM Auchtermuchty Weather 
>> wrote:
>>
>>> I much prefer the output of NOAATable for making the NOAA reports
>>> available.
>>>
>>> However my template where I want this to appear is creating a Dokuwiki
>>> Page, so if the name in the link ends with '.txt' it looks for a file
>>> ending in '.txt.txt'.
>>>
>>> I have it working with the drop-downs as per the header in the Standard
>>> website by not appending the '.txt' in the Javascript that loads the page.
>>>
>>> What I'd like to do is customise NOAATable so the link is missing the
>>> '.txt' - I'd rather not write my own version of it if possible.
>>>
>>> But I've searched & searched and can't find where & how it's
>>> implemented.
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/79992f9a-7079-42bb-bb20-9df8fd088fbdn%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/8efe627d-02a3-498b-9148-9552721f6127n%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/CAPq0zEDzmP_vr0%3DJ_5vLXBCgStXQ-hx6uwTTv2nGkz6rqJ39MQ%40mail.gmail.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Tom Keffer]

Did you check line 570 in the skin.conf for the Belchertown skin?

On Mon, Feb 15, 2021 at 11:04 AM Parker Lohrenz  wrote:

>  Thanks for the thoughts.  The whole system is on the raspberry pi,
> nothing on a NAS yet.  I don't recall any specifics what might have
> triggered it since i was slow to realize the problem.  I noticed the last
> date it was working was Jan 5 2021.   The only thing I have been doing with
> the system was trying to apt-get update to keep things current.   I did
> recently notice I was pulling the wrong source list (python3 instead of
> python2):
>
> For python3 (debian10 and later):
> curl -s http://weewx.com/apt/weewx-python3.list | sudo tee
> /etc/apt/sources.list.d/weewx.list
> For python2 (debian9 and earlier):
> curl -s http://weewx.com/apt/weewx-python2.list | sudo tee
> /etc/apt/sources.list.d/weewx.list
>
> The raspberry pi is still debian 9, and running python2.7.   Once I
> updated this I was able to update from 3.9.2 to 4.4.0, but that
> hasn't fixed the problem.
>
> I hope the SD card is still good(only a couple years old, and weewx is
> really all this pi is doing).   My best guess is that i did an apt-get
> update that must have broken something last month that I didn't notice
> until recently.
>
> On Monday, February 15, 2021 at 11:46:30 AM UTC-7 vince wrote:
>
>> Are you doing anything unusual like running off a weewx tree out on a NAS
>> on your LAN or the like ?
>> Did you change anything ?
>>
>> The logs look like it's having issues reading files including perhaps
>> even your weewx.conf.   Is your SD card maybe going bad ?
>>
> --
> 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/7e98fa08-a972-4662-9737-92aca81a33f3n%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/CAPq0zEBZAWrtpGZ0XkMXSDtPAvRAFJWa5Y_QNZfvp3vABwQiJg%40mail.gmail.com.

[weewx-user] Sky Cover data to pwsweather

[bchap...@gmail.com]

Would someone please explain how to send sky cover data to pwsweather.  
I've been searching this group all weekend without results.  Thanks!

-- 
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/9a50077a-6ec6-49fa-9e15-a60e733a663cn%40googlegroups.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Parker Lohrenz]

/etc/weewx/skins/Belchertown/skin.conf is only 515 lines.here is an 
excerpt there:

[CheetahGenerator]
# This section is used by the generator CheetahGenerator, and specifies
# which files are to be generated from which template.

search_list_extensions = user.belchertown.getData

# Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
encoding = html_entities

[[SummaryByMonth]]
# Reports that summarize "by month"
[[[NOAA_month]]]
encoding = strict_ascii
template = NOAA/NOAA--MM.txt.tmpl

[[SummaryByYear]]
# Reports that summarize "by year"
[[[NOAA_year]]]
encoding = strict_ascii
template = NOAA/NOAA-.txt.tmpl

[[ToDate]]
# Reports that show statistics "to date", such as day-to-date,
# week-to-date, month-to-date, etc.
[[[weewx_data]]]
template = json/weewx_data.json.tmpl

[[Belchertown]]
template = js/belchertown.js.tmpl

[[[home]]]
template = index.html.tmpl

[[[about]]]
template = about/index.html.tmpl

[[[graphs]]]
template = graphs/index.html.tmpl

[[[reports]]]
template = reports/index.html.tmpl

[[[records]]]
template = records/index.html.tmpl

[[[pi]]]
template = pi/index.html.tmpl

[[[manifest]]]
encoding = utf8
template = manifest.json.tmpl

###

[CopyGenerator]

# This section is used by the generator CopyGenerator

# List of files to be copied only the first time the generator runs
copy_once = favicon.ico, images/*, json/index.html, js/index.html, 
js/responsive-menu.js, robots.txt

# List of files to be copied each time the generator runs
copy_always = *.css


###

#
# The list of generators that are to be run:
#
[Generators]
generator_list = weewx.cheetahgenerator.CheetahGenerator, 
weewx.reportengine.CopyGenerator, user.belchertown.HighchartsJsonGenerator


On Monday, February 15, 2021 at 12:26:14 PM UTC-7 tke...@gmail.com wrote:

> Did you check line 570 in the skin.conf for the Belchertown skin?
>
> On Mon, Feb 15, 2021 at 11:04 AM Parker Lohrenz  wrote:
>
>>  Thanks for the thoughts.  The whole system is on the raspberry pi, 
>> nothing on a NAS yet.  I don't recall any specifics what might have 
>> triggered it since i was slow to realize the problem.  I noticed the last 
>> date it was working was Jan 5 2021.   The only thing I have been doing with 
>> the system was trying to apt-get update to keep things current.   I did 
>> recently notice I was pulling the wrong source list (python3 instead of 
>> python2):
>>
>> For python3 (debian10 and later):
>> curl -s http://weewx.com/apt/weewx-python3.list | sudo tee 
>> /etc/apt/sources.list.d/weewx.list
>> For python2 (debian9 and earlier):
>> curl -s http://weewx.com/apt/weewx-python2.list | sudo tee 
>> /etc/apt/sources.list.d/weewx.list
>>
>> The raspberry pi is still debian 9, and running python2.7.   Once I 
>> updated this I was able to update from 3.9.2 to 4.4.0, but that 
>> hasn't fixed the problem.  
>>
>> I hope the SD card is still good(only a couple years old, and weewx is 
>> really all this pi is doing).   My best guess is that i did an apt-get 
>> update that must have broken something last month that I didn't notice 
>> until recently.  
>>
>> On Monday, February 15, 2021 at 11:46:30 AM UTC-7 vince wrote:
>>
>>> Are you doing anything unusual like running off a weewx tree out on a 
>>> NAS on your LAN or the like ?
>>> Did you change anything ?   
>>>
>>> The logs look like it's having issues reading files including perhaps 
>>> even your weewx.conf.   Is your SD card maybe going bad ?
>>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7e98fa08-a972-4662-9737-92aca81a33f3n%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/fe2643f8-01ea-490e-96dd-efa7f9206bcbn%40googlegroups.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Parker Lohrenz]

I think i found it.   I must have been editing the graphs to change the new 
annual totals, etc after year end.   

I found a typo on line 570 of the graphs.conf file.Now that it is 
fixed, things are a bit better. but I am digging into the graphs.conf file 
to see where I may have broken something.   Here is the latest syslog:

Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: MQTT: Published 
record 2021-02-15 13:30:33 MST (1613421033)
Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: Windy: Published 
record 2021-02-15 13:30:00 MST (1613421000)
Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: Wunderground-PWS: 
Published record 2021-02-15 13:30:00 MST (1613421000)
Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
'Belchertown'
Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', u'user.belchertown.getData']
Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.manager: Daily summary 
version is 4.0
Feb 15 13:30:34 weatherpi weewx[10773] INFO user.belchertown: New forecast 
file downloaded to 
/var/www/html/weewx/belchertown/json/darksky_forecast.json
Feb 15 13:30:35 weatherpi weewx[10773] INFO user.belchertown: Update 
Checker: New GitHub Version file downloaded to 
/var/www/html/weewx/belchertown/json/github_version.json
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   argument of type 'NoneType' is not iterable
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   Traceback (most recent call last):
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   obj.start()
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   self.run()
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 150, in run
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   ngen = self.generate(gen_dict[section_name], self.gen_ts)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in 
generate
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   ngen += self.generate(section[subsection], gen_ts)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in 
generate
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   ngen += self.generate(section[subsection], gen_ts)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in 
generate
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   default_binding)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 385, in 
_getSearchList
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   searchList += obj.get_extension_list(timespan, db_lookup)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/user/belchertown.py", line 836, in 
get_extension_list
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   obs_output = getattr(current, obs)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/tags.py", line 506, in __getattr__
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   vt = weewx.xtypes.get_scalar(obs_type, self.record, db_manager)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/xtypes.py", line 71, in get_scalar
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
   return xtype.get_scalar(obs_type, record, db_manager)
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/wxxtypes.py", line 89, in get_scalar
Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
    

Re: [weewx-user] Added time to produce report on Ver 4.3

[philip....@gmail.com]

I have 2 davis consoles connected to the same Pi, the second one is only 
used to record sun hours via the rain terminal and is then stored on the 
sun.sdb database in the rain field.
This database is exactly the same as the weewx.sdb just with a different 
name and are both sqlite and Im using WEEWX MULTI to achieve this along 
with a third for AIRLINK.
The $WM is similar to the one used in NOAA reports #set $WM="%6.2f"
The log with debug=1 will take a 2/3 days.
On Monday, February 15, 2021 at 5:34:33 PM UTC tke...@gmail.com wrote:

> Not much information here, but I am not aware of any changes that would 
> cause this. 
>
> What is the nature of the binding 'sun_binding'? Is it a sqlite database? 
> MySQL on a remote server?
>
> I assume the placeholder $WM is a simple formatting string.
>
> How about a log? Set debug=1, restart weewxd, then post the log through 
> the first reporting cycle. Or, if it's easier, you can use wee_reports.
>
>
> On Mon, Feb 15, 2021 at 9:02 AM philip@gmail.com  
> wrote:
>
>> Hi
>> I upgraded from v4.1.1 to v4.4 and noticed in the logs that a report took 
>> 36 seconds to generate where it use to be only 1 second.
>> Starting back from v4.1.1 I found that the extra time started when I 
>> upgraded  from v4.2 to v4.3.
>> Im using a Pi4 and on a Pi3 the time was over 70 seconds.
>> After eliminating various pieces of code I find that the line
>> #set $min1 = $day.rain.sum.inch.format($WM, add_label=False) was causing 
>> the extra time.
>> The following is an extract and not the full code but as the NOOA report 
>> uses something similar and that works ok Im thinking that the data_binding 
>> is perhaps the cause or have I got the code wrong and was just lucky in 
>> older versions.
>>
>> #for $day in $month($data_binding='sun_binding').days 
>> =
>> #set $min1 = $day.rain.sum.inch.format($WM, add_label=False)
>> ===
>> ===
>> #end for
>> Just wondered what changed in v4.3 as v4.2 work perfectly
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9a1f1311-b9a2-4f09-9349-7eaddc54ca4dn%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/110ba2c4-4a4a-4395-9e9c-4fba20e998c7n%40googlegroups.com.

[weewx-user] Re: wee_import from WD logs fails

[gjr80]

Hi Peter,

Before you start it off again can you describe how you are doing the 
import; ie time period per import,  one big import, multiple smaller 
periods? How is you data organised on disc, one large directory with all 
file, year by year directories etc.

Gary

On Tuesday, 16 February 2021 at 00:00:27 UTC+10 peter.su...@gmail.com wrote:

> Hi Gary,
>
> today my Raspberry 4 arrived, which will hopefully be my long-running 
> weather computer.
> I tried to import all my data on Pi3. It worked back for about 8 years, 
> but then the performance crashed into hell.
> The import of one year took about 1 week and was getting worse.
>
> Now I'm starting it all over on a fresh install and report, what will be 
> the result.
>
> Peter
> gjr80 schrieb am Montag, 1. Februar 2021 um 23:28:04 UTC+1:
>
>> Hi Peter,
>>
>> On Tuesday, 2 February 2021 at 06:03:36 UTC+10 peter.su...@gmail.com 
>> wrote:
>>
>>> Hey Gary,
>>> its looking perfect. I just separated the logs for each year and right 
>>> now I am testing the 6th year in a row, doing a quick dry-run.
>>> The script is finding some duplicates, but it looks like every complete 
>>> year from 01/01 to 12/31 should be imported into the database.
>>>
>>
>> That is interesting, the screen output you posted originally clearly 
>> showed an error decoding a date-time, I am surprised that re-arranging the 
>> log files fixed that. The first person that trialled the WD import module 
>> was in a similar boat to you; they had many years of WD data and when they 
>> first tried to import the data they did it in one run and not only did it 
>> take many hours but wee_import eventually ground to a halt and crashed 
>> (the exact details escape me). So importing/processing a year at a time may 
>> be more manageable and safer.
>>
>> The duplicates issue is not uncommon, the few suites of WD logs I have 
>> worked on all contained the odd duplicate date-time. wee_import will 
>> simply ignore the duplicates, the  only issue is when the data for each 
>> duplicate is different. Probably not going to make too much difference over 
>> 15 years of data at one minute intervals.
>>
>> One more question from my side: Would you prefer a MySQL database with 
>>> all this mass of data?
>>>
>>  
>> I think the consensus is that unless you have good reason to use 
>> MySQL/MariaDB stick with SQLite. SQLite is faster and simpler to 
>> backup/restore. SQLite will easy handle all of your 15 years of data.
>>  
>> 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/c9b2b67d-9377-488f-8d5c-94662cf13315n%40googlegroups.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Tom Keffer]

I don't completely understand what is going on, but it looks like you're
asking for cloud base in the belchertown skin, but the belchertown search
list extension is not supplying a record from which to calculate it.

Most likely this is a bug in the skin, but it could be from the way you are
using the tag. I assume it is something like $current.cloudbase?

On Mon, Feb 15, 2021 at 12:39 PM Parker Lohrenz  wrote:

> I think i found it.   I must have been editing the graphs to change the
> new annual totals, etc after year end.
>
> I found a typo on line 570 of the graphs.conf file.Now that it is
> fixed, things are a bit better. but I am digging into the graphs.conf file
> to see where I may have broken something.   Here is the latest syslog:
>
> Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: MQTT: Published
> record 2021-02-15 13:30:33 MST (1613421033)
> Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: Windy: Published
> record 2021-02-15 13:30:00 MST (1613421000)
> Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: Wunderground-PWS:
> Published record 2021-02-15 13:30:00 MST (1613421000)
> Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.reportengine: Found
> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
> 'Belchertown'
> Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras', u'user.belchertown.getData']
> Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.manager: Daily summary
> version is 4.0
> Feb 15 13:30:34 weatherpi weewx[10773] INFO user.belchertown: New forecast
> file downloaded to
> /var/www/html/weewx/belchertown/json/darksky_forecast.json
> Feb 15 13:30:35 weatherpi weewx[10773] INFO user.belchertown: Update
> Checker: New GitHub Version file downloaded to
> /var/www/html/weewx/belchertown/json/github_version.json
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine: Caught
> unrecoverable exception in generator
> 'weewx.cheetahgenerator.CheetahGenerator'
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    argument of type 'NoneType' is not iterable
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    Traceback (most recent call last):
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    obj.start()
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    self.run()
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 150, in run
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    ngen = self.generate(gen_dict[section_name], self.gen_ts)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in
> generate
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    ngen += self.generate(section[subsection], gen_ts)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in
> generate
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    ngen += self.generate(section[subsection], gen_ts)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in
> generate
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    default_binding)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 385, in
> _getSearchList
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    searchList += obj.get_extension_list(timespan, db_lookup)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/user/belchertown.py", line 836, in
> get_extension_list
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    obs_output = getattr(current, obs)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/tags.py", line 506, in __getattr__
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>    vt = weewx.xtypes.get_scalar(obs_type, self.record, db_manager)
> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/xtypes.py", line 71, in g

Re: [weewx-user] Re: Cheetah Generator Errors

[Parker Lohrenz]

Yeah,  somewhere in the skin, things were mixed up.   I just got the skin 
up to date and though it took some effort with the breaking changes, the 
errors are gone now.  Thanks all, for the help.

On Monday, February 15, 2021 at 2:26:46 PM UTC-7 tke...@gmail.com wrote:

> I don't completely understand what is going on, but it looks like you're 
> asking for cloud base in the belchertown skin, but the belchertown search 
> list extension is not supplying a record from which to calculate it.
>
> Most likely this is a bug in the skin, but it could be from the way you 
> are using the tag. I assume it is something like $current.cloudbase?
>
> On Mon, Feb 15, 2021 at 12:39 PM Parker Lohrenz  wrote:
>
>> I think i found it.   I must have been editing the graphs to change the 
>> new annual totals, etc after year end.   
>>
>> I found a typo on line 570 of the graphs.conf file.Now that it is 
>> fixed, things are a bit better. but I am digging into the graphs.conf file 
>> to see where I may have broken something.   Here is the latest syslog:
>>
>> Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: MQTT: Published 
>> record 2021-02-15 13:30:33 MST (1613421033)
>> Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: Windy: Published 
>> record 2021-02-15 13:30:00 MST (1613421000)
>> Feb 15 13:30:33 weatherpi weewx[10773] INFO weewx.restx: 
>> Wunderground-PWS: Published record 2021-02-15 13:30:00 MST (1613421000)
>> Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
>> 'Belchertown'
>> Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.cheetahgenerator: 
>> Using search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>> 'weewx.cheetahgenerator.Extras', u'user.belchertown.getData']
>> Feb 15 13:30:33 weatherpi weewx[10773] DEBUG weewx.manager: Daily summary 
>> version is 4.0
>> Feb 15 13:30:34 weatherpi weewx[10773] INFO user.belchertown: New 
>> forecast file downloaded to 
>> /var/www/html/weewx/belchertown/json/darksky_forecast.json
>> Feb 15 13:30:35 weatherpi weewx[10773] INFO user.belchertown: Update 
>> Checker: New GitHub Version file downloaded to 
>> /var/www/html/weewx/belchertown/json/github_version.json
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'weewx.cheetahgenerator.CheetahGenerator'
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    argument of type 'NoneType' is not iterable
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    Traceback (most recent call last):
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    obj.start()
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    self.run()
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 150, in run
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    ngen = self.generate(gen_dict[section_name], self.gen_ts)
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in 
>> generate
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    ngen += self.generate(section[subsection], gen_ts)
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 220, in 
>> generate
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    ngen += self.generate(section[subsection], gen_ts)
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in 
>> generate
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    default_binding)
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 385, in 
>> _getSearchList
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>    searchList += obj.get_extension_list(timespan, db_lookup)
>> Feb 15 13:30:35 weatherpi weewx[10773] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/user/belchertown.py", line 836, in 
>> get_extension_list
>> Feb 15

[weewx-user] Midnight data applied to previous day in NOAA report

[Dan Ciarniello]

I recently noticed that the earliest data record in my DB which happens to 
be at midnight is listed in the NOAA reports on the previous day.  

To illustrate, the dateTime of the first data record in my archive table is 
1513670400 
which corresponds to Tue 19 Dec 2017 12:00:00 AM PST but it's included in 
the NOAA reports on Dec 18.

A side-effect of this is that the Belchertown Records page gives Dec 18 as 
the day with the smallest daily temperature range with a value of 0 degrees.

This seems a little strange to me so I'm wondering if it's intentional or a 
bug.  If it's intentional, what's the rationale?

-- 
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/42a334be-8095-43ab-8ce1-d4c72abea926n%40googlegroups.com.

Re: [weewx-user] Midnight data applied to previous day in NOAA report

[Tom Keffer]

It's intentional.

Say you have a ten minute archive interval. When a weather station emits a
record at, say, midnight, it actually includes observations from 2350 to
, that is, from the previous day. Now, you could timestamp this 2350,
but most weather stations actually timestamp it with the "current" time,
which is .

WeeWX consistently uses this time convention.

-tk


On Mon, Feb 15, 2021 at 4:41 PM Dan Ciarniello 
wrote:

>
> I recently noticed that the earliest data record in my DB which happens to
> be at midnight is listed in the NOAA reports on the previous day.
>
> To illustrate, the dateTime of the first data record in my archive table
> is 1513670400 which corresponds to Tue 19 Dec 2017 12:00:00 AM PST but
> it's included in the NOAA reports on Dec 18.
>
> A side-effect of this is that the Belchertown Records page gives Dec 18 as
> the day with the smallest daily temperature range with a value of 0 degrees.
>
> This seems a little strange to me so I'm wondering if it's intentional or
> a bug.  If it's intentional, what's the rationale?
>
> --
> 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/42a334be-8095-43ab-8ce1-d4c72abea926n%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/CAPq0zEDaPWu%3D0G72B6rsbbGzDNAp5i1upRPSAzsyxUBYJ_Q%2BUA%40mail.gmail.com.

Re: [weewx-user] Midnight data applied to previous day in NOAA report

[John Kline]

It’s intentional.  Midnight is considered part of the previous day.  If you 
think about it, the midnight archive period is for the period from 
 minutes before midnight (often 23:55) through to midnight.  
It belongs in the previous day.

> On Feb 15, 2021, at 4:41 PM, Dan Ciarniello  wrote:
> 
> 
> I recently noticed that the earliest data record in my DB which happens to be 
> at midnight is listed in the NOAA reports on the previous day.  
> 
> To illustrate, the dateTime of the first data record in my archive table is 
> 1513670400 which corresponds to Tue 19 Dec 2017 12:00:00 AM PST but it's 
> included in the NOAA reports on Dec 18.
> 
> A side-effect of this is that the Belchertown Records page gives Dec 18 as 
> the day with the smallest daily temperature range with a value of 0 degrees.
> 
> This seems a little strange to me so I'm wondering if it's intentional or a 
> bug.  If it's intentional, what's the rationale?
> -- 
> 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/42a334be-8095-43ab-8ce1-d4c72abea926n%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/A9E1910D-C90B-479D-84D2-CDAA1DB17123%40johnkline.com.

Re: [weewx-user] Midnight data applied to previous day in NOAA report

[Dan Ciarniello]

Yes, of course, that makes perfect sense.  

Thanks for the explanation.

On Monday, February 15, 2021 at 4:50:19 PM UTC-8 jo...@johnkline.com wrote:

> It’s intentional.  Midnight is considered part of the previous day.  If 
> you think about it, the midnight archive period is for the period from 
>  minutes before midnight (often 23:55) through to 
> midnight.  It belongs in the previous day.
>
> On Feb 15, 2021, at 4:41 PM, Dan Ciarniello  wrote:
>
> 
>
>
> I recently noticed that the earliest data record in my DB which happens to 
> be at midnight is listed in the NOAA reports on the previous day.  
>
> To illustrate, the dateTime of the first data record in my archive table 
> is 1513670400 which corresponds to Tue 19 Dec 2017 12:00:00 AM PST but 
> it's included in the NOAA reports on Dec 18.
>
> A side-effect of this is that the Belchertown Records page gives Dec 18 as 
> the day with the smallest daily temperature range with a value of 0 degrees.
>
> This seems a little strange to me so I'm wondering if it's intentional or 
> a bug.  If it's intentional, what's the rationale?
>
> -- 
>
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/42a334be-8095-43ab-8ce1-d4c72abea926n%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/f627e54a-d1fb-4bad-bb65-e96f5dd02025n%40googlegroups.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Graham Eddy]

dunno whether this is a config error but the indentation and number of ‘[’s are 
not consistent here

> On 16 Feb 2021, at 7:06 am, Parker Lohrenz  wrote:
> 
> [[Belchertown]]
> template = js/belchertown.js.tmpl
> 
> [[[home]]]
> template = index.html.tmpl
> 

-- 
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/9D8F6D1C-B735-4C37-ADF3-114E7E71FB70%40gmail.com.

[weewx-user] Reboot GW1000 using monit?

[se...@bitkickers.us]

Not bothering to post logs, etc., because this isn't a "problem" with the 
software.

Been using Weewx for a few years with Acurite 01525 but finally got fed up 
with the horribly flaky RF from sensors to console and recently 
transitioned to Ecowitt and the GW1000 with temp, wind, and rain sensors. 
Loving it so far although the WS View app on Android apparently had a bug 
that initially prevented me from configuring the gateway properly. Kudos to 
the Ecowitt team who were very responsive (supp...@ecowitt.com).

Browsing the weewx-user group I found https://github.com/gjr80/weewx-gw1000 and 
that's a delightful piece of code, every bit as good an useful as Weewx 
itself.

The gateway has gone offline a couple of times in the past 48 hours for 
reasons unknown. Its leds are flashing as if it's online, and it can 
sometimes be pinged so it's on the wlan, but it doesn't respond to API 
requests for the driver. I'd like to monitor the gateway from a monit 
server that I have running on my network and while I can test for the host 
alive and send an alert, I'd really like to monitor the gateway function 
itself somehow. 

If it were a linux box under the covers and had access, I could script a 
solution on the gateway itself but I don't think that's possible. I note in 
the GW1000 driver that the command list has a "reset" and "reboot" command 
and wonder if the driver will allow me to send either one of those by 
itself?

Any other suggestions?

Thanks!

Sean

-- 
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/a73c6f68-8136-4de0-ae8e-de8eedf8fc1bn%40googlegroups.com.

[weewx-user] Re: Reboot GW1000 using monit?

[gjr80]

Can't speak for Monit, haven't used it and only briefly skimmed an article 
on it a year or two back. Whilst the GW1000API has commands to reset and 
reboot the device I have not implemented them int he GW1000 driver and I 
have been loathed to do so. I really don't see much point in giving the 
driver the ability to factory reset the GW1000; if the device is factory 
reset you need to use the WS View app to pair/configure the device again so 
you might as well goto the device or use the WS View app to factory reset 
if such action is warranted. I could see some utility in being able to 
reboot the GW1000, but I suspect that in almost all situations where you 
would want to take such action you have lost contact with the GW1000 and I 
doubt you will be able to command the GW1000 to reboot via the API.

That being said WeeWX and the GW1000 driver have a couple of features that 
attempt recovery if contact with the GW1000 is lost. Firstly, if a driver 
cannot be loaded WeeWX has the ability to keep trying to load the driver 
every 60 seconds rather than exiting (refer loop_on_init config option 
 in weewx.conf). Secondly, if 
the GW1000 driver cannot contact the GW1000 on startup, or if contact is 
lost during normal operation, the driver re-attempts contact a number of 
times and if contact cannot be made the driver will attempt to re-discover 
the GW1000 on the network. These may or may not work depending on the 
issue, the log would be need to be checked to see what the symptoms were 
and what WeeWX/the driver did. 

Ultimately if the GW1000 cannot be contacted and cannot be discovered then 
there is not much that can be done short of notifying you to go and hit the 
reset button.

Gary

On Tuesday, 16 February 2021 at 11:56:49 UTC+10 se...@bitkickers.us wrote:

> Not bothering to post logs, etc., because this isn't a "problem" with the 
> software.
>
> Been using Weewx for a few years with Acurite 01525 but finally got fed up 
> with the horribly flaky RF from sensors to console and recently 
> transitioned to Ecowitt and the GW1000 with temp, wind, and rain sensors. 
> Loving it so far although the WS View app on Android apparently had a bug 
> that initially prevented me from configuring the gateway properly. Kudos to 
> the Ecowitt team who were very responsive (sup...@ecowitt.com).
>
> Browsing the weewx-user group I found 
> https://github.com/gjr80/weewx-gw1000 and that's a delightful piece of 
> code, every bit as good an useful as Weewx itself.
>
> The gateway has gone offline a couple of times in the past 48 hours for 
> reasons unknown. Its leds are flashing as if it's online, and it can 
> sometimes be pinged so it's on the wlan, but it doesn't respond to API 
> requests for the driver. I'd like to monitor the gateway from a monit 
> server that I have running on my network and while I can test for the host 
> alive and send an alert, I'd really like to monitor the gateway function 
> itself somehow. 
>
> If it were a linux box under the covers and had access, I could script a 
> solution on the gateway itself but I don't think that's possible. I note in 
> the GW1000 driver that the command list has a "reset" and "reboot" command 
> and wonder if the driver will allow me to send either one of those by 
> itself?
>
> Any other suggestions?
>
> Thanks!
>
> Sean
>

-- 
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/797b7a4e-92d2-44de-a59c-f485f871eae6n%40googlegroups.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[gjr80]

Unlike python, configobj has no specific indentation requirements, it's 
just us humans that like indentation. Square brackets on the other hand are 
important, in this case there would have been no error (the square brackets 
were consistent/matched) but [[Belchertown]] and below would have been 
ignored by CheetahGenerator.

Gary

On Tuesday, 16 February 2021 at 11:49:58 UTC+10 graha...@gmail.com wrote:

> dunno whether this is a config error but the indentation and number of 
> ‘[’s are not consistent here
>
> On 16 Feb 2021, at 7:06 am, Parker Lohrenz  wrote:
>
> [[Belchertown]]
> template = js/belchertown.js.tmpl
>
> [[[home]]]
> template = index.html.tmpl
>
>
>

-- 
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/a8d9aeb8-3af3-4523-afd2-0ce32559e760n%40googlegroups.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Graham Eddy]

that was my point. i think it was a subtle config error, not yet picked up by 
the authour, that did not cause a syntax error, but would truncate his expected 
reports. but, not knowing belchertown, perhaps this strange configuration was 
correct for it...

> On 16 Feb 2021, at 4:31 pm, gjr80  wrote:
> 
> Unlike python, configobj has no specific indentation requirements, it's just 
> us humans that like indentation. Square brackets on the other hand are 
> important, in this case there would have been no error (the square brackets 
> were consistent/matched) but [[Belchertown]] and below would have been 
> ignored by CheetahGenerator.
> 
> Gary
> 
> On Tuesday, 16 February 2021 at 11:49:58 UTC+10 graha...@gmail.com wrote:
> dunno whether this is a config error but the indentation and number of ‘[’s 
> are not consistent here
> 
>> On 16 Feb 2021, at 7:06 am, Parker Lohrenz > > wrote:
>> 
>> [[Belchertown]]
>> template = js/belchertown.js.tmpl
>> 
>> [[[home]]]
>> template = index.html.tmpl
>> 
> 
> 
> -- 
> 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/a8d9aeb8-3af3-4523-afd2-0ce32559e760n%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/03A06CBF-672A-490E-9D74-EB57D517BE5A%40gmail.com.