# \[App\]\[Pro\] OpenWeather

**URL:** <https://community.homey.app/t/app-pro-openweather/61482>\
**Category:** Apps\
**Tags:** app, tools, weather, homey-pro\
**Created:** [March 8, 2022, 5:55pm UTC](https://community.homey.app/t/app-pro-openweather/61482 "2022-03-08T17:55:16Z")\
**Posts on this page:** 18\
**Page:** 25

<div class="post-metadata">

**Author:** ![Dennis\_H74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_h74/32/11177_2.png) [@Dennis\_H74](https://community.homey.app/u/Dennis_H74)\
**Post date:** [August 2, 2026, 1:13pm UTC](https://community.homey.app/t/app-pro-openweather/61482/487 "2026-08-02T13:13:10Z")

</div>

Hi ronnie

Wel sure … but it worked for years with no issue.

Also … i do not make my api calls that much ( its on 10 minutes actually ). My sunscreen FLOW checks the data every 10 secconds but inot only for windgusts but also for rain … sun position etc etc . That why the jnterval is higher in the FLOW that uses wind data

So it should not matter homey is checking a variable that refreshes every 10 minutes many more times …. It just means the fliw breaks every 10 secconds because that 10 MINUTE data is not being received.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 2, 2026, 1:17pm UTC](https://community.homey.app/t/app-pro-openweather/61482/488 "2026-08-02T13:17:00Z")

</div>

Yes, that’s ok this way. I thought you are calling the API that much.

If you get the error again, you can send me a diagnostics report. Perhaps I can see some details. But I think it’s just a http connection error, but let’s hope the log has some details.

---

<div class="post-metadata">

**Author:** ![Dennis\_H74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_h74/32/11177_2.png) [@Dennis\_H74](https://community.homey.app/u/Dennis_H74)\
**Post date:** [August 2, 2026, 1:19pm UTC](https://community.homey.app/t/app-pro-openweather/61482/489 "2026-08-02T13:19:05Z")

</div>

Thanks

Now the air quality broke 😬

b5163919-e488-4523-af1d-e0b7894f4613

 ![IMG_3571](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/c/9c1c87acbc69c187c53bb58d5366482de7d7cce5.jpeg)

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 2, 2026, 1:23pm UTC](https://community.homey.app/t/app-pro-openweather/61482/490 "2026-08-02T13:23:27Z")

</div>

It’s a network timeout.  
Are you using the device tokens in your flows? And these tokens are not available if the device is unavailable (with error message)?

---

<div class="post-metadata">

**Author:** ![Dennis\_H74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_h74/32/11177_2.png) [@Dennis\_H74](https://community.homey.app/u/Dennis_H74)\
**Post date:** [August 2, 2026, 1:27pm UTC](https://community.homey.app/t/app-pro-openweather/61482/491 "2026-08-02T13:27:25Z")

</div>

Wel i use a variable i think ( not at computer atm )

With an avarage of 3 windusts calcutaled from 3 different apps … because all give different outcomes 🤷😬

when the app is down no app card can be used and the avarage is not calculated either because it does not find the data of your app

A network timeout froM my side u mean ?

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 2, 2026, 2:21pm UTC](https://community.homey.app/t/app-pro-openweather/61482/492 "2026-08-02T14:21:50Z")

</div>

Ok, so if the device is unavailable, the flow cards are not available. Ihave no quick fix for that. Not to show a message for an unavailable device would mean a user can’t see that something is wrong. The data just would not update.

The app get’s a timeout. You don’t know where it happens. Could be that the server is too slow or something is blocked on way there.  
The app itself doesn’t use a timeout, so it’s a default timeout, I think around 60sec (just a guess).

I will check if I can add additional information to the error message…

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 2, 2026, 4:19pm UTC](https://community.homey.app/t/app-pro-openweather/61482/493 "2026-08-02T16:19:53Z")

</div>

I added a logging for the technical error message.  
The device still get unavailable on timeout error, but I want to know the error details.  
If you updated to test version and the error comes again, please send me another report. Thanks.

> **[OpenWeather | Homey](https://homey.app/en-us/app/nu.baretta.openweathermap/OpenWeather/test/)**
>
> Get current weather data and forecasts from openweathermap.org

---

<div class="post-metadata">

**Author:** ![Dennis\_H74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_h74/32/11177_2.png) [@Dennis\_H74](https://community.homey.app/u/Dennis_H74)\
**Post date:** [August 2, 2026, 4:35pm UTC](https://community.homey.app/t/app-pro-openweather/61482/494 "2026-08-02T16:35:32Z")

</div>

Thanks

installed and immediately an error for air quality

059ef2e7-fef0-4e13-80be-62b74a5b79ef

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 2, 2026, 5:16pm UTC](https://community.homey.app/t/app-pro-openweather/61482/495 "2026-08-02T17:16:37Z")

</div>

Sorry, tried to fix another small isue and broke the air quality device. New test version is online.

---

<div class="post-metadata">

**Author:** ![Dennis\_H74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_h74/32/11177_2.png) [@Dennis\_H74](https://community.homey.app/u/Dennis_H74)\
**Post date:** [August 2, 2026, 5:21pm UTC](https://community.homey.app/t/app-pro-openweather/61482/496 "2026-08-02T17:21:00Z")

</div>

🤪

Installed the new one.

Will let you know

---

<div class="post-metadata">

**Author:** ![Erik\_W](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erik_w/32/81557_2.png) [@Erik\_W](https://community.homey.app/u/Erik_W)\
**Post date:** [August 20, 2026, 2:39pm UTC](https://community.homey.app/t/app-pro-openweather/61482/497 "2026-08-20T14:39:25Z")

</div>

Hi,

I hope someone can help me. What I would like is that at 21:00 we look at how many mm of rain have fallen in the past 24 hours. So from 21:00 the day before until 21:00 now. I don’t know which device to choose from OpenWeather and how best to set this up.

Would someone like to help me get started what exactly to set?

Thanks in advance.  
Erik

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 20, 2026, 8:42pm UTC](https://community.homey.app/t/app-pro-openweather/61482/498 "2026-08-20T20:42:46Z")

</div>

You can use the daily summary:

 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/4/24df69f4c3dceeff6e261383ab692fdcdd1ed961.png)

But it’s only daily.

You can set an offset in days. 0=today. -1=yesterday.  
So you can check the amount of rain for today in the evening. But not for some hours across two days.

---

<div class="post-metadata">

**Author:** ![SuperVHS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/supervhs/32/172303_2.png) [@SuperVHS](https://community.homey.app/u/SuperVHS)\
**Post date:** [August 26, 2026, 10:05am UTC](https://community.homey.app/t/app-pro-openweather/61482/499 "2026-08-26T10:05:51Z")

</div>

When setting up Openweather 1.8.3 on Homey Pro (early 2019) as a new user, it is not possible to select OneCall 4.0. It is not there because the option is missing. This file might be the source of the problem: [homey.openweathermap/drivers/owmOnecallCurrent/pair/city\_geocode.html at master · RonnyWinkler/homey.openweathermap · GitHub](https://github.com/RonnyWinkler/homey.openweathermap/blob/master/drivers/owmOnecallCurrent/pair/city_geocode.html) . I can add the API-key using OneCall 3.0. When i want to adjust the settings to “OneCall 4.0” it gives me an error: “Invalid\_setting\_type”.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 26, 2026, 5:13pm UTC](https://community.homey.app/t/app-pro-openweather/61482/500 "2026-08-26T17:13:35Z")

</div>

Thanks for the hint. Yes, the 4.0 item was missing there. It’s added now with **test version 1.8.4.**

It would be nice if you could test and confirm that it’s ok now. Thanks.

> **[OpenWeather | Homey](https://homey.app/en-us/app/nu.baretta.openweathermap/OpenWeather/test/)**
>
> Get current weather data and forecasts from openweathermap.org

---

<div class="post-metadata">

**Author:** ![SuperVHS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/supervhs/32/172303_2.png) [@SuperVHS](https://community.homey.app/u/SuperVHS)\
**Post date:** [August 27, 2026, 8:29am UTC](https://community.homey.app/t/app-pro-openweather/61482/501 "2026-08-27T08:29:14Z")

</div>

I removed the openweather app, installed your 1.8.4 test version, and confirm that:

- I can select OneCall 4.0.
- Am able to succesfully use the API-key from openweather.
- The app receives weather data from openweather.

---

<div class="post-metadata">

**Author:** ![bigcspecv](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@bigcspecv](https://community.homey.app/u/bigcspecv)\
**Post date:** [September 2, 2026, 2:52am UTC](https://community.homey.app/t/app-pro-openweather/61482/502 "2026-09-02T02:52:50Z")

</div>

Small bug in the **Daily Summary** device: `forecast_time` shows a date one day earlier than the day it actually fetched.

I’m in America/Los\_Angeles (UTC-7). Offset 0 shows yesterday’s date, offset 1 shows today’s. The forecast data itself is correct, it’s only the displayed date that’s wrong.

Cause is in `drivers/owmOnecallDailySummary/device.js`, line 270 on master (v1.8.4):

```js
let date = new Date(data.date).toLocaleString('en-US', { ..., timeZone: tz, ... });

```

`data.date` from the `day_summary` endpoint is a bare date string like `"2026-09-01"`. JavaScript parses a date-only ISO string as midnight **UTC** , so rendering that instant back in a negative-offset zone lands on the previous evening:

```auto
$ node -e 'console.log(new Date("2026-09-01").toLocaleString("en-US",
    {timeZone:"America/Los_Angeles",day:"2-digit",month:"2-digit",year:"numeric"}))'
08/31/2026

```

`getOnecallDailySummaryURL()` in `lib/owm_api.js` is correct, it derives the target date from the Homey timezone, so the right day is being requested. Only the display is off.

At UTC+0 or east of it, midnight UTC renders as the same calendar day, which is probably why this hasn’t come up before.

The other drivers aren’t affected, since they format a real unix `dt` value rather than a date string.

Parsing as local time would fix it:

```js
let date = new Date(data.date + "T00:00:00").toLocaleString('en-US', { ... });

```

I would have opened a GitHub issue but Issues are disabled on the repo, so posting here instead.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [September 2, 2026, 6:28pm UTC](https://community.homey.app/t/app-pro-openweather/61482/503 "2026-09-02T18:28:53Z")

</div>

Hi @bigcspecv

thanks for the hint. This way - just for copy/paste fix - is good.  
A new test version is online. Can you check if it’s correct now? Thanks.

New test version 1.8.5:

- fixed OneCall daily summary timestamp.

> **[OpenWeather | Homey](https://homey.app/en-us/app/nu.baretta.openweathermap/OpenWeather/test/)**
>
> Get current weather data and forecasts from openweathermap.org

---

<div class="post-metadata">

**Author:** ![Tim\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tim_s/32/56366_2.png) [@Tim\_S](https://community.homey.app/u/Tim_S)\
**Post date:** [October 24, 2026, 9:11am UTC](https://community.homey.app/t/app-pro-openweather/61482/504 "2026-10-24T09:11:49Z")

</div>

Hi, has something changed ? using this app for 2 years or s now. Almost never lost connection, since yesterday I needed to restart the app 3 times to refresh the readings. “current” remains active while forecast for future hours / days is giving an error. After restart of the app it works again. I did not make any changes to my setup or homey.

[Previous page](https://community.homey.app/t/app-pro-openweather/61482.md?page=24)
