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:
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):
