Well this finally explains a couple of occasions recently where all my automations were disabled. At least I now have a course of action to fix it (though it’s a pain to edit over 100 automations spread across dozens of yaml files)
My main question though, is how did this not rate “breaking change”? It certainly broke things here!
I appreciate the dedication to making things load previous state, that’s a big positive. Future note though, the behaviour I think most people expect is:
- obey initial state if defined
- if no initial state is defined, load previous state
- if no initial state is defined, and unable to load previous state, default to on. (as opposed to what it does now which is default to off)
This behaviour would ensure priority given to manual initial state definitions and previous states, but would behave as people are used to if those fail.