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

Timeout after waiting for trigger returns 'null' in stead of the documented 'none'. #81781

Closed
lenwar opened this issue Nov 8, 2022 · 4 comments
Labels

Comments

@lenwar
Copy link

lenwar commented Nov 8, 2022

The problem

In an automation, I wait for an external trigger (response from an actionable notification in my case) with a time-out.
When the timeout has been reached it should provide the wait variable 'wait.trigger = none', it however returns 'wait.trigger = null'
https://www.home-assistant.io/docs/scripts/#wait-variable .

What version of Home Assistant Core has the issue?

core-2022.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Scripts

Link to integration documentation on our website

https://www.home-assistant.io/docs/scripts/

Diagnostics information

No response

Example YAML snippet

- wait_for_trigger:
    - platform: event
      event_type: mobile_app_notification_action
      event_data:
        action: '{{ action_uitzetten }}'
    - platform: event
      event_type: mobile_app_notification_action
      event_data:
        action: '{{ action_aanlaten }}'
    timeout:
      hours: 0
      minutes: 15
      seconds: 0
      milliseconds: 0
    continue_on_timeout: true
  - if:
    - condition: template
      value_template: '{{ wait.trigger != none }}'
    then:
    - choose:
      - conditions:
        - condition: template
          value_template: '{{ wait.trigger.event.data.action == action_uitzetten }}'
        sequence:
        - service: light.turn_off
          data:
            transition: 2
          target:
            device_id:
            - d99XXXXXXXXXXXXXXXXXXXXXXXXXX870
            - acdXXXXXXXXXXXXXXXXXXXXXXXXXX848
        - service: notify.gezin
          data:
            message: clear_notification
            data:
              tag: '{{ action_tag }}'
      - conditions:
        - condition: template
          value_template: '{{ wait.trigger.event.data.action == action_aanlaten }}'
        sequence:
        - service: notify.gezin
          data:
            message: clear_notification
            data:
              tag: '{{ action_tag }}'
    else:
    - service: notify.gezin
      data:
        message: Geen reactie - De lichten in de woonkamer blijven aan
        title: Lichten in Woonkamer
        data:
          tag: '{{ action_tag }}'

Anything in the logs that might be useful for us?

No response

Additional information

Output

@lenwar lenwar changed the title Timeout after waiting for trigger returns 'null' in stead of the documented 'none' Timeout after waiting for trigger returns 'null' in stead of the documented 'none'. Dec 7, 2022
@lenwar
Copy link
Author

lenwar commented Dec 7, 2022

Edited outside to conform more to the template. (I think it slipped through because of it)

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@lenwar
Copy link
Author

lenwar commented Mar 10, 2023

👎 issue is still there in latest version

@github-actions github-actions bot removed the stale label Mar 10, 2023
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jul 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant