In the example you’ve provided, I’m curious to know why you don’t define the input_select’s options with the names you wish to have displayed in the UI?
input_select:
fan_speed_room_fabian:
name: Fan speed room Fabian
icon: mdi:speedometer
options:
- low
- medium
- high
What is the purpose of defining an option name the user won’t see? What are you doing (in an automation?) with level1, level2, level3 that you can’t do with low, medium, high?
BTW, there’s an existing, similar Feature Request for input_selects. The difference is that it proposes that each option can be assigned a value (as opposed to a friendly_name). This is for use in automations where you wish to present the user with text-based choices (low, medium, high) but need numeric values within the automation’s template (35, 65, 100).
This is currently achieved by creating a map within the automation. However, from a design perspective, the map doesn’t belong in the automation (and must be duplicated if there’s another automation using the same input_select), the map belongs with the input_select.