Send me a print screen of the repair settings?
Try the newest version?
I have added all default boolean capabilities with from the sensor.
I just tested it, and you need to activate Create Flowcards for that to work (which is in many cases if you want default Homey behavior).
Step is being added right now.
Yeah, already added it into some devices 
the new interface really makes it easy, even on mobile.
Unfortunately it also overwrites the icons of those capabilities 
, low key finding that annoying.
1 Like
You mean the icon gets overwritten (what i have had today one time with a device icon, dont now why), or you mean with default alarm/sensors you cannot set a custom icon?
Indeed, it uses the default capabilitiesâ icon, not the custom one.
1 Like
Yeah, sorry about that, have not found a solution to that 
I see you already changed for that behaviour in the latest update by auto hiding the icon input 
.
Does free up for some more custom icons I guess.
1 Like
Why?
The definitions still needs to be there?!
In Test: Show As Lists are order. by special index and then by name (some will stay at the top or top few). We can later translationobjects in it, and then order by language. The onceâs that must stay at top, will.
Iphone S5 looks good, but scrolling is a bit irritating.
You can just pick a random Icon thatâs already in use for something else .
1 Like
@Arie_J_Godschalk Still looking forward if you could support something like this.
I am trying to create a device that allows me to switch my heating/lighting/⌠to the settings: on/automatic/off and this approach suggested by @Le_Cactus might just do the trick.
1 Like
Wow, that is the almost, like, the complete infamous Windows 95 OS, I guess (okay, it was on 10 x 1.1MB diskettes, but nevertheless)
.
12 hours later: done 
Really impressive.
1 Like
Support what?
Well that is possible already, so look no further
I did it with advanced flows, but even with a handfull of regular flows and the right settings for button1 this work flawlessly
1 Like
One thing I noticed with this new implementation is that Homey really doesnât like that the newly added device has no class yet, and sets the device unavailable when you interact with it in any way (like renaming it) until you set a class and reboot the app (or set it available again manually).
Perhaps a default (other) class would be nice to prevent this. 
Edit: seems like adding the class as the very first thing (and the only one) still puts the device as unavailable.
1 Like
