Add both name and value for the input_select integration options

[mariusz.schimke]

Currently, the input_select integration only lets you specify item names that display in the drop-down menu. For my use case (ViCare integration), I would like to choose a heating mode from the input_select box and have an automation apply that selected mode to ViCare. But the modes are programmatic enumerations, and exposing them on the UI is not very user friendly. That’s why I think it would be perfect to be able to specify for each input_select option a name and a value. This way you could have a user-friendly option like DHW and heating in the list, and an underlying programmatic value dhwAndHeating that would be sent by the automation to the ViCare integration. I would make the value setting optional so when no set, it would be equivalent to name.

[Didgeridrew]

Select helper with label and values

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

Input_select enhancement. Support mapping

An input_select currently allows you to specify a selection list: input_select: my_selector: name: My Selector options: - Kitchen - Garage - Bedroom - Office The options (Kitchen, Garage, Bedroom, Office) will appear as choices in the selector’s list. However there are situations where the chosen option is not the value we wish to use (in an automation). For example, “Garage” may represent the temperature value to set for the garage. However, input_select only allows…