WDL bugs, I found so far

[wfpost]

Trend arrows with WDL are always the same: horizontal :(
How do I get the trend arrows with WDL instruments to work?
Where does WDL get the trend info from? clientraw-files?

Cheers,

[skyewright]

Where does WDL get the trend info from? clientraw-files?

Have you come across this link to the documentation of the clientraw file formats?

http://www.weather-watch.com/smf/index. ... #msg199677

There are several 'trend' fields mentioned e.g.

Code: Select all

50     Baro Trend                      hPa

[admin]

Meteohub does not provide trend info yet. As not all weather station provide it, Meteohub will have to compute this itself. yes, it is in the clientraw files.

Any idea how this is computed?
how long to look back?
what are the thresholds for flat, raising, falling?

[admin]

In regard to the records pages of WDL.

Meteohub is not computing all-time records up to now. biggest step back is records for the current year.

historical wind and gust maximum is not recorded with a direction by Meteohub up to now. So no chance for me to deliver this. I thought it would be less important, as it would be quite complicated to implement this in general.

Solar data should be working. did you try selecting the solar sensor on the "WD-Live" page and pressing "save"?
If you have strings like "???_radiation" in your /home/Meteohub/clientrawextra.conf file, that this is an indication that the solar sensor has not been selected correctly.

P.S: Found a bug that prevents solar data to be displayed in graphs and records. will be fixed with 2.6e.

[sevenless]

Regarding trendlines, here's what the VantagePro2 manual says about barometric pressure:

Barometric Trend Arrow shows change over the last three hours:

* "Rising rapidly" is an increase of 2.0 hPa or more.
* "Rising slowly" is an increase of 0.7 hPa or more.
* "Steady" is a change of less than 0.7 hPa.
* "Falling slowly" is a decrease of 0.7 hPa or more.
* "Falling rapidly" is a decrease of 2.0 hPa or more.

Their system does not provide trend lines for any other measurements, but for barometer this seems to be a reasonable period of time to track change and provide a trend.

[wfpost]

Big thanks for all done so far, WD-Live looks more complete right now.

Do you know where to look for that error?
The Temp bulb has two markers (red and blue) for Max. Min. temp. (please check screenshot)

But these markers are not showing correct values. To high.



What´s somewhat strange though, the min.max. field (on left of temp bulb) are displaying the correct Min-Max. figures :blink:
What could causing that?

[wfpost]

There´s something wrong with the Forecast icons of VP2.
VP2 has five icons for forecast >>

At the moment my VP2 Console shows the one named Partly Cloudy.


But the icons uploaded with meteohub´s forecast0 and the WDL icon both show this one



current sensor
actual_thb0_fc 1
actual_thb0_fc_wdlive 2

Is it because there are 7 Forecast icons with meteohub and VP2 has only five?

[wfpost]

Regarding trendlines, here's what the VantagePro2 manual says about barometric pressure:

Barometric Trend Arrow shows change over the last three hours:

* "Rising rapidly" is an increase of 2.0 hPa or more.
* "Rising slowly" is an increase of 0.7 hPa or more.
* "Steady" is a change of less than 0.7 hPa.
* "Falling slowly" is a decrease of 0.7 hPa or more.
* "Falling rapidly" is a decrease of 2.0 hPa or more.

Their system does not provide trend lines for any other measurements, but for barometer this seems to be a reasonable period of time to track change and provide a trend.

That´s from VP2´s manual:

[admin]

There is a very useful clientraw parser at http://www.tnetweather.com/wd-parser.php

I will try to spot the error, but if you like you can also inspect your clientraw files with this.

P.S.: The error seems not to occur on my system (demo section of meteohub.de looks fine). Parsing your clientraw-files might shed some light on this.

[admin]

In regard to forecast icons Meteohub has defined:
#define FC_LIGHT_SNOWY 8
#define FC_LIGHT_RAINY 7
#define FC_CLEAR_NIGHT 6
#define FC_HALF_CLOUDY_NIGHT 5
#define FC_SNOWY 4
#define FC_SUNNY 3
#define FC_HALF_CLOUDY 2
#define FC_CLOUDY 1
#define FC_RAINY 0

Forecast icons of weather stations are mapped to these. WD-Live again has its own mapping, so WD-Live forecast has a different number again.

Mapping from Vantage to Meteohub is a bit complicated and we are loosing info here, because vantage provides a bit pro icon and can combine icons so that a lot of different forecasts can occur (see vantage loop doc, byte 89):
buf[89] & 0x01 ? FC_RAINY :
buf[89] & 0x02 ? FC_CLOUDY :
buf[89] & 0x04 ? FC_HALF_CLOUDY :
buf[89] & 0x08 ? FC_SUNNY :
buf[89] & 0x10 ? FC_SNOWY : -1;


Mapping from Meteohub to WD-Live:
FC_LIGHT_SNOWY: return 27; // snow showers
FC_LIGHT_RAINY: return 22; // showers
FC_CLEAR_NIGHT: return 1; // clear night
FC_HALF_CLOUDY_NIGHT: return 4; // cloudy night
FC_SNOWY: return 25; // snowing
FC_SUNNY: return 0; // sunny
FC_HALF_CLOUDY: return 19; // partly cloudy
FC_CLOUDY: return 2; // cloudy
FC_RAINY: return 20; // rain

[wfpost]

There is a very useful clientraw parser at http://www.tnetweather.com/wd-parser.php

I will try to spot the error, but if you like you can also inspect your clientraw files with this.

P.S.: The error seems not to occur on my system (demo section of meteohub.de looks fine). Parsing your clientraw-files might shed some light on this.

This is a WDL bug. The (very helpful) parser did not come up with any errors.
Yesterday I downloaded the most recent WDL version 6.01, that comes now with a graphical config tool (very nice), but with the new applet version I´m getting the error described below.
When switching back to WDL5.04 my output looks fine as with your demo.

[wfpost]

There is a very useful clientraw parser at http://www.tnetweather.com/wd-parser.php

I will try to spot the error, but if you like you can also inspect your clientraw files with this.

P.S.: The error seems not to occur on my system (demo section of meteohub.de looks fine). Parsing your clientraw-files might shed some light on this.

This is a WDL bug. The (very helpful) parser did not come up with any errors.
Yesterday I downloaded the most recent WDL version 6.01, that comes now with a graphical config tool (very nice), but with the new applet version I´m getting the error described below.
When switching back to WDL5.04 my output looks fine as with your demo.

WDL has fixed this issue with a new WDL 6.01, available from their website.