-
Notifications
You must be signed in to change notification settings - Fork 119
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
Configure actions on labels #949
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I'd still really like this feature. I hope it gets considered. |
There's a similar open request for sensors by label. Implementing both would be ideal. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I'd still like to see this. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
@nielsfaber Would you mind pinning this or rejecting the request? |
This is probably simpler to implement than my request for the sensors. I might give a try implementing this one when I get some time |
I'll just go ahead and bump this now before the bot gets to it. :D |
Is this request specifically for being able to select labels/areas via the UI (dropdown menus)? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I would also be interested in trigger some automation or other entities and not only switch devices. It would be also helpful to change the "services" to "actions" (according to HA 2024.8) And over all...thanks for this great tool! |
Checklist
Proposal
I would like to be able to select labels (or areas, etc) when configuring actions, rather than only entities.
Ideally, the actions should support any of the targeting modes for services.
Additional info
This works in an action to trigger a single light to turn on full red, then flash for a while:
However, to do the same for multiple lights, I would need to a) create two more service calls for each one, or b) create a script and trigger that. Either option is excessively complicated.
Instead, it would be preferable to use something this:
These list items work as expected in the service dev tool, so presumably it's just a matter of having Alarmo pass along the
target
field (and not breaking the yaml when loading the UI view, which happens now.)This would make Alarmo actions a lot easier to set up without making a bunch of extra scripts.
The text was updated successfully, but these errors were encountered: