šŸŽ® ZHA, deCONZ, Zigbee2MQTT - IKEA E2001/E2002 STYRBAR Remote control Universal blueprint - all actions + double click events - control lights, media players and more with Hooks

Same issues here, using ZHA, getting those same, slightly odd event names. which differ from the ZHA event names if I listen to events.

Executed: July 19, 2022 at 4:06:46 PM
Result:
params:
  domain: input_text
  service: set_value
  service_data:
    entity_id: input_text.tradfri_4_button_living_text
    value:
      trigger_action: move_with_on_off_MoveMode.Up_83
      last_triggered: '2022-07-19 16:06:46.197476+01:00'
  target: {}
running_script: false
limit: 10
{
    "event_type": "zha_event",
    "data": {
        "device_ieee": "50:",
        "unique_id": "50:",
        "device_id": "6b47d2815d22ef",
        "endpoint_id": 1,
        "cluster_id": 8,
        "command": "move_with_on_off",
        "args": [
            0,
            83
        ],
        "params": {
            "move_mode": 0,
            "rate": 83
        }
    },
    "origin": "LOCAL",
    "time_fired": "2022-07-19T15:06:46.168223+00:00",
    "context": {
        "id": "01G8BFYK0R5F8XMY",
        "parent_id": null,
        "user_id": null
    }
}

This is the correct solution.
Iā€™m seeing the same issue with the left and right buttons too.

Hereā€™s a modified version of the blueprint with these fixes: ikea_e2001_e2002_modified.yaml (github.com)

Like I explained above, I solved the all the issues I had with my E2001/E2002 remote controller and is working as expected for all functions like single, double, press and hold. You didnā€™t add the release fix yet. I will try to share my code so it is more clear for everyone.

1 Like

Iā€™m going to work on a pull request very soon. Iā€™ll add the release action fixes too. Bug - Ikea E2002 Styrbar Brightness/Up,Down Hold action doesn't work Ā· Issue #399 Ā· EPMatt/awesome-ha-blueprints Ā· GitHub

3 Likes

Great blueprint! Works great for the most part, except double-clicks on the brightness (up and down) do not work, they just seem to get registered as single clicks.

Correction: I was wrong, double-clicks do work, I just have to pace myself. Double-clicking like I do on the mouse seems to be too fast for a double-click to register, I have to have a longer delays between the clicks for the double-click to register.

Double-clicks on left/right work as expected (even when clicking fast, like on a mouse).

I struggle to set this up with z2m. My E2002 does not expose a action entity? Do I need to this up somehow?

I just have the device and 5 entities for battery and updates :confused:

Is it the Helper Entity you need help setting up? Check here:
Controllers-Hooks Ecosystem | Awesome HA Blueprints.


Thanks, I needed to set this checkbox so the action entities became available.

Now the blueprint works quite nice, but I did not get the double click working yet.
Is this helper entity setup correctly?

Also I did not figure out how to combine the hook with the blueprint. I could get the hook working but then it was using like a standard mapping of the controller, however I want to map the buttons myself.

The hook offers some nice functionality like the smooth turn on though, which I would love to use with the blueprint. I am a bit confused why one would need both the hook and blueprint, for me it seems they replace each other?

Iā€™ve no experience with Zigbee2MQTT, I canā€™t speak for the configuration of that side.
Your helper looks fine though.

Iā€™ve used both the Hook and the Controller automations together. I just added a small delay before the action in the Controller automation so that itā€™s an override. Iā€™m aware itā€™s not the cleanest of solutions, Iā€™m happy to be told thereā€™s a better way! It does work though.

thanks, can you please elaborate on how to combine hook and controller?

Thanks for this great blueprint!

Is there a way to shorten the long press hold time, i.e. the amount of time you need to long press the buttons before they trigger the action? Right now the hold time seems to be about 4 seconds, which seems kind of long.

Actually, playing around with the blueprint a bit more, it shows some very strange behaviours with long presses. When I long press the left button, it triggers properly, but takes about 4 seconds. But when I long press the right button, it takes only about 2-3 seconds, but triggers both the intended target device, as well as another device with a similar name (intended target is ā€œbasement stairs lightsā€, but it also affects ā€œbasement lightsā€). When I long press the down button, nothing happens.

Hi, I think the suggestions and fixes that I made were not yet merged. I have the controller blueprint working as expected after I made several corrections. Just download the file from here ikea_e2001_e2002.zip, unzip it and put it on the config folder under the path blueprints/automation/EPMatt, you better save the existing file before. Regards, Luis Sismeiro

1 Like

Hi, Iā€™m replying to myself because I just verified the current blueprint available and there was a change regarding the helper size optimization. I made the necessary changes and there is now a new file for download with my same fixes that are in the previously file. Here is the link to download ikea_e2001_e2002-v02.zip, same instructions apply. Regards, Luis Sismeiro

2 Likes

Sorry if this has been discussed before. I have two of these buttons which I have been using the controller automation (and hook) with. Both behave strangely, but not in the same way.

Button 1 controls a single IKEA White light lightbulb. Firstly, Whenever I come home and want to turn it on, I seem to have to ā€œwake it upā€ before it turns on, like I have to press up once or twice, or even long press it, to turn it on. Itā€™s also very sluggish when changing the white light tone using the right and left buttons, but.I can live with that. The main problem is dimming. Whenever I long press up it dims to 100%, and long press down to 100%, no matter when I release the button. Iā€™ve tried different settings in the controller automation for looping but I canā€™t get it to function properly.

Button 2 controls a chandelier with 6 Livarno Home RGB lightbulbs. And its just whacky. Sometimes (especially if I make somewhat quick button presses) the lightbulbs seem to loose sync with each other. Dimming a little results in four out of six lights dimming, leaving two shining brightly, or reverse, dimming down to 5% turns three lightbulbs off. I can usually still use double click to call a scene where all 6 lights shine bright white, but the odd desync often still remains when I do something further.

I guess Im asking for any help or ideas for any of these issues.

Do you experience issues with other Zigbee devices? It could be your coordinator. Check battery levels and signal strength (RSSI) on the Controllerā€™s device in HASS.


Try using the following blueprint: it contains fixes for hold presses made by @Isismeiro. When you try the revised blueprint, make sure you disable your old Controller Hook Automation to avoid conflicts. (This also means youā€™ll use the default parameters, which is reccomended)
ikea_e2001_e2002_luis.yaml (github.com)


Try using a group if possible. If the lightbulbs recieve the commands at different times, they will become desynced.


This might be due to the ā€œSmooth Power Offā€ setting in your Hook automation.

Hope this helps!

The problem is unfortunately not fixed for me for the E2002 version. The release number is random every time, e.g my left release was just 2336, and my right release waas 7264. If I do it again these numbers completely change, sometimes they are negative

Can we somehow modify the blueprint to only look for the ā€œreleaseā€ word and ignore if it has something after it? The values are different on every single release

Your reply is in relation for an older version of improvements - try the latest iteration by @lsismeiro ikea_e2001_e2002_luis.yaml Ā· GitHub

Dear @LewisSpring first of all thanks for great blueprint.

however I have questions. I use long press button to increase/decrease light intensity, but the speed is too fast. how it can be slow down?
maybe it is worth considering adding the next parameter, which will allow us to specify the delay in repetitions of the long press loop.

greetings
Wojtek Z.

You might be able to add delays after the brightness changes, but you would be better off using the Hook for light entities

Itā€™ll be a lot more responsive. It will take away your up and down single press actions though.

You can disable the left and right actions inside the hook automation to free up those buttons.