It’s perfectly possible to work around it. Trivial, even.
I don’t understand the problem(s)…
Why does an app rely on another (not optional)? Why not building a dedicated library used in all the apps needing similar functionality? So like npm does, too.
Please stop FUD’ing.
This wasn’t done to spite you, or as a reaction to your apps, you only found out about this change that has been present in HP2023 since the very beginning.
In short: the onInit()
of an app cannot take more than 30 seconds. This has to do with app lifecycle management and how apps on the HP2023 are run (inside Docker containers).
It’s not documented yet, because the SDK is still in flux, but because the previous error message (CreateClientTimeout
) wasn’t very descriptive and useful it was changed to what it’s now showing.
I’m pretty much the last person to defend Athom, but I can see they’re working extremely hard to get to a stable firmware, and your drama is just misguided.
If it’s not trivial, I fully understand that and also yours frustration, just surprised after what you have achieved seeing how you are giving up - but you very well know your app code so just hope that Robert is right here (even doing it"his" way)
Can someone suggest, why those triggers doesn’t work for me ?

The device itself updates it’s values fine and well as insights… any suggestions ?
No, it should work as i see it. Send me a diag?
I thought maybe I’m doing something wrong…thank you, diag sent. I even tried just on Trigger and then simply send me value - never got triggered, not sure why…
Hi Arie!
Not sure if already asked, but what is the “text” tag for in the retrieve card? Seems not returning anything.
Hey Anders,
Well, i guess you are right, since there are (currently) no text/string insights, i guess text will never be filled.
ill fix it when i have a DC day/moment: QlusterIT / nl.qluster-it.DeviceCapabilities / issues / #28 - Remove Text token from Retrieve insights. — Bitbucket
Thank you very much Arie for adding the picker:
Working like a blaze! I use it for heating and for lights.
- Heating: when person leaves the room, and automatic, turn off the IR panels.
- Lights: Automatic = switch on if there is zone activity; switch off a little while after zone activity ends.
You’re welcome Roger!
Keep the lists coming, that way we will get a good long lists of default pickers and lists to pick a list from
(Pun intended)
DC moment
2 new Pickers are in test now:
- Heating, Cooling, Off
- Automatic, Electricity, Gas, Off
And please note: i changed the values of the recently added picker Auto, On, Off: the actually values are now lowercase, just like all other pickers and default Homey pickers.
Sorry about the breaking change for the few that were already using this picker!
I’ll watch better next time when adding a list that the values are “correct”.
Awesome control with one AVD now: select heating or cooling (or off) for heating type and if heating then select automatic natural gas / electric as nature of heating:
If other zones are using Natural gas based heating the ‘automatic’ setting makes sure I use gas for heating my office room. If no others use gas, I use electricity.
Arie - you have outdone yourself! Thanks!
@RogerSt Perhaps you can create a nice AVD template with it?
@Arie_J_Godschalk Yes, I had thought about that.
I still need to refactor it because it is way to complex now. I will do that once I have my new HP23.
Then I can do the wizardry and post a template.
This might be a nice feature, while there isn’t any ‘last_changed’ data available in flows:
Does not seems like Cumulative energy is working on the new Homey Pro 2023.
Don’t know if that is an error from Athom or via this app
I have created new devices and given them the cumulative setting, but they show up as “load” and not as energy-meters.
No, i’m talking about the Device capabilities app
Arie added cumulative energy a few weeks/months ago, and that worked great on the “old” Pro, but does not seem to be working on the new Pro.
Ah ok, my apologies