Hi,
I’m a big fan of HomeAssistant, after evaluating a lot of other options I’m stuck here for >3 years.
My current setup contains a git managed directory with docker-compose & configuration files. My instance is hosted in my private network (only), but has a valid certificate by using a customized jwilder nginx proxy setup.
For xmas vacations I planned to cleanup my configuration from all the trial, error & did not persue projects by reinstalling from scratch. Here are a couple of thoughts / questions:
- I’m attracted by the devops idea of ‘rebuild from scratch’ regulary
- I was planning to use the “include_dir_merge_list” to structure my automations etc by function
- Like others I’m struggeling to keep up with the high change (deprecation) rate of HomeAssistant. Its a curse and a mercy at the same time
So - I do see multiple ways forward that I’ll not persue
- Move to supervised as that seems to be ‘the new shit to go for’. However, docker-compose (actually fedora 34 with podman) is my way forward for reasons out of scope here.
- I could stick with my old instance - however when re-staring from scratch I found the UI contains elements that my old instance doesn’t have. Also some integrations that changed a lot (denonavr) and never really work seem to integrate better on a fresh instance.
What’s a proper way of configuration management?
- The oldstyle yaml definition & backup gave me some rest of mind - however today there is a lot of UI based definitions that I’d miss out
- I can still (git) backup my config & volumes - however that’s NOT permitting a regular ‘start from scratch’
- backup / restore would be in the middle - but I don’t see that option in the new version, probably because its not running in hass.io or supervised?
How are others handling this - and to be very clear - moving away from HA is not an option at all!
ItsMee
1 post - 1 participant