Capability pollutantMeasurement

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

@AaronZON

What the heck are we suppose to do with capability.sensor?

Aaron, @JDRoberts et al.,

You make great observations in various posts in this thread.

Capability is a little twisted in the current implementation because of the limitations in the way it must be used in the UI for Device Selection in the SmartApp Preferences “input()” section.

It’s no rush, but I would appreciate feedback on my discussion of this in the following Topic:

DRAFT: Guidelines for Capabilities (under construction...)

Continuing the discussion from About the New Capability Types category: Disclaimer: This should probably be written by an official SmartThings Architect (or authorized technical writer), but I’m outlining my understanding of what makes for “good” Capability Definitions. This is based on my analysis of the existing Capabilities Taxonomy, and the SmartApp Developer’s Guide (particularly the section on device selection via preferences { input() }, and, most importantly, the Anatomy of a Device Type (Device Type Developer’s Guide), partially extracted here: Capabilities are the interactions that a device allows. We have a reference document that lists all available capabilities. When you define a capability, you are stating that your device supports the given capability. Commands are …