Power User wasn't referring to YAML gurus, but rather those who manage large-scale installations that you can't even begin to imagine.
These now-defunct automations weren't "YaMLed in," by the way, but were created some time ago via the regular UI and had been running for up to two years.
What was supposed to be experimental about that?
If you spent as much time on a property of that size as I do, you might also understand why I work almost exclusively on a lightweight Android tablet instead of using a bulky and relatively heavy laptop. Unfortunately, your Ctrl+F shortcut doesn't exist on tablets.
Yes, of course, nobody forced me to use Home Assistant, and nobody is forcing me to pay for Nabu Casa either.
Up until now, updates have always worked flawlessly.
Now, regarding the update to version 2.7.1 (translated from German):
"An automation, script, or template entity is using the any behavior option for triggers, which has been renamed to each. The old value will still work for now, but support for it will be removed in a future version.
To resolve this issue, open each affected automation or script in the editor and save it again. Home Assistant will automatically detect and update the deprecated option. Alternatively, you can directly edit your configuration files (e.g., automations.yaml) and change behavior: any to behavior: each.
Then restart Home Assistant."
The same applies to changing behavior: any to behavior: each.
Since the system automatically repairs automations as soon as you open them, they could have offered a "Fix all" button instead of expecting paying users with large installations to spend 1-2 days manually opening one automation after another so the system can update them individually, or struggling with YAML.
I simply expect user-friendly solutions like "Fix all" to be offered, because it's completely unacceptable that my smart home keeps me busy instead of providing convenience.
I'm now simply going to revert to the last backup to be able to use the automations again, because I don't have time to spend two days clicking through all the automations, especially since the "great update" isn't even able to tell me exactly which automations are affected.
I will definitely not update again until a corresponding "Fix all" option is available. Without it, my installation will remain at a version < 2.7.1, which also means that it makes no sense for me to continue financing the further development of the project with my paid subscription, in which I can no longer participate.
