fanSpeed UI Display change

[nayelyz (SmartThings Developer Support)]

@Patate

the dashboard has been changed in the above way. However, [actions] have changed the value according to the key value, but the label appears as Fan speed. I think we need to change the fan speed label of actions in a different way, how can I change it?

I mentioned how to do that in the posts above, please, let me know if you have questions:

@nayelyz

For automation.conditions, the value in “key” is still fanSpeed.value but changes to setFanSpeed in automation.actions due to its presentation configuration.

@Patate

However, when I changed it, I don’t think automation needs it because it specifies the streaming method of the PM value.
Is there a way to delete the item itself from automation?

Do you mean you want to remove it from the automation section? If so, in the device configuration, you only need to omit that capability in the section you want it not to appear. For example, if you have 3 capabilities in your profile but you only want to show two, you omit the corresponding capability:

"automation": {
    "conditions": [//Here, you would omit capability3
        {
            "component": "main",
            "capability": "capability1",
            ...
        },
        {
            "component": "main",
            "capability": "capability2",
            ...
        },
    ],
    "actions": [//Here, you would omit capability2
        {
            "component": "main",
            "capability": "capability1",
            ...
        },
        {
            "component": "main",
            "capability": "capability3",
            ...
        }
    ]
}

@Patate

So even if I changed it as you said, the history tab will keep showing the previous content? Is there any way I can modify what’s in the History Tab?

Yes, it will show the original configuration and cannot be modified.

@Patate

In this case, which capability is most appropriate? Could you recommend it?

I looked at this list of capabilities and I didn’t find one that would match yours exactly. Would you pursue the Works With SmartThings (WWST) certification of the device you’re integrating?
If not, you can create a custom capability, and you would need to consider they won’t be recognized by third-party integrations like Alexa/Google Home.

[Patate (J.)]

@nayelyz

I mentioned how to do that in the posts above, please, let me know if you have questions:

As you said, I modified the fan speed of the action part, but the label did not change and the fan speed remained the same.
However, label of detailview or automation has been changed.

    "actions": [
      {
        "component": "sensors",
        "capability": "fanSpeed",
        "version": 1,
        "values": [
          {
            "key": "fanSpeed.value",
            "label": "PMx",
            "enabledValues": [
              "0",
              "1",
              "2"
            ],
            "range": [
              0,
              2
            ]
          }
        ],
        "patch": [
          {
            "op": "replace",
            "path": "/0/list/alternatives",
            "value": [
              {
                "key": "0",
                "value": "PM10",
                "type": "active"
              },
              {
                "key": "1",
                "value": "PM2.5",
                "type": "active"
              },
              {
                "key": "2",
                "value": "PM1.0",
                "type": "active"
              }
            ]
          }
        ],
        "exclusion": []
      }
    ]

@nayelyz

Do you mean you want to remove it from the automation section? If so, in the device configuration, you only need to omit that capability in the section you want it not to appear. For example, if you have 3 capabilities in your profile but you only want to show two, you omit the corresponding capability:

OK. I will try it.

@nayelyz

I looked at this list of capabilities and I didn’t find one that would match yours exactly. Would you pursue the Works With SmartThings (WWST) certification of the device you’re integrating?
If not, you can create a custom capability, and you would need to consider they won’t be recognized by third-party integrations like Alexa/Google Home.

I understand what you mean. Thanks for checking!

[nayelyz (SmartThings Developer Support)]

@Patate

I modified the fan speed of the action part, but the label did not change and the fan speed remained the same.

The value in “key” is incorrect, you must use the command name. The difference is because of the capability’s presentation, you can see there’s no property “value” but there’s a “command”, you must use the last one for the reference in the device-config:

//Capability presentation of fanSpeed
"automation": {
    "conditions": [
        {
            "label": "{{i18n.label}}",
            "displayType": "list",
            "list": {
                "alternatives": [...],
                "value": "fanSpeed.value",/**HERE**/
                "valueType": "integer",
                "multiSelectable": false
            }
        }
    ],
    "actions": [
        {
            "label": "{{i18n.label}}",
            "displayType": "list",
            "list": {
                "alternatives": [...],
                "command": "setFanSpeed",/**HERE**/
                "argumentType": "integer"
            }
        }
    ]
}

Here’s an example:

//Section of Automation.actions in the device-config
"actions": [
    {
        "component": "main",
        "capability": "fanSpeed",
        "version": 1,
        "values": [
            {
                "key": "setFanSpeed",
                "label": "newLabel",
                ...
            }
        ],
        "patch": [],
        "exclusion": []
    }
]

Please, let me know your results.

[Patate (J.)]

@nayelyz

@Patate

I modified the fan speed of the action part, but the label did not change and the fan speed remained the same.

The value in “key” is incorrect, you must use the command name. The difference is because of the capability’s presentation, you can see there’s no property “value” but there’s a “command”, you must use the last one for the reference in the device-config:

//Capability presentation of fanSpeed
"automation": {
    "conditions": [
        {
            "label": "{{i18n.label}}",
            "displayType": "list",
            "list": {
                "alternatives": [...],
                "value": "fanSpeed.value",/**HERE**/
                "valueType": "integer",
                "multiSelectable": false
            }
        }
    ],
    "actions": [
        {
            "label": "{{i18n.label}}",
            "displayType": "list",
            "list": {
                "alternatives": [...],
                "command": "setFanSpeed",/**HERE**/
                "argumentType": "integer"
            }
        }
    ]
}

Here’s an example:

//Section of Automation.actions in the device-config
"actions": [
    {
        "component": "main",
        "capability": "fanSpeed",
        "version": 1,
        "values": [
            {
                "key": "setFanSpeed",
                "label": "newLabel",
                ...
            }
        ],
        "patch": [],
        "exclusion": []
    }
]

Please, let me know your results.

It works very well! Thank you very much!!

@nayelyz

1. Change the range to 0-4 and the step is still 1.

//detail view and automation.conditions
{
  "component": "main",
  "capability": "switchLevel",
  "version": 1,
  "values": [
      {
        "key": "level.value",
        "range": [
          0,
          4
        ],
        "step": 1
      }
    ],
  "patch": []
}

//automation - actions
{
  "component": "main",
  "capability": "switchLevel",
  "version": 1,
  "values": [
      {
        "key": "setLevel",
        "range": [
          0,
          4
        ],
        "step": 1
      }
    ],
  "patch": []
}

2. Leave the range of 0-100 and change the step to 25 (it depends on how many levels you have)

//detail view and automation - conditions
{
  "component": "switch1",
  "capability": "switchLevel",
  "version": 1,
  "values": [
      {
        "key": "setLevel",
        "range": [
          0,
          100
        ],
        "step": 25
      }
    ],
  "patch": []
}

//automation - actions
{
  "component": "switch1",
  "capability": "switchLevel",
  "version": 1,
  "values": [
      {
        "key": "setLevel",
        "range": [
          0,
          100
        ],
        "step": 25
      }
    ],
  "patch": []
}

By the way, I’m going to use 0-100% range on dimLight because of history tab.
As a key value, there are cases where ‘level.value’ is added in the 0-4 range, and ‘setlevel’ is added in the 0-100 range, could you tell me what difference is?

@nayelyz

Yes, you need to add the patch of the sample below to the device configuration for switchLevel:

{
    "component": "main",
    "capability": "switchLevel",
    "version": 1,
    "values": [
        {
          "key": "level.value",
          "range": [
            0,
            3
          ],
          "step": 1
        }
      ],
    "patch": [//THIS
      {
        "op": "remove",
        "path": "/0/slider/unit"
      } 
    ]
}

And when I remove a unit, is there a way to remove only the unit with a value of 0%?

[nayelyz (SmartThings Developer Support)]

@Patate

As a key value, there are cases where ‘level.value’ is added in the 0-4 range, and ‘setlevel’ is added in the 0-100 range, could you tell me what difference is?

In that post I provided two samples for the case of SwitchLevel. One with the range of 0-4 and the other of 0-100 but with steps (or jumps) of 25, this means that when the user moves the slider, the values possible will be only 0,25,50,75, and 100.
About using level.value or setlevel in key, it changes due to the capability presentation as I mentioned for fanSpeed. It generally changes in automation.actions but not all capabilities have the same configuration, in this case, fanSpeed and SwitchLevel are very similar.
That’s why you need to query the capability’s presentation to create the device-config because you must use the correct references on each view (dashboard, detail and automations) based on it. To do so, you can use this CLI command:

smartthings capabilities:presentation switchLevel -j

@Patate

And when I remove a unit, is there a way to remove only the unit with a value of 0%?

No, it cannot be removed based on a condition because the presentation has the property unit in this section and we cannot modify it, only remove it using the patch property. Even if we added alternatives, the unit property would be still there applying for all numbers no matter their value.

[Patate (J.)]

It’s been a great help:) Thank you for your help!