I have a question about the efficiency of a couple of different approaches to structuring your automations in general. If one has a several triggers (or events) that do something like turn a light, is there any difference to creating an automation for each light that uses all the triggers for that light, or have automations for each trigger that turn on the lights in each automation.
I use a mix of both methods, so I’m curious if one approach is better performance wise or for any other reason really. I’m thinking that the same events are fired on the bus either way in the end so it shouldn’t make a difference but that’s just a not so educated hunch based on my limited knowledge of how HA works.
I don’t think it makes a difference either way tbh, as you say an event occurs and homeassistant determines a reaction. Whether that event was one of seven triggers in one automation, or the only trigger in one of seven automations makes no difference.
My personal preference is that one automation is one moving part, seven automations is seven moving parts and one moving part is ‘more efficient’ because there are fewer potential breaking points.
I disagree with the notion others have that seven automations are easier to manage. For a start, a well written single automation is less code. It’s also all in one place. However, it’s also personal choice and all of our minds work in slightly different ways, so what I consider to be ‘easy to manage’ may not correlate with others.
I’m more or less in the same boat as @anon43302295, I tend to try to keep it all in one automation and when I want to make it more “readable” than the UI allows using things like Choose, etc, I just write a script and have the automation fire the script instead of trying to squeeze it all into the UI.