Hey mate,
I had the same issue. I am using the “control anything” version of the blueprint.
In that version you can define the action for the hold button events. I use a transition in these.
Here’s my yaml code of the automation:
alias: MH Auto Rodret
description: ""
use_blueprint:
path: damru/ikea_E1743-E2201-E2213_ZHA-Z2M_control-anything.yaml
input:
remote_devices:
- e784somedeviceidherejustchoseitinthegraphiceditor9d6c
on_press_action:
- action: light.turn_on
metadata: {}
data: {}
target:
entity_id: light.mh_deckenlicht
off_press_action:
- action: light.turn_off
metadata: {}
data: {}
target:
entity_id: light.mh_deckenlicht
on_hold_action:
- action: light.turn_on
metadata: {}
data:
brightness_step: 10
transition: 1
target:
entity_id: light.mh_deckenlicht
off_hold_action:
- action: light.turn_on
metadata: {}
data:
transition: 1
brightness_step: -10
target:
entity_id: light.mh_deckenlicht
Just make sure to use the other blueprint here.
If want to increase or decrease the transition speed change the brightness_step values.