first of all thanks to every contributor into that great openhab solution, I really appreciate.
Second, after years, I found again little time adjust and optimize of my own openhab installation and the used bindings, one of them is OpenWeatherMap. There was a subscription change towards OneCall API 3.0 quite a while ago, where I just adopted the need changes to before and left it run as years before.
These days I wanted to check and adjust the usage of OWM, e.g. testing a higher call frequency but not to exceed the 1000 free calls limit. I also realized, binding has the changes to access OneCall API 3.0, but looks like it doesn’t provide some data as channels:
E.g. I just find 24 forecast hours instead of 48h, current day & 5 days forecast instead of 8 days forecast in summary, I cannot see channels for government weather alerts, as also none for the provided (textual) weather overview.
I can’t exactly say what’s the problem with your SetUp, as I do not running the binding at the moment. But when testing the account with a “http-request” I get all the data(without minutely) with my api-call
Yes, I had an intensive look into that documentation, as I compared the channels provided by my openHAB with that binding to that documentation.
Looks like OWM does provide more data for free, configured properly, compared to old OWM 2.5 API.
I barely see a need for minute based forecasts, except somebody is sitting on control boards while a formula 1 race. And how does that work if they recommend to gather data every 10min.?
Maybe cloudiness might helpful in short cycles on forecast based PV setups, but I would think 10min might be good enough overall.
Sure, I could do that, too. But there’s that very nice binding, what might just be adopted a little to the added available data with OneCall API 3.0 …
And if I would have a wish, some control to gather OneCall data just along full hours or full 10min cycles would it be …
Sorry with the HTTP-Request I only tested what JSON-String (values) I got back.
If you want get back actual data you have to adjust your refresh-interval (max.: 3600/1000=3,6). In my thinking this means a “refreshInterval” (Bridge) greater than 3,6 Minutes. So every 10 Minutes-Refresh are 360 Calls a day (danger:my mathematics-knowings are not the best and school is nearly sixty years ago )
Of course you have to adjust your Bridge and Things a bit and at the very end naturally your items. (Maybe it’s possible to generate Items via MainUI or VSC - textual - ?!)
Sure, but that’s fairly ok. OneCall API 3.0 subscription does offer 1000 calls/day without additional costs. And they allow to define 1000 calls per day as limit for your OWM account, that’s kind of fair from my point of view. Within that 1000 calls per day, it would be possible to grep more data out of that subscription compared to what binding actually does provide.
Before I started to check and change possibilities of OWM binding some days ago, my OH did still run on OWM-2.5 setting for years, so 60min cycle, making 48 calls per day … … now it does just little more than 300 per day.
PS.: I disabled the onecall history thing today, as I don’t need historic OWM data, assuming this does reduce number of calls again …
)
… now it does just little more than 300 per day.