I’m a bit lost. I tried pasting your code snippet into the template yaml that makes the light stop at 1% when dimming down. But I can’t get it to work. Would be grateful for some guidance.
Not sure how to configure the On - Hold action to increase brightness and the Off - Hold action to decrease brightness
On - Double press event to switch color temp and same with Off - Double press event
1 Like
Hi, I got a couple of Rodret remotes just to try this blueprint. Something is wrong though and I can’t seem to be able to identify it.
The first remote I paired with ZHA is working fine - I can see events coming in HA when I press the buttons.
The blueprint imported ok and I can see it in blueprints. I can start adding an integration based on it, I can select the remote device and the actions to perform (persistent notification for testing). Then I press Save, and Rename on the next screen - I get no error whatsoever, but there is no new automation showing in the automation list. It does show up in the automations.yaml file.
At this point it doesn’t matter if I reload just the automations, all YAML or if I completely restart home assistant, the new automation never triggers, while the remote events are still received over zigbee.
Any ideas, please, for what to check? This is the very first time I am trying blueprints and I am lost. Thanks a lot!
LE: Never mind, I managed to find the issue and a solution for it - the very last paragraph on this page: Splitting up the configuration - Home Assistant - the “automation manual” and “automation ui”.
The blueprint is now working fine and I’m a happy, albeit very tired, bunny.
Using Controller - IKEA E1743 TRÅDFRI On/Off Switch & Dimmer Blueprint to use with my new RODRET didn’t have any problem to control my Aqara E1 Blinds motor.
I am on Z2M with Sonoff Zigbee stick.
I’m unable to configure the device. i’ve triggered the pairing mode by cliclyng the button 4 times. after that it shows up in the ZAH discovery but i’m stuck in “configuring” phase (even after pressing the reset button for 10 second). Someone can help me?
IKEA started bundling the Rodret with their cheap smaller Tretakt smart plug so I bought a bunch. It was easy to link to ZHA, and the blueprint works to switch on and off a ZHA group of lights (I’m not interested in using them with the plugs).
I got dimming to work by installing the Smart Dimmer blueprint which creates a script associated with the ZHA light entity. I then call this script with the On Hold and Off Hold actions:
service: script.hallway_ikea_rodret_dimmer
data:
action: dimm_up
Action dimm_down dims the light down.
Works well.
I pushed the pairing button 4 times, let it do its thing for 5 or so seconds(long enough to stall but not long enough to time out) then pulled the battery and plugged it back in after 1-2 seconds. no additional button presses.
I’ve spent about 3 hours trying to get the RODRET remote to connect to HA. Tried the 4 button thing, holding the button, rebooting, pulling battery out, but nothing. I’ve got 2 and they both get stuck at Configuring, and even if I get them to connect (so they show the battery percentage), I can’t get them to work with any automations. I have patience like many have sugessted, but I’m thinking I might give up. (I’m using ZHA, rPi3, and a Sonoff 3.0 Plus thing)
1 Like
I notice in my logs that this blueprint is trying to use zigbee2mqtt even when the device is set as a ZHA - I see a lot of these error messages:
Logger: homeassistant.components.automation.controller_hallway_dimmer_3
Source: components/automation/__init__.py:842
integration: Automation (documentation, issues)
First occurred: 16:23:43 (5 occurrences)
Last logged: 16:23:43
Got error 'Cannot subscribe to topic 'zigbee2mqtt//action', make sure MQTT is set up correctly' when setting up triggers for Controller - Hallway Dimmer 3
I use a similar blueprint for Styrbar remote controls where one of the settings is which Integration to use - ZHA, Zigbee2MQTT or Deconz. Perhaps that would work better.
That blueprint suggests it can also work for Rodret, but I have not been successful, so sticking with this one for now
Thanks, this worked effortlessly!
Is there any way to control the steps when using it for dimming (hold). It goes in too big steps on my setup.
Like many I had massive issues getting these RODRET’s to pair. What worked for me was doing the initial pairing which stalls at configuring but the device shows with no battery or events firing. I then pulled out the battery, held the pairing button and kept it held whilst I inserted the battery. After about 10 seconds of still holding the pairing button after the battery was inserted I released it and all button events were now firing, battery was showing and this blueprint worked.
I’m using ZHA on 2024.8.1 with a Sonoff Zigbee 3.0 USB Dongle
1 Like
@Maart3n It seems like we could do this. I found this guy on Youtube:
I was able to replicate this using the SOMRIG shortcut button (it’s the same thing as the RODRET but has the double pressed event by default). It seems like all we need for this to work is to be able to select the already defined triggers and for the script to be set to “restart” instead of single. It seems that @damru already has the “release from hold” trigger set which would have been the 3rd requirement.
Cant’t upload a screenshot since i’m new ! [hass|690x371](upload:// ncv4c3YBFMVDnx4eqhpeKJJNTUW.png)
Hello,
Thank you for this blueprint. I succeed to use single on/off & hold press buttons but i absolutely don’t understand how to activate double/triple press actions ?
You talk about activate with expose ? How i manage to do this ? I’m running under Z2M.
Excuse me if this is a noob question 
Following setting ‘expose’/activate the double press action:
If it is still not working care to share your yaml and a printscreen of yours?
It’s strange because i don’t see the “double press event” like yours :
the yaml:
alias: IKEA Rodret Dimmer (Zigbee2MQTT)
description: ""
use_blueprint:
path: Grateful-J/ikea-rodret_E2201_ZHA-Z2M_control-light.yaml
input:
remote_name: Telecommande Chambre
on_click_action:
- action: light.turn_on
metadata: {}
data:
transition: 2
brightness_pct: 20
target:
area_id: chambre
off_click_action:
- action: light.turn_off
metadata: {}
data:
transition: 2
target:
area_id: chambre
off_hold_action:
- sequence:
- action: light.turn_off
metadata: {}
data: {}
target:
area_id:
- salon
- meuble_tv
- type: turn_on
device_id: 8ff4668a7f07565e792896e4d9efc407
entity_id: d20be2967b1c097d308651fcac051733
domain: light
brightness_pct: 20
flash: short
off_double_click_action:
- type: turn_off
device_id: 6e480e775d43c511d43167b731ecbc14
entity_id: 2a0eb7b72d6563907f7e3c1614a9de4e
domain: light
helper_multi_click_delay: 250
off_triple_click_action: []
on_double_click_action:
- type: turn_on
device_id: 6e480e775d43c511d43167b731ecbc14
entity_id: 2a0eb7b72d6563907f7e3c1614a9de4e
domain: light
brightness_pct: 50
Ohh God , i guess what is false : reading my yaml title, i saw that i use the wrong blueprint "light & not the anything blueprint 
Edit : @MrBearPresident : thanks for the help 
New release of the blueprint is here.
The code is now available in github.
v2.0.0
BREAKING CHANGE
- when using Zigbee2MQTT, device must be reselected in the automation as the device selector was merged with ZHA instead of having a plain text input.
What’s Changed
- feat: add IKEA SOMRIG support
- chore: change syntax from platform to trigger
- chore(z2m): move from mqtt topic to device action
Hey, I also use this blueprint.
Any reason for existing automations to do the change?
I’ve copied alot of your code. (see IKEA STYRBAR Dimmer Remote (E2001/E2002) - ZHA/Z2M - Control anything) do you advice me to change this?
If you dont own a Somrig remote there’s no real need so far.
Other than that, the thing is that the v1 trigger syntax (ie using platform: event for ZHA or platform: mqtt for Zigbee2MQTT) might become unsupported at some point.
I’ve switched from ‘direct’ connection between Rodret and TRÅDFRI (IKEA LED driver for kitchen under-cabinet lights) to HA integration and this blueprint because I wanted to control the lights not only with the remote but also automations and so on.
But, after I switched I experience the same two issues that others reported here earlier (but I couldn’t find a solution):
-
Brightness change steps are too “big” (10%), especially if you compare with the ‘direct’ integration (it was completely smooth and you could not notice a step).
Is there a way to improve this and make changes more smooth? -
If I hold a dim button too long - lights go to 0%. It was mentioned here that they should go to 5% (or something) and stop, but it’s not a case for me.
Am I doing anything wrong?