Do more with buttons!
This release is focused on improving buttons and custom actions. Custom actions now follow Home Assistant actions syntax, and supports a subset of actions defined there along with the key
and source
actions from this card. Confirmations are also supported.
The following actions are supported:
key
source
call-service
navigate
url
none
Buttons now support not only tap actions, but double tap and hold actions! Just like the touchpad center
tap. The touchpad center
double tap and hold actions are now configured in this way, and the old separate fields for enabling and remapping center taps have been deprecated. Also, double tap actions on buttons and the touchpad now work on iPhone!
custom_actions:
light_color:
icon: mdi:lightbulb{{ "-outline" if is_state("light.sunroom_ceiling", "off") }}
style:
color: rgb({{ state_attr("light.sunroom_ceiling", "rgb_color") }}
tap_action:
action: call-service
service: light.turn_on
data:
entity_id: light.sunroom_ceiling
color_name: red
hold_action:
action: call-service
service: light.turn_on
data:
entity_id: light.sunroom_ceiling
color_name: blue
double_tap_action:
action: call-service
service: light.turn_on
data:
entity_id: light.sunroom_ceiling
color_name: green
Other changes:
- Remapped hold actions do not add
hold_secs: 0.5
toremote.send_command
service calls. - Deprecated options:
enable_double_click
anddouble_click_keycode
- touchpad double tap is now enabled and reassigned by creating a custom action forcenter
and creating adouble_tap_action
.long_click_keycode
- now reassigned by creating a custom action forcenter
and creating ahold_action
.custom_keys
andcustom_sources
- are now justcustom_actions
.
Patch version changes:
- Do not add
hold_secs = 0.5
to data on custom hold call-service actions. - Use js-yaml to parse template results in rows array that are yaml strings so templating can be used to define multiple remote elements.
Full Changelog: 3.1.3...3.2.2