meteohub.de

It appears that meteohub is putting the Vantage Pro 2 "forecast" in the current conditions field. WDL shows the forecast where current conditions should appear and shows 'undefined' where the forecast should appear.

Would like to be able to use current conditions icons in WDL. Possibly an easy fix?

Thanks!

Andy
http://mapaverdesanmiguel.org/

Sorry, but where in the data that a vantage returns in the LOOP packets do you find a "current conditions" field. I cannot find any.

There really isn't a "current condition" listed by the VP2.

There is a long range (24-48 hr) text forcast that must be retrieved by the forecast rule number in the LOOP packets and then there is the 12 hr or less forecast shown by the icons on the console. That short range forecast may be what you think of as current conditions.

Perhaps the 24-48 hr forecast could be alternated with the short range forecast using the text for it that Davis lists in their Serial Protocol Docs? That text would have to be embedded by Boris into the software.

LOOP packets know "Forecast Icons" (pos 89) and "Forecast Rule Number" (pos 90).

Meteohub reports value of pos 90 as "actual_thb0_fc_rule" and corresponding English text as "actual_thb0_tc_text". "actual_thb0_fc" reports forecast as values as defined by Meteohub for all stations and "actual_thb0_fc_wdlive" reports a mapping to WD-Live compatible values from that".

I will change "actual_thb0_fc_wdlive" to directly report pos 89 when using a vantage.

I will change "actual_thb0_fc_wdlive" to directly report pos 89 when using a vantage.

Then what sort of forecast icon values would be reported by "actual_thb0_fc_wdlive" after the change? Would it be a decimal number such as 18 or the corresponding text forecast for 18 of "Mostly Cloudy, Snow within 12 hours"? Thanks.

Please check in the Vantage specs, loop packet position 89. Meteohub just reports what they deliver.

http://www.davisnet.com/support/weather ... s_v230.pdf

I was reading those Vantage specs for loop packet position 89 and trying to compare those outputs with what WDL requires for "current" conditions. As I understand it, WDL expects the "current" condition input to be composed of text. It even parses that text to determine which icon will be displayed based on keywords within. So if the output from position 89 are numbers, will WDL be able to handle those inputs?

I asked Julian to give me some more insight on that.