Tom,
Yep, same parser just a different entry point. Ken appears to now be
hosting the previous tnetweather wd parser page.
Gary
On Monday, 20 May 2019 22:21:52 UTC+10, Tom Robertson wrote:
>
> This might the site you are talking about.
>
> http://saratoga-weather.org/wdparser.php
>
> -
>
Sean,
OK, the issue is the day = %X under [StdReports] [[Detfaults]] [[[Units]]]
TimeFormats. We need to leave that alone as changing it may affect
other reports. What we need to do is add an override for the clientraw
reports. Add a TimeFormats section to the [[wdClientraw]]
Good morning everyone!
Again - thank you for looking into this. This is just a pet project for me
and it's been fun, but long times between me messing with it, so takes me a
bit to find all the parts, and make adjustments... I have the parser from
Saratoga weather up and keep refreshing
This might the site you are talking about.
http://saratoga-weather.org/wdparser.php
-
Tom
On May 19, 2019, 6:35 PM -0500, gjr80 , wrote:
> Ok, that fixed a few issues with clientraw.txt but now the parsing of
> clientraw.txt is failing when it hits fields containing a time. Again no spec
>
Ok, that fixed a few issues with clientraw.txt but now the parsing of
clientraw.txt is failing when it hits fields containing a time. Again no
spec for clientraw.txt to work from but we have found that any field
representing a time needs to be in the format HH:MM:SS or HH:MM. At the
moment
Good morning!
Thanks Gary for that insight. I've noticed the behavior of the correct
into being overwritten by something in the past and didn't really
understand what was happening. It's very clear now.
What was really interesting is that although N/A was still present in the
clientraw.txt,
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
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
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
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
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!
>
11 matches
Mail list logo
