Can you give me more info ?
Which integration are you using (ZHA/Z2M)? If Z2M, which version?
Did you update the blueprint path in your automation after update ?
Did you update the remote selection ?
Can you share a workflow execution or an error message of any kind ?
Yes, the remote_devices list. This is basically configured when you make an automation from the blueprint.
But in step 2 of the automation, after the trigger event, there is a comparison of the variable called remote_device to the list called remote_devices:
But from my last post you can see that it cannot match because the variable is an empty string: remote_device: ''
But the correct value for the variable is in device_id.
And just for the records: My HAOS version is 14.2, Home Assistant core is 2025.2.2, the blueprint version is 2.2 (the light variant).
To verify that I didnāt do anything wrong I created the automation fresh from the latest blueprint.
Id like to thank you for your work, I would really appreciate if you could help me to add a function to this blueprint.
I find very interesting use the hold function to shut covers and when you release the button, it stops moving, I used to use a blueprint that included that option do an action when holding and a different when releasing.
I can help you to test it, or whatever you need.
PD: I needed to z2m, but would be nice to add to your BP
That could be interesting indeed.
Currently, the release event is only used to cancel the hold, but I could add an option to execute something in addition as well.
Iāll look into it
@damru Any chance in using this to also support the IKEA Tradfri Shortcut button? Iām using it for every other IKEA remote I have and it works so well that I would love to use it for the Tradfri shortcut buttons as well.
Hi @damru! First, thanks for the great blueprints. Iāve been using the Light version for some of my RODRET switches, and it works perfectly. However, Iām unfortunately having some issues with this blueprint. Iām quite new to HA and especially blueprints, so was hoping you/someone could offer some insight.
Iām using RODRET switches with ZHA. Iām running the latest version of HA and of this blueprint (I only added it a few days ago). What I want to do is use the switch to control a light (on/off, dimming) as in the āLightā blueprint, but also expose the double press action to control something else (so it seems this blueprint is the way to go).
My issues:
Hold: When using the hold action, e.g., to dim lights, the hold action repeats until the max number of loops is reach, regardless of when the button is released. It somehow seems the āreleaseā action is not triggered. Changing the hold delay only changes how quickly it goes through all the loops.
Double press: Even though I have enabled the option to expose the double press, I still canāt get it to work. When exposed, it simply waits the ādouble press delayā time, and then executes the single press action. This is regardless of how long the delay is, even if it is multiple seconds.
In the log for the RODRET switch, it seems that all the key presses are registered correctly (i.e., hold, release, presses).
Any help with this would be greatly appreciated! Iām not sure what info I can provide to help troubleshoot, but let me know, and Iām happy to post it. Thanks!
First of all, thank you very much for this blueprint.
Unfortunately, I cannot get double click to work. The automation is triggered, but it does not do anything. If I set the same actions to a single click, it does work.
Do you have any advise on how to get the double click to work?
Thank you for your work! I believe I am running in the same issue as @THECASE99 mentioned above.
My setup: ZHA, Ikea Rodret E2201, blueprint just imported v2.2 ( git hash ef0961d554294f386b1ae79e4fe7af9f2635d1b9 ). Enabled virtual on double click as well as off. I experimented with different values of double-click delay.
Behavior: Single-click action gets executed even on double clicks. If I set a very high double-click delay (say 3 seconds), i can see the delay, so I believe the virtual double click action is correctly configured.
In the trace window I can see that the wait_for_trigger is being executed. But it will always run into the timeout.
Iām still trying to figure out how to debug this, but is it possible that the variable remote_device is never set? The conditional a few steps before uses trigger.event.data.device_id and not remote_deviceā¦
At the same time, i see a trace of the second press that HA ignores because it is a single automation.
@lassef@THECASE99@lluki
Sorry I couldnāt get back to you guys sooner.
After looking at @lluki remark, I pushed a fix for the double press and release issues with zha devices.
Could you please refresh the blueprint ?
Thanks
Thank you @damru , I just checked it and it works perfectly! Now i need to get my Zigbee stable enough such that the double clicks make it to home-assistant consistentlyā¦