MQTT Select command_template

[lanwin (Steve Wagner)]

The new MQTT Select support work very well! Good work. But there is a draw back. Its not possible to rename values for the users interface. Example.

My robomower mqtt endpoint accepts a list of commands. One is eod. Witch meed, “stop mowing for today”. I can now use a state_topic to name the incoming value from eod to “stop today”. But whats currently missing is that I can remap outgoing values and let “stop today” to be renamed to eod when its getting publised via mqtt.

So I would like to suggest a command_template. Witch works like state_template but the other way around.

[123 (Taras)]

This Feature Request is similar to an existing one.

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…

The only difference is that the other one was for input_select because (MQTT) select didn’t exist at the time. However, the principle remains the same: add the ability to remap the option’s name.

[mtrista]

Looks like this was implemented in December '21.