Meteoblue errors, missing things and prayin for a meteoangel :)

I wonder how can I be the first who noticed and write about this…
glad to help and be the first in something ahah :slight_smile:
meteoblue gives windspeed data in meter per second but oh assumes it is in kmh if I use %unit%. If I use m/s it makes a conversion on the wrong assumption so it always show wrong data.

The wiki miss some available data in the example items file:
mean and felt temperature and other useful data.
I managed to obtain the mean temperature by guessing (just follow the mean humidity) but can’t do more because I have no experience on this kind of things.

proof os what I said is here: the raw data available is this:

{
“metadata”:
{
“name”: “Rome”,
“latitude”: xxx
“longitude”: xxx
“height”: 20,
“timezone_abbrevation”: “CET”,
“utc_timeoffset”: 1.00,
“modelrun_utc”: “2020-01-31T12:00+01:00”,
“modelrun_updatetime_utc”: “2020-01-31T19:18+01:00”
},
“units”:
{
“time”: “ISO8601”,
“predictability”: “percent”,
“precipitation_probability”: “percent”,
“pressure”: “hPa”,
“relativehumidity”: “percent”,
“co”: “ug/m3”,
“temperature”: “C”,
“winddirection”: “degree”,
“precipitation”: “mm”,
“windspeed”: “ms-1”
},
“data_day”:
{
“time”: [“2020-02-01”, “2020-02-02”, “2020-02-03”, “2020-02-04”, “2020-02-05”, “2020-02-06”, “2020-02-07”],
“pictocode”: [4, 4, 2, 12, 2, 1, 1],
“uvindex”: [1, 1, 2, 2, 2, 2, 2],
“temperature_max”: [14.95, 15.21, 17.71, 15.65, 13.37, 12.07, 12.45],
“temperature_min”: [10.46, 10.38, 9.03, 9.47, 2.68, 1.06, -0.74],
“temperature_mean”: [12.26, 12.17, 12.61, 12.33, 7.49, 5.30, 5.24],
“felttemperature_max”: [14.17, 14.45, 17.58, 12.91, 7.92, 6.30, 8.72],
“felttemperature_min”: [9.71, 9.66, 7.71, 4.65, -2.31, -4.15, -4.89],
“winddirection”: [225, 225, 270, 180, 0, 45, 45],
“precipitation_probability”: [16, 15, 0, 37, 16, 0, 0],
“rainspot”: [“0000000000000000000000000000000000000900000000000”, “0000000000000000000000000000000000000000000000000”, “0000000000000000000000000000000000000000000000000”, “0000001000009100000910001111000912299009220901222”, “0000000000000000000000000000000000000000000001112”, “0000000000000000000000000000000000000000000000000”, “0000000000000000000000000000000000000000000000000”],
“predictability_class”: [4, 4, 4, 3, 3, 4, 4],
“predictability”: [73, 79, 77, 40, 54, 66, 72],
“precipitation”: [0.00, 0.00, 0.00, 0.70, 0.00, 0.00, 0.00],
“snowfraction”: [0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00],
“sealevelpressure_max”: [1022, 1022, 1021, 1019, 1021, 1036, 1037],
“sealevelpressure_min”: [1019, 1019, 1018, 1004, 1006, 1022, 1034],
“sealevelpressure_mean”: [1020, 1021, 1019, 1011, 1013, 1030, 1035],
“windspeed_max”: [1.69, 1.88, 1.20, 4.77, 5.10, 4.90, 2.28],
“windspeed_mean”: [1.02, 1.11, 0.91, 2.90, 3.57, 3.34, 1.59],
“windspeed_min”: [0.73, 0.71, 0.72, 0.75, 2.66, 1.67, 0.98],
“relativehumidity_max”: [95, 96, 96, 98, 61, 53, 69],
“relativehumidity_min”: [78, 76, 66, 56, 38, 34, 39],
“relativehumidity_mean”: [88, 88, 85, 86, 50, 45, 55],
“convective_precipitation”: [0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00],
“precipitation_hours”: [0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00],
“humiditygreater90_hours”: [11.00, 12.00, 11.00, 11.00, 0.00, 0.00, 0.00]
}
}

by the way…I also have the missing icons problem and example only shows me today’s data…if some angel wish to help me I would really be an happy man :slight_smile:

UPDATE1:
I found all the missing things in paper ui, but I also found 2 bridges, if I edit from the one of the bridges it returns error conflict 409. I just folowed wiki, I think it needs to be updated with more informations.

The docs show 2 examples for temperature. And all of the temperature channels work the same.

Temperature was the easiest example but there a a lot more missing.
Why have an incomplete wiki, callin it a “full example” is misleading.
Anyway people will find this thread and solve this going in the paper ui (thing-channels).
Also detailed instructions about icons would be really good.

More important imho is that the unit for wind is wrong, this one I can’t fix it but I will try if someone points me in the right direction.

Please open an issue on GitHub so it can be fixed then. Not all developers use this users forum.

First off, a “full example” does not include every possible configuration. To try to do so would be pointless.
Second, anything you think is “missing” is covered adequately by what is already there. (Unless you have a unique sighting I’ve overlooked)

Based on your original post, you’re wanting units of m/s, right? But the service is already returning that by default, so there’s no need to use a conversion term.

So you can complete it instead of complaining here :wink:

Something is wrong with my words. Please forgive my english. My point wasnt to complain.
wind in m/s is not possible to have the correct value and correct unit both showed.
you think you have mph or kmh or m/s because you see that unit but the conversion is made on wrong assumptions so the value is wrong, (lets say meteoblue give value of 2 in m/s, oh assume 2kmhand shows 2 kmh instead of 2 m/s. if you tell oh to use m/s he will show you 0.55 m/s, anything you do you will never have correct values:units). anyone who has an api key can see that.
I tried to study how a binding works but honestly I don’t have the skills to do it.

incomplete full example I would be really happy to contribute but I have no github account (I have an offline life, no social, I only have email and some forums to give back something for what I lurk) so I thought the best I Could do was to make it reachable posting here so people would know that full is not all the infos they can get.

So my intentions was and is to informate people about wrong windspeed unit and that in the wiki full does not mean all. No complain really, I invested precioust time posting here and I did that for other members not for myself or to complain, I already knew what I said there is no reason to complain.

Hope I explained right :slight_smile:

I don’t believe this is true.

You haven’t shown your item config, but this should show the value correctly:

Number:Speed  todayWindSpL   "Low Wind Speed [%.2f]"

namraccr I did that, just try to use %unit% and you will see that oh think the default is kmh even if meteoblue says clearly that data is in m/s, at least in europe, rome.
Why don’t you compare by yourself instead of assuming I am wrong?

anyway:
item:

Number:Speed todayWindSpL “Low Wind Speed [%.1f %unit%]” (weatherDay0) {channel=“meteoblue:weather:metBridge:A51:forecastToday#minWindSpeed”}
plese note A51 is mapped to my home in rome now.

prevision for tomorrow is 0.8 m/s oh shows 0.8 kmh
if I enforce kmh in the item oh shows 0.8
if I enforce m/s shows 0.8/3.6

You are wrong. Your claim was:

wind in m/s is not possible to have the correct value and correct unit both showed.

Which is not so.

However it is true that the binding assumes km/h as the default unit when doing conversions, because that is the default SI Unit of Measure for speed.

I have created a fix for this that I might get around to proposing a PR for.

3rd row of my first opening post:
“meteoblue gives windspeed data in meter per second but oh assumes it is in kmh”
your ticket shows more than anything wwho’s wrong.
I got the patience of repeating the same thing in a stranger language because of you, in the end you open a ticket saying exactly my words and I am the wrong one.
Lets stop here, my wish to give back what I had from the forum is completely gone for now.