@pc-zookeeper wrote:
I’ve migrated my Home Assistant installation from the venv
(as another user) alternative install method, to the Docker recommended method. Prior to doing this, I did my research by scouring these forums and it seems the migration process is fairly straight forward:
- Build a new Home Assistant server on the new platform
- Start it up
- Shut it down
- Copy over all your config files from the previous server
- Start it up
- Profit!
Once the migration was complete and I started up my new server for step 5 above, I was missing a bunch of pieces that I think should have carried over.
- My configurations in the LoveLace UI are gone. I had to go back to my old server and copy the code from the Raw Config Editor and paste it into my new server to get my UI back
- My additional user (my wife) account is gone
- The Person entity for my wife is also gone (it was also linked to her logon account above)
- All configured rooms are gone
- Custom names for entities are gone
- Possible other items I’m forgetting that are not as important
Are these issues to be expected?
I’ve fixed the UI issues and the custom names for entities by hand so some of my automations that we depend on daily are functional. Though there are still lingering issues with those custom named entities working correctly. For example, my Hue bulbs follow the schedule/automations I have configured, but random bulbs won’t always change their state/color almost as if it was a communication issue between the bulb and the hub. This wasn’t an issue with the old server, and nothing has changed physical locations (including the server, both are virtualized on the same host) - they were working fine for over a year before the migration.
Some technical details:
- I’m using Home Assistant version 0.102.3 - I started the migration at 0.102.2 but the container has upgraded as I’ve been troubleshooting
- CentOS is my OS for both the old (CentOS 7 & venv) and new (CentOS 8 & Docker) server
- I’m using a MySQL DB on a separate server instead of the Home Assistant internal DB - the new server was granted access to the existing MySQL DB and is making an active connection
- I ensured file permissions were correct after transferring the config files to the new server prior to starting up
At this point I’m thinking of rebuilding from scratch, but am curious if anyone here has any suggestions to salvage my migration in its current state. The old server is still around and has not been modified, I could still perform another migration from the beginning if necessary.
Posts: 7
Participants: 4