It seems to be related to controlling the group of 10 lights. When I link it to just one of the ten it is very responsive. Is this expected?
Worked fine after I re created the automation. Maybe I missed to re-import the Blueprint?
Thx for the hard work.
Additional question: would double click (on and off) support multiple actions or building blocks?
Hi,
I want to start a script from the blueprint, but I can’t find a way to do so?
With best regards
Gerhard
Hey,
Double clicks already does support actions/building block
Hello,
If you “Add action” and start typing the name of your script, it should show up and you can use it from any of the available commands.
Oh … I always check the lists first … ok, thanks.
Hmmm.
It worked for two scripts. I added one script (for ‘hold’) but now I cant find the new script in the list.
And after a restart, the two scripts I alrady selected were gone.
It is strange.
With best regards
Gerhard
Ok.
I have scripts, I can run this scripts but when I want to add an action as you described above, there is no script at all.
This happend after a reboot of HA.
Whats wrong?
Thanks for helping
Made an account just to reply to this.
The issue (which I also have) seems to be related to grouping entities with Z2M.
Bypass this by utilizing the Light Group from the Group Helper add-on instead.
Apparently this pushes commands on a per-entity basis as opposed to the native Z2M group command, which initially deterred me, but in practice it works reliably with this blueprint whereas Z2M grouping does not.
Hi there, my first post here so please forgive me for any mistakes…
I used this blueprint to operate a RODRET to switch a smart plug that’s kind of difficult to reach. I use both single press as double-press to switch on (single is on until one power cycle is completed, double to just switch on without further action) and just a single press to force a switch-off.
My problem is: After pressing the button (switching on) the automation seems to ‘hang’. Pressing another button afterwards, won’t do anything (the press is detected bij HA, proven by the logging, but the automation isn’t reacting anymore). I have to re-open the automation, then it will work again for a single time.
What can be the issue here?
Setup is a Home Assistant green, up to date with core updates, a ZBT-1 dongle for Zigbee and complete Zigbee network configured and connected by ZHA. Blueprint imported through the link in this forum-thread above.
You ever find out how to increase the brightness steps value?
I want to press and hold the on/off buttons, but 10% is too slow for me too.
Very nice blueprint, great to have!
I have a considerate number of TRADFRI and RODRET switches, meaning I like using this blueprint for all of them, no matter what they control. Some of these (TRADFRI) switches only using a single-press action on either button and don’t use long, double or hold at all. Since the TRADFRI exposes a single-press start event, it would be nice if the automation could recognize that there are no other actions set and respond immediately, instead of waiting for a single-press finish event which delays the light switching on. Is something like this possible in either the config of my setup or in the blueprint itself?
1 Like
That’s a good idea but unfortunately I don’t have a tradfri so I cannot develop this feature on my own.
As of now, Rodret and Tradfri are binded to these events:
- trigger: event
event_type: zha_event
event_data:
command: "on"
cluster_id: 6
endpoint_id: 1
id: press-on-zha-e1743-e2201
- trigger: mqtt
topic: "+/+/action"
payload: "on"
id: press-on-z2m-e1743-e2201
- trigger: event
event_type: zha_event
event_data:
command: "off"
cluster_id: 6
endpoint_id: 1
id: press-off-zha-e1743-e2201
- trigger: mqtt
topic: "+/+/action"
payload: "off"
id: press-off-z2m-e1743-e2201
And if there is no second press configured, it will answer immediately.
If you are referring to another event then I’d need to make the change.
I will check with the Rodret I have
Don’t bother, the only modern button that sends something that could be considered a “initial press” is the SOMRIG (and the dots in the SYMFONISK gen2). The others are dimmer switches and just send the one command depending on the type of press.
I suppose that’s the TRADFRI shortcut button in the newest firmware version, the TRADFRI on/off or previous versions will not. They’re probably using the same algorithm of the SOMRIG which makes the single press soo slow until it confirms there’s no double press.
1 Like
Until this week, the double press event worked fine! I used a what older version of damru/ikea-rodret_E2201_ZHA-Z2M_control-anything.yaml. Updated to v.2.2m no luck.
Is it really just the latest firmware? And did min only get the firmware this week?
What device exactly? If it’s the RODRET, the double press is emulated, the button only sends the “On” or “Off” commands and those events have not changed.
The old blueprint however would not work with the new firmware of RODRET because IKEA changed the model name from “RODRET Dimmer” to “RODRET wireless dimmer”. More recent blueprints account for that.
Would it be possible to update this blueprint to include the new IKEA Bilresa (E2489) 2 button remote? I already use both versions of the blueprint with my rodret switches and am super pleased, so I just thought I’d ask if you could extend the functionality to the new switch as well. THANK YOU!
Hey,
I might. I purchased one Brisera a couple weeks ago, and I’m still unable to add to to HA wether it’s with Matter or ZHA. If at some point I’m able to, I’ll look into it 
1 Like
Hi,
using this Blueprint for a while with Rodret and Tradfri Dimmers without any issues - thanks so far for your work on this.
While reviewing my logs I found this warning quite often:
WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'topic' when rendering '{{ trigger.topic }}'
After some searching around I found this to be caused by your blueprint somewhere in the area of:
condition:
- condition: template
value_template: "{{ \n (trigger.event.data.device_id in remote_devices if is_zha)
or\n (trigger.topic.split('/')[1] in remote_devices_names if is_mqtt) \n}}"
Since I am using ZHA only I decided to completely remove any mqtt stuff from your blueprint and found this to be working for me also without any warnings mentioned above. I changed the relevant section to:
- condition: template
value_template: "{{ (trigger.event.data.device_id in remote_devices )
}}"
Unfortunately my programming skills are not sufficient to propose a patch for this to keep the mqtt functionaltiy - maybe you can review this section and fix this in a future version?
Hey !
New version is here 
with Bilresa (2 buttons) support for Z2M
Check the 
first post to download the blueprint
See the 
Changelog
3 Likes