IKEA RODRET + SOMRIG + TRADFRI Remotes - ZHA/Z2M - Control anything

@nisay @ArronTay

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 ?

Thanks

Hi @damru

The variable remote_device is empty.

Here are the changed variables of the trigger event:

this:
  entity_id: automation.mh_auto_rodret_test
  state: 'on'
  attributes:
    id: '1739280869073'
    last_triggered: null
    mode: restart
    current: 0
    friendly_name: MH Auto Rodret (Test)
  last_changed: '2025-02-11T13:34:53.866733+00:00'
  last_reported: '2025-02-11T13:34:53.866913+00:00'
  last_updated: '2025-02-11T13:34:53.866733+00:00'
  context:
    id: 01JKTKGHXA93Y1HQ5KKRJG66JG
    parent_id: null
    user_id: null
trigger:
  id: press-on-zha-e1743-e2201
  idx: '0'
  alias: null
  platform: event
  event:
    event_type: zha_event
    data:
      device_ieee: c4:d8:c8:ff:fe:5a:df:82
      unique_id: c4:d8:c8:ff:fe:5a:df:82:1:0x0006
      device_id: e784a2d9ed7c77aa4bd156a8072e9d6c
      endpoint_id: 1
      cluster_id: 6
      command: 'on'
      args: []
      params: {}
    origin: LOCAL
    time_fired: '2025-02-11T13:35:45.713170+00:00'
    context:
      id: 01JKTKJ4HHDGXXX6X9P69CGF45
      parent_id: null
      user_id: null
  description: event 'zha_event'
helper_force_brightness: false
helper_hold_delay: 0.1
helper_hold_dim_step: 4
light: light.mh_deckenlicht
remote_devices:
  - e784a2d9ed7c77aa4bd156a8072e9d6c
remote_device: ''
mqtt_topic: ''

Hope it helps!

Hey @LtKowalski

Please refer to this, the input remote_device was renamed to remote_devices to reflect that you can now select more than one.

Hi @damru

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.
:slight_smile:

Thanks!

Are you using ZHA integration ? If so, could you update the blueprint and try again?

1 Like

Yes, I’m using ZHA.

Awesome! You’ve fixed it!
Works perfectly now!

remote_devices:
  - e784a2d9ed7c77aa4bd156a8072e9d6c
remote_device: e784a2d9ed7c77aa4bd156a8072e9d6c

Thank you! :+1:

Hello @damru

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

this is the blueprint: IKEA Somrig remote E2213 ZHA

Hey @mareqte and thanks for the kind words.

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 :eyes:

2 Likes

Hello @damru, thank you for to blueprint!

m using RODRET Dimmer to control TRADFRI bulb, everything is working great, except for dimming down, anyisea why?

Absolutely amazing, Ikea Redret remote started working right away.
Thank you for making this happen.

@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!

1 Like

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?

It appears as tough the first click gets trough, but the second one is blocked when looking at the tracing.

UPDATE: It appears as tough the issue originates because the blueprint is configured in single automation mode.

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.

wait_for_trigger:
  - trigger: event
    event_type: zha_event
    event_data:
      device_id: '{{ remote_device }}'
      command: 'on'
      cluster_id: 6
      endpoint_id: 1
timeout:
  milliseconds: 2960
continue_on_timeout: true

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 :pray:t2:

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…