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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add trigger service to template #48630
Conversation
Removed milestone and moving the bug fix to new PR. |
0ad1e59
to
1eb3741
Compare
As a user, it would be nice if this could be rolled into Could we at least support |
Right now hitting |
6bcd386
to
caa365e
Compare
Actually, thinking about it a bit more, I am not quite sure what is being proposed here. Can you provide a use case? It seems a bit odd for me to support variables in the forced trigger when those are not available to normal triggers but I guess you have something in mind?
I don't think it should set unavailable; that value is user controlled. Just treat |
Just like we pass variables to scripts, you would pass variables to the rendering method. It could be a way to have an automation conditionally update an entity. |
Sure, I understand what the feature does ... just not when that would actually be needed. We shouldn't add features just because they are easy to implement, they should preferably be useful too ;-)
So I guess that I am now suggesting to drop this PR entirely and instead support |
We can revisit in future |
Breaking change
Proposed change
Add a new service to manually trigger a trigger-based template entity with ability to pass variables.
Also fixes a bug for trigger-based entities without a unique IDBug fix extracted to #48631Type 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: