Proposed Capabilities are scheduled to be finalized and released in the future, but are subject to change. You can begin incorporating these Capabilities into your integration, but the Capability may not function in its entirety, particularly in the mobile app detail view.
Would a proposed capability introduce a breaking change that would make the driver crash? Or the kind of changes are “additions” and not “removals” so it does not break things?
I’m looking at knob specifically, which is being integrated into the Matter Switch driver but was wondering if it’s fine if I integrate it in my custom driver now since it’s better than my current workaround using custom capabilities.
Also the statelessColorTemperatureStep and statelessSwitchLevelStep which right now don’t even have labels in the SmartThings app and the action appears as the command name but would be nice to have.
The team mentioned that they can’t guarantee there won’t be changes that require code updates. However, in general, if a command changes, it shouldn’t affect other driver functionality. That said, it also depends on how the driver code is written.
Thanks @Itati . By the way, is it possible to submit feedback for the proposed capabilities?
Right now the aforementioned statelessColorTemperatureStep and statelessSwitchLevelStep capabilities for brightness and colour temperature accept steps from -100 to 100, which is fine since they are percentages.
However, the presentation in the app routine actions, while unfinished since there’s no text for them, only allow -50 to 50. Seems like an arbitrary limitation introduced on purpose to limit the usage inside the app since with Rules API you can use -100 to 100.
Can they update it so it accepts the whole -100 to 100 range in the app too? It’s useful for some less typical cases, like setting the brightness level of a light to the minimum without turning on the light, something you can’t do with the regular Dimmer action that will always turn on the light.
