-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Comments
Edited outside to conform more to the template. (I think it slipped through because of it) |
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. |
👎 issue is still there in latest version |
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. |
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
Anything in the logs that might be useful for us?
No response
Additional information
The text was updated successfully, but these errors were encountered: