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
The title pretty much sums it up, as does the YAML test case I'm attaching.
I am able to use wait_for_trigger in scripts and in automations to wait for an event using the "event" platform. But the same exact code fails when it's in the action block of a trigger-based template sensor; given a timeout, it simply times out despite the event occurring.
What version of Home Assistant Core has the issue?
core-2025.1.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
I am actually not sure what integration is responsible for the action blocks; there is no "this" object and no entity that I can find that corresponds to the action block, as opposed to individual sensors.
The problem
The title pretty much sums it up, as does the YAML test case I'm attaching.
I am able to use wait_for_trigger in scripts and in automations to wait for an event using the "event" platform. But the same exact code fails when it's in the action block of a trigger-based template sensor; given a timeout, it simply times out despite the event occurring.
What version of Home Assistant Core has the issue?
core-2025.1.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
I am actually not sure what integration is responsible for the action blocks; there is no "this" object and no entity that I can find that corresponds to the action block, as opposed to individual sensors.
Link to integration documentation on our website
https://www.home-assistant.io/docs/scripts/#wait-for-a-trigger
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
I am happy to provide further information. What I've put here is my best attempt to tersely and precisely describe the issue.
The text was updated successfully, but these errors were encountered: