🎮 ZHA, deCONZ, Zigbee2MQTT - Ikea E1743 On/Off Switch & Dimmer Universal blueprint - all actions + double click events - control lights, media players and more with Hooks

Blueprints Exchange
, , , ,
149

Hi @Vanessa
Have you tried this version of the blueprint?
awesome-ha-blueprints/blueprints/controllers/ikea_e1743/ikea_e1743.yaml at main · lsismeiro/awesome-ha-blueprints (github.com)

We do have an issue open ( E1743 long press still doesn’t work with latest pull · Issue #4 · lsismeiro/awesome-ha-blueprints (github.com)) Re Long press but I am unable to verify it as I don’t have the device.

150

Yes, i tried the fork. Unfortunately still unsuccessful.

151

It turns out I have an E1743 :laughing:

I will test this and get back to you!!

1 Like
152

Seeing the same issue, Please check the issue I linked above and will continue there.

1 Like
153

Hey everyone!

Thanks to SandaleZ and Rofo.

I finally read this topic to the end and with your help I managed to get this blueprint to work with ZHA with IKEA E1743 button.

  1. The code needs to be edited:

config/blueprints/automation/EPMatt/ikea_e1743.yaml

By file editor

Afterwords create a new text helper by UI and extent the maximum letters to 255

At the end, refresh your automation.

For me it was lines between 216 - 228

    zha:
      button_up_short:
      - 'on'
      button_up_long:
      - move_with_on_off_MoveMode.Up_83
      button_up_release:
      - stop_with_on_off
      button_down_short:
      - 'off'
      button_down_long:
      - move_MoveMode.Down_83_0_0
      button_down_release:
      - stop_with_on_off
  1. I also had to edit the code below in the same file as recommended by Rofo
    For me it was lines between 287-293
    trigger_delta: '{{ (as_timestamp(now()) - ((states(helper_last_controller_event)
      | from_json).t if helper_last_controller_event is not none and (states(helper_last_controller_event)
      | regex_match("^\{((\"a\":\".*\"|\"t\":\d+\.\d+)(,)?){2}\}$")) else as_timestamp("1970-01-01
      00:00:00"))) * 1000 }}'
    last_controller_event: '{{ (states(helper_last_controller_event) | from_json).a
      if helper_last_controller_event is not none and (states(helper_last_controller_event)
      | regex_match("^\{((\"a\":\".*\"|\"t\":\d+\.\d+)(,)?){2}\}$")) else "" }}'
155

Hey @Hari_Hari

These work, thank you!
Will contribute these to GitHub - lsismeiro/awesome-ha-blueprints: A curated collection of automation blueprints for Home Assistant. with credit to you

Update ikea_e1743.yaml - change actions by LewisSpring · Pull Request #5 · lsismeiro/awesome-ha-blueprints (github.com)

cc @Vanessa

Please test if possible by importing and switching your automations: raw.githubusercontent.com/lsismeiro/awesome-ha-blueprints/69707d91de11a3317d9276216e3c28c4f2e95f41/blueprints/controllers/ikea_e1743/ikea_e1743.yaml

1 Like
156

Hey @LewisSpring

I downloaded your blueprint and ran my automation on it. Everything works great. Single, double and long presses work perfectly.

157

Sweet. I will look at merging this now :slight_smile:

1 Like
158

@LewisSpring Thanks for this plugin! I have a question. I got 3 GU10 LEDs together in one light.

  • How do I set this blueprint so it fades while holding (long press)? I’ve tried setting loop until release, but it causes the lights actions to jam. Probably because Zigbee2MQTT cant handle the massive loops.
159

Hi @viezevis

You should set up the Hook Blueprint alongside your controller blueprint, ensuring that the hold and press actions won’t clash.

Hope that helps

PS: If you want to override or supplement a hook action, like “up single click”, it might work to add a 10ms or so delay and then your action; and they’ll work together.

160

Just a note for anyone looking for support from me with ZHA specifically going forward, I have now moved to Zigbee2MQTT. I intend to keep my old coordinator that I can do ZHA specific tests with if needed. :slight_smile:

2 Likes
161

Ah, I’ve missed that. Is there like an instruction to basically set the default settings of IKEA into the controller and Light Hook Blueprint?

On and Off is working perfect. But once I start dimming the light it just turns off, no matter how long I ‘long hold’ the button down. Theres no ‘fast stop’. Do I have to setup something in the controller for Up/Down Up button long press?

(Optional) Up button long press - loop until release = off
Maximum loop repeats = 250 (default, but I tried 3 also)
Minimum brightness = 3 (tried in light-specific Z2M config)

In logs I can see it keeps spamming anyways. Hope theres some documentation about this? Or can you help me out? :smiley:

162

EPMatt’s documentation should help you with this: Awesome HA Blueprints | Awesome HA Blueprints (epmatt.github.io)

There could be a conflict with the controller automation and the hook - if you are using the hook, you don’t need to use the Loop until release settings.

To begin with, you should:

  1. Start with a blank Controller automation and configure it with your remote entities.
  2. Add your Light hook automation, configure it with your remote entities and target light
  3. Test and see if the dimming and power controls work fine.
163

What you describe is basically what I did based on documentation. Thats probably why I messed a little with the settings without needed to.

  1. I setup a Controller with no other configurations then Controller Entity and Last Controller Event. In Z2M I can see On/Of/Brightness Up/Down events.

  2. I installed the Light Hook. Set te device + entity, controller module and set the light group which to control.

  3. When testing, on/off works fine. Dimming works, but the dimming does not stop whatsoever. If I dim the lights, it keeps dimming untill its off somehow.

I can upload a video?

164

Im seeing the same behaviour while trying to setup my Ikea Styrbar remote and Ikea 1100 lumen colour temp bulbs. Loading the controller and light hook automations works fine for on and off but brightness results in a loop of the command until an short button up or down command which is evident in the z2m logs. It’s as if it needs a “stop” command when releasing the long press.

1 Like
165

Yep. I see that I basically can ‘dim’ the light and by pushing the on-button the dimming stops at a certain point. But thats not how it should work.

166

Can you confirm that you are using the latest blueprint from lsismeiro 's repository?

Just want to make sure, this seems like something that’s now been fixed.

I have checked this myself using the latest from there and am not experiencing the same issue as yourself.

1 Like
167

To keep on topic for this thread you are best to ask here:

:video_game: ZHA, deCONZ, Zigbee2MQTT - IKEA E2001/E2002 STYRBAR Remote control Universal blueprint - all actions + double click events - control lights, media players and more with Hooks - Blueprints Exchange - Home Assistant Community (home-assistant.io)

My advice is the same as the above comment

168

Hoooo shiittt. This indeed did the trick. Damn! Good job. I was using the old EPMATTs one.

1 Like
169

@epmatt my config sometimes doesn’t work and i have no idea what the reason is.
for me it seems it has to do with the helper-state, but not sure where this “wrong” state comes from.

image
image2722×1346 327 KB

id: '1705691991633'
alias: 'Taster (IKEA): Wohnzimmer:  wechselt Szenen & schaltet TV'
description: ''
use_blueprint:
  path: EPMatt/ikea_e1743.yaml
  input:
    integration: Zigbee2MQTT
    controller_entity: sensor.schalter_dimmer_wohnzimmer_action
    action_button_up_short:
      - service: script.scene_toggle_wohnzimmer
        metadata: {}
        data: {}
    action_button_down_short:
      - service: scene.turn_on
        metadata: {}
        target:
          entity_id: scene.wohnzimmer_lichter_aus
    helper_last_controller_event: input_text.taster_ikea_wohnzimmer_last_controller_event
    helper_debounce_delay: 50
    action_button_up_long:
      - service: switch.toggle
        metadata: {}
        data: {}
        target:
          device_id: 48a288eff61e88051d30284943a87360