Basically the title. This seems to be the best way to do things as it keeps similar triggers and actions together, but am I sacrificing some performance/speed/reliability by doing it this way?
#Is there a downside to having multiple triggers and if-then statements in one automation
edgy nimbus
fresh tree
Technically it makes no difference. It's a stylistic choice, as multiple nested if: blocks or a choose: with many branches may be less easily interpretable.
strong cosmos
No percievable downsides. You get less automations and more modularity (e.g. in case you want to turn one such automation off instead of 6)