🔁 ZHA, deCONZ, Zigbee2MQTT - IKEA E2001/E2002 STYRBAR Remote control Universal blueprint (Redux)

Blueprints Exchange
22

Should this work as a dimmer with a long press? I cannot get it working. It dims only one step and thats it. For the same button is also registered toggle light command. Enabling loop doesn’t make it any better.

23

Grab the Light Hook automation, it’s designed alongside the Controller automation and provide dimming and such.
Hope that helps

1 Like
24

Hey, thank you for the hook. The only problem is that if I long press up or down for about 1 second and then let go the light continues to increase/decrease brightness until it is fully on/off.
What am I doing wrong?

And what is the technical explanation for the automation not supporting continuous dimming? If I add an action to “Down button long press” to step brightness by -10% and enable “(Optional) Down button long press - loop until release” in the automation this should work, shouldn’t it?

25

You can do dimming in the Remote blueprint - I have done it before by adding a small delay after the dim action but the Hook is preferred.

Make sure your Remote blueprint does not have actions that conflict with the Light Hook. And make sure you are using the latest lsismeiro version as well as this is a bug that was fixed previously.

Welcome and hope that helps.

26

I have the same problem as xnor. Everything works fine, except for the “long press down”. When I do that, my lights keep dimming until they’re fully off. What’s odd is that “long press up” does work, and stops increasing brightness when I let go of the button 
 It’s just the “long press down” that seems to repeat 


27

The only workaround I can offer is to start dimming by holding button up (or down) and releasing it. When you are satisfied with the brightness, click button up (not down) to stop auto dimming.

I can’t get colors up and running though. I have recent versions of light hook and button blueprints.

28

When I enable double click in remote hook l, single click doesn’t work on light hook. Is it possible to turn on single light using light hook and turn all the lights on the room by double click using remote hook?

29

Hi and Welcome.

Are you using the Light Hook or just the Controller blueprint on it’s own?
(and from this repo GitHub - lsismeiro/awesome-ha-blueprints: A curated collection of automation blueprints for Home Assistant.)

If you are still having issues it would be good if you could raise an issue there.

Thanks!

(edit please also see end section of next comment for a bit of info)

30

Hi and Welcome!

You should be able to use the Double Click action alongside the single click of the Light Hook - just make sure the Controller blueprint Single Click action is empty.
Here are some tips from Drublin from an older issue:

  • did you enable the switches “(Optional) Expose up button double press event” ?
  • i increased the “(Optional) Helper - Double Press delay” to 900ms. (but it works also with default 500ms).
  • a usual fast “mouse-like” double click does not work on my remote neither. Try slower clicks, with a pause in between.

In regards to the press and hold issue, appears you are having the same issue as @DuncanDoyle.
We have had a ticket before about this but it appeared they were using the old EPMatt Blueprint and was encountering a bug that has since been fixed.

31

My “action” sensor has just disappeared for my Styrbar remote. It is visible in the Zigbee2MQTT GUI, but does not appear in HA, which (of course) breaks this blueprint. I’m trying to figure out what has happened; most likely a result of upgrading to HA 2024.12 and/or Z2M 1.42.0-2.

Have anyone else run into this problem?

32

It turned out that I had added:

advanced:
  homeassistant_legacy_triggers: false

to my Z2M configuration.yaml in preparation for Z2M migration to 2.0. This was what caused the breakage.

So consider this a heads-up – when Z2M switches to version 2.0 early next year, this Blueprint will not work. I’ll see if I can figure out how this is supposed to work without the “legacy triggers”


33

Im using the Styrbar E2002 with ikea lights. ZHA. I can turn the light on and off. Change color. But long press only moves one step. Then nothing. Whats missing?

34

Hi - we are disussing this here Z2M legacy triggers are being deprecated · Issue #26 · lsismeiro/awesome-ha-blueprints · GitHub

35

Hi - please can you send a copy of the automations you are using?

Thanks

36

These ?
alias: FjÀrr Spottar Kök Controller
description: “”
use_blueprint:
path: lsismeiro/ikea_e2001_e2002.yaml
input:
integration: ZHA
controller_device: 71b3ad522417991a00ed069d187047d5
helper_last_controller_event: input_text.helper_last_controller_event
button_up_long_loop: false
button_down_long_loop: false

alias: FjÀrr Spottar Kök Hook
description: “”
use_blueprint:
path: EPMatt/light.yaml
input:
controller_device: 71b3ad522417991a00ed069d187047d5
controller_model: IKEA E2001/E2002 STYRBAR Remote control
light: light.spottar_kok
light_color_mode: Color Temperature
min_brightness: 12
on_brightness: 33
force_brightness: true

37

also forced brightness isnt working.

38

Thanks for the link. I’ve subscribed to the issue now.

39

I don’t understand. How do I add multiple STYRBAR controller to modify the same light with this?

40

Hi Lewis, thanks for keeping this blueprint updated! The AwesomeHA blueprints are a key part of my setup and are still super useful after 3 years. Using them with ZHA.

Recently I dug deeper into the blueprint. As I understand the logic, on line 409, the trigger_action variable is set to the new action that was received when the Styrbar is pressed. Then in line 412, the previous action stored in the input_text helper is loaded onto the last_controller_event variable. In line 414, the input_text is then overridden with the new trigger_action.

I’d like to understand why the logic for checking virtual double-presses is like this (eg. in line 428 but it is the same for all buttons):

conditions: '{{ trigger_action | string in states(helper_last_controller_event) and trigger_delta | int <= helper_double_press_delay | int }}'

states(helper_last_controller_event) would return the value of the input_helper, but that value was updated to the latest trigger_action in line 414. So the first part of the condition will always return true right?

I’ve tried this version instead in my setup as it seems to reflect the intent of the double press logic better, and it seems to work correctly:

conditions: '{{ trigger_action | string == last_controller_event and trigger_delta | int <= helper_double_press_delay | int }}'

Do you think this modification is correct, or I am misunderstanding the logic? I am also not sure how this change would affect all scenarios under which the blueprint could be used, but it fits my use case. Also the issue may also exist in other blueprints that use the same condition for virtual double presses.

41

Hi @LewisSpring, if I add

homeassistant: legacy_action_sensor: true
to the zigbee config file as per Zigbee2MQTT 2.0.0 breaking changes · Koenkk/zigbee2mqtt · Discussion #24198 · GitHub
Do you think the blueprint will continue to work after I upgrade to zigbee2mqtt 2.0.0?

1 Like