Clientrawhour.txt

[EmjayNet]

Whlist adding extra data display to my site, I was trying to get data from Clientrawhour.txt but came accross a lot of errors due to invalid charters.

Running the client raw files through http://www.tnetweather.com/wd-parser.php I found loads of the following:

0.00 - } {math- 0.00
And the file is filled with to much data, loads of set of 0.00 which should not be there either.

I'm assuming there is a error somewhere! (can anyone else confirm this who uses MH for WDL)

Since updating to 4.6k (Build 144) I'm also having problems getting the Solar Last 24 Hours graph & Solar Last Hour to display any data.



The forcast Icon appears to be going wrong as well, VP display show full sun but WDL has heavy rain?

The version I updated from was update-v4.6e.upd which worked great, whats gone wrong?

[d_l]

The forcast Icon appears to be going wrong as well, VP display show full sun but WDL has heavy rain?

The version I updated from was update-v4.6e.upd which worked great, whats gone wrong?

This is what is wrong with the icons viewtopic.php?f=16&t=8033

Unfortunately the forecast icon number values from the VP2 LOOPs do not match up with the icon number values out of Weather Display which are what WDL expects for an input. See WD's forecast icon values listed here: http://www.tnetweather.com/nb-0100.php

The Meteohub needs to run a translation matrix to convert VP2 values to WD values, e.g. VP2 value 8 representing sunny conditions would need to be mapped to WD value 0 which equals sunny for that software. The switch that Boris made allows the Meteohub to show more possible weather conditions for Davis systems than what were previously displayed. Now to just get the conditions to be correct for WDL.

[admin]

yes, you are right. But I have no real clue how to map Vantage icon values to WD-Live values. Anybody out there who is volunteering to make the transfer matrix?

WD-Live expects this:

Code: Select all

0= sunny
1= clear night
2= cloudy
3= cloudy2
4= cloudy night
5= dry
6= fog
7= haze
8= heavy rain
9= mainly fine
10=mist
11=night fog
12=night heavy rain
13=night overcast
14=night rain
15=night showers
16=night snow
17=night thunder
18=overcast
19=partly cloudy
20=rain
21=rain2
22=showers2
23=sleet
24=sleet showers
25=snow
26=snowmelt
27=snowshowers2
28=sunny
29=thundershowers
30=thundershowers2
31=thunderstorms
32=tornado
33=windy
34=stopped raining
35=windy rain

And the vantage Icon codes are like this:

Code: Select all

Forecast Icons field 89 in LOOP packet are bit-coded:
Forecast Icons, Bit #
Rain, 0
Cloud, 1
Partly Cloudy, 2
Sun, 3
Snow, 4

Examples: 
decimal, hex, meaning
6, 0x06, Partially Cloudy
2, 0x02, Mostly Cloudy
3, 0x03, Mostly Cloudy, Rain within 12 hours
18, 0x12, Mostly Cloudy, Snow within 12 hours
19, 0x13, Mostly Cloudy, Rain or Snow within 12 hours
7, 0x07, Partially Cloudy, Rain within 12 hours
22, 0x16, Partially Cloudy, Snow within 12 hours
23, 0x17, Partially Cloudy, Rain or Snow within 12 hours

If someone defines a transformation list to map a Vantage icon (0-31) code to a WD-live current code (0-35), I will implement this into next Meteohub version.

[EmjayNet]

Ok, that answers the icons issue.
I don't understand why we move to something that does not work from something that was working resonably well, just my opinion.

What about the Clientrawhour.txt issue and the solor graphs issue?

[d_l]

I don't understand why we move to something that does not work from something that was working resonably well, just my opinion.

Previously only five different weather conditions were possible with just the icons, but by using the icon's values, up to nine conditions can be listed.

IMHO, the nine VP2 weather conditions would map to the WD conditions as follows:

Code: Select all

VP2                                                    WD
8=Sunny                                               0=SUNNY
6=Partially Cloudy                                    19=PARTLY CLOUDY
2=Mostly Cloudy	                                    2=CLOUDY
3=Mostly Cloudy, Rain within 12 hours                 20=RAIN
18=Mostly Cloudy, Snow within 12 hours                25=SNOW
19=Mostly Cloudy, Rain or Snow within 12 hours        23=SLEET
7=Partially Cloudy, Rain within 12 hours              22=SHOWERS2
22=Partially Cloudy, Snow within 12 hours             27=SNOWSHOWERS2
23=Partially Cloudy, Rain or Snow within 12 hours     24=SLEET SHOWERS

Any alternative mapping suggestions would be welcome.

Those nine VP2 conditions are actually combinations of the five VP2 icons that can display on the console with either one or two icons being displayed at one time

Note: As far as I understand it, WDL then looks at both the WD input icon value AND the text forecast to decide what icon it will display.

[EmjayNet]

Yes, I understood the argument, but it seems illogical to make the change without a working solution.

I don't dispute the newer way would be better, when it works but thats not the case.

I'm really asking for some discreation to be used when implementing improvements, thats is not a total solution that have a ditrement effect on others users who would perfer a consistant working weather site.

Don't get wrong I'm all for improving MH but this is testing on production websites.

[admin]

As I don't have a VP2 myself, it is a bit hard for me to test that at all. I thought that WD-live could directly handle the vantage icon codes, but it turns out, that WD does some undocumented abstraction from that and that WD-live parses for key words in the resulting icon text strings. Again, WD acts like a black box here. So we have to go a little through experimentation and guess work. As long as the icon thing (which WD seems to handle as current weather although Vantage does not report anything on current weather, but only on forecast) is not understood, I would recommend to go with the forecast rules for display via WD-live, these are untouched.

To my understanding the 9 examples of vantage codes are just examples. I guess all 32 situations can show up and we will need a mapping for all that.

[d_l]

To my understanding the 9 examples of vantage codes are just examples. I guess all 32 situations can show up and we will need a mapping for all that.

Boris, I really think there are only nine VP2 forecast values.

This is how I understand it. The console's display can show only five different icons. Three of those define the cloud conditions: sunny, partly cloudy, or cloudy. The other two define precipitation types: no icon (no precip), rain, snow, or rain and snow. There are therfore only nine possible combinations of these five icons:

Code: Select all

Sunnny
Partly Cloudy
Cloudy
Cloudy & Rain
Cloudy & Snow
Cloudy & Rain/Snow
Partly Cloudy & Rain
Parly Cloudy & Snow
Partly Cloudy & Rain/Snow

These combinations are of course the same as the icon values' definitions. I hope my explanation makes sense. If there is a different explanation, I'd be glad to hear it.

[EmjayNet]

My vote goes to the faster solution for a working WDL a quickest as possible, for me is to switch back to the way it was with the five icons.

For me the extra four icons don't really seem to add that much, but I appreciate others have a different view.

[admin]

I just uploaded a 4.6m variant, which might cure the problem. As I don't have a vantage to test with, please give it a try yourself.

[EmjayNet]

No, still the same.

It does not appear to be effecting WDL, (except for solar graphs) I just can't extract data from the file for my own purposes.

As it not to important, it can wait till you return.

Have a nice holiday!

[EmjayNet]

Boris,

I know your busy doing the new 'virtual sensors' but any chance you could fix the clientrawhour.txt output in a upcoming update!

Still got these "0.00 - } {math- 0.00" errors

Would also be nice if we could have the Solar Last 24 Hours graph & Solar Last Hour graphs work for version 6.05 of WDL

[admin]

where can I inspect your defective clientraw file? which url?

[birdfeedr]

Same problem here that EmjayNet has. See this topic for info. viewtopic.php?f=8&t=8094
Clientraw files are uploaded to same directory as http://www.elbedo.com/weather/wx.htm

Maybe with EmjayNet's data plus mine, you'll see the problem. If you need to, later on I can open up my meteohub for remote access.

Thank you very much for taking a look at this.

[admin]

Bug will be fixed with next update.