FR: Button state_display

[matt8707]

Thanks - yes I see the logic now.
I think it would be useful to allow for decoupling the displayed 'state' on the button - for example I have a power socket which I would like to display the power draw attribute as the state for the button (which I now can thanks to the templates) but if I use that the button no longer goes 'on' since the 'state' is none of the values in the 'onStates' array you linked.

If the displayed state and 'on state' where 2 separate templates it would allow for that extra flexibility, since we could use templates to say for example if the entity_id state is > 10 output 'on' (which then matches against your static list).

Hopefully that makes sense and I'm not talking complete rubbish 😄

Originally posted by @realroywalker in #353 (comment)