-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Add id to automation triggers #48464
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
Conversation
Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with an integration ( |
if "trigger" in variables and "id" in variables["trigger"]: | ||
trigger_path = f"trigger/{variables['trigger']['id']}" | ||
else: | ||
trigger_path = "trigger" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note; this is a breaking change and requires a frontend update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In what cases do we not have a trigger_Id? It's making things quite complicated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the automation is force started from the frontend it was not triggered by any of the triggers
Proposed change
Add a
trigger_id
to theautomation_info
dict and update all triggers to loop that back in the trigger variables.Most device_trigger don't need to be updated as they use an
event
,numeric_state
orstate
trigger under the hood.Type of change
Example entry for
configuration.yaml
:# Example configuration.yaml
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: