FR: I should be able to define define 'on' state easily in Button

[saya6k]

Since there is template now, I can define preview value.

However, since I can't define when is 'on' or 'off' in button, I need to create every binary_sensor that indicate that define on or off of that button. Which is annoying.

I wish I can just define 'on' or 'off' state of that button with template.

[realroywalker]

The change made does appear to have fixed the case sensitivity issue, but unless I miss something there isn't any way to configure what the 'on' state for a given button should be (which this FR requests) - Should we be seeing a new option somewhere to configure this?

[matt8707]

• select an entity that is 'off'
• add template (beside entity dropdown) to edit state
• write on or any of these

  ha-fusion/src/lib/Stores.ts

  Lines 30 to 54 in 1a012c5

  	export const onStates = readable([
  	'active',
  	'auto',
  	'cool',
  	'dry',
  	'fan_only',
  	'heat',
  	'heat_cool',
  	'heating',
  	'home',
  	'on',
  	'open',
  	'playing',
  	'unlocked',
  	// vacuum
  	'cleaning',
  	'returning',
  	// water_heater
  	'eco',
  	'electric',
  	'performance',
  	'high_demand',
  	'heat_pump',
  	'gas'
  	]);

[realroywalker]

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 😄