This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Device classes - how to?
jorden
Member
in Developers
I am working on an app that uses the "Curtains & Blinds" device class. The information is found on https://developer.athom.com/docs/apps/tutorial-Drivers-Reference.html
This generates a set of "default" premade flow cards:
Triggers:
- Opened
- Closed
- Position Changed #level
Conditions:
- Is open
Actions:
- Open Curtain
- Close Curtain
- Set to position
Now I made a capability "dim", which works for the mobile card but also gets the "Set to position" value correctly. Because that works, also the "Position Changed #level" trigger works directly.
However, I am wondering how I can make the other 2 cards... is that the "onoff" capability? Do I have to create a windowcoverings_tilt_up and windowcoverings_tilt_down capability? Or does this work differently?
This generates a set of "default" premade flow cards:
Triggers:
- Opened
- Closed
- Position Changed #level
Conditions:
- Is open
Actions:
- Open Curtain
- Close Curtain
- Set to position
Now I made a capability "dim", which works for the mobile card but also gets the "Set to position" value correctly. Because that works, also the "Position Changed #level" trigger works directly.
However, I am wondering how I can make the other 2 cards... is that the "onoff" capability? Do I have to create a windowcoverings_tilt_up and windowcoverings_tilt_down capability? Or does this work differently?
Comments
He hacked them in the app as they were not yet implemented in 1.5.6 ....
Guess there is more to be done.