What about tools for migrating away from YAML? I’d love to use the new UI based zones editor, but I don’t feel like spending my time manually entering all my 35 YAML zones into the editor because at that point, the zone editor is creating more work than it reduces. Why not allow a one time import to switch over to the UI?
Also, I don’t feel that just adding .storage into a Git repository really solves the primary use cases of those of us using Git repositories
These use cases for me are the following:
-
Sharing. I like to share parts of my config with others, and with YAML, I can easily show exactly what I’ve created to others. I don’t believe .storage provides the same benefits. What is the strategy for sharing configurations with others in a UI based world?
-
Revision tracking. With YAML, I can easily go back and look as far as I want and see how I was doing something previously in a readable and understandable format. So if I want to go roll back just that part because it worked better or because I broke something, it’s an easy copy paste to get it back. The same is true of if I break something and hass won’t start. I can fix the config without hass needing to be running first. Putting things in the UI increases the chances that something will get broken that can’t be fixed because we have the chicken and egg scenario that hass needs to be running to fix it but it won’t start up.
Even as a backup mechanism in a git repo, .storage is pretty much useless, because I can’t really just copy part of it back into my active .storage folder and expect it to work. Restoring is an all or nothing proposition, so it provides no benefit over supervisor snapshots. If one fails, the other almost definitely will too. That was not the case with YAML, where I could copy only part of my config back over.