Restricting Device Setup with Multiple Capabilities

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

Excellent question – and an excellent “feature request”!

Unfortunately, to the best of my knowledge, this is not currently possible.

If you have the time to read (and contribute?), I initiated an extensive relevant discussion.
NB: multiple capabilities filtering is in the discussion, but there are a lot of related things.
I’ve emphasized that not all the ideas / features we discuss need to implemented at once, or ever.

Capabilities: Existing and Process to Add New. Note: Capabilities ~= Interfaces?: Capabilities MUST be very strictly defined and enforced (attributes / commands / events)?

Continuing the discussion from How to add a new device “capability”?: Hi guys… Great topic! This is something I’ve brought up in discussion with @Ben ages ago, and with @Jim very recently. My discussions with SmartThings (at great length) are tied to the fact that Capabilities are quite similar to the concept of OO Interfaces (Java and other strict object-oriented environments). Interfaces are a very powerful way to manage polymorphism and extensibility of classes and functionality. Ummm… somewhat briefly…(?) Capabilities (including all existing ones) must be thoroughly documented, particularly all attributes, commands, and event types. (NB: For interfaces, I believe that only methods (i.e., commands and getters/setters) are a part of the definition, so Capabilities have some extras…