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

Did you also bind the levelCtrl?
I have this working for me.

I did it like this. I want to control an Ikea 30W LED Controller

You’re doing it wrong you are binding the state of the lamp - > rodret.
But you have to do it the other way around.
State of the rodret - > lamp.

I hope this is clear.

Fix for flickering dimming

If you experience visible flickering between the dimming steps while holding on of the buttons, there is a fix.
@damru I kindly ask you to consider integrating this in your blueprint.

Fix

Use the transition functionality within the light_on-change brightness.

Simply set the transition time to 0.2 and the brightness percentage to 3 and remove the delay block.

This results in a fast and smooth dimming.

Hi,

Would it be possible to paste the script here? Thanks

Hey

Thanks for the suggestions :bulb:
I removed the transition some times back but I’ll re-add it with the same value as the delay, this should smoothen the transition for lights that support it.
I’m considering removing the delay at once, but I have to run some tests as for the moment:

  • it loops too fast so the light “goes back to random %” instead of going to 1%
  • sometimes it even becomes an endless loop as it’s never triggering the end-loop condition
  • I dont find it good practice to spam actions to HA and the network
  • if HA is not blocking the script for the “transition” time (specialy for lights that dont support it), this would be a blocker

I’m reworking this and will post an update once I’m done (at least with the transition).

Now, if you have more questions/remarks, please use the related topic instead of this one :pray:

Thanks all for such a prompt responses and help!

First: yes, definitely, I used a wrong blueprint. I installed this one, while the other one (IKEA RODRET Dimmer + SOMRIG Remotes - ZHA/Z2M - Control Light) would fit my needs better.
I was just confused with names and didn’t notice that the last word is different :slight_smile:

Anyways, for my purposes direct binding remote to the group of lights worked better - basically offering the same experience as when it was just a connection w/o HA.

Next I’m going to purchase few more ikea remotes and use the “control light” blueprint to control other, non-ikea lights around the house.

This method worked for me when nothing else did. Pairing near another Ikea router was the key, I think. Thank you!

I have z2m + mqtt running and one somrig and 2 rodrets.
With z2m v2.0 the blueprint says no device found


Would be great to get some advice

edit:
I edited the blueprint and removed the filter and could manually select my rodret.

#         - integration: mqtt
#           manufacturer: IKEA
#           model: RODRET wireless dimmer/power switch (E2201)

image
Nevertheless the filter values are correct

hi, can you explain what you did?

regards

1 Like

I access the configuration/blueprint path and edited the yaml with a text editor:

Perfect.This works.

Tank you!

@damru With z2m in V2 the double press event is also broken. If I click once it is handled as a double click event. Both buttons affected.


Hi,

Thanks for pointing this out.
I did the change in the blueprint, this should be fixed now.

1 Like

Hey,

I tried with my Rodret + Z2M, and could not reproduce your issue.
Did you try lowering the Double press delay ?

1 Like

I will try again

Thanks a lot!
Just yesterday I had the problem, that the Ikea Rodret and the Ledvance mini switches I had just installed, were not accessible by the blueprints I had installed for them. In your blueprint, I was not able to select a device.
Since I am quite new to Z2M, and also new to these switches and to blueprints, I was not sure if this was a configuration problem, and in which part of home assistant.

Some minutes ago, I saw your posting, that you “did the change in the blueprint”, re-imported it, and now it is possible to select a device!

Thank you!

Hopefully the other blueprint for the Ledvance will also be updated to work with Zigbee2MQTT 2.0., I will see how to contact the author.

Single press is still recognized as a double press.
This seems to be a general problem:

The delay is on 300ms (also tested with 100ms) now.

this is that I get in the logs for a single press:

in zigbee2mqtt itself:


info 2025-01-06 09:53:48z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"on","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
info 2025-01-06 09:53:48z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
info 2025-01-06 09:53:48z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
info 2025-01-06 09:53:58z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"off","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
info 2025-01-06 09:53:58z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
info 2025-01-06 09:53:58z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'

in Home Assistant → Addons → z2m → log

[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"on","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
[2025-01-06 09:53:47] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'on'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"off","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1', payload '{"action":"","battery":84,"identify":null,"linkquality":212,"update":{"installed_version":16777303,"latest_version":16777303,"state":"idle"},"update_available":false}'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'
[2025-01-06 09:53:56] e[32minfoe[39m: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Rodret1/action', payload 'off'

@damru looks like that the on action appears 6 times instead of just a single hit.

on the other side:

in the logbook the actions do not appear 6 times. They correctly reflected my button presses.

Can you check if you have some legacy option in your configuration.yaml ?
The behaviour on my end is correct.
I also already migrated the blueprint to the new device trigger specification (instead of using action button) a while back.
The only thing different from you that I can see is that I dont have the Action available anymore since migrating to Z2M v2.

1 Like


No “legacy” options in my configuration (also checked the yaml file)