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 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/aa468867-16b5-49e8-bdc3-41665e6f5c4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
