If an automation cannot run by itself 100% of the time without being annoying, then users should be able to easily opt-in or out without violating any of the other rules
Conditions are key! I have my whole house go to night mode flawless every time and only when it should because there are enough conditions to make sure that it only happens when it is 100% sure. For example both sides of the bed occupied. Both phones charging. No guests in the house etc etc etc And for the time that the conditions are not met but I do want night mode on... It's a Boolean that I can manually turn on as well. Which only happens when my wife hasn't plugged her phone for some reason or another. So I agree with nuances...
Sounds like you got your automation down to a science 👍🏾 I’m curious how often you had to refine the automation’s conditions before you dialed it in to where it’s at now?
@@technithusiastI wish i had it down to a science! With complex automations like this I work the other way around. Before i put my automation in production I make the automation triggers and conditions without the Action. Instead I make a permanent notification in HA. This gives me the time to refine and make sure "it just works". When it does... It's production aka automagic.
My night time automation is based on my setting my smart watch to sleep tracking so there is never a chance of falsely triggering it. In the morning when I stop the sleep tracking it also triggers more actions.
