You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Controller - IKEA E2001/E2002 STYRBAR Remote control
Home Assistant Core Version
2024.12.5
Home Assistant Installation Type
Home Assistant Operating System
Description
When any two buttons are pressed within the double-press delay, the double-press action will trigger. Which double-press action triggers depends on which double-pressed actions are exposed and which is the second button pressed. Tested with E2001/2002, E1743, E1766, E1524/E1810.
Define action_button_*_short and action_button_*_double for left, right, up, down buttons. Eg. to set an input_text helper to the value of the variable trigger_action.
Set button_*_double_press to true for left, right, up, down buttons.
Expected behavior
When two different buttons are pressed within the helper_double_press_delay, ideally two different single press actions should be triggered. However, as the blueprint relies on restart mode to detect double-presses, only the second single press action should be triggered.
Double-press action should only be triggered if the same button is pressed within the helper_double_press_delay.
Actual Behaviour
Press any button then up button within the duration helper_double_press_delay. action_button_up_double will trigger. Same for any other combination of 2 buttons pressed - the double-press action associated with the second button will trigger.
Additional Details
I'd like to help developing a fix for this issue.
Screenshots
No response
Additional context
The issue seems to be with the logic for checking for virtual double-presses. First, the old state of the input_text helper is saved to variable last_controller_event, then the input_text is updated to the new trigger_action. Finally, the check for double-press uses the condition trigger_action | string in states(helper_last_controller_event). This effectively checks that trigger_action is in itself. Changing the condition to trigger_action | string == last_controller_event seems to reflect the intended logic correctly and results in the expected behaviour.
The text was updated successfully, but these errors were encountered:
Blueprint name
Controller - IKEA E2001/E2002 STYRBAR Remote control
Home Assistant Core Version
2024.12.5
Home Assistant Installation Type
Home Assistant Operating System
Description
When any two buttons are pressed within the double-press delay, the double-press action will trigger. Which double-press action triggers depends on which double-pressed actions are exposed and which is the second button pressed. Tested with E2001/2002, E1743, E1766, E1524/E1810.
Automation YAML config
To Reproduce
action_button_*_short
andaction_button_*_double
forleft
,right
,up
,down
buttons. Eg. to set aninput_text
helper to the value of the variabletrigger_action
.button_*_double_press
totrue
forleft
,right
,up
,down
buttons.Expected behavior
helper_double_press_delay
, ideally two different single press actions should be triggered. However, as the blueprint relies onrestart
mode to detect double-presses, only the second single press action should be triggered.helper_double_press_delay
.Actual Behaviour
Press any button then
up
button within the durationhelper_double_press_delay
.action_button_up_double
will trigger. Same for any other combination of 2 buttons pressed - the double-press action associated with the second button will trigger.Additional Details
Screenshots
No response
Additional context
The issue seems to be with the logic for checking for virtual double-presses. First, the old state of the
input_text
helper is saved to variablelast_controller_event
, then theinput_text
is updated to the newtrigger_action
. Finally, the check for double-press uses the conditiontrigger_action | string in states(helper_last_controller_event)
. This effectively checks thattrigger_action
is in itself. Changing the condition totrigger_action | string == last_controller_event
seems to reflect the intended logic correctly and results in the expected behaviour.The text was updated successfully, but these errors were encountered: