Thank you very much for your response. Iām fairly new here and experimenting with HA a lot. How do I create a zigbee group? And what is the difference between the groups behind the āgroupsā folder, the groups you can create yourself in HA and zigbee groups? Sorry but I canāt follow anymore!! 
Thank you for your response;
Setting up ZigBee groups is done through ZHA, Zigbee2MQTT or deconz - you didnāt say which you use. For ZHA you go to Settings > Devices & Services, then locate the ZHA integration, click on Configure menu, and select Groups tab where you can then create new groups.
The main difference between the two, I think, is that ZigBee devices know they belong to a ZigBee Group, and will respond to any messages sent to that group, whereas with Home Assistant Groups separate messages are sent to each device in the group. This can lead to lights coming on at slightly different times - something Iāve heard as the popcorn effect.
Iām not sure if there are any downsides to ZigBee groups. Probably a bit harder to troubleshoot. In general I use ZigBee groups when I can.
Checking in here, and also canāt get double click for up/down working.The rest of the buttons work perfectly!
From what I see, the up/down button triggers donāt get repeated in ZHA, unlike the left/right buttons.
Hi there, please see these posts.
Thanks for the tips - I am indeed using the latest blueprint but just canāt double press to trigger on the Top and Bottom buttons. In the logbook they just register as only one press. The left and right double presses work perfectly.
Sorry for the obvious question: Is the toggle switch for double press turned on?
What Firmware version is your Styrbar? You can find it under the device via the Settings > Devices & Services > ZHA Integration ā Devices > {Remote}.
I am running Firmware 0x00010024 with no issues (with the Double Press Down, at least.)
You might need to set up ZHA Firmware Updates to upgrade.
Also make sure your signal strengths are strong, and your Zigbee stick is separated from the host device (using USB extensions) and WiFi Access Points.
Thanks for the tip! The double press switch toggle is turned on. Signal strength is strong with no issues on double press on the left and right buttons.
Iām also running a later 2.4.5 firmware (which was manually installed, see here Ikea Styrbar Force OTA if on V1.0.024). The double press wasnāt working on 1.024 firmware either.
Try going to developer tools > events and in the bottom input box type āzha_eventā then hit the start listening button.
Press the button once, make note of the data, do a double press and make note of the data.
Compare them. If they are equal then your remote might be at fault. If they are different then remote is OK and itās most likely the blueprint 
Thanks for sharing. Based on this, zha_event captures 2 successive clicks on the Left and Right buttons, but captures only 1 click on the Top and Down buttons, even when I clicked twice.
So not sure whatās at fault here - the remote, the quirk, or the blueprintā¦
Hmm. It would appear that my presses are all the Same aswell. No difference between single and double press in terms of whatās picked up.
Are you using any debounce in your BP? The last setting when setting up the BP. I have it at 100 millis
My debounce is set at 0, setting to 100 is no-go too. zha_event doesnāt register top/bottom clicks twice.
Well it would seem that my remote works as yours. There is no other event fired based on single/double click.
yet my BP with double-tap works but I canāt hit the buttons to fast then double-click wont register.
Since the code is not picking up any special codes but seems to rely on timing and the last_press helper Iād advise you to use the debounce at 100 and try to find the right timing between your presses.
@borez
The timing can be a bit precise at times, and often itās slower than you think.
Using a stopwatch might help you get used to it; that helped for me.
Thanks all! I did manage to get double presses to work - and yes, the timing needs to be precise.
Itās a bit too slow for my taste (almost 0.5-0.75s delay between presses), and I often get accidental single clicks.
No worries!
I think itās just how it is unfortunately. The hardware doesnāt support double clicks - itās all being done in software, so any delays caused by interference, CPU load, cosmic radiation can trip it up. I think thatās why the delay needs to be so high.
I share your problems!
Thank you so much for this. It fixed my issues with the Ikea e2001 / e2002.
Thanks for creating this blueprint.
I installed the latest version from @lsismeiro (dropbox), figured out the double click delay and debounce on the up button. Works beautifully.
Then I enabled double left and right click, which seemed to have broken single left/right click 
Can anyone reproduce/fix?
Is it possible in some way to toggle through a few preset color settings with this blueprint?
I would like to assign click-up to on/2700K/x%brightness and if already on toggle between that setting and 4200K/100%Brightness.
It would also be nice to be able to use left/right to toggle between around 10 preset colors/brightness settingsā¦
I saw there is a link in documentation to Hook - Light blueprint, but I donāt really understand how to use it or what it doesā¦ and in itās comments it looks to have issues with Styrbar E2001, E2002ā¦
I use a list of colors and step through in a similar way. I think a list of āprofilesā will do the trick for you. (You create a list in your version of āhomeassistant.local:8123/config/helpersā). For your first issue, simply have a list of two profiles (and make sure you set ācycle: trueāā¦)
action_button_right_short:
- service: input_select.select_next
data:
cycle: true
target:
entity_id: input_select.janyc_light_color
- service: light.turn_on
data:
color_name: "{{ states('input_select.janyc_light_color') }}"
target:
entity_id: light.janyc_roof
action_button_left_short:
- service: input_select.select_previus
data:
cycle: true
target:
entity_id: input_select.janyc_light_color
- service: light.turn_on
data:
color_name: "{{ states('input_select.janyc_light_color') }}"
target:
entity_id: light.janyc_roof
hmmmā¦I see there is some opportunityā¦but I donāt really understandā¦
Profiles looks to be one csv-file )light_profiles.csv in the config folder that is supposed to have a header with the info used, e.g. profile,color_x,color_y,brightness,transition
One profile entry can be marked as default by adding ā.defaultā after the profile name
ā¦but how to handle it with profiles for several lights or as if I want one list with two color temperatures and another list with a set of colorsā¦?
Those color profiles, isnāt that something else than using helpers?
If using helpers, what kind of helper is that? Text or dropdown or which one to select.
In your example, does input_select.janyc_light_color refer to the helper and light.janyc_roof to the entity?
Feels like Iām close to the solution nowā¦might have to buy some toys soon and start testingā¦(but too much else going on now, so might have to wait 2 weeksā¦even though it will be difficultā¦)