If this is OH 1, you need to make sure that you have a `weather_<condition_id>.png" file for each possible value that wTemp_Icon can become. For example, if the wTemp_Icon can be a number between 1 and 30 you would need a weather_1.png, weather_2.png, and so on.
These icons need to be in your webapps/images folder.
The sitemap will choose the correct icon based on the state of vTemp_Icon.
For one, if the value you need to get is text, not a number you need to define wTemp_Icon as a String, not a Number.
If this full JSON formatted line of text is what your Item is being set to you will need to add a transform or a rule to extract the icon field, though I thought that is what the weather binding is supposed to do for you. At least that is what it does for Yahoo and Wunderground.
Yeah, that´s what happening when you just copy Items from a guide …
I´m sitting here and starting to setup everything in OpenHAB that i did with the Telekom Qivicon system before.
Set it up as String and now it shows the right informationen.
See this example for how to download and rename the icons for proper display on your sitemap. You should be able to use the same overall approach for forecastio. the key is in the naming of the icon files.
In the interest of the community I wrote DarkSky (forecast.io) asking about them potentially developing directly for OH as as addon. Their Android and iOS apps are polished with several options and $3 annual subscription is something I’m sure several folks would be willing to pay if that meant getting reliable information. Looking forward to hearing back from them.