I dipped my first toe in the home automation water when I learned about Homey SHS only last week. Although my use cases are limited at the moment, I like the potential and easy of use. At the same time I wonder if in the future I start doing more and more automations, what would happen if my instance would break somehow.
Currently I run Homey SHS in a Portainer docker on a miniPC. Would it be possible to have a second instance installed on a NAS f.e? Does not even have to be in active-standby, just an instance I can turn on and assign to my account if needed.
Is such setup a logical? How would that work with licencing? Do I need to keep the “cold” instance periodically in sync, or can I import a backup of the main instance when needed?
I think you can use a single license. Just sync the .homey-shs folder every day for example, and then turn it on when needed. As long as only 1 is up at a time, it shouldn’t be an issue
As you are running Homey in a container, you should have no problem moving the container from one host to another, provided that you have correctly configured the volume as described in the how to installation for your platform.
What you need to do is:
Create a compose file for Homey on your NAS, according to the instructions for your NAS
Copy the folder to which the /homey/user folder is mapped from your mini pc to the appropriate location on your NAS.
You should then be able to launch Homey from docker on your NAS.
When done correctly, and only one instance is running at a time, you will not need an additional license.
You probably want to make sure that the copy from the mini pc to the NAS happens on a regular basis in order to keep the configuration and data up to date.
