I want to use a plug that I previously used for other things for christmas lightning, and then go back to using it for the same other thing when Christmas is done. But in the meantime, I don’t want it to be affected by it’s usual automations.
On the device page, I should be able to toggle this device’ inclusion in all automations tied to it respectively. It should just affect the specific device, not disable the full automation.
You can create a helper called “Christmas Mode” and toggle it on an off during the Christmas season (or automatically via a schedule). Then in the automation you check the mode before performing the action.
A bit more of an advanced solution (that doesn’t require checking in every automation) would be to create a “Template Light” that checks the mode. So, each time you run light.turn_on on the “Template Light” it would automatically check the helper toggle (or even check the date) and respond accordingly. Then you could use the “Template Light” anywhere you want to only run the automation during a certain season.
Yeah, of course there’s workarounds. But it shouldn’t be that hard.
It really is exactly what you want.
If you want a toggle on the device page then that makes no sense for every other switch.
If you want to make it even simpler then just add a condition if it’s between dates and it will toggle automatic.
No, it is not, because this creates clutter/editing of each automation which is not relevant for the automation 11/12 of the time - and this was just an example of a use case.
Depending on how this was built, it could also be used to simplify buidling a “guest mode” without having to include a condition in all automations.
But if you don’t see the need, you don’t have to vote!
Adding a toggle to the device page makes it cluttered and if this condition is not listed in the actual automation then the automation will make no sense when debugging it.
There´s a switch in the device page that is not listed in the automation but still makes the automation behave differently than the automation is coded.
Yeah… that will help usability.
It should obviously be grayed out or similar in the automation editor. Not a hurdle that is impossible to overcome.
Wouldn’t that be the same as adding the condition that would just clutter?
And make it greyed out to make it even more confusing?