Not sure how that would conflict with anything… Maybe a schedule? Then just add an override toggle helper that you check in your schedule.
I feel like you’re trying to use it in your specific way. Instead of using home assistant as intended. Sure that’s a valid criticism for your use cases. But it doesn’t make home assistant objectively terrible imho.
You can either directly disable an automation e.g. automation.turn_off: ... or set/read the state of a helper entity that you use to disable certain functionality in another automation. There are probably more tricks too. Though I try to make my automations as atomic as possible so they don’t need to be connected this way.
Not sure how that would conflict with anything… Maybe a schedule? Then just add an override toggle helper that you check in your schedule.
I feel like you’re trying to use it in your specific way. Instead of using home assistant as intended. Sure that’s a valid criticism for your use cases. But it doesn’t make home assistant objectively terrible imho.
How do you build controls to toggle automations as you described?
You can either directly disable an automation e.g.
automation.turn_off: ...or set/read the state of a helper entity that you use to disable certain functionality in another automation. There are probably more tricks too. Though I try to make my automations as atomic as possible so they don’t need to be connected this way.