IKEA RODRET Dimmer + SOMRIG Remotes - ZHA/Z2M - Control Light

IKEA RODRET & SOMRIG - Control Light (ZHA/Z2M)

Hello people.

This is a lighter version of IKEA RODRET Dimmer + SOMRIG Remotes - ZHA/Z2M - Control anything.
This blueprint will allow you to control a light with an IKEA RODRET Dimmer (On/Off remote + dimming) or IKEA SOMRIG via ZHA or Zigbee2MQTT.

:bulb: Features

This blueprint provides the following actions:

  • :arrow_down_small: Press “on” button to turn on a light
  • :arrow_double_down: Press “off” button to turn off a light
  • :arrows_counterclockwise: Hold “on” button to increase the brightness
  • :arrows_counterclockwise: Hold “off” button to decrease the brightness, down to 1%

:blue_book: Blueprint v2

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

(deprecated) v1 without Somrig support and with old trigger syntax

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

:page_facing_up: Check the code

v1 (deprecated) :eyes:
v2 (contains v1 for history as well) :new:

:notebook: Changelog

v2.1.0

  • chore: use new yaml syntax
  • fix: turn off in control_light for zha e2201 by @leahoswald
  • feat(CL): increase dimming step delay from 0.05s to 0.1s

v2.0.0

  • :bomb: 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.
  • feat: add IKEA SOMRIG support
  • chore: change syntax from platform to trigger
  • chore(z2m): move from mqtt topic to device action
History

v1.1

  • Add Zigbee2MQTT support :mosquito: with 2 new options:
    • (Zigbee2MQTT) Remote Name: specify your device name as shown in Z2M
    • (Zigbee2MQTT) Base mqtt topic: Z2M topic. Defaulted to zigbee2mqtt
  • Minor enhancements

v1.0

  • First version of this automation featuring the following actions:
    • press on button to turn on the light
    • press off button to turn off the light
    • hold on button to increase the brightness
    • hold off button to decrease the brightness down to 1%
12 Likes

Hmmm, it’s not working for me, is there anything I can do to help troubleshoot? I’ve imported the blueprint, I am able to select the Rodret dimmer remote which paired with HA (via ZHA), I have used an existing hue light which I already know is working via existing hue remote controls or manual HA control.

I am just trying to do some more troubleshooting currently.

I’ve tried deleting the switch in HA, resetting, re-pairing the device and trying to control different lights but nothing helps :(.

Hey,
Did you check the automation history? To see if it’s triggered properly.

No it’s not triggered sadly when I press the selected IKEA remote buttons.

1 Like

I have just updated to the latest HA (only around a month newer), still the same. Here is my debug output, how does it compare to yours please? It seems to match up with your code. Perhaps this one is faulty there is always that I guess… I have another I will try.

Thanks

  "data": {
    "ieee": "**REDACTED**",
    "nwk": 35107,
    "manufacturer": "IKEA of Sweden",
    "model": "RODRET Dimmer",
    "name": "IKEA of Sweden RODRET Dimmer",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "manufacturer_code": 4476,
    "power_source": "Battery or Unknown",
    "lqi": 65,
    "rssi": null,
    "last_seen": "2023-08-07T21:33:22",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4476, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0820",
          "input_clusters": [
            "0x0000",
            "0x0001",
            "0x0003",
            "0x0020",
            "0x1000",
            "0xfc7c"
          ],
          "output_clusters": [
            "0x0003",
            "0x0004",
            "0x0006",
            "0x0008",
            "0x0019",
            "0x1000"
          ]
        }
      },
      "manufacturer": "IKEA of Sweden",
      "model": "RODRET Dimmer"
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "button.ikea_of_sweden_rodret_dimmer_identify",
        "name": "IKEA of Sweden RODRET Dimmer"
      },
      {
        "entity_id": "sensor.ikea_of_sweden_rodret_dimmer_battery",
        "name": "IKEA of Sweden RODRET Dimmer"
      }
    ],
    "neighbors": [],
    "routes": [],
    "endpoint_names": [
      {
        "name": "NON_COLOR_CONTROLLER"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "***REMOVED***",
    "area_id": null,
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "NON_COLOR_CONTROLLER",
          "id": 2080
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "IKEA of Sweden"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "RODRET Dimmer"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 200
              },
              "0x0020": {
                "attribute_name": "battery_voltage",
                "value": 16
              }
            },
            "unsupported_attributes": {}
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0020": {
            "endpoint_attribute": "poll_control",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x1000": {
            "endpoint_attribute": "lightlink",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0xfc7c": {
            "endpoint_attribute": "manufacturer_specific",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0004": {
            "endpoint_attribute": "groups",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0006": {
            "endpoint_attribute": "on_off",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0008": {
            "endpoint_attribute": "level",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x1000": {
            "endpoint_attribute": "lightlink",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}
1 Like

Hi,

Since the last core update it now works for me (I had the same issue as you).
You should check !

2 Likes

Thanks. I just paired the other one today and all is working great straight away so thanks so much for this blueprint. It works great and the kids are very happy now.

There was an immediate difference in the pairing process. I’ll try the existing one in a minute after resetting it again. (press 4 times quickly on reset button - wait for flashy red light show - for anyone reading)…

Edit. Yeah the first one I tried still doesn’t work. Stuck on the configuring stage but shows up as a normal added device etc. I am going to guess it’s a faulty device.

Edit 2. I preserved and done the classic, or at least my classic ZigBee reset of pressing the buttons loads and also holding it down for luck sometimes and by some miracle it managed to fully pair this time. Seems like quite a “sticky” device for resets / pairing perhaps? With this first one it didn’t need resetting to pair out of the box but the 2nd one did. HA was updated to a couple of months newer version between so that doesn’t help conclude where the issue was.

3 Likes

Hey people,

New release with Z2M support is here :sparkles:

Check the :blue_book: first post to download the blueprint

@damru : THANK YOU.

If I can assist improving Documentation, UX/UI … just let me know by pm/pn. “I’m the normal one.”

Credits to Simon42 (German !!!):

Simon gave me the final kick in my … to leave ZHA and jump over the cliff to Zigbee2MQTT.

I went with ZHA due to the name and the expectation that ZHA would prosper and integrate better in HASSIO. Mistake … Big Mistake.

Zigbee2MQTT is by far best choice.

@damru
How does your Hold on / Off selections look like on yours?
I tried different things and nothing seems to happen when I hold down the on and off button on my RODRET.

The same goes for the double and triple click :confused:

The pairing went fine and it looks like correctly exposed in Z2M.
But so far I have only been able to get the turn on and off feature to work.

Thanks for this. Love the simplicity. I would LOVE it though if you could choose the color temp too. I want the on function to always turn to a set brightness, and set temp (not the last color used)

Thanks for this! Generally it’s working fine for me, but there is a bug.
If I press the off button while my light is off, the light will turn on. Pressing the off button again will do nothing. I then have to press the on button before the off button will turn off the light.
It’s not a big problem for me because I know it, but guests could be confused if they accidentally turn on the light using the off button.

Hi @all,

first thank you for the great work.
Is it possible to integrate deCONZ integration?

I can only find Blueprints with ZHA or Z2M support …

Many thanks

New release of the blueprint is here.
The code is now available in github.

v2.0.0

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

:blue_book: Import the blueprint from first message

@damru great work! Only problem I’m having is when holding off button, it is dimming directly to 1% and dimming up goes very fast. Possible to slow down dimming speed? Using somrig.

Hey,

I increased the timing between 2 steps from 0.05s to 0.1s. With the 5% brightness step, it should take ~2sec from 100% to 1%.
I could have exposed these 2 parameters, but I’d prefer to keep this blueprint as simple as possible.
If you want more flexibility, you could check my other blueprint IKEA RODRET Dimmer + SOMRIG Remotes - ZHA/Z2M - Control anything

v2.1.0

  • chore: use new yaml syntax
  • fix: turn off in control_light for zha e2201 by @leahoswald
  • feat(CL): increase dimming step delay from 0.05s to 0.1s

:blue_book: Import blueprint from first message

Thank you, this helped.

When holding down off button, dimming down starts but does not stop when releasing the button like it does when dimming up. I have to press down button again for it to stop. Is this on purpose?

This should not happen. What integration are you using: ZHA or Zigbee2MQTT ?

I’m using ZHA