A thread to share some coding techniques for QuickApps?
Because QAs are "long running scenes" (they don't have to be loaded and restarted for every event) - it is actually worthwhile to build up a library of "nice to have" code and include them in QAs.
Please login or register to see this link.
Please login or register to see this link. s
Please login or register to see this link.
Please login or register to see this link. client
List of posts:
Introduction to the QuickApp ana
each interface might have (at least) 3 following definitions: properties, actions and events (and if there are values defined, they can be used to catch events, run actions read/write properties)
Example the voip interface type definition:
Please login or register to see this code.
Device itself can belongs to specific type, which defines as well things (e.g. this is how type com.fibaro.alphatechFarfisa.xml has been defined)
Please login or register to see this code.