Hi,
i am currently trying to streamline my hand written automations for the new automations editor. I have a problem with the following error during startup:[state] is an invalid option for [automation]. Check: automation->trigger->0->state.
I donât know if this is articulated very well anywhere, but, the main idea is that Home Assistant isnât even at version 1.0 yet. Itâs being developed so fast, and components are being added so quickly, that occasionally breaking changes have to be made so that the system can be improved, or so that awkward designs arenât programmed into it for all eternity. Itâs the trade-off we have for having cutting edge features!
@zarthan The users of the platform are volunteering their time as well reporting bugs and debugging the code. Itâs not really a decent argument anyway for an open source platform. At some point you need to decide to lock down the core.
And thatâll happen nearer version 1.0. Until then itâs up to you to read the change log and the highlighted Breaking Changes section before you blindly update.
Running with a platform thatâs under heavy development isnât for everybody, but complaining that itâs under heavy development and that things change is like complaining that water is wet. If you donât like it, nobodyâs forcing you to use Home Assistant - though maybe itâs the only one out there that meets your needs