Okay I started with HA, 3 to 4 years ago, and a lot has changed since then
I’ve decided using what I’ve learned I want to start from scratch. However this gives me a few issues.
Firstly I want to finish up with the same fixed IP, when all is done, but I want to migrate one room at a time, so as I migrate devices most of which use a fixed IP for the MQTT server. I assume I can use a local DNS for this.
Secondly I have 4 years of Temperature/Power Usage data that I would like to migrate accross, is it possible to migrate just this data.
I just migrated HA from a RPI4 to a Beelink SER3 Mini PC a few days ago. I took a full snapshot before from the RPI4, newly installed Debian 11 and HA on the Beelink and restored that snapshot onto the new installation.
The whole procedure took me no longer than 1 hour: HA all back to as it was before (incl. the Logbook), no hazzle at all.
And yes, local IP-addresses are best assigned through the Address Reservation page of the router.
How do you exactly define “from scratch”? You can choose what exactly to restore from a Backup (formerly Snapshot).
As I described above the underlying OS on the Mini PC including certain applications (i.e. SSH Server, Mosquitto, Samba Server) were installed from scratch using the latest OS/Software.
Also Home Assistant Supervised was installed from scratch. I personally chose to restore all formerly installed Add-Ons, Automations, Scripts, Scenes, Z2M configs and therelike. But as said, you can individually choose what exactly to restore.
Really it’s just historical data I want to restore. Didn’t realise that I could pick and choose, I’ll have to have a play, worst case I’ll have to re-install a few times
Yup, you’ll see: Basically it’s a walk in the park
If it really just the Hisory you want to preserve (and reuse) look for the file “home-assistant_v2.db” inside the config-folder. It’s a SQL-file (SQLlite) which holds all Logbook/History. Just make sure you shutdown HA before you backup it. Otherwise it can get corrupted and unusable.
