Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug - Automation delay step cancels when (Optional) Expose up button double press event or (Optional) Expose down button double press event are on #616

Open
1 task
atrain2009 opened this issue Oct 3, 2024 · 7 comments
Labels
blueprint An issue related to a blueprint bug Something isn't working

Comments

@atrain2009
Copy link

Blueprint name

Controller - IKEA E1766 TRÅDFRI Open/Close Remote

Home Assistant Core Version

2024.10.0

Home Assistant Installation Type

Home Assistant Container

Description

The automations for two of my IKEA TRADFRI E1766 remotes cancel after a delay when I have either "Optional) Expose up button double press event" or "Optional) Expose down button double press event" toggled on. I'm not sure why, since I use the same blueprint for another IKEA TRADFRI E1766 remote that works fine, but those two remotes seem to get stuck at a delay built to check the Double Press Delay during the automation - when I check the Trace for the delay, I see "done: false", which seems to cancel the automation. I find that the automation completes successfully once I toggle "Optional) Expose up button double press event" and "Optional) Expose down button double press event" off.

Automation YAML config

alias: IKEA Desk Remote - E1766 TRÅDFRI Open/Close Remote
description: ""
use_blueprint:
  path: EPMatt/ikea_e1766.yaml
  input:
    integration: Zigbee2MQTT
    controller_entity: sensor.ikea_remote_desk_action
    action_button_up_short:
      - action: scene.create
        metadata: {}
        data:
          scene_id: desk_window_revert
          snapshot_entities:
            - cover.blinds_desk
      - if:
          - condition: state
            entity_id: timer.tamper_lock_desk_down
            state: active
        then:
          - action: switch.toggle
            metadata: {}
            data: {}
            target:
              entity_id: switch.buzzer
          - action: cover.stop_cover
            metadata: {}
            data: {}
            target:
              device_id: 29a333085a757dc7543fa3ed613ea110
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.desk_window_revert
        else:
          - action: cover.open_cover
            data: {}
            target:
              device_id: 29a333085a757dc7543fa3ed613ea110
          - action: timer.start
            metadata: {}
            data: {}
            target:
              entity_id: timer.tamper_lock_desk_up
    action_button_down_short:
      - action: scene.create
        metadata: {}
        data:
          scene_id: desk_window_revert
          snapshot_entities:
            - cover.blinds_desk
      - if:
          - condition: state
            entity_id: timer.tamper_lock_desk_up
            state: active
        then:
          - action: switch.toggle
            metadata: {}
            data: {}
            target:
              entity_id: switch.buzzer
          - action: cover.stop_cover
            metadata: {}
            data: {}
            target:
              device_id: 29a333085a757dc7543fa3ed613ea110
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.desk_window_revert
        else:
          - action: cover.close_cover
            data: {}
            target:
              device_id: 29a333085a757dc7543fa3ed613ea110
          - action: timer.start
            metadata: {}
            data: {}
            target:
              entity_id: timer.tamper_lock_desk_down
    helper_last_controller_event: input_text.helper_last_controller_event_back
    action_button_up_double:
      - action: cover.open_cover
        data: {}
        target:
          device_id:
            - fe90be58cced7f98bd28b66310097b94
            - 29a333085a757dc7543fa3ed613ea110
    action_button_down_double:
      - action: script.assess_side_blinds_for_ac_on_close
        data: {}
    button_up_double_press: true
    button_down_double_press: true
    action_button_up_release: []
    action_button_down_release: []
    helper_double_press_delay: 1000
    helper_debounce_delay: 0

To Reproduce

Unsure exactly how to reproduce considering one of my remotes works fine, but this happens when I press up or down on either of my other IKEA E1766 remotes. I check the trace for when my helper changes to include "open" or "close" in the trigger action and see that the automation cancels after a delay that is part of a default action within a choose action.

Expected behavior

The automation continues after the delay.

Actual Behaviour

The automation cancels at the delay.

Additional Details

  • I'd like to help developing a fix for this issue.

Screenshots

I've included a screenshot of the Trace log to help show where the automation fails.
Screenshot 2024-10-03 124326

Additional context

No response

@atrain2009 atrain2009 added blueprint An issue related to a blueprint bug Something isn't working labels Oct 3, 2024
@blackthornedk
Copy link

I seem to have a similar issue with my E1743 blueprint: two automations use it, one have 'Expose up/down button double press event' enabled, and does not work after 2024.10, and the other have it disabled, and works fine.
I'll get more logs when I'm back home and can test the automations again.

@MelindaJaphines
Copy link

I'm having similar issue where automations actions are being "stopped because of unknown reason". My Ikea E1743 blueprint is not executing most actions because it seems to kill the actions.
image

@MelindaJaphines
Copy link

Is it possible this has something to do with the blueprint run mode? Modifying the run mode to "Parallel" instead of the default "Restart" seems to fix this issue.

@atrain2009
Copy link
Author

Can you change the run mode without Taking Control of the blueprint? I'm not seeing an option to change the mode like I do with my non-blueprint automations.

@MelindaJaphines
Copy link

I don't think so, I took control of the blueprint to convert it to a regular automation. This allowed me to modify it.

@patvdleer
Copy link

I'm having similar issue where automations actions are being "stopped because of unknown reason". My Ikea E1743 blueprint is not executing most actions because it seems to kill the actions.

I'm having similar issues with the E1812 blueprint ever since the 2024.10 Hass update, since I use it every night as a "shut down the house" button I fairly sure that's the point when it stopped working.

@MadWalnut
Copy link

I'm having similar issues with the E1812 blueprint ever since the 2024.10 Hass update, since I use it every night as a "shut down the house" button I fairly sure that's the point when it stopped working.

I can also confirm this time frame. A few weeks ago my E2001/E2002 triggered actions started aborting at the first delay step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blueprint An issue related to a blueprint bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants