Thanks for the info, very helpful
I was able to stop and remove the hassio services and stop the containers. for now I just renamed the hassio folder into hassio.die
added the homeassistant:stable into my docker-compose and started it.
first time when it run it asked me to create new username, I ignored it and stopped the new instance of ha and moved the content from my old home assistant folder to the new, but that did not work, ha would show the login screen and wouldn’t pass that even if you create a new user. so I removed the new instance and deleted the ha folder and recreated the container, this time I created a user and continued with a setup as I was setting up fresh, when all is well, I stopped the container and copied my old ha config folder (including subfolders, hacs) to the new instance. Then I started the container.
It seem to work, but only partially,
- all the integrations I had is gone,
- it shows Homekit integration already setup but somehow my iPhone home app still looking for old setup. on the ha side it shows the pin code (that tells me its not connected to HomeKit). Looks like I have to remove my current pairing on the HomeKit from my iPhone home app and try connect with this new pin, for some reason my mind tells me I am going to have the same situation like before not connecting to HomeKit.
Even though I coped every file and folder from the homeassistant folder to the new instance, why am I not getting my old setup? any help.