Maybe I’m doing it wrong. But dealing with states and actions in a button is horrible for me. Creating a helper device to the have an automation triggered by the button changing its state is so different from any other programming concept I’ve seen.
Let’s say I’d like a start/stop button in one icon. The start triggers an entity activity, the stop triggers another one, and the state of the icon is determined by one or more sensor with different states.
When I bind a Button Card to a Device Helper of type input boolean, nothing happens. I have no clue how to bind a state of an entity to this input boolean. Are you saying that entity state changes need to be monitored with automations to set this input boolean and then have a bunch of more automations to act on tap actions?
So helpers are like global variables modified by different processes (automations). This just asks for troubles.
You make an automation using the input boolean. When the boolean triggers on, run this set of action, when off run this other set of actions. It’s not done from your frontend dashboard, it’s done from the automation ui dashboard.
The automation isn’t modifying the input boolean. You are when you press the button. The automation just fires actions when the input boolean changes from off to on or on to off depending how you set up the automation.
I personally don’t see this ever being added because the logic is meant to be applied in the backend for selecting actions. I know automation reworks are coming this year where you can likely tie an action to an entities state, but it still wouldn’t be done via the card. It would be done via the entity.
As for your color and icon requests, there are already WTHs requesting this.