Documentation error for Valve or platform bug

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

@workmonk

We are sending both the values for compatibility with existing smartapps that would be relying on the contact events for these devices.

Thanks, bud!

I know one reason I’m obsessed with this thread, though…

Glance at my post from February 2015:

Y’all know I’m not a SmartThings employee; but this isn’t the first time that I was prescient! .

Capability Valve: Attribute "contact" seems mis-named

(Perhaps this doesn’t belong “literally” in the New Capability Types Category … though maybe this Category can be renamed to handle definition issues related to existing Capabilities as well?) I am concerned that Capability “Valve” has it’s main attribute called: contact ["closed", "open"]. [image] A Valve is not a “contact sensor”. (NB: Is this just a Documentation error, @Jim ?). Per the Capability Guidelines (in draft by yours truly…), I recommend that the Primary Attribute of a Capability be named similarly to the Capability: i.e., valve ["closed", "open"] (For grammar reasons, to avoid using the word "open-ed ", I would prefer: valve ["shut", "open"] … Whatever, I’m Canadian ). Next: My Guidelines also suggest a Best Practice to avoid using Command…