In previous guides, we saw how to install, for example, Jeedom on a Synology NAS, or Home Assistant on Synology. A Synology NAS already runs 24/7, consumes reasonably, and offers reliable storage: it’s a perfect host for a home automation system. And now that there is a Homey Self-Hosted Server, it is entirely possible to install the Homey system on a Synology NAS. The idea is simple: we launch the Homey server in a container, store the data in a dedicated folder on the NAS, and control everything from the Homey app on iOS/Android. Clean, efficient… and we keep control over the hosting! Athom, the company behind Homey, has developed an extremely simple procedure to take advantage of it.
On the hardware side, Homey requires a Synology with Intel/AMD CPU, DSM 7 or higher, at least 1 GB of free RAM, and 2 GB of free storage.
In practice, plan for a bit more if you install many Homey apps: the server itself remains light, but the apps and history can drive up disk usage.
You also need the Container Manager package (this is the “Docker” version for Synology on recent DSMs). The official Homey procedure involves managing Docker Compose projects in the Container Manager.
Finally, keep an important network point in mind: Homey Self-Hosted Server uses dedicated ports (and local discovery). On Docker, Homey recommends operating in network_mode: host, which fits very well in the home NAS context.
Install Container Manager on the Synology NAS
Open the Package Center on Synology, search for Container Manager, and install it. The first opening may take a few seconds while the service initializes everything.
If your NAS is old or on a DSM version that still displays “Docker,” don’t panic: the logic remains similar, but the “Project / docker-compose.yml” interface is typically that of Container Manager (DSM 7+).
Create the Homey data folder on Synology
Before creating the container, the simplest thing is to prepare a “clean” location for Homey data.
In File Station, Docker folder, create a folder like homey-shs. This folder will contain the configuration, database, and server files.
Why is this important? Because you will be able to update/rebuild the container without losing your data, as long as this folder remains in place (it is the one that counts).
Open Container Manager, then go to Project and click Create.
Name the project, for example, homey-shs.
For Path, select the folder you just created (e.g.: the folder “homey-shs”).
In Source, choose Create a docker-compose.yml file, then paste the official compose file below.
services:
homey-shs:
image: ghcr.io/athombv/homey-shs:latest
container_name: homey-shs
restart: unless-stopped
network_mode: host
privileged: true
volumes:
- ./:/homey/user
Two remarks:
- The mount
./:/homey/usermeans that the “Path” folder of the project serves as persistent storage on the Homey side. This is perfect on Synology, as Container Manager manages this folder for the project. - The
network_mode: hostavoids quite a few network/discovery issues and aligns Synology with Homey’s official Docker recommendation.
Start Homey Self-Hosted Server on Synology
Confirm with Next. In Web Portal Settings, change nothing (Homey explicitly states to change nothing here), then continue.
On the Summary screen, check that Start the project upon creation is checked, then finish with Done.
If you like to check that “everything is working,” open the container logs from Container Manager: you should see Homey starting without error loops.
As you can see, the installation is really very simple!
Add Homey Self-Hosted Server in the Homey app
Once the project is launched, open the Homey app on iOS or Android, add a new device/Homey, and then choose Self-Hosted Server.
The app will then load to associate your self-hosted Homey server.
Practical tip: if the app doesn’t detect anything automatically, test the URL http://IP_OF_SYNOLOGY:4859 from a browser on your local network (this is the default HTTP port of the server).
The app then prompts us to configure our home: number of floors, rooms, etc.
Some ideas for concrete uses once Homey is on Synology
Once Homey is hosted on the NAS, you can centralize all the equipment in the house. Homey offers many applications to install to add compatibility for certain connected hardware, which is very useful especially for devices that do not require a specific protocol via a USB key.
Here, for example, adding the Netatmo weather station, my Marstek solar battery, or my Philips Hue lights poses no problem.
My Shelly DIN rail modules also integrate without any problems, allowing me to follow my electricity consumption on the dedicated dashboard:
It is, of course, possible to create very “smart home” automations without relying on a dedicated little box. Typically, a “leaving” scenario can turn off non-essential plugs, lower the heating, activate the alarm, and switch certain cameras to surveillance mode.
Another classic that always works: presence + lighting management. As soon as the last person leaves the house, Homey can turn off forgotten lights and reduce ventilation. Conversely, when someone returns after sunset, Homey turns on a soft scene in the entrance and living room (and no need to think about it, that’s the point).
And if you need Zigbee / Z-Wave / 433 MHz / IR radios, Homey can expand via Homey Bridge depending on your equipment, while keeping the server on your own machine!
Watch out for the license
Unlike Home Assistant or Jeedom, Homey is not open source or free. Each new installation includes a 30-day free trial without a credit card.
Afterwards, there are two options: €4.99 per month or a lifetime license for €149, which can be subscribed to via your account on the Homey website.
Detail not to miss: if the monthly subscription expires, the instance goes offline until re-subscribed or a lifetime license is purchased.
Update Homey on Synology (Clean + Build)
You will of course need to think about updating the system from time to time, as Homey is very prolific in this area. The official Homey method on Synology is very simple: in Container Manager → Project, right-click on homey-shs, then Clean.
Right-click again and choose Create.
Homey indicates that after that, the server is running on the latest version.
This “Clean + Create” flow is precisely the advantage of having a persistent data folder: you rebuild the image, but you keep the history and configuration.
Homey Self-Hosted Server uses several ports by default: 4859 (HTTP), 4860 (HTTPS), and “Bridge” ports 4861/4862.
If the Synology firewall is enabled, allow at least these ports to enter from your LAN, otherwise, you will pull your hair out for no reason.
If local IP detection is not working well (this can happen depending on networks, VLANs, or some “exotic” configurations), Homey provides a variable HOMEY_LOCAL_ADDRESS to force the local IPv4 of the NAS.
On Synology, the simplest approach remains to keep network_mode: host and check that the NAS has a fixed DHCP/reserved IP.
Do you want to access Homey from outside with a domain name? Homey documents setting it up via a HTTPS reverse proxy (with WebSocket support) pointing to http://<ip-homey>:4859.
On Synology, this can be done with the integrated reverse proxy or a tool like Nginx Proxy Manager, as long as TLS + WebSocket are properly managed.
Please remain courteous: a hello and a thank you cost nothing! We're here to exchange ideas in a constructive way. Trolls will be deleted.