Hoi eerst wel, maar toen had ik nog niet betaal gegevens ingevoerd. Hij geeft nu apparaat fout
New test version 1.8.0:
- OneCall API 4.0 added.
Currently untested, just added the 4.0 URL and device settings to OneCall current weather device.
@Bramweer FYI and test. I hope it’s working. Don’t have a 4.0 key yet.
Yes het is oké. I have 4 select en have it change to 3. Thanks for respons. When you do nothing it gone to v4
So is it working for you with “4.0’” selected and you get weather data?
No v4 is not working
Hello yesterday I install open weather app with Current weather (location).
I have choose 5 minutes intervals.
I create a simple flow to test the ultraviolet index has change to send a message to me but for testing purposes I receive the notification every hour and not every 5 minutes or any other time interval.
how can I change it to receive it more quickly than 1 hour ? with the WHEN Ultraviolet index has change? (Of course the values changes more quickly)
The test was:
WHEN Ultraviolet index has changed AND (logic) Ultraviolet index is greater than 2.5 send notification. (The notification was every hour)
If I start with:
WHEN every 15 minutes AND (logic) Ultraviolet index is greater that 2.5 THEN send notification, the flow stops with error at the logic card!
Just downloaded this on my Homey Pro, and i managed to obtain my API key but when selecting a city, it keeps on say cant find the city. Not sure if im doing it right?
OWM is using local weather providers for getting the data. If the weather data provider only offers hourly forecast data, you will only get hourly triggers.
If you’d just like to use Homey’s location, the manuals in the first posts say:
OWM only returns up to 5 cities when selecting with a given name. Try to use common naming, perhaps english or if the name is part of other city names, it could be that others are shown first.
Tty to ose Homey location (no city defined). Or set coordinates manually in device settings.
Thanks Peter
Update about OWM OneCall 4.0 version:
OWM intoduced OneCall 4.0 as new API version.
Changes are:
- Same price/limit (up to 1000 calls free/day)
- New API endpoint with different JSON response.
- One API call can only read one set of data:
- current weather
- hourly forecast, up to 20 response entries/hours (based on pagination, you need a second call to read entries 21-40…
- daily forecast, up to 10 entires/days (based on pagination, you need a second call to read entries 11-20…
Summary:
It’s not possible with OneCall 4.0 to read all data with just one API call.
If you already have several forecast devices for a location, you currently need only one call. With 4.0, you will need at leas three calls. But this would need a whole new implementation for 4.0 (new devices).
Can please anyone without active 3.0 subscription check if OneCall 3.0 is still available in subscriptions section? Or if it’s only visible for users with active subscription. You can find it in user section.
PS: I try to use JSON mapping to use 4.0 API for current OneCall devices, so current devices can still be used. At the end, one device update will use 3 API calls for 4.0. You have to use an update interval that fits into your free limit of 100 calls&day.
New test version 1.8.1:
- Added OneCall 4.0 API.
The OneCall devices now support OWM OneCall API 4.0.
You can select the API version while adding the “Location” device or in device settings.
There are some changes you have to know to calculate the amount of used API calls and find a matching polling interval.
The 4.0 API is not longe a “one call” API. OWN changed it. Every type of data must be read now with a seperate call.
- If OneCall 4.0 is selected, the Location device is reading the current weather data (1 API call)
- If you have assigned daily forecast devices, another call is done (1 call for the whole forecast data, so 1 call for all daily forecast devices).
- If you have assigned hourly forecast devices, another call is done (1 call for the whole forecast data, so 1 call for all hourly forecast devices).
- If you have alert devices assigned and alerts are present in current weather data, 1 call for every alert is done.
There are also changes in provided data. Daily forecast devices are not providing all data compared to 3.0. Description and weather type is missing. The capabilities will be empty in your devices.
In summary, you should stay at API 3.0 if you have already a subscription.
If you have to use 4.0 (if 3.0 is not possible to select for new users), you have to check the amount of API calls that are needed to find a matching polling interval.
@Bramweer FYI and test
I can still subscribe to API 3.0…
And on other account I’m subscribed
Since I setup the account that the time you created this integration, I’m still using 3.0 but how to see/check the calls per day ? Would be nice to have this information also included 
update found it at the bottom of the page - Members
| June 21, 2026 | 501 | 0 | 0.0 |
|---|---|---|---|
| June 20, 2026 | 472 | 0 | 0.0 |
| June 19, 2026 | 468 | 0 | 0.0 |
| June 18, 2026 | 474 | 0 | 0.0 |
| June 17, 2026 | 516 | 0 | 0.0 |
| June 16, 2026 | 477 | 0 | 0.0 |
| June 15, 2026 | 556 | 0 | 0.0 |
| June 14, 2026 | 567 | 0 | 0.0 |
This is for 7 devices I have… different update periods etc.
Hm, can’t see the real reason of the issue. Seems to be a kind of race condition - the parent device (location device) was not found. Perhaps the app was restarted after that and all was initialized right.
Thanks for looking into it. I’ve tried rebooting the app several times. My best guess would be an interval update, but not sure. Anyway, it works 
Hi … keep getting this a couple of times per hour i think.
Solves itself after a couple of minutes but it means errors in the flows using weather data ( like checking windforce for sunscreen several times a minute )
Could be a kind of rate limit.
Weather data is not refreshed in this period for most providers. So Checking every mimute or every xx minutes would be ok. It’s not really made for getting realtime windgusts data. Windforce woul dbe ok, but it’s just a forecast over a longer period, not for “now”.
