Hi, their comments were:
-
supportedButtonValues
is a field that is not included by every device, that’s why you need to specify if it’s used or not in yours. - To do so, you need to add this in your device configuration:
{
...
"automation": {
"conditions": [
{
"component": "button1",
"capability": "button",
"version": 1,
"patch": [
{
"op": "replace",
"path": "/0/list/supportedValues",
"value": "supportedButtonValues.value"
}
]
}
...
}
I noticed that when we create the device config with the same configuration as before and we add these new values in patch
, it is not included in the creation, like this:
automation:
conditions:
- component: main
capability: button
version: 1
values: []
patch:
- op: replace
path: /0/list/supportedValues
value: supportedButtonValues.value
- component: main
capability: healthCheck
version: 1
values: []
patch: []
actions: []
type: dth
presentationId: 3d3312c5-1be6-3fed-8b30-257180e6c3cc
manufacturerName: SmartThingsCommunity
vid: 3d3312c5-1be6-3fed-8b30-257180e6c3cc
mnmn: SmartThingsCommunity
version: 0.0.1
We have to make a modification to the device config and a new VID will be generated. (We can add/delete capabilities that don’t affect the device UI, eg. Refresh, HealthCheck).
I already notified the team about this behavior, for now, I suggest that workaround. I’ll see if there’s something else that we can do.