search

Poeschl-HomeAssistant-Addons / repository

The Home Assistant Add-on repository of Poeschl
Apache License 2.0
11 stars 2 forks source link

How to migrate from Poeschl/Hassio-Addons to Poeschl-HomeAssistant-Addons/repository? #3

Open shalak opened 3 weeks ago

shalak commented 3 weeks ago

I cannot remove the https://github.com/Poeschl/Hassio-Addons repository, because there are add-ons that are in use.

image

Is there a way to migrate to https://github.com/Poeschl-HomeAssistant-Addons/repository without removing all installed add-ons and configuring everything from scratch?

Poeschl commented 3 weeks ago

Unfortunately I don't know a migration way.

But it is possible to have the legacy and the new one installed side-by-side to migrate the configuration over.

JanPetterMG commented 1 week ago

Not necessarily! I can't even start the new addon in paralell because of conflicting port numbers. Changing those will definitively break my environment.

This is something that should have been accounted for a long time ago, I've discovered this new repo by an accident. There weren't any warnings about this anywhere else than in the add-on store, and I really think an update should have been released before archieving, triggering an warning in HA, with link to an migration wiki, so that everyone affected got informed, and not left in the dust without notice...

Poeschl commented 1 week ago

@JanPetterMG I understand your points about the migration and I would be more than happy to implement this nice way with even flowers on the sides. But reality strikes and this is still a project which I'm working on in my limited free time and for free. I was glad that I managed to split my add-ons into own repositories in my available time to make maintaining them easier and less time consuming for me.

For a migration guide feel free to note down your migration steps in this issue to help others and fill this lack of documentation for me. Also note: The "legacy" add-ons will not stop working and can be used as long as needed.

The rough steps for migration (out of my head) are:

  1. Install the new addon (don't start it)
  2. Copy the configuration as YAML from the legacy addon to the new addon
  3. Stop the legacy addon
  4. Start the new addon
JanPetterMG commented 1 week ago

Again, it's not that simple...

I'm using Synching in a multi-device environment, with full encryption and zero-trust enabled. Having to set up like new would require access to about a dozen devices, if not more, just to initialize the device handshake and enter the encryption key again.

Instead I ended up doing a full backup and restore over the SSH protocol, with certificates and everything. Luckily my 200GB of data was stored in the /share directory, meaning I didn't need to do anything about them, and my configuration could stay unchanged.

Now up and running again, but this time I migrated away from your repositories, and then I deleted them both.

I appreciate your time and commitment, I also know that voluntary community work can be hard sometimes, but you abounded your own community store without notice, further, leaving all the users in the dust with no updates ever more (repo is read only), and with no info about the migration process either. In fact, I had to Google the new repository as you didn't even leave a link to it before you abounded it.

All this just to save a few minutes uploading to GitHub. I hope it was worth it...

Open source is about trust, thanks, but no thanks.