Hi I tried to use your blueprint but the long press action doesn’t work. I’m using the Zigbee2MQTT integration. Firstly I tried to change brightness of my lightbulbs but later on I just tried to use the long action to just turn it on, nothing worked. In the history of the automation I can see that it triggers when I make the long press but as was said nothing happens. (the short action works fine)
Hi @Flagun,
I’m sorry for what you’re experiencing with this blueprint.
Could you please provide the YAML for the automation you are having issues with?
Thank you!
description: ''
use_blueprint:
path: EPMatt/ikea_e1743.yaml
input:
integration: Zigbee2MQTT
controller_entity: sensor.0x000d6ffffee470bb_action
action_button_up_long:
- type: brightness_increase
device_id: 8634008f52261c1542dba301757e4c62
entity_id: light.living_room
domain: light
button_up_long_loop: false
action_button_up_short:
- type: turn_on
device_id: 8634008f52261c1542dba301757e4c62
entity_id: light.living_room
domain: light
brightness_pct: 10
flash: short
action_button_down_short:
- type: turn_off
device_id: 8634008f52261c1542dba301757e4c62
entity_id: light.living_room
domain: light
action_button_down_long:
- type: brightness_decrease
device_id: 8634008f52261c1542dba301757e4c62
entity_id: light.living_room
domain: light
button_down_long_loop: false
action_button_down_release: []
Here you go
Hi @Flagun, sorry for my late response.
Thank you for posting. The automation config looks good to me.
Do you notice any entries related to this blueprint in the Home Assistant logs?
Moreover, to check that this is not an issue with the light integration, could you please check if the following configuration for the action_button_up_long input works as expected?
action_button_up_long:
- service: persistent_notification.create
data:
message: up long action
This should create a web notification in the Home Assistant frontend whenever the up button is long pressed.
Thank you!
Hi
I tried to configure an automation with this blueprint - hoping that a double press on the off/down button could power off multiple bulbs.
The Automation code:
- id: '1617696315852'
alias: Indkørsel - sluk alt udelys (BP)
description: Dobbeltklik på sluk - slukker både indkørsel og fordør
use_blueprint:
path: EPMatt/ikea_e1743.yaml
input:
integration: deCONZ
controller_device: 289eff47b12c36ea2065aa727ea04beb
action_button_down_double:
- service: light.turn_off
target:
entity_id:
- light.outdoor_frontdoor
- light.outdoor_driveway
helper_double_press_delay: 2000
But for some reason the specified entities are not powered off ?
With the new trace tool in 2021.4.0, I see:
Not sure how to proceed from here …
Regards
Brian
Tried to add this:
action_button_down_double:
- service: persistent_notification.create
data:
message: Down double press
Gives no notification in WebUI on double press
Trying to add similar code for single press gives two notifications for single press (both clicks within 2 seconds)
I got two entries in the log:
Logger: homeassistant.components.automation.controller_ikea_e1743_on_off_switch_dimmer
Source: helpers/script.py:1156
Integration: Automatyzacja (documentation, issues)
First occurred: 2 kwietnia 2021, 22:19:36 (226 occurrences)
Last logged: 11:09:47
Controller - IKEA E1743 On/Off Switch & Dimmer: Choose at step 2: choice 5: Choose at step 1: choice 1: Error executing script. Invalid data for call_service at pos 1: not a valid value for dictionary value @ data['entity_id']
Controller - IKEA E1743 On/Off Switch & Dimmer: Choose at step 2: choice 5: Error executing script. Invalid data for choose at pos 1: not a valid value for dictionary value @ data['entity_id']
Controller - IKEA E1743 On/Off Switch & Dimmer: Error executing script. Invalid data for choose at pos 2: not a valid value for dictionary value @ data['entity_id']
Controller - IKEA E1743 On/Off Switch & Dimmer: Choose at step 2: choice 2: Choose at step 1: choice 1: Error executing script. Invalid data for call_service at pos 1: not a valid value for dictionary value @ data['entity_id']
Controller - IKEA E1743 On/Off Switch & Dimmer: Choose at step 2: choice 2: Error executing script. Invalid data for choose at pos 1: not a valid value for dictionary value @ data['entity_id']
Logger: homeassistant.components.automation.controller_ikea_e1743_on_off_switch_dimmer
Source: components/automation/__init__.py:416
Integration: Automatyzacja (documentation, issues)
First occurred: 2 kwietnia 2021, 22:19:36 (76 occurrences)
Last logged: 11:09:47
Error while executing automation automation.controller_ikea_e1743_on_off_switch_dimmer: UndefinedError: 'trigger' is undefined
Error while executing automation automation.controller_ikea_e1743_on_off_switch_dimmer: not a valid value for dictionary value @ data['entity_id']
Hi @bipsen,
thank you for reporting here.
When using this blueprint with double press actions for any integration, you need to provide a valid input_text entity for the helper_last_controller_event input. You can read more about the reasons why this helper is required in the documentation.
Please let me know if adding the missing input solves your issue. 
Thanks!
Hi @Marek,
I’ve just noticed you’re using Zigbee2MQTT to integrate the controller with Home Assistant. This integration requires a valid input_text for the helper_last_controller_event input, as stated in the docs.
Please try to apply the fix I suggested in my previous reply, and let me know if it solves your issue. 
Thank you!
Hi
Defined a text_input as helper:
And did a re-config on the automation:
- id: '1617696315852'
alias: Indkørsel - sluk alt udelys (BP)
description: Dobbeltklik på sluk - slukker både indkørsel og fordør
use_blueprint:
path: EPMatt/ikea_e1743.yaml
input:
integration: deCONZ
controller_device: 289eff47b12c36ea2065aa727ea04beb
action_button_down_double:
- service: persistent_notification.create
data:
message: Down double press
- service: light.turn_off
target:
entity_id:
- light.outdoor_frontdoor
- light.outdoor_driveway
device_id:
- 921d1d63f8624beb3b0a26d3a98cb6a1
- 34031d1823f6b62f2d94ba9a5a2abfbc
helper_double_press_delay: 2000
action_button_down_short:
- service: persistent_notification.create
data:
message: Single click
helper_last_controller_event: input_text.btn_driveway
Still popping up as single press… Maybe not right type for the helper input ?
Hi @bipsen,
you also have to enable double press events by setting the button_down_double_press input to true.
This should solve your issue.
Should be done here - but not quite working yet:
- id: '1617696315852'
alias: Indkørsel - sluk alt udelys (BP)
description: Dobbeltklik på sluk - slukker både indkørsel og fordør
use_blueprint:
path: EPMatt/ikea_e1743.yaml
input:
integration: deCONZ
controller_device: 289eff47b12c36ea2065aa727ea04beb
action_button_down_double:
- service: persistent_notification.create
data:
message: Down double press
- service: light.turn_off
target:
entity_id:
- light.outdoor_frontdoor
- light.outdoor_driveway
device_id:
- 921d1d63f8624beb3b0a26d3a98cb6a1
- 34031d1823f6b62f2d94ba9a5a2abfbc
helper_double_press_delay: 3000
action_button_down_short:
- service: persistent_notification.create
data:
message: Single click
helper_last_controller_event: input_text.btn_driveway
button_down_double_press: true
But at least I don’t get 2 single click notifications any longer.
Hi @bipsen, thank you. The blueprint config should be fine now.
Are you now able to trigger the double press action by double clicking the down button?
Tried to pull the latest blueprint - but still no luck.
Trace from first press:
Trace from 2nd press:
Unfortunately the trace files cannot be attached here…
Hi @bipsen, thank you for the trace images.
It looks like the second press does not recognize the previous one was a down button short press, hence it executes the short press action.
What’s the state for the helper_last_controller_event text input immediately after pressing the button for the first time? You can check this on Developer Tools->States in the HA web interface.
Thank you!
Hi @bipsen,
sorry for my late response. I eventually found what was causing your issue: in detecting the double press action, a comparison between 2002 from the action_mapping variable, and '2002' from the text helper was made. The condition would always produce a falsy value when using deCONZ, since comparing a number and a string returns false.
I’ve just updated the blueprint with the fix. Please let me know if the automation now works as expected.
Moreover, I’d like to point out that the problem was present on the majority of controller blueprints. Your feedback helped to improve all of them as well, so thank you very much for reporting.
1 Like
Hi @epmatt
For some reason I still seem to have issues.
Should the helper be of type text or number ?
Tried to delete automation and blueprint, re-import blueprint and create automation again.
New automation code:
- id: '1618861271656'
alias: (BP) Switch off outdoor light on doubleclick
description: Switch off outdoor light on doubleclick
use_blueprint:
path: EPMatt/ikea_e1743.yaml
input:
integration: deCONZ
controller_device: 289eff47b12c36ea2065aa727ea04beb
action_button_down_double:
- service: persistent_notification.create
data:
message: double click
helper_last_controller_event: input_text.btn_driveway
helper_double_press_delay: 2000
button_down_double_press: true
Hi @bipsen,
sorry for my late response. I’ve opened a Pull Request which will hopefully solve this issue. I’m now waiting for confirmation that the problem is solved for the user who opened the linked issue on GitHub.
In the meantime, you can test PR changes by importing the following blueprint into your Home Assistant instance.
Thank you!
I get the double click notification now… Great 
1 Like