Openweathermap 3.0 binding: only 24 hourly forecasts available any more

Add-ons Bindings
1

Dear all!

I converted to the openweathermap 3.0 binding.

The free api provides 48 hourly forecasts, and indeed a request via the webpage using:
https://api.openweathermap.org/data/3.0/onecall?lat=0&lon=0&appid={myAPIkey} contains 48 hourly forecast fields, ranging from 0 to 47:

grafik
grafik157×709 3.43 KB

This used to work with the old 2.5 version of the binding: I defined 48 items to store the different forcast values.

Bridge openweathermap:weather-api:api "OpenWeatherMap Account" [apikey="xxx", apiVersion="3.0", refreshInterval=10, language="de"] {
   Thing onecall local "Local Weather and Forecast"         [location="0,0", forecastMinutes=0, forecastHours=48, forecastDays=3]
}

However, the openhab binding 3.0 only receives 24 hourly forecasts, the items form 24 to 47 remain NULL.

grafik
grafik748×387 21.9 KB

I would like to use items like:

{ channel="openweathermap:onecall:api:local:forecastHours25#cloudiness" }

Looking at the thing in mainUI, the list of available channels stops at 24, channels for hours 25-47 are no longer available as they used to be:

grafik
grafik745×548 24.5 KB

Thus a question: is this an intended behaviour or am I doing something wrong?

regards,
Sulla

2

Did you configure the hours in your one-call-api Thing correctly ?

You need to set the yours to 48 in the Thing config.

3

well, I have in the Thing-file:

Bridge openweathermap:weather-api:api "OpenWeatherMap Account" [apikey="xxx", apiVersion="3.0", refreshInterval=10, language="de"]
{
   Thing onecall local "name" [location="0,0", forecastMinutes=0, forecastHours=48, forecastDays=3]
}

should be correct, shouldn’t it?

4

I don’t use file based configs, but at first sight, it looks ok.

5

I might be mistaken but I think I recall that together with the binding there was also a switch in ow API (“onecall” is 3.0).
So it might be because ow is intentionally only giving 24 values.
Even might or might not also depend on your apikey (which identifies you as an old or a newer user).

6

I also tried with a newly created api key, no difference…

7

I’m struggling with the same problem.
If I let the things be generated automatically via the UI, the channels from ‘forecastHours25’ to ‘forecastHours47’ are missing, no matter what I specify in the configuration.
Does anyone use a thingfile and/or have 48 hour forecast running?