new PID suggestion: disable

[diane]

I would like to propose a PID for disabling mechanisms. It would have SET and GET capabilities: set would allow you to disable a specific mechanism; get would return a list of mechanisms which are already disabled.

[sblair]

Diane,

Can you elaborate a bit more on how you would see this being used and applications where you would use it? I want to make sure we understand it better.

[diane]

We use it for teching automated lights, disabling specific motors (pan, tilt, etc) or determining which are in an error condition, but now that I think about it the command may not have a broad enough application to be useful to others.

[ericthegeek]

Diane, can your propose a packet format?

Sometime like this?

GET FEATURE_DISABLE
-Feature number (8-bit)

GET FEATURE_DISABLE Response
-Feature number (8-bit)
-Total number of features
-0=Feature not Disabled, 1=Feature Disabled
-32 Character Feature Description string

SET FEATURE_DISABLE
-Feature number (8-bit)
-0=Feature not Disabled, 1=Feature Disabled

SET FEATURE_DISABLE Response
(No data)

[diane]

Hi Eric, that packet format looks great. It covers all of the functionality I had in mind.

[ericthegeek]

Additional thoughts:
Feature number 0xFF means "All features"

SET for "All Features" can disable/enable all at once
GET for "All Features" is not defined and shall return "Unsupported Command Class"

Features must be numbered sequentially starting at 1.

Feature 0 shall return "Out of Range"