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?
I think you’re mistaking with this other blueprint IKEA RODRET Dimmer + SOMRIG Remotes - ZHA/Z2M - Control Light ?
This one does nothing to the lights, you have to implement it yourself.
The other one, however, does handle a light. The steps are 5% brightness every 0.1s until 1%
The fact that it sometimes go to 0% is because the template does not pick up the correct brightness in real time. I’m trying to fix that but I’m not sure I can as it’s probably related to the entity refresh rate.
Also, it will probably never be as smooth as direct ZigBee connection because of the extra processing time within HA.
1 Like
Hi,
First of all thank you for this blueprint is very helpful.
What Sergey means is that when the lights are dimming, the process is not smooth like when you would connect an ikea light directly to the RODRET switch, but when the lights are getting dimmed, you can see every dimm step.
I have modified the blueprint to dimm it 1% for every step, and it’s still not smooth but rather noticeable.
Do you know if there is a way to dim the lights and not notice a sudden increase in the brightness? I am using the ligh control bluepring
@Serega and @iamnewtoautomations and all others that not know this.
You can connect the rodret directly to hass/z2mqtt AND directly to the desired lamp.
You have to link them in de config minder bindings.
Example for z2mqtt
Did you also bind the levelCtrl?
I have this working for me.
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 
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 
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
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)
Nevertheless the filter values are correct
hi, can you explain what you did?
regards
1 Like
