Re: [weewx-user] Problem with display after some updates

[gjr80]

Sean,

troubleshooting WeeWX, WeeWX-WD and the Saratoga templates can be complex 
but straight forward if you logically follow the flow of data through from 
WeeWX to the Saratoga templates. You use the Alternate dashboard which is 
fine, but it does add one more layer. It also helps to have a basic 
understanding of what WeeWX-WD outputs are used by the Saratoga templates 
and how they are used.

Briefly, there are two key files produced by WeeWX/WeeWX-WD that are used 
by Saratoga; testtags.php and clientraw.txt. testtags.php provides the data 
that is displayed by the dashboard when you first load the dashboard or 
refresh the page. The units used in testtags.php are set by the user via 
the testtags skin.conf or preferably through weewx.conf. The Saratoga 
templates must be configured to accept data in these units. There are 
separate config options in the Saratoga template config files to determine 
the actual units displayed. A similar arrangement is in place for date-time 
formats. clientraw.txt is used to provide dynamic updates of the Saratoga 
dashboard (unfortunately the WeeWX-WD generated clientraw.txt is generated 
each report cycle so it is not too dynamic). clientraw.txt uses fixed units 
(largely) metric units and fixed date-time formats. The clientraw.txt 
units/formats are set in skin.conf and as these are fixed they should not 
be changed.

If you have issues with wrong units, date-time formats etc on the Saratoga 
dashboard you can often make a fairly good guess where the issue is by 
doing a screen refresh and carefully observing the incorrect data. Upon 
refresh the Saratoga templates load data from testtags.php then the dynamic 
updates kick in using data from clientraw.txt. If you have a field that is 
displaying say a nonsense date, you will often see the correct (or 
incorrect) date be displayed initially then it quickly changes to the 
incorrect (or correct) date. This is the testtags.php data being displayed 
then the dynamic update updating the display to show the clientraw.txt 
data. If the first lot of data is wrong you look at testtags.php, if the 
second you look at clientraw.txt.

In your case when I look at your dashboard I see the 'Updated:' date is 
obviously wrong, but on a page refresh I see the correct date briefly 
display then the incorrect date. This leads me to look at clientraw.txt. If 
I look at your clientraw.txt I see a number of '   N/A' entries. 
clientraw.txt is a (single) space delimited file, there is no properly 
defined format for clientraw.txt that I am aware of (there are list of 
fields but not what I would call a proper specification). When writing 
WeeWX-WD we found that fields for which we had no data were best handled in 
the clientraw files by using '---' or '--', the default WeeWX '   N/A' 
usually caused parsing problems. Hold that thought.

One of the changes introduced in WeeWX v3.9.0 was a new way of handling 
defaults. You can read about this in the Upgrade Guide and Customization 
Guide, but to cut a long story short the [StdReport] [[Defaults]] section 
will now override corresponding skin.conf settings so the behaviour of some 
skins will change when upgrading to 3.9.x.

Back to '   N/A', I suspect what is happening is that your upgrade to 3.9.1 
has seen the [StdReport] [[Defaults]] kick in and override the default None 
value used in the clientraw skin. This has resulted in the '   N/A' in 
clientraw.txt which upsets the parsing of clientraw.txt by 
Saratoga/Alternate dashboard.

When I look at your 'High Today' and 'Low Today' I see similar behaviour on 
a refresh, so again likely the incorrect parsing of clientraw.txt is 
causing some nonsense data to be displayed (given 212F=100C I would say a 
100 is being converted to F and displayed). Not sure about your wind gust 
issue, quite possibly related. There may be other similar problems but I 
have not noticed them, though looking at your Saratoga page I suspect you 
have Saratoga/Alternate dashboard configured correctly.

Anyway, I suggest we fix the clientraw.txt issue and then see how things 
are. Since [StdReport] [[Defaults]] overrides skin.conf any change needs to 
occur in [StdReport] [[Defaults]] or [StdReport] [[wdClientrawReport]], 
since [StdReport] [[Defaults]] will affect all skins we really need to make 
the change to [StdReport] [[wdClientrawReport]]. In weewx.conf try this 
change:

[StdReport]

[[wdClientrawReport]]
HTML_ROOT = WD
skin = Clientraw
[[[Units]]]
StringFormats
NONE = --

Save weewx.conf and do a WeeWX config reload or restart. After the next 
report cycle check your dashboard for correct display or look at 
public_html/WD/clientraw.txt and verify all '   N/A' have gone.

If any issues persist we can deal with them separately.

Gary

On Sunday, 19 May 2019 07:04:19 UTC+10, Sean Garland wrote:
>
> Also it appears if my wind gust isn't working right since the gust is 
> lower than the 

Re: [weewx-user] Re: upgrade from 3.8.2 to 3.9.1 failure

[Ian Prescott]

Hi Mathew
used wee_device --clear-memory
appears to have cleared memory according to console display
then restarted weewx
the following is a c from the log

May 19 14:24:03 weatherpi rsyslogd-2007: action 'action 17' suspended, next
retry is Sun May 19 14:25:33 2019 [try http://www.rsyslog.com/e/2007 ]
May 19 14:24:04 weatherpi wee_device[4443]: fousb: driver version is 1.9
May 19 14:24:04 weatherpi wee_device[4443]: fousb: power cycling enabled
for port 4 on hub 001:004
May 19 14:24:04 weatherpi wee_device[4443]: fousb: polling mode is PERIODIC
May 19 14:24:04 weatherpi wee_device[4443]: fousb: polling interval is 60
May 19 14:24:04 weatherpi wee_device[4443]: fousb: found station on USB
bus=001 device=011
May 19 14:24:47 weatherpi systemd[1]: Starting LSB: weewx weather system...
May 19 14:24:48 weatherpi weewx[4480]: engine: Initializing weewx version
3.9.1
May 19 14:24:48 weatherpi weewx[4480]: engine: Using Python 2.7.9 (default,
Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
May 19 14:24:48 weatherpi weewx[4480]: engine: Platform
Linux-4.14.78-v7+-armv7l-with-debian-8.0
May 19 14:24:48 weatherpi weewx[4480]: engine: Locale is 'en_AU.UTF-8'
May 19 14:24:48 weatherpi weewx[4480]: engine: pid file is
/var/run/weewx.pid
May 19 14:24:48 weatherpi weewx[4470]: Starting weewx weather system: weewx.
May 19 14:24:48 weatherpi systemd[1]: Started LSB: weewx weather system.
May 19 14:24:48 weatherpi weewx[4484]: engine: Using configuration file
/etc/weewx/weewx.conf
May 19 14:24:48 weatherpi weewx[4484]: engine: Debug is 1
May 19 14:24:48 weatherpi weewx[4484]: engine: Initializing engine
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading station type
FineOffsetUSB (weewx.drivers.fousb)
May 19 14:24:48 weatherpi weewx[4484]: fousb: driver version is 1.9
May 19 14:24:48 weatherpi weewx[4484]: fousb: power cycling enabled for
port 4 on hub 001:004
May 19 14:24:48 weatherpi weewx[4484]: fousb: polling mode is PERIODIC
May 19 14:24:48 weatherpi weewx[4484]: fousb: polling interval is 60
May 19 14:24:48 weatherpi weewx[4484]: fousb: found station on USB bus=001
device=011
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading service
weewx.engine.StdTimeSynch
May 19 14:24:48 weatherpi weewx[4484]: engine: Finished loading service
weewx.engine.StdTimeSynch
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading service
weewx.engine.StdConvert
May 19 14:24:48 weatherpi weewx[4484]: engine: StdConvert target unit is 0x1
May 19 14:24:48 weatherpi weewx[4484]: engine: Finished loading service
weewx.engine.StdConvert
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading service
weewx.engine.StdCalibrate
May 19 14:24:48 weatherpi weewx[4484]: engine: Finished loading service
weewx.engine.StdCalibrate
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading service
weewx.engine.StdQC
May 19 14:24:48 weatherpi weewx[4484]: engine: Finished loading service
weewx.engine.StdQC
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading service
weewx.wxservices.StdWXCalculate
May 19 14:24:48 weatherpi weewx[4484]: wxcalculate: The following values
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
dewpoint=prefer_hardware, appTemp=prefer_hardware,
rainRate=prefer_hardware, windrun=prefer_hardware,
heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
humidex=prefer_hardware, pressure=prefer_hardware,
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
cloudbase=prefer_hardware
May 19 14:24:48 weatherpi weewx[4484]: wxcalculate: The following
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
May 19 14:24:48 weatherpi weewx[4484]: engine: Finished loading service
weewx.wxservices.StdWXCalculate
May 19 14:24:48 weatherpi weewx[4484]: engine: Loading service
weewx.engine.StdArchive
May 19 14:24:48 weatherpi weewx[4484]: engine: Archive will use data
binding wx_binding
May 19 14:24:48 weatherpi weewx[4484]: engine: Record generation will be
attempted in 'software'
May 19 14:24:48 weatherpi weewx[4484]: engine: Using archive interval of
300 seconds (software record generation)
May 19 14:24:48 weatherpi weewx[4484]: engine: Use LOOP data in hi/low
calculations: 1
May 19 14:24:48 weatherpi weewx[4484]: manager: Daily summary version is 2.0
May 19 14:24:48 weatherpi weewx[4484]: engine: Using binding 'wx_binding'
to database 'weewx.sdb'
May 19 14:24:48 weatherpi weewx[4484]: manager: Starting backfill of daily
summaries
May 19 14:24:48 weatherpi weewx[4484]: engine: Caught unrecoverable
exception in engine:
May 19 14:24:48 weatherpi weewx[4484]:   Non-positive value for
record field 'interval': 0
May 19 14:24:48 weatherpi weewx[4484]:   Traceback (most recent
call last):
May 19 14:24:48 weatherpi weewx[4484]: File
"/usr/share/weewx/weewx/engine.py", line 884, in main
May 19 14:24:48 weatherpi weewx[4484]:   engine =
engine_class(config_dict)
May 19 14:24:48 weatherpi weewx[4484]: File
"/usr/share/weewx/weewx/engine.py", line 

[weewx-user] Belchertown skin for weewx now available!

[WILWetter25]

Hey everyone, 

I have a problem with the main-page of the skin: Forecast, Earth-Quakes and 
Graphs aren't loading since a week. 

My Website: http://www.mosel-wetter.com/

Does anyone know a solution?

-- 
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/3eb39651-49af-4f72-8a93-834f387f8d8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] upgrade from 3.8.2 to 3.9.1 failure

[Leon Shaner]

Hey, Ian,

You can use "wee_debug --info > /var/tmp/wee_debug.txt 2>&1" to write a helpful 
file at /var/tmp/wee_debug.txt for attaching to an e-mail.

You may want to scan the output anyway, in case something important didn't get 
obfuscated.  It does a good job with passwords, but ya never know... 
software... bugs happen.  :-/

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 18, 2019, at 9:02 PM, Ian Prescott  wrote:
> 
> sorry
> the station is an Aercus 3080
> and I am trying to find the howto on posting the config file
> 
>> On Sun, 19 May 2019 at 10:40, Leon Shaner  wrote:
>> Logs too abbreviated, or at least I am not able to pick out which driver / 
>> weatherstation version of are running.  Please expound.
>> WMR200, WMR300, both have this issue.  Maybe others.
>> Which model is yours?
>> 
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>> 
>>> On May 18, 2019, at 8:05 PM, Ian Prescott  wrote:
>>> 
>>> Hi
>>> I did an upgrade on my pi and by default weewx got upgraded as well.
>>> After a reboot the syslog shows the following.
>>> Any help would be appreciated.
>>> Thanks
>>> 
>>> 
>>> May 19 09:18:31 weatherpi systemd[1]: Starting LSB: weewx weather system...
>>> May 19 09:18:31 weatherpi weewx[2257]: engine: Initializing weewx version 
>>> 3.9.1
>>> May 19 09:18:31 weatherpi weewx[2257]: engine: Using Python 2.7.9 (default, 
>>> Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> May 19 09:18:31 weatherpi weewx[2257]: engine: Platform 
>>> Linux-4.14.78-v7+-armv7l-with-debian-8.0
>>> May 19 09:18:31 weatherpi weewx[2257]: engine: Locale is 'en_AU.UTF-8'
>>> May 19 09:18:31 weatherpi weewx[2257]: engine: pid file is 
>>> /var/run/weewx.pid
>>> May 19 09:18:31 weatherpi weewx[2247]: Starting weewx weather system: weewx.
>>> May 19 09:18:31 weatherpi systemd[1]: Started LSB: weewx weather system.
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Using configuration file 
>>> /etc/weewx/weewx.conf
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Debug is 1
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Initializing engine
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading station type 
>>> FineOffsetUSB (weewx.drivers.fousb)
>>> May 19 09:18:31 weatherpi weewx[2261]: fousb: driver version is 1.9
>>> May 19 09:18:31 weatherpi weewx[2261]: fousb: power cycling enabled for 
>>> port 4 on hub 001:004
>>> May 19 09:18:31 weatherpi weewx[2261]: fousb: polling mode is PERIODIC
>>> May 19 09:18:31 weatherpi weewx[2261]: fousb: polling interval is 60
>>> May 19 09:18:31 weatherpi weewx[2261]: fousb: found station on USB bus=001 
>>> device=006
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
>>> weewx.engine.StdTimeSynch
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
>>> weewx.engine.StdTimeSynch
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
>>> weewx.engine.StdConvert
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: StdConvert target unit is 0x1
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
>>> weewx.engine.StdConvert
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
>>> weewx.engine.StdCalibrate
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
>>> weewx.engine.StdCalibrate
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
>>> weewx.engine.StdQC
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
>>> weewx.engine.StdQC
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
>>> weewx.wxservices.StdWXCalculate
>>> May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following values 
>>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>>> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
>>> rainRate=prefer_hardware, windrun=prefer_hardware, 
>>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>>> humidex=prefer_hardware, pressure=prefer_hardware, 
>>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
>>> cloudbase=prefer_hardware
>>> May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following 
>>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
>>> weewx.wxservices.StdWXCalculate
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
>>> weewx.engine.StdArchive
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Archive will use data 
>>> binding wx_binding
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Record generation will be 
>>> attempted in 'software'
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Using archive interval of 
>>> 300 seconds (software record generation)
>>> May 19 09:18:31 weatherpi weewx[2261]: engine: Use LOOP data in hi/low 
>>> calculations: 1
>>> May 19 09:18:31 weatherpi weewx[2261]: manager: Daily summary version is 2.0
>>> May 

Re: [weewx-user] upgrade from 3.8.2 to 3.9.1 failure

[Ian Prescott]

sorry
the station is an Aercus 3080
and I am trying to find the howto on posting the config file

On Sun, 19 May 2019 at 10:40, Leon Shaner  wrote:

> Logs too abbreviated, or at least I am not able to pick out which driver /
> weatherstation version of are running.  Please expound.
> WMR200, WMR300, both have this issue.  Maybe others.
> Which model is yours?
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 18, 2019, at 8:05 PM, Ian Prescott  wrote:
>
> Hi
> I did an upgrade on my pi and by default weewx got upgraded as well.
> After a reboot the syslog shows the following.
> Any help would be appreciated.
> Thanks
>
>
> May 19 09:18:31 weatherpi systemd[1]: Starting LSB: weewx weather system...
> May 19 09:18:31 weatherpi weewx[2257]: engine: Initializing weewx version
> 3.9.1
> May 19 09:18:31 weatherpi weewx[2257]: engine: Using Python 2.7.9
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> May 19 09:18:31 weatherpi weewx[2257]: engine: Platform
> Linux-4.14.78-v7+-armv7l-with-debian-8.0
> May 19 09:18:31 weatherpi weewx[2257]: engine: Locale is 'en_AU.UTF-8'
> May 19 09:18:31 weatherpi weewx[2257]: engine: pid file is
> /var/run/weewx.pid
> May 19 09:18:31 weatherpi weewx[2247]: Starting weewx weather system:
> weewx.
> May 19 09:18:31 weatherpi systemd[1]: Started LSB: weewx weather system.
> May 19 09:18:31 weatherpi weewx[2261]: engine: Using configuration file
> /etc/weewx/weewx.conf
> May 19 09:18:31 weatherpi weewx[2261]: engine: Debug is 1
> May 19 09:18:31 weatherpi weewx[2261]: engine: Initializing engine
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading station type
> FineOffsetUSB (weewx.drivers.fousb)
> May 19 09:18:31 weatherpi weewx[2261]: fousb: driver version is 1.9
> May 19 09:18:31 weatherpi weewx[2261]: fousb: power cycling enabled for
> port 4 on hub 001:004
> May 19 09:18:31 weatherpi weewx[2261]: fousb: polling mode is PERIODIC
> May 19 09:18:31 weatherpi weewx[2261]: fousb: polling interval is 60
> May 19 09:18:31 weatherpi weewx[2261]: fousb: found station on USB bus=001
> device=006
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
> weewx.engine.StdTimeSynch
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
> weewx.engine.StdTimeSynch
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
> weewx.engine.StdConvert
> May 19 09:18:31 weatherpi weewx[2261]: engine: StdConvert target unit is
> 0x1
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
> weewx.engine.StdConvert
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
> weewx.engine.StdCalibrate
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
> weewx.engine.StdCalibrate
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
> weewx.engine.StdQC
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
> weewx.engine.StdQC
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
> weewx.wxservices.StdWXCalculate
> May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following values
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
> dewpoint=prefer_hardware, appTemp=prefer_hardware,
> rainRate=prefer_hardware, windrun=prefer_hardware,
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
> humidex=prefer_hardware, pressure=prefer_hardware,
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
> cloudbase=prefer_hardware
> May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
> weewx.wxservices.StdWXCalculate
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
> weewx.engine.StdArchive
> May 19 09:18:31 weatherpi weewx[2261]: engine: Archive will use data
> binding wx_binding
> May 19 09:18:31 weatherpi weewx[2261]: engine: Record generation will be
> attempted in 'software'
> May 19 09:18:31 weatherpi weewx[2261]: engine: Using archive interval of
> 300 seconds (software record generation)
> May 19 09:18:31 weatherpi weewx[2261]: engine: Use LOOP data in hi/low
> calculations: 1
> May 19 09:18:31 weatherpi weewx[2261]: manager: Daily summary version is
> 2.0
> May 19 09:18:31 weatherpi weewx[2261]: engine: Using binding 'wx_binding'
> to database 'weewx.sdb'
> May 19 09:18:31 weatherpi weewx[2261]: manager: Starting backfill of daily
> summaries
> May 19 09:18:32 weatherpi weewx[2261]: engine: Caught unrecoverable
> exception in engine:
> May 19 09:18:32 weatherpi weewx[2261]:   Non-positive value for
> record field 'interval': 0
> May 19 09:18:32 weatherpi weewx[2261]:   Traceback (most recent
> call last):
> May 19 09:18:32 weatherpi weewx[2261]: File
> "/usr/share/weewx/weewx/engine.py", line 884, in main
> May 19 09:18:32 weatherpi weewx[2261]:   engine =
> 

Re: [weewx-user] upgrade from 3.8.2 to 3.9.1 failure

[Leon Shaner]

Logs too abbreviated, or at least I am not able to pick out which driver / 
weatherstation version of are running.  Please expound.
WMR200, WMR300, both have this issue.  Maybe others.
Which model is yours?

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 18, 2019, at 8:05 PM, Ian Prescott  wrote:
> 
> Hi
> I did an upgrade on my pi and by default weewx got upgraded as well.
> After a reboot the syslog shows the following.
> Any help would be appreciated.
> Thanks
> 
> 
> May 19 09:18:31 weatherpi systemd[1]: Starting LSB: weewx weather system...
> May 19 09:18:31 weatherpi weewx[2257]: engine: Initializing weewx version 
> 3.9.1
> May 19 09:18:31 weatherpi weewx[2257]: engine: Using Python 2.7.9 (default, 
> Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> May 19 09:18:31 weatherpi weewx[2257]: engine: Platform 
> Linux-4.14.78-v7+-armv7l-with-debian-8.0
> May 19 09:18:31 weatherpi weewx[2257]: engine: Locale is 'en_AU.UTF-8'
> May 19 09:18:31 weatherpi weewx[2257]: engine: pid file is /var/run/weewx.pid
> May 19 09:18:31 weatherpi weewx[2247]: Starting weewx weather system: weewx.
> May 19 09:18:31 weatherpi systemd[1]: Started LSB: weewx weather system.
> May 19 09:18:31 weatherpi weewx[2261]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> May 19 09:18:31 weatherpi weewx[2261]: engine: Debug is 1
> May 19 09:18:31 weatherpi weewx[2261]: engine: Initializing engine
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading station type 
> FineOffsetUSB (weewx.drivers.fousb)
> May 19 09:18:31 weatherpi weewx[2261]: fousb: driver version is 1.9
> May 19 09:18:31 weatherpi weewx[2261]: fousb: power cycling enabled for port 
> 4 on hub 001:004
> May 19 09:18:31 weatherpi weewx[2261]: fousb: polling mode is PERIODIC
> May 19 09:18:31 weatherpi weewx[2261]: fousb: polling interval is 60
> May 19 09:18:31 weatherpi weewx[2261]: fousb: found station on USB bus=001 
> device=006
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
> weewx.engine.StdTimeSynch
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
> weewx.engine.StdConvert
> May 19 09:18:31 weatherpi weewx[2261]: engine: StdConvert target unit is 0x1
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
> weewx.engine.StdConvert
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
> weewx.engine.StdCalibrate
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
> weewx.engine.StdCalibrate
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
> weewx.engine.StdQC
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
> weewx.engine.StdQC
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
> May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
> windrun=prefer_hardware, heatindex=prefer_hardware, 
> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
> altimeter=prefer_hardware, cloudbase=prefer_hardware
> May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service 
> weewx.wxservices.StdWXCalculate
> May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service 
> weewx.engine.StdArchive
> May 19 09:18:31 weatherpi weewx[2261]: engine: Archive will use data binding 
> wx_binding
> May 19 09:18:31 weatherpi weewx[2261]: engine: Record generation will be 
> attempted in 'software'
> May 19 09:18:31 weatherpi weewx[2261]: engine: Using archive interval of 300 
> seconds (software record generation)
> May 19 09:18:31 weatherpi weewx[2261]: engine: Use LOOP data in hi/low 
> calculations: 1
> May 19 09:18:31 weatherpi weewx[2261]: manager: Daily summary version is 2.0
> May 19 09:18:31 weatherpi weewx[2261]: engine: Using binding 'wx_binding' to 
> database 'weewx.sdb'
> May 19 09:18:31 weatherpi weewx[2261]: manager: Starting backfill of daily 
> summaries
> May 19 09:18:32 weatherpi weewx[2261]: engine: Caught unrecoverable exception 
> in engine:
> May 19 09:18:32 weatherpi weewx[2261]:   Non-positive value for 
> record field 'interval': 0
> May 19 09:18:32 weatherpi weewx[2261]:   Traceback (most recent call 
> last):
> May 19 09:18:32 weatherpi weewx[2261]: File 
> "/usr/share/weewx/weewx/engine.py", line 884, in main
> May 19 09:18:32 weatherpi weewx[2261]:   engine = 
> engine_class(config_dict)
> May 19 09:18:32 weatherpi weewx[2261]: File 
> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
> 

[weewx-user] upgrade from 3.8.2 to 3.9.1 failure

[Ian Prescott]

Hi
I did an upgrade on my pi and by default weewx got upgraded as well.
After a reboot the syslog shows the following.
Any help would be appreciated.
Thanks


May 19 09:18:31 weatherpi systemd[1]: Starting LSB: weewx weather system...
May 19 09:18:31 weatherpi weewx[2257]: engine: Initializing weewx version
3.9.1
May 19 09:18:31 weatherpi weewx[2257]: engine: Using Python 2.7.9 (default,
Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
May 19 09:18:31 weatherpi weewx[2257]: engine: Platform
Linux-4.14.78-v7+-armv7l-with-debian-8.0
May 19 09:18:31 weatherpi weewx[2257]: engine: Locale is 'en_AU.UTF-8'
May 19 09:18:31 weatherpi weewx[2257]: engine: pid file is
/var/run/weewx.pid
May 19 09:18:31 weatherpi weewx[2247]: Starting weewx weather system: weewx.
May 19 09:18:31 weatherpi systemd[1]: Started LSB: weewx weather system.
May 19 09:18:31 weatherpi weewx[2261]: engine: Using configuration file
/etc/weewx/weewx.conf
May 19 09:18:31 weatherpi weewx[2261]: engine: Debug is 1
May 19 09:18:31 weatherpi weewx[2261]: engine: Initializing engine
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading station type
FineOffsetUSB (weewx.drivers.fousb)
May 19 09:18:31 weatherpi weewx[2261]: fousb: driver version is 1.9
May 19 09:18:31 weatherpi weewx[2261]: fousb: power cycling enabled for
port 4 on hub 001:004
May 19 09:18:31 weatherpi weewx[2261]: fousb: polling mode is PERIODIC
May 19 09:18:31 weatherpi weewx[2261]: fousb: polling interval is 60
May 19 09:18:31 weatherpi weewx[2261]: fousb: found station on USB bus=001
device=006
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
weewx.engine.StdTimeSynch
May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
weewx.engine.StdTimeSynch
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
weewx.engine.StdConvert
May 19 09:18:31 weatherpi weewx[2261]: engine: StdConvert target unit is 0x1
May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
weewx.engine.StdConvert
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
weewx.engine.StdCalibrate
May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
weewx.engine.StdCalibrate
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
weewx.engine.StdQC
May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
weewx.engine.StdQC
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
weewx.wxservices.StdWXCalculate
May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following values
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
dewpoint=prefer_hardware, appTemp=prefer_hardware,
rainRate=prefer_hardware, windrun=prefer_hardware,
heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
humidex=prefer_hardware, pressure=prefer_hardware,
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
cloudbase=prefer_hardware
May 19 09:18:31 weatherpi weewx[2261]: wxcalculate: The following
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
May 19 09:18:31 weatherpi weewx[2261]: engine: Finished loading service
weewx.wxservices.StdWXCalculate
May 19 09:18:31 weatherpi weewx[2261]: engine: Loading service
weewx.engine.StdArchive
May 19 09:18:31 weatherpi weewx[2261]: engine: Archive will use data
binding wx_binding
May 19 09:18:31 weatherpi weewx[2261]: engine: Record generation will be
attempted in 'software'
May 19 09:18:31 weatherpi weewx[2261]: engine: Using archive interval of
300 seconds (software record generation)
May 19 09:18:31 weatherpi weewx[2261]: engine: Use LOOP data in hi/low
calculations: 1
May 19 09:18:31 weatherpi weewx[2261]: manager: Daily summary version is 2.0
May 19 09:18:31 weatherpi weewx[2261]: engine: Using binding 'wx_binding'
to database 'weewx.sdb'
May 19 09:18:31 weatherpi weewx[2261]: manager: Starting backfill of daily
summaries
May 19 09:18:32 weatherpi weewx[2261]: engine: Caught unrecoverable
exception in engine:
May 19 09:18:32 weatherpi weewx[2261]:   Non-positive value for
record field 'interval': 0
May 19 09:18:32 weatherpi weewx[2261]:   Traceback (most recent
call last):
May 19 09:18:32 weatherpi weewx[2261]: File
"/usr/share/weewx/weewx/engine.py", line 884, in main
May 19 09:18:32 weatherpi weewx[2261]:   engine =
engine_class(config_dict)
May 19 09:18:32 weatherpi weewx[2261]: File
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
May 19 09:18:32 weatherpi weewx[2261]: 
 self.loadServices(config_dict)
May 19 09:18:32 weatherpi weewx[2261]: File
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
May 19 09:18:32 weatherpi weewx[2261]: 
 self.service_obj.append(weeutil.weeutil._get_object(svc)(self,
config_dict))
May 19 09:18:32 weatherpi weewx[2261]: File
"/usr/share/weewx/weewx/engine.py", line 500, in __init__
May 19 09:18:32 weatherpi weewx[2261]: 
 self.setup_database(config_dict)
May 19 09:18:32 

Re: [weewx-user] Problem with display after some updates

[p q]

The date thing is weird, Weewx uses unix epochs as the base unit, which is
the number of seconds since 1/1/1970. I don't know how you're getting 1049
as I was seeing an hour ago or 1899 as it's showing now. It shouldn't be
possible to get a date before 1970.

I bet for the temp, you're double converting C to F. It's a guess.

Sorry, I'm not much help.

On Sat, May 18, 2019 at 2:04 PM Sean Garland  wrote:

> Also it appears if my wind gust isn't working right since the gust is
> lower than the wind
>
> 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/ba748479-4308-4180-b73c-301628adb6a3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
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/CAA1SM23DYQnZ4sA_%2B9e1-s6tC0cq3Q_VjrAizRT4HhDKTwOdHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Problem with display after some updates

[Sean Garland]

Also it appears if my wind gust isn't working right since the gust is lower 
than the wind

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/ba748479-4308-4180-b73c-301628adb6a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Problem with display after some updates

[Sean Garland]

Good afternoon Peter...  No snow, but it's windy... ;)

Which values are you looking for?  In the skin.conf for both the Testtags 
and Clientraw I have the following for the TimeFormats section:
date_f = %-m/%-d/%Y
date_time_f= %-m/%-d/%Y %H:%M

And I just corrected a typo I had in weewx.conf, but here is the similar 
section:
[[[Units]]]
TimeFormats
date_time_f = %m/%d/%Y %H:%M
date_f = %m/%d/%Y

The data in the testtags.php looks correct.  I just don't know where i 
messed it up.  I also don't have any 212 degree anything in the data files, 
only in the display because something somewhere else is off.  

Thanks!
Sean


On Saturday, May 18, 2019 at 1:36:02 PM UTC-7, p q wrote:
>
> Snowing up there today?
>
> What do you have in the template for the date and for the today's high 
> temp?
>
> When you update the skin you don't have to restart, but if you change 
> weewx.conf you need to restart for it to take effect.
>
> On Sat, May 18, 2019 at 1:20 PM Sean Garland  > wrote:
>
>> Hello group!
>>
>> I upgraded my Weewx to the latest, and then updated Weewx-WD to 1.0.3 
>> (then had to update to 1.0.4 because of outTemp issue).  During this 
>> transition everything switched to metric.  In the process of "fixing" the 
>> metric issue, I now am having an issue with the date displaying correctly, 
>> and the "todays high temp" is all screwy.  
>>
>> I've probably messed with too much junk, but currently have my WDdateMDY 
>> set to True, and have the weewx.conf WD sections set to -m/-d/Y...  AND 
>> have also set the Testags and clientraw skin.conf to be -m/-d/Y in each 
>> location.  It still seems like nothing is changing no matter what I set any 
>> of that stuff to.  Not sure what I've done or am doing wrong at this 
>> point.  
>>
>> I also don't understand the correlation of the weewx.conf, and the 
>> skin.conf at this point.  It seems like we're setting the same thing in 
>> many places and maybe I've messed it up from there?  Just not sure at this 
>> point as I've been banging my head on it for a while, and really it's been 
>> a couple years since I built the system, so I can't remember all the spots 
>> that changes need to be made.  
>>
>> Any help would be great!  
>> https://weather.lavacrawlers.com is the site
>>
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/57ccc655-6986-40bf-b1e8-773c0a5b93ef%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> 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/9ee6d1ed-2d28-4bb6-ae6a-aa99cd2da8a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Problem with display after some updates

[p q]

Snowing up there today?

What do you have in the template for the date and for the today's high temp?

When you update the skin you don't have to restart, but if you change
weewx.conf you need to restart for it to take effect.

On Sat, May 18, 2019 at 1:20 PM Sean Garland  wrote:

> Hello group!
>
> I upgraded my Weewx to the latest, and then updated Weewx-WD to 1.0.3
> (then had to update to 1.0.4 because of outTemp issue).  During this
> transition everything switched to metric.  In the process of "fixing" the
> metric issue, I now am having an issue with the date displaying correctly,
> and the "todays high temp" is all screwy.
>
> I've probably messed with too much junk, but currently have my WDdateMDY
> set to True, and have the weewx.conf WD sections set to -m/-d/Y...  AND
> have also set the Testags and clientraw skin.conf to be -m/-d/Y in each
> location.  It still seems like nothing is changing no matter what I set any
> of that stuff to.  Not sure what I've done or am doing wrong at this
> point.
>
> I also don't understand the correlation of the weewx.conf, and the
> skin.conf at this point.  It seems like we're setting the same thing in
> many places and maybe I've messed it up from there?  Just not sure at this
> point as I've been banging my head on it for a while, and really it's been
> a couple years since I built the system, so I can't remember all the spots
> that changes need to be made.
>
> Any help would be great!
> https://weather.lavacrawlers.com is the site
>
> 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/57ccc655-6986-40bf-b1e8-773c0a5b93ef%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
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/CAA1SM20aXn3-ewLjdJ6D9ipr%3D5psVRHnN5CqVHyS6Jit0Ofv3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Problem with display after some updates

[Sean Garland]

Hello group!

I upgraded my Weewx to the latest, and then updated Weewx-WD to 1.0.3 (then 
had to update to 1.0.4 because of outTemp issue).  During this transition 
everything switched to metric.  In the process of "fixing" the metric 
issue, I now am having an issue with the date displaying correctly, and the 
"todays high temp" is all screwy.  

I've probably messed with too much junk, but currently have my WDdateMDY 
set to True, and have the weewx.conf WD sections set to -m/-d/Y...  AND 
have also set the Testags and clientraw skin.conf to be -m/-d/Y in each 
location.  It still seems like nothing is changing no matter what I set any 
of that stuff to.  Not sure what I've done or am doing wrong at this 
point.  

I also don't understand the correlation of the weewx.conf, and the 
skin.conf at this point.  It seems like we're setting the same thing in 
many places and maybe I've messed it up from there?  Just not sure at this 
point as I've been banging my head on it for a while, and really it's been 
a couple years since I built the system, so I can't remember all the spots 
that changes need to be made.  

Any help would be great!  
https://weather.lavacrawlers.com is the site

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/57ccc655-6986-40bf-b1e8-773c0a5b93ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: On this date

[p q]

Oh wait. I it's outputting "0.0 in"
I do need to do .raw, but as
$day.rain.sum.raw >0

Thank you. That was it.

On Saturday, May 11, 2019 at 6:30:47 AM UTC-7, Robin wrote:
>
> I apologise if this has been asked before or if there is a simple and 
> obvious way to do this, but I can't see it.
>
> I want to display the temperature (min,max) for today's date for each year 
> since we started keeping records.
>
> Can somebody point me in the right direction?
>
> Thanks people.
>

-- 
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/24c50f53-d3e0-4a26-8c5a-97fde772acfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: On this date

[p q]

Nope. I get a KeyError when I switch to $day.rain.raw. No errors with 
$day.rain.sum. 

I tried
$day.rain.sum >0
$day.rain.sum >0.0
$day.rain.sum >0.00
$day.rain.sum

Same deal. Is there a string/real conversion problem? Can I force it to a 
number?

On Saturday, May 18, 2019 at 10:21:22 AM UTC-7, Andrew Milner wrote:
>
> wouldnt it just be day.rain.raw > 0 ???
>
> On Saturday, 18 May 2019 20:15:15 UTC+3, p q wrote:
>>
>> This is great. I implemented it on my site this morning. I added it to 
>> the bottom of the Since Midnight table at the bottom. Does exactly what I 
>> was looking for.
>>
>> The only issue I'm having is that I want to display the rain total only 
>> if it's not zero. I live in an area where there's typically no rain from 
>> May to October so I want to skip the line for the rain when it's 0. I tried 
>> an if statement but it's not effective. Any hints?
>>
>> Here's the template code: 
>>   
>> 
>>   On This Day
>>   $day.dateTime.format("%b %d")
>> 
>> 
>> #for $day in $this_span.periods
>>$day.dateTime.format("%Y")
>> H: $day.outTemp.max : 
>> $day.outTemp.min
>>#if $day.rain.sum > 0
>>Rain: $day.rain.sum
>>#end if
>> #end for
>> 
>>   
>>
>>
>> On Wednesday, May 15, 2019 at 7:03:35 AM UTC-7, V. Kelly Bellis wrote:
>>>
>>> Thanks for doing this Gary. I'm too new to all of this stuff to have 
>>> anything to look back on, but it's very cool to see what can be done with 
>>> weewx.
>>> - Kelly
>>>
>>> On Tuesday, May 14, 2019 at 8:37:55 PM UTC-4, gjr80 wrote:

 I should have given this a little more thought before publishing. I 
 have since made a slight change to the tag name to make it a little more 
 logical and consistent with the other iterative tags that WeeWX supports 
 (and to remove a 'this'). The tag now uses .periods in lieu of .this; 
 for example, you would now use the $this_span tag as follows:

 #for $day in this_span.periods
 $day.outTemp.max at $day.outTemp.maxtime
 #end for

 Any existing template code will work fine with the current version with 
 just the need to change '.this' to '.periods'.

 I have also created a page 
  
 in the wiki of the repo containing the this search list extension code 
 that explains the installation and usage of the this search list 
 extension. Hopefully this is a little more user friendly and easier to 
 read than comments in the code.

 Gary

 On Monday, 13 May 2019 17:40:37 UTC+10, gjr80 wrote:
>
> I've put together a search list extension that should do what you 
> want. You will find the code here 
> .
>  
> The SLE is based on the existing WeeWX tag machinery that enables 
> iteration  over 
> periods. So with the SLE installed you can do something like:
>
> #for $day in this_span.this
> $day.outTemp.max at $day.outTemp.maxtime
> #end for
>
> to display the maximum daily temperature and the time it occurred on 
> this day in all years in the archive. The output would be something like:
>
> 24.5°C at 11 May 2017 12:51:00
> 26.7°C at 11 May 2018 13:31:00
> 23.4°C at 11 May 2019 13:15:00
>
> There are various parameters that can be set against $this_span to 
> limit the period covered (the default is all records but you can limit it 
> to the last x years, months etc as with the existing $span tag). 
> There are various parameters that can be applied to .this to set the 
> day to be used, for example, .this($period='week') and 
> .this($period='month') will provide stats for this week and this 
> month respectively over all years. There are many variations and 
> permutations, I have tried to capture a variety of use cases in the up 
> front comment in this.py 
> 
> .
>
> To install/use:
>
> 1. Download the file this.py to the WeeWX machine and save to the 
> $BIN_ROOT/user directory:
>
> for a setup.py install:
> 
> $ wget -P /home/weewx/bin/user https://
> raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py
>
> otherwise:
>
> $ wget -P /usr/share/weewx/user https://
> raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py
>
> 2.  Add the 

[weewx-user] Re: On this date

[Andrew Milner]

wouldnt it just be day.rain.raw > 0 ???

On Saturday, 18 May 2019 20:15:15 UTC+3, p q wrote:
>
> This is great. I implemented it on my site this morning. I added it to the 
> bottom of the Since Midnight table at the bottom. Does exactly what I was 
> looking for.
>
> The only issue I'm having is that I want to display the rain total only if 
> it's not zero. I live in an area where there's typically no rain from May 
> to October so I want to skip the line for the rain when it's 0. I tried an 
> if statement but it's not effective. Any hints?
>
> Here's the template code: 
>   
> 
>   On This Day
>   $day.dateTime.format("%b %d")
> 
> 
> #for $day in $this_span.periods
>$day.dateTime.format("%Y")
> H: $day.outTemp.max : 
> $day.outTemp.min
>#if $day.rain.sum > 0
>Rain: $day.rain.sum
>#end if
> #end for
> 
>   
>
>
> On Wednesday, May 15, 2019 at 7:03:35 AM UTC-7, V. Kelly Bellis wrote:
>>
>> Thanks for doing this Gary. I'm too new to all of this stuff to have 
>> anything to look back on, but it's very cool to see what can be done with 
>> weewx.
>> - Kelly
>>
>> On Tuesday, May 14, 2019 at 8:37:55 PM UTC-4, gjr80 wrote:
>>>
>>> I should have given this a little more thought before publishing. I have 
>>> since made a slight change to the tag name to make it a little more logical 
>>> and consistent with the other iterative tags that WeeWX supports (and to 
>>> remove a 'this'). The tag now uses .periods in lieu of .this; for 
>>> example, you would now use the $this_span tag as follows:
>>>
>>> #for $day in this_span.periods
>>> $day.outTemp.max at $day.outTemp.maxtime
>>> #end for
>>>
>>> Any existing template code will work fine with the current version with 
>>> just the need to change '.this' to '.periods'.
>>>
>>> I have also created a page 
>>>  
>>> in the wiki of the repo containing the this search list extension code 
>>> that explains the installation and usage of the this search list 
>>> extension. Hopefully this is a little more user friendly and easier to 
>>> read than comments in the code.
>>>
>>> Gary
>>>
>>> On Monday, 13 May 2019 17:40:37 UTC+10, gjr80 wrote:

 I've put together a search list extension that should do what you want. 
 You will find the code here 
 .
  
 The SLE is based on the existing WeeWX tag machinery that enables 
 iteration  over 
 periods. So with the SLE installed you can do something like:

 #for $day in this_span.this
 $day.outTemp.max at $day.outTemp.maxtime
 #end for

 to display the maximum daily temperature and the time it occurred on 
 this day in all years in the archive. The output would be something like:

 24.5°C at 11 May 2017 12:51:00
 26.7°C at 11 May 2018 13:31:00
 23.4°C at 11 May 2019 13:15:00

 There are various parameters that can be set against $this_span to 
 limit the period covered (the default is all records but you can limit it 
 to the last x years, months etc as with the existing $span tag). There 
 are various parameters that can be applied to .this to set the day to 
 be used, for example, .this($period='week') and .this($period='month') 
 will provide stats for this week and this month respectively over all 
 years. There are many variations and permutations, I have tried to capture 
 a variety of use cases in the up front comment in this.py 
 
 .

 To install/use:

 1. Download the file this.py to the WeeWX machine and save to the 
 $BIN_ROOT/user directory:

 for a setup.py install:
 
 $ wget -P /home/weewx/bin/user https://
 raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py

 otherwise:

 $ wget -P /usr/share/weewx/user https://
 raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py

 2.  Add the following line to the skin config file [CheetahGenerator] 
 stanza for the skin in which the SLE is to be used:
 
 search_list_extensions = user.this.ThisSLE

 if the search_list_extensions config option already exists add 
 user.this.ThisSLE to the end of the option using a comma as a 
 separator, eg:
 
 search_list_extensions = user,another.SLE, user.this.ThisSLE

 3.  Add the required 

[weewx-user] Re: On this date

[p q]

This is great. I implemented it on my site this morning. I added it to the 
bottom of the Since Midnight table at the bottom. Does exactly what I was 
looking for.

The only issue I'm having is that I want to display the rain total only if 
it's not zero. I live in an area where there's typically no rain from May 
to October so I want to skip the line for the rain when it's 0. I tried an 
if statement but it's not effective. Any hints?

Here's the template code: 
  

  On This Day
  $day.dateTime.format("%b %d")


#for $day in $this_span.periods
   $day.dateTime.format("%Y")
H: $day.outTemp.max : 
$day.outTemp.min
   #if $day.rain.sum > 0
   Rain: $day.rain.sum
   #end if
#end for

  


On Wednesday, May 15, 2019 at 7:03:35 AM UTC-7, V. Kelly Bellis wrote:
>
> Thanks for doing this Gary. I'm too new to all of this stuff to have 
> anything to look back on, but it's very cool to see what can be done with 
> weewx.
> - Kelly
>
> On Tuesday, May 14, 2019 at 8:37:55 PM UTC-4, gjr80 wrote:
>>
>> I should have given this a little more thought before publishing. I have 
>> since made a slight change to the tag name to make it a little more logical 
>> and consistent with the other iterative tags that WeeWX supports (and to 
>> remove a 'this'). The tag now uses .periods in lieu of .this; for 
>> example, you would now use the $this_span tag as follows:
>>
>> #for $day in this_span.periods
>> $day.outTemp.max at $day.outTemp.maxtime
>> #end for
>>
>> Any existing template code will work fine with the current version with 
>> just the need to change '.this' to '.periods'.
>>
>> I have also created a page 
>>  
>> in the wiki of the repo containing the this search list extension code 
>> that explains the installation and usage of the this search list 
>> extension. Hopefully this is a little more user friendly and easier to 
>> read than comments in the code.
>>
>> Gary
>>
>> On Monday, 13 May 2019 17:40:37 UTC+10, gjr80 wrote:
>>>
>>> I've put together a search list extension that should do what you want. 
>>> You will find the code here 
>>> .
>>>  
>>> The SLE is based on the existing WeeWX tag machinery that enables 
>>> iteration  over 
>>> periods. So with the SLE installed you can do something like:
>>>
>>> #for $day in this_span.this
>>> $day.outTemp.max at $day.outTemp.maxtime
>>> #end for
>>>
>>> to display the maximum daily temperature and the time it occurred on 
>>> this day in all years in the archive. The output would be something like:
>>>
>>> 24.5°C at 11 May 2017 12:51:00
>>> 26.7°C at 11 May 2018 13:31:00
>>> 23.4°C at 11 May 2019 13:15:00
>>>
>>> There are various parameters that can be set against $this_span to 
>>> limit the period covered (the default is all records but you can limit it 
>>> to the last x years, months etc as with the existing $span tag). There 
>>> are various parameters that can be applied to .this to set the day to 
>>> be used, for example, .this($period='week') and .this($period='month') 
>>> will provide stats for this week and this month respectively over all 
>>> years. There are many variations and permutations, I have tried to capture 
>>> a variety of use cases in the up front comment in this.py 
>>> 
>>> .
>>>
>>> To install/use:
>>>
>>> 1. Download the file this.py to the WeeWX machine and save to the 
>>> $BIN_ROOT/user directory:
>>>
>>> for a setup.py install:
>>> 
>>> $ wget -P /home/weewx/bin/user https://
>>> raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py
>>>
>>> otherwise:
>>>
>>> $ wget -P /usr/share/weewx/user https://
>>> raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py
>>>
>>> 2.  Add the following line to the skin config file [CheetahGenerator] 
>>> stanza for the skin in which the SLE is to be used:
>>> 
>>> search_list_extensions = user.this.ThisSLE
>>>
>>> if the search_list_extensions config option already exists add 
>>> user.this.ThisSLE to the end of the option using a comma as a 
>>> separator, eg:
>>> 
>>> search_list_extensions = user,another.SLE, user.this.ThisSLE
>>>
>>> 3.  Add the required $this_span.this code to the template concerned.
>>>
>>> 4.  After the next report cycle is complete confirm there are no errors 
>>> in the log and the report has been generated as expected.
>>>
>>> Gary
>>>
>>> On Saturday, 11 May 2019 

Re: [weewx-user] Re: Is There an Alternative to Windy for Embed in Belchertown Skin

[Pat]

I haven't found a good embed other than windy which is why I put it in 
there. The URL variables have a metricTemp option but setting it to 0 or 1 
doesn't change the temp to imperial, so it seems like a windy problem like 
you've mentioned. 

I once ran and developed a live storm chasing video streaming website 
called TornadoChannel.com (which I still own, but it's offline) where I 
used radar data provided Iowa State University through their Mesonet. 
TornadoChannel would request transparent radar overlays from iastate, which 
I would overlay on top of Google Maps. I haven't dug around their website 
in a couple of years - so I don't recall if they have an embed 
radar/temperature model, but it may exist. Feel free to see what they've got 
. Maybe it'll help?

On Friday, May 17, 2019 at 4:55:46 PM UTC-4, G Hammer wrote:
>
> It's along running issue with the embed.
> Been reported for at last as long as I've used it.
>
> Thus, find a different radar embed.
>
> On Friday, May 17, 2019 at 3:30:22 PM UTC-4, Colin Larsen wrote:
>>
>> Also just a thought, there is a switch in the Windy API to force the 
>> units, but I would have thought it was in the generated link too. I'll see 
>> if I can fish it out but I know it's documented on the Windy website 
>> somewhere
>>
>> On Sat, 18 May 2019, 07:13 G Hammer,  wrote:
>>
>>> I understand that the embed configuration indicates you can choose how 
>>> to display wind and temperature.
>>> The temperature never shows any but metric no matter what I choose in 
>>> the setup. See image step-01
>>> Rain is always in mm, wind however does show mph. See image step-02
>>>
>>> What I mean by 'clicking the label' is, for example, click the C next to 
>>> Temperature and it should change to F. That applies to any of the data 
>>> displayed, Rain Wind Wind Gusts
>>> This also only works with Wind.
>>>
>>> Are these Windy problems? Yes. Which is why I wanted to know if anyone 
>>> had a different radar display they like.
>>>
>>>
>>>
>>> On Friday, May 17, 2019 at 2:23:48 PM UTC-4, Colin Larsen wrote:

 As was pointed out this map is highly configurable via Windy.com, just 
 decide what you information you want and paste the link into the 
 appropriate conf file. Otherwise you may of course change the link to any 
 other source you like too.
 Can you post an example of what you mean by "clicking the label"

 On Sat, 18 May 2019, 06:17 G Hammer,  wrote:

> The radar map. 
>
> On Fri, May 17, 2019 at 2:16 PM Colin Larsen  
> wrote:
>
>> Are you wanting to change the map picture or the 8 day forecast?
>>
>> On Sat, 18 May 2019, 02:34 G Hammer,  wrote:
>>
>>> Except that doesn’t work. 
>>>
>>> On Fri, May 17, 2019 at 10:33 AM HoracioDos  
>>> wrote:
>>>
 Hello.
 Windy iframe designer allows to change wind and temperature units 
 to F and mph. This is the link
 https://www.windy.com/-Embed-widget-on-page/widgets?
 Then you can generate the iframe code that suits you and paste in 
 radar_html keyword

 On Friday, May 17, 2019 at 10:04:59 AM UTC-3, G Hammer wrote:
>
> I use and like the Belchertown skin.
> I like the Windy.com website and the app on my mobile.
>
> I do not care for the embed, it only shows metric values and 
> clicking the label does not change this as it should.
>
> So, any favorite to replace the Windy embed?
>
> -- 
 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/Gt0v5Tf79T4/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com
>>>  
>>> 
>>> .
>>> For more 

[weewx-user] Re: Belchertown skin 0.9 now available

[Pat]

This is a bug which will be fixed in the next version, 1.0. It is due to 
there being no earthquakes in your area and no timestamp being available. 

To fix this, either disable earthquakes for now by setting earthquake_enabled 
= 0

Or increase your earthquake radius to something larger than your current 
one. Example, 2000km. Change setting earthquake_maxradiuskm = 2000

Skin version 1.0 comes with a fully re-written Graph Generator, automatic 
dark mode and more user customization and translations. If you want to test 
skin version 1.0, there's a small group of testers helping me test new 
Graph features and kill bugs. You can follow along on my GitHub 
 under the development branch 
, and 
because the skin has been almost entirely re-written, there's specific 
upgrade instructions here 

. 

Please understand this is a *beta version* and it's being updated very 
frequently. Please only install if you're willing to help test the new 
features (so I can fix and document them).


On Saturday, May 18, 2019 at 6:53:38 AM UTC-4, WILWetter25 wrote:
>
> Hey guys,
>
> I have a problem with the skin: Forecast Earth-Quakes and Graphs aren't 
> loading any more. This problem exists only on main page.
>
> http://www.mosel-wetter.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/f79ffb0d-e12b-4057-a736-04dcf7c96745%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Belchertown skin 0.9 now available

[WILWetter25]

Hey guys,

I have a problem with the skin: Forecast Earth-Quakes and Graphs aren't loading 
any more. This problem exists only on main page.

http://www.mosel-wetter.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/ec747be9-51f3-46f5-a1a9-d08735aeb1ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.