ESPHOME Feature Request

[Antasp3136]

Not sure if there is where to put this or if others have requested this. It would be cool to see a Version history feature in the ESPHOME add on for homeassistant that allows you to roll back to a previous version of a config if it fails for some reason without having to manually go to a backup and restore the yaml file or do a backup restore. Just have a version history option on the config file and when you click it, it will ask if you want to restore and flash the pervious config to the device.

[Edwin_D]

It is certainly useful to have version history. But that is not limited to esphome, it also is useful for other configuration files such as your entire Home Assistant configuration.

That is why many people use version control systems such as GIT to keep version history of all config files, including esphome yaml files needed to do what you want.

I use github (many do, it is where Home Assistant stores all source including history). It allows you to see exactly what you changed, when and why. You can start doing this right now.

[Antasp3136]

Interesting, did not know about this. Do you have a direct link on how to get this setup?

[Edwin_D]

There are many online guides, pick one you like. If you use the Studio Code addon to edit your config, there are plugins to assist you - the a guide based on that is preferrable.

There is a guide here on the forum, but it seems outdated, and using Stidio Code with Github is much simpler:

Sharing your configuration on GitHub

This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that. Sharing and regularly syncing your Home Assistant configuration to GitHub has several benefits: A remote copy of your Home Assistant YAML files in case you need to recover. A documented history of your changes for troubleshooting purposes. It will help the Home Assistant community learn from your configuration examples. …

Sharing is optional, you can make a private repository.

[Cake1468]

Thanks for the lead on this. I have a question if I may, does running the example script or a similar script to update keep UI changes current in GitHub? I think the answer is yes, but just wanted to verify.

Edit- I think also dashboards wouldn’t have a version history, unless you included the .json versions from the storage directory right?

[Edwin_D]

Personally, I manually check in changes with a description so I know what I changed. I guess you could run a script to do it automatically, but then you’ll mis the information about what change is what.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Hello

@Antasp3136

Not sure if there is where to put this or if others have requested this

This is the place: ESPHome Feature Requests
This post will not be seen here by people that chould help and searching there would tell you if there is already a request that you could thumbs-up or contribute to.

[Cake1468]

Thanks. I’ll have to experiment with the process. My experience with git is pretty much limited to git clone, and some basic PRs via the web interface.

[tom_l]

Closing as not a core feature request.

@Sir_Goodenough

This is the place: ESPHome Feature Requests