Topic: WL Tags

[Curly]

I'm working on a project to parse all of the WeatherLink  (ver 5.8.0) tags that are separated by a comma.
The problem is WL won't parse any outside temperature or time tag above station 5. The same goes for all Humidity and time tags from station 4 and above. I've also tried to parse each problem tag separately with no luck. Here is the first one that won't work.  <!--Temperature5-->

Any ideas on why they won't convert ???

Curly

[xmas1313]

Hey Curly...

This is a shot in the dark, but do you have your tags separated by comma in a single line in your .htx file?  I've noticed in the past that if WL tags are past a certain column in the .htx file, the program won't replace them with data.  I'm not sure what the limit is or whether this has been corrected since the last time I ran into it.

Hope this helps,

Scott
arlingtonweather.net

[Curly]

This is a shot in the dark, but do you have your tags separated by comma in a single line in your .htx file?  I've noticed in the past that if WL tags are past a certain column in the .htx file, the program won't replace them with data.  I'm not sure what the limit is or whether this has been corrected since the last time I ran into it.

I've discovered that.  The tags are split up so there are 5 tags per line. It just won't convert a single "bad" tag in a htx.
Something is telling me it's a WL thing and that they must be used in a combination with something else. ?

[ncpilot]

There is a documented string length limit for the WL .htx parser... it's 200 characters...

You'll have to break up your template file into more separate lines... I've run into this issue myself...

[Curly]

There is a documented string length limit for the WL .htx parser... it's 200 characters...

You'll have to break up your template file into more separate lines... I've run into this issue myself...

Limiting 5 tags per line keeps it under the 200 rule. I've even broke it down to two tags a line to see if there was a difference. The output should be --- so that wouldn't go near the 200 characters.
I've determined that it is the tag itself that doesn't get parsed instead of the line. It won't parse just one of those tags by itself in a htx file.

[ncpilot]

Maybe it's a bug in 5.8? Can you try 5.7?

Nevermind, I just tried it, and it will parse the tags up to temp5, then just prints the tag itself... curious...

[Curly]

It's been a head-scratcher.

Makes me wonder if anybody has more than 5 temp and 5 humidity sensors.

[Cienega32]

What's interesting (to me) is that Temp5 is where the "changes from the previous version" is noted in the Tag List doc that came with 5.6. Same with Humidity4.

[anchorageweather]

What's interesting (to me) is that Temp5 is where the "changes from the previous version" is noted in the Tag List doc that came with 5.6. Same with Humidity4.

Hmmm....yes, wierd.  There is something up with the exact tags mentioned - those tags are bolded in the Weather Tag List.rtf file that comes with WL?!?

[Curly]

I have the latest scoop on the tags.

A message was sent to davisnet.com about the these tags and they replied with this:

Hello,

This is a bug. The support for the tags was added but the software was never
updated to support the new tags. This has been reported as a bug to be fixed.
I can't tell you when the fix will be available, but when it is, you can
download it from the link below...

http://www.davisnet.com/support/weather/software_sftwr.asp

[Cienega32]

Not that it concerns me but that sounds as if the software from ver 5.6 and later never supported the new tags that were detailed as "new tags" in the 5.6 docs!

[Curly]

I doubt if there is anybody that has a station with at least 4 humidity and 5 temp sensors connected and running WL.
There could be a few out there and maybe they are just testing the field to see if it's worth the effort to change the software. ?

I'm not slamming WL but  it just shows how well the other vendors are concerned about their software, customers and support.

I'm still laughing over the reply-  added support with no support. 

[Cienega32]

... and talking about WL tags -

I asked WL Support about utilizing tags for monthly/yearly event DATES such as "Year's High temp on: {HiYearlyOutsideTempDate}" and the response was, after a reference to the 5.6 docs: "If it not a tag then I will ask for it to be added in future release."

I hope they actually add it to more than just the docs...

[Curly]

While they fix the bug, maybe they will add some more tags in the next release.