[Archived][APP][Pro] OpenWeatherMap

Hi Ronny, thanks for all the work and your views.
The 1h ahead device installed well.

Now, this device has 13 enum capabilities, and n# 13 (Windforce Beaufort), is slightly visible in the device ‘Status Indicator’ selection view.

After quite a few hit and miss, I was able to select it :crazy_face: (setting a smaller phone font did not help, the table row height seems fixed):

I’m sure it’s an Homey app design (no scroll enabled) for that screen. I will inform at Athom about this.


Hi Peter,
yes, that’s a Homey App issue. It seems for me a list with fixed row hight, too.

On my phone with a hgher resolution and some longer german words it seems to be ok.

There shoule be the “none” entry be visibe, too. But I have a fixed bar of android buttons. Have you them configured to hover?

To compare: the longer word is still visible in a line.

But I have textsize on position 2 from 8 possible settings. Really small. Perhaps that’s a reason why the date/time is not shown correctly in your example.

I’ve seen a error with the hourly forecast icon. It’s set wrong on pairing. A new testversion is online.
So best would be to delete the forecast device and ceate it new. Then it should have the correct icon with sun and clock.

Thanks, of course the resolution is a factor, didn’t realize.
The bottom bar can be hidden as I just discovered, and now the 13th capability is shown, still “None” is out of range.
This is all of my screen now:

Now I’m waiting on Athom’s reply


Oh I made a mistake earlier with the flowcard translations.
Windspeed (km/h) = Windsnelheid (km/u)

Other findings:

  • Tile 1h forecast install:
    If you set forecast time to 0 hours during install, there will be no data loaded.
    If you set forecast time to 1 hour, data gets loaded.
    If you set the forecast time back to 0, then it halts.
    If you set it back to 1 or up again, it only starts updating after an app restart.

  • Current weather per 5min.
    The time of “Forecasted time” is correct, but sunrise/sunset seems to be at UTC instead of local time.
    At my location the timezone is +1GMT and both timestamps are an hour early.

I have already helped with the translation of some apps into German. So far, I didn’t recognized any app that the units were translated into local language.

The international unit for speed according to the international system of units SI is m/s. km/h is based on the unit m/s. km/h is therefore an international unit.

Thanks, that is fixed with the test version 0.1.3
The problem with the time I will check later. Perhaps the new API is providing UTC timestamps instead of local timestamps. I just copied the logik from the old devices but it doesn’t seem to fit.

1 Like

That’s wrong for the old devices, too. I think it depends on the Homeys firmware update last year where Homey internally started to use only UTC. I have to correct it for all devices of OWM app.

The sunrise/sunset should be in local timezone now.
Testversion: 0.1.4

1 Like

Thanks @Robin_van_Kekem for the hint. I’ve seen your comment and adjusted the description.

Hi Dirk, thanks! You’re right, before I never really noticed it appearantly.
My focus was on the description though.
Windforce = Windkracht
Windspeed = Windsnelheid

I’m sure that’s the cause, Ronny

They are, thanks!

The 0 hours setting in hourly forecast now works indeed: :heavy_check_mark:

1 Like

A new testversion (0.1.5) is online adding the daily forecast device for OnecallAPI.
Please be aware I forgot something to implement with this amount of triggers and conditions :sweat_smile:

1 Like

Hi Ronny,
Will it be available for the Homey Bridge? Hear great things about this app… Hope to hear from you. Grtz Dennis

Hi Dennis,
this app will not be accessible on the bridge.
Technically it’s no problem because all is done via cloud-API, but…

  • OWM would have to develop this app (or hire me to do)
  • The developer would need a to be a ‘validated developer’
    I can’t imagine that OWM is interested. And our way of individual API keys is something, that is not welcomed by OWM.
    So sorry, at the moment not.

A new test version ist online


  • changed some icons to keep a commen material design
  • changed capability values for moon phase (moon only, text was too long) and wind direction (including arrow and translated direction names).


  • fixed capability title (wind speed for km/h/ wind strength for Beaufort)


  • Corrected some text translations (wind speed/strength).
  • adjusted unicode characters for wind direction. Please report if it’s not shown correctly. It seems, the possible unicode charaters are different on mobile devices.

The new app version is online.
Because of the big changes a new thread was started for a new beginning.

Please follow me here…
:arrow_right: https://community.homey.app/t/app-pro-openweather/61482

@Admins: Please close this thread. Thanks :slight_smile:

Found a small omission in the timestamp of my “Luchtkwaliteit actueel” device. I’m using version 1.1.11
The timestamp is not correct

[EDIT: typo in versionnumber]

Hi, I just adjusted the “new” device types (OneCall), not the deprecated ones.
I will take a look at it. Other way you can use this as a reason to move on to the new devices :slight_smile:

Edit: Please use the new topic from the last post.

Please continue here: [App][Pro] OpenWeather

1 Like