Yes and no. Be aware that a free API is restricted to 1000 calls per day (see https://openweathermap.org/price). If you want to use multiple things or combine old and new ones you should choose your refresh interval respectively.
But it now will be much better by using the One Call API because before it’s implementation the binding had to request current weather, forecast and UV Index separately.
you are absolutely right.
But based on your current implementation of a minimum polling of 10 min, we get 144 calls per API, per day. So there’s plenty enough room for additional locations and/or APIs.
BTW: As you are the maintainer of the “offical” OWM binding, I expect you being the developer for implementing the one call API mentioned by Michael ;-). Please let me know, if you need beta testers.
I am the initial contributor of the OWM binding. AFAIK @Wolfgang1966 and @MPH1980 are working on the implementation of the One Call API. You can find a test version inside the related GitHub issue. Kudos to both of them .
Thanks for your efforts! Working fine so far with OH3.
What would be the preffered way to getting the current weather and daily forecasts now as they’re available in the “weather-and-forecast” thing as well as the “oneapi” thing of the binding? (besides location informations and ConditionID as far as I see)
Is it better to use the oneapi here, as it gets called anyway or are there any benefits using the “weather-and-forecast” part for it?
One thing that I noticed when I’m using the current weather informations from the onecall part of the binding is, that it returns the same values as the hour01 forecast (uncluding the timestamp) - is this by design or a bug which I should open an issue for?
I read many threads about this great binding, but still not found any solution for my problem.
I need to know the last 36hours of rain precipitation.
I used to use the direct openheathermap api and parse the result myself, but i see that the binding now can call the one-call-history.
My problem is that it seems that the binding can only call the last day history (and 5 days before), not the history for the current day.
I tried to put “historyDay=0” in the things but i got the response : “historyDay value of 0 is not supported”
TLTR : How can i get the rain volume history of the current day ?
Any clue or tips ?
(Note that the API from openweathermap allow this call for the current day.)
It seems that there is not a lot of people concerned by the bug/feature I talked earlier
Anyway, I have another bug, more annoying : it seems that the onecall-history is refresh only once a day (02h05 - 02h10 in my local time). But when the refresh does not work (I guess problem with API ?) the plugin seems to not give a retry. And so I have no new data for this day.
To “force” a refresh of a history call, I have to restart the bundle in the console.
Is there another way to do so ?
Maybe, I missunderstand something, but why don’t you just additionally use the “Current weather data” API.
It gives you the rain of today’s last 3h.
This should be sufficient, to calculate the total rain for today.
I dont see how to use the “Current weather” that you mentionned for my use case.
Perhaps I am not clear with my explanations : I want to know exactly the rain volume for the CURRENT day between 00h00 and 13h00 in my example. (to decide wether mower starts or not, dry ground or not)
The native API offers this, as-is (anytime for current day).
The binding offers this for PREVIOUS days only, not current day.
Until this binding limitation is resolved, I have to use the native API call in a specific http request (onecall/timemachine) and parse myself the result… in other words all the job of the binding
That works … but I would prefer to use the binding of course.
could you share some more details about your workaround?
I´m facing the same issue, would like to base the decision whether my automatic plant watering should be triggered on the amount of rain in the past hours.
Thanks in advance!
Sorry i have no access to my dev environment currently.
But I can tell you that I do a URL/HTTP request directly to openweathermap API, and I parse the result in a rule. Be carefull : when there is no rain data, the field disappears in the response (for the specified hour) > the field only appears when there is actualy rain data.
I spent so much time to understand this behavior …