It would be interesting to have some sort of version management for automations, scenes and scripts. I don’t think it needs a lot of explanation but I think it could help people creating automations, etc. In the proces of creating or optimizing automations, etc. this could help reverting back to a workable situation. It doesn’t have to be as extensive as Git with approval mechanisms, but a rather “simplified” version that keeps track of the changes would be nice. I think it would also be fun to see how your skills and how some automations have improved or evolved over time.
I absolutely agree.
I came here assuming someone had written some github integration already, but seemingly not.
The backup system already allows some possibility to go back in time.
But even better would be that the user can assign a version number; and every version is kept saved.
This could be a manual action: the user decides this script is ready so she/he assigns it a new number.
Even better would be some automatical way: evaluate once a day if the automation changed more than 2 days ago. If yes this means it can be assigned a new number (i see some flaws but they can be solved)
The question would be how to code this; i’m not much of a coder; so we’d have to get up a decent analysis, then check with HA-devs if it’s something they’re interested in picking up; if not if it would be accepted if we find someone to code it.
I would already be happy if I could store automations in seperate files and still edit them from the UI, so I could use git properly on these files. But I think this isn’t a solution fitting all users, especially not ones who use Home Assistant only via UI.
Yes, this would be great! maybe a GIT Integration to use a personal repo for the scripts and automations to upload and version?
Versioning in HA is a game-changer that solves real home automation headaches. Right now, experimenting with automations and scripts means playing a risky game of duplicating, renaming, and manually managing versions. Imagine being able to try out a brilliant new idea and then effortlessly roll back to the version that was working far more reliably for the last year. No more lists cluttered up with “Kitchen Lights Motion V2” and “Kitchen Lights Motion V3”. No more second-guessing before deleting an old version or keeping disabled automations for years “just in case”. Native versioning would eliminate all this friction, giving users the confidence to innovate and experiment without the current manual management nightmare. HA is an automation platform after all…let’s automate it.
maybe we can get a connector to Visual Studio Code? maintining the code their via GitHub and “posting” the code to HA?