fanSpeed UI Display change

Developer Programs Support
8

No, the engineering team mentioned the reference “___PO_CODE…” is converted code from the i18n notation by an internal service logic, and it can’t be reverse referenced to the corresponding “i18n.label”, especially from another capability.
So, they suggested using a custom capability or use a plain text label.

An option is to modify the switchLevel capability instead by changing the range and/or the steps defined for the slider. I made two different examples in a single presentation:

reference VID: 3f79f831-4539-3e4b-a47f-9de7068d7113

  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": []
}
  1. 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": []
}

This is how it looks:

Would it be useful in your case?