Ryan6338
(Ryan)
September 11, 2024, 3:08am
1
I’ve been trying to figure out if it’s possible to use multiple trigger inputs in a blueprint. Below is working code for a single trigger. I cannot find a way to use the second trigger since reading a trigger input puts the trigger dict it into a list. I have tried using templates to extract the dict and make a list with both triggers but I haven’t been able to get it to work - I believe due to the restricted templates in triggers. Is it possible to use multiple input triggers in a blueprint?
blueprint:
name: example multi-trigger
domain: automation
input:
on_button_trigger:
name: On Button Trigger
selector:
trigger:
off_button_trigger:
name: On Button Trigger
selector:
trigger:
trigger: !input on_button_trigger
action:
karwosts
(karwosts)
September 11, 2024, 3:35am
2
If you wait there is a new feature added for next month that allows for this:
home-assistant:dev
← karwosts:nestable-trigger-list
opened 04:08PM - 18 May 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
The user of Trigger Selectors in blueprints currently has a significant limitation in that the selector returns a list of triggers, but there is no yaml syntax to merge a list of triggers from the selector with a list of triggers hardcoded in the blueprint.
So if a blueprint wants to trigger on some predefined behavior, it cannot allow user to configure additional triggers with a selector because the lists cannot be merged.
To mitigate this, I propose a syntax (under ~platform: trigger~ `triggers:`) for triggers which will allow for combining a list of triggers from an input with a hardcoded list of triggers. When the backend encounters this list, it will just be flattened into a single list of triggers.
E.g.:
```yaml
blueprint:
name: Nested Trigger Blueprint
domain: automation
input:
usertrigger:
selector:
trigger:
trigger:
- platform: time_pattern
seconds: /10
- triggers: !input usertrigger
condition: []
action: []
```
This can trigger the blueprint on the predefined time pattern, in addition to any triggers specified by the user.
I'm sure there's still more work to be done here with testing, but wanted to see if this idea has merit. It worked for me as a basic proof of concept.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue:
fixes #106706
fixes https://github.com/home-assistant/frontend/issues/19050
- This PR is related to issue:
https://community.home-assistant.io/t/merge-trigger-selector-with-other-triggers/655399
https://community.home-assistant.io/t/help-using-the-new-trigger-selector-2023-12-in-blueprint/653107
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
https://github.com/home-assistant/home-assistant.io/pull/34404
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
You will be able to write:
trigger:
- triggers: !input on_button_trigger
- triggers: !input off_button_trigger
1 Like