Put value id of enum capability in tag

To create a picker GUI component, the following is defined in driver.flow.compose.json:

  "actions": [
    {
      "id": "change_measure_my_picker_dir",
      "title": {
        "en": "Verander richting"
      },
      "args": [
        {
          "name": "dropdown_richting",
          "type": "dropdown",
          "values": [
            {
              "id": "Auto",
              "label": {
                "en": "naar Auto"
              }
            },
            {
              "id": "Buiten",
              "label": {
                "en": "naar Buiten"
              }
            },
            {
              "id": "Binnen",
              "label": {
                "en": "naar Binnen"
              }
            }
          ]
        }
      ]
    },

The capability is used in driver.compose.json:

  "capabilities": [
    "measure_my_picker_dir"
  ],

In principle this is functioning. However, the tag which shows up for the device has the number 1, 2 or 3.
I would like that the id (or label) “Auto”, “Buiten” or “Binnen” is printed in the tag such that it can be used within a flow as text.
Does anyone know how to get this done?

Can you show as screenshot where ‘the tag shows up’?

If you mean the tag list where you can select a tag to enter it into a flow card, they just show examples for such tags, because a design time, you don’t know a value.

Only tags for ‘real’ capabilities are showing the current value.

As example I just print the tag value on the timeline:

There it shows 1, 2 or 3. So that’s the real value of the capability.

First: I think you answered the thread, not my answer, so I get no notification.

About your tag. It’s the tag for a device capability, right?

Then you are right. It should show the IDs from your capability (‘Auto’ etc).

I will check my devices later if I get the IDs or not.

I used an enum caopability as tag:

It’s using the capability enum ID:

Thanks for your replies. I don’t get the IDs. The difference is probably that I did not define the capability explicitly myself. Only the actions in driver.flow.compose.json as indicated in my initial post.