Transfer SHS user data between platforms?

[Olex]

I’m using SHS on my good but old Synology DS918+.
I have an old HP NUC that can’t be used any longer because it is not compatible with windows 11.
Just testing SHS on Proxmox on this NUC.

As I understand, you can transfer the user data from one setup to another.
Does this mean that I could transfer the SHS user data from Synology and to my Proxmox setup and be good to go?
Have anyone transferred data from one platform to another one with success?

[Anoniemand]

Not yet transferred data from one to another, but according to this support file it is possible. Just make sure you copy the data to the user folder after you have installed SHS on Proxmox and before you start it for the first time on Proxmox. Also make sure you’re not running two instances at the same time, because that might lead to unexpected behavior / data issues.

[Peter_Kawa]

@Olex

I have an old HP NUC that can’t be used any longer because it is not compatible with windows 11.

You can install linux Debian 13 for example.
I use it to run Home Assistant as Virtualbox VM 24/7

My 2011 laptop runs Linux Mint Cinnamon.

In general everything gets recognised by linux OS. The ‘geeky command line’ days were gone long ago.

More linux OS & window manager flavors for Windows users here.

[Olex]

Thanks!
Linux has really changed for sure since my last try with Linux decades ago

[Olex]

Thanks again for your input.

Since you seem to know a lot about Linux:
”Data should be transferred before you start Proxmox for the first time”.
This will probably be difficult since SHS automatically starts up after installation on Proxmox.

Another thing — I’m trying to shut down SHS so I can transfer data to Proxmox.
When SHS is shut down, I can’t access the data folder where SHS is located.
Is this how it’s supposed to be?

[Anoniemand]

Let me see if I can test it myself later today. I’ll get back to you.

[Anoniemand]

So i’ve taken a look at the install script and it indeed auto starts (–now in below line):

systemctl enable --now homey-shs.service

I have created an interactive install script, in which (among some other things) you can choose not to autostart Homey SHS after installation. The script is available on github, with a readme.

–Edit: Also created a tutorial:

[TUTORIAL] Homey SHS on Proxmox Interactive installer

After a question about how to migrate to a Proxmox Homey SHS environment, I have created an interactive installer. With this installer you are able to install Homey SHS on Proxmox with some more flexibility: You can choose your storage (current Athom installer might refer to storage that doesn’t exist) Select a VLAN (if bridge is VLAN aware) Disable auto start of Homey SHS (to migrate data) Disable auto update (for those who like to be in control of when an update starts) You can view the scr…

You should be able to enter the directory, it’s just the filesystem so I don’t see any reason why it’s not available. But maybe… the word “container” is confusing:

• Proxmox Container: If you shut this down, the filesystem isn’t accessible. It has an ID and probable (also the name homey-shs)
• Docker container: If you shut this down (inside the Proxmox container), Homey-SHS isn’t running, but the filesystem (inside the Proxmox container) is still available.

You can stop Homey SHS in multiple ways, one of those are:
In the Proxmox container (SSH): systemctl stop homey-shs
From the PVE node: pct exec <container id> -- systemctl stop homey-shs

An image explaining the differences:
Proxmox container:

Docker container (inside the proxmox container):