You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am interested in using this card with button entities (both button.* entities provided by integrations and input_button.* entities that I create as helpers). The default tap action for these button entities is to open the info dialog, which I find confusing and unintuitive. I like that this card allows button behaviors to be modified using service calls, but that feels like a clunky workaround to me (and it doesn't work with cards like custom:auto-entities because I cannot use the {{ entity }} name for the target of the button press service call).
Describe the solution you'd like
I think it would be more intuitive for button entities to be triggered (call the button press service on themselves) with tap_action and to show the detailed information with hold_action by default.
Alternately, if there was a shorthand way to specify in the base_config that the entity used for service calls should be the entity itself, that would be pretty easy to implement without extra boilerplate for every button.
Describe alternatives you've considered
The workaround I have is to not use a tool like custom:auto-entities and instead manually add entries for each button, including manually specifying the service call for the tap_action on the button itself. This seems like a lot of unnecessary boilerplate to me.
Additional context
My current workaround that works but feels clunky/verbose/redundant:
Is your feature request related to a problem? Please describe.
I am interested in using this card with button entities (both
button.*
entities provided by integrations andinput_button.*
entities that I create as helpers). The default tap action for these button entities is to open the info dialog, which I find confusing and unintuitive. I like that this card allows button behaviors to be modified using service calls, but that feels like a clunky workaround to me (and it doesn't work with cards likecustom:auto-entities
because I cannot use the{{ entity }}
name for the target of the button press service call).Describe the solution you'd like
I think it would be more intuitive for button entities to be triggered (call the button press service on themselves) with
tap_action
and to show the detailed information withhold_action
by default.Alternately, if there was a shorthand way to specify in the
base_config
that the entity used for service calls should be the entity itself, that would be pretty easy to implement without extra boilerplate for every button.Describe alternatives you've considered
The workaround I have is to not use a tool like
custom:auto-entities
and instead manually add entries for each button, including manually specifying the service call for thetap_action
on the button itself. This seems like a lot of unnecessary boilerplate to me.Additional context
My current workaround that works but feels clunky/verbose/redundant:
What I would like to be able to do instead:
The text was updated successfully, but these errors were encountered: