Sometimes the values are not friendly, so the input select has options as Program1, Program2 so allow set labels to value could be more friendly for user.
There was talk about implementing input selects with values for each option. Not sure if it is being actively developed. It has been recently introduced for Schedule helpers.
Yes please! It is kind of implemented in blueprints for the select selector with label/value pairs. Use case selecting a media player where the label is Kitchen Speaker and value is media_player.sony_QA_1234_AA. If no label is specified it should default to same as the value
Brining this one back, it was there in 2022.
2022: Select helper with label and values
Feature Request: Input_select enhancement. Support mapping
Sometime you need use a selector for a service that use certain values “not human”, so, you can create a selector with ugly labels or pretty label and remaped with map or if/else the human value to valid value, that is very boring and add complexity to automation
Example:
- input_select:
oven_program:
name: Oven Program
options:
- label: Pizza
value: 12
- label: Potates
value: 15
initial: 12