[SOLVED] METEOBLUE: Can't retrieve weather data

Add-ons Bindings
1

Hi,
I sucessfully installed the Weather binding (weather1 - 1.13.0.)

My weather.cfg file is:
apikey.Meteoblue=xxxxxxxx
location.home.name=Berlin
location.home.latitude=52.4306
location.home.longitude=13.2499
location.home.provider=Meteoblue
location.home.language=de
location.home.updateInterval=14
location.home.units=ison

The api is working when using the direct test link and/or the associated meteogram link.

Problem shown in the log:

2019-01-09 21:11:27.409 [INFO ] [eather.internal.common.WeatherConfig] - ProviderConfig[providerName=METEOBLUE,apiKey=xxxxxxxxx]

2019-01-09 21:11:27.413 [INFO ] [eather.internal.common.WeatherConfig] - LocationConfig[providerName=METEOBLUE,language=de,updateInterval=14,latitude=52.4306,longitude=13.2499,woeid=,locationId=home,name=Berlin]

2019-01-09 21:11:30.465 [INFO ] [ternal.scheduler.WeatherJobScheduler] - Starting and scheduling weatherJob-home with interval of 14 minutes

2019-01-09 21:11:33.770 [WARN ] [ther.internal.parser.CommonIdHandler] - CommonId not found: CommonIdHandler[provider=METEOBLUE,id=,icon=]

2019-01-09 21:11:33.776 [ERROR] [nal.provider.AbstractWeatherProvider] - METEOBLUE[home]: Can’t retreive weather data: MB_REQUEST::DISPATCH: This datafeed is not authorized for your api key

Any idea what the problem could be?

2

Meteoblue does not provide “CommonId”. You can remove the item.

And you want to read data e g. “daily forecast” that is not provided with your api key. E.g. you have a “free apikey” and not a “paid apikey”.

It also could be, that your apikey is wrong in general.

3

Thanks Celeano1,

    • There is no item CommonId in my items. How/where to remove this?
  2. Where from do you deduct that I want to read data like the “daily forecast”
    • And as I wrote, my API key is correct as tested with a direct http-link

Rgds,

4

Show the link. @Celaeno1 is almost certainly correct. Unless you have a paid subscription, this will not work.

5

here’s the link:

http://my.meteoblue.com/packages/basic-day?name=Berlin&lat=52.5244&lon=13.4105&asl=74&tz=Europe%2FBerlin&apikey=xxxxxxxxxxxxxxxxx&temperature=C&windspeed=ms-1&winddirection=degree&precipitationamount=mm&timeformat=iso8601&format=json

apikey masked of course

and that is the result of that link (and now I kindly ask you to take my word for it that this comes from the link…):

{
“metadata”:
{
“name”: “Berlin”,
“latitude”: 52.52,
“longitude”: 13.41,
“height”: 74,
“timezone_abbrevation”: “CET”,
“utc_timeoffset”: 1.00,
“modelrun_utc”: “2019-01-10T00:00+01:00”,
“modelrun_updatetime_utc”: “2019-01-10T06:54+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”: [“2019-01-10”, “2019-01-11”, “2019-01-12”, “2019-01-13”, “2019-01-14”, “2019-01-15”, “2019-01-16”],
“pictocode”: [3, 11, 12, 12, 16, 12, 12],
“uvindex”: [0, 0, 0, 0, 0, null, null],
“temperature_max”: [2.17, 3.82, 5.29, 7.28, 6.24, 6.14, 7.07],
“temperature_min”: [-0.88, -1.03, 1.94, 4.97, 2.03, 1.29, 5.62],
“temperature_mean”: [0.95, 1.38, 3.75, 6.08, 4.19, 3.95, 6.12],
“felttemperature_max”: [-2.84, -1.51, -1.50, 1.83, -1.33, -1.02, 0.69],
“felttemperature_min”: [-4.74, -5.37, -3.33, -1.81, -4.72, -4.56, -2.68],
“winddirection”: [0, 270, 270, 270, 315, 270, 270],
“precipitation_probability”: [9, 72, 90, 98, 75, 74, 68],
“rainspot”: [“9009911900001190001110000911000009100009910000901”, “2222222222222222222222222222222222222222222222222”, “2222222222222222222222222222222222222222222222222”, “3333333333333333333333333333233333323333332223333”, “2222222222222222222222222222222222222222222222222”, “2223333223333333333333333333333333333333333333333”, “2222222222222222222222222222222222222222222222222”],
“predictability_class”: [4, 4, 3, 3, 2, 2, 2],
“predictability”: [77, 63, 57, 42, 26, 26, 20],
“precipitation”: [0.00, 2.01, 3.03, 7.52, 3.84, 6.76, 3.73],
“snowfraction”: [0.00, 0.75, 0.00, 0.00, 0.00, 0.00, 0.00],
“sealevelpressure_max”: [1023, 1023, 1018, 1003, 1016, 1017, 1010],
“sealevelpressure_min”: [1017, 1015, 1003, 989, 989, 1008, 997],
“sealevelpressure_mean”: [1021, 1018, 1012, 998, 1005, 1013, 1005],
“windspeed_max”: [4.72, 5.52, 7.99, 9.63, 9.41, 8.80, 9.58],
“windspeed_mean”: [3.37, 4.42, 6.05, 7.59, 7.32, 6.90, 7.99],
“windspeed_min”: [1.49, 1.77, 4.36, 6.31, 6.00, 4.91, 7.30],
“relativehumidity_max”: [92, 99, 92, 95, 86, 99, 90],
“relativehumidity_min”: [72, 86, 84, 84, 52, 80, 78],
“relativehumidity_mean”: [84, 94, 89, 90, 74, 93, 86],
“convective_precipitation”: [0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00],
“precipitation_hours”: [0.00, 3.00, 4.00, 10.00, 4.00, 8.00, 5.00],
“humiditygreater90_hours”: [8.00, 18.00, 5.00, 11.00, 0.00, 20.00, 3.00]
}
}

6

For comparison, this is the URL used by the OH1 binding:
http://my.meteoblue.com/dataApi/dispatch.pl?apikey=[API_KEY]

So, as it was stated. You are using the free API. The binding uses the commercial (paid) API, and will not work with your api key.

There is a new ESH binding that will work with the free API key that you have. You should use that.

1 Like
7

Thank you for the hint to the new binding - it works.
Issue solved.