That is weird that your devices do not expose the _action entity.
All my dimmers have those, for example:
sensor.bedroom_hue_dimmer_action
@thotha - Looks like your dimmer switch is not exactly the “Philips Hue Dimmer Switch v2” as indicated in the subject of this thread. Your’s dimmer got a dial, so that’s a different model.
Ok, so where should I search fir a solution?
In/for Zigbee2MQTT, MQTT, Mosqitto Brocker, Home Assistant Core, Hassio, Sonoff Stick?
After search the internet with this search one of the first results is this one and close to the bottom I did find the solution to this problem.
I do not know with which update within the last few days this happened but suddenly the mentioned setting legacy triggers was disabled.
Maybe you could mention somewhere that if a user as problems with your blueprint, he should check that setting within Zigbee2MQTT.
Sorry for this trouble.
1 Like
Bit confused, does this reprogram the buttons just like Switch Manager, and can it also support RWL021?
It’s a blueprint so that you can create an automation and specify different actions for different buttons and press types.
It may work with RWL021 as the action names look compatible, but I didn’t test it.
This blueprint is perfect for my needs! 
Recently, I added a new automation to the blueprint and selected my light group. However, I have noticed a slight delay of around 1 second when I toggle the light and it turns on. But when I toggle it again and the light turns off, there is no delay. I wonder if anyone knows how I can change the delay only when the light turns off, so it matches the same delay as when the light goes on.
Thank you.
Thanks for this blueprint - works perfectly within areas or specific lights.
But I don’t understand why the dimming is not supported.
I tried to use “UP Button hold” to let the lights go up in 10% steps.
Tried to change the brightness_pct which didn’t work.
But changing it via yaml editor did not work:
service: light.toggle
metadata: {}
data:
brightness_step_pct: 10
transition: 1
target:
area_id: kuche
Why is that not supported and how can I achieve this?
THX!
You probably need to use light.turn_on service instead of the toggle.
I’m trying to hunt down a hue dimmer switch v1 blueprint, if anyone has one?
Thanks @JetSerge, this is great! I’m new to HA and this is just what I was looking for. I have a few binary sensors for the times of day (e.g. morning, afternoon, evening, night) so I can change automations based on the time of day. I’m trying to figure out a way to add a control to the press release button where if the ‘night’ sensor is on, then it will trigger a dimmed light, but I can’t work out a way to do this as the blueprint throws up an error if I try if-then-else in the yaml. May I ask if you are able to provide any guidance? Thanks again!
You should be able to if-then-else via the UI editor in the automation, no need to use YAML. Sorry, it doesn’t seem to be specific to my automation, maybe post your code in another thread and ask the community for help?
1 Like
Thanks @JetSerge , I love this blueprint. If double press could be implemented it would be perfect. I have tried some other ones for RWL022 and Zigbee2MQTT but double pressing does not work. somebody could help me? I need the double press please.
@JetSerge love your blueprint!
Just figured that something in z2m or HA must have changed with the recent updates.
My actions for up_hold_once and down_hold_once didn’t work anymore.
Everything else kept working like a charm.
Figured out that the helper field becomes “unknown” in between the real states.
So the following code needed to be changed to don’t let the helper field take status “unknown”:
condition:
- condition: template
value_template: '{{ trigger.event.data.new_state.state not in ("", "None", "unknown") }}'
After adding “unknown” to the exclusion list the up_hold_once und down_hold_once actions are working again 
Maybe you want to add that to your great blueprint to keep it working?
If you’re already at it, this
- service: input_text.set_value
data:
entity_id: !input helper_last_controller_event
value: '{{ command }}'
should better become something like this
- action: input_text.set_value
metadata: {}
data:
value: '{{ command }}'
target:
entity_id: !input helper_last_controller_event
according to the new best practice I guess.
2 Likes
Thanks for the fix. I didn’t test it myself yet, but I updated the blueprint gist.
As for the new syntax keywords, I’ll wait for some time before updating it to maintain compatibility with the older HA versions.
1 Like
Thanks for the template! It didn’t work until I replaced underscores with hypens in the dimmer actions.
e.g. {{ command == “on_press” }} becomes {{ command == “on-press” }}
I recently moved from ZHA to Zigbee2QTT so it may be a config issue on my side?
Edit: I realise that I’m using a V1 dimmer (324131137411), not V2 which might be the reason.