I have bought a mini PC and installed Ubuntu and Docker to run Homey SHS. I have one major problem: if I follow the instructions on https://support.homey.app/hc/en-us/articles/24010537261980-How-to-install-Homey-Self-Hosted-Server-with-Docker-on-Linux But with network_mode: host, I dont get a port. I see my container in Docker, with no port(s) so it won’t work. If I remove and force the port with something like this:
–name homey-shs
–restart=always
-p 4859:4859
-p 4860:4860
My Homey SHS works and I can add the IP / setup the android app and there’s a lot that works: adding Hue lights, installing apps and importing devices etc. There are als some things that will not work: adding the Homey Bridge or finding Google Cast (Chromecasts, Nest Hubs) devices for example… I cannot get it working with network_mode: host and not everything works without network_mode: host. It’s driving me crazy! Anyone has idea’s? Would be apprenticed!
Hi thanks for your reply. But this is basically the same right? Both use Docker, one with a yaml/docker compose and one directly. But I have the same issue regarding network_mode: host
I run SHS on a Lenovo SFF, Ubunutu server 24.0.4 LTS
My compose file:
services:
homey-shs:
image: ghcr.io/athombv/homey-shs:latest
container_name: homey-shs
restart: unless-stopped
network_mode: host
privileged: true
volumes:
- ~/.homey-shs:/homey/user
uname -a
Linux homey-shs 6.17.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 9 17:01:16 UTC 2026 x86_64 GNU/Linux
Docker version 29.3.0
Are there any hints in th elog output when the container starts up? (docker run without the -d will spew it all to the terminal screen). Also logs are in the .homey-shs directory.
Not sure what you mean exactly, but you can view the logs by executing this command (in a second terminal):
$ docker compose -f homey-shs.yml logs --follow
As per KB article https://support.homey.app/hc/en-us/articles/24010537261980-How-to-install-Homey-Self-Hosted-Server-with-Docker-on-Linux
No sure what you mean either.
To verify if docker container is running as expected i usually use docker ps. It will show each docker container status (and some other details).
To get docker logs from a container docker logs <container name>.
yes, better choices to use ‘docker logs’ if the container is already running. (–follow is aslo a good option to keep watching) But that only show recent stuff.
The full log file is actually also visible in ~/.home-shs/logs if you want to root around finding specific things.
True, but it shows everything from the start on when I start that “follow” command prior to the container start.
I have a similar issue. From my HPE 2019 I can’t reach SHS by using Homesh controller APP on my HPE2019. Viceversa it is working fine: from my SHS i can reach HPE2019 by using Homesh controller APP on my SHS. Did you have any suggestion?
The error that rises on my HPE2019 side is “connect ECONNREFUSED :80”, it happens when I try to connect to the Homesh Satellite APP on SHS.
Please could anyone help me?
I’d first try the HomeyLink app instead.
Otherwise, you probably have to change the default port temporary from 4859 to 80 to see if it connects;
Make sure there’s no other local web server running on port 80.
Hi,
SHS in Docker on TerraMaster F2-223 (TOS 7, Docker Manager): every app crashes immediately on start.
Error from container logs:
CreateClientError: ManagerDrivers.getDrivers is not a function
at SDK.createClient (/app/packages/homey-local/lib/AppProcess/…)
Homey [err][ManagerAppsLocal] Error Starting: App Crashed
Exit Code: 1
SHS itself is healthy — discovery, login, app store browsing all work, trial active. Only the app spawn step fails.
Already tried, none resolved it: restart, rebuild, fresh image pull, full nuclear reinstall (deleted project + image + volume + Athom account instance), HOMEY_LOCAL_ADDRESS env var
Anyone seen this ManagerDrivers.getDrivers error
Hi All,
Just tried to follow the install in docker on Ubuntu.
I think it is running as I get the blurb that says it is…
However the Android App says it has “1 Self Hosted Server found…” at the correct IP address but then timer whirrs and nothing happens. With manual I get “unable to connect to your Self Hosted Server”.
EDIT - I had started my thread and then realised it was a firewall blocking the port 4859 and 4860.
I will still post it if this is useful to other newbies.
Dave
If it matters - Server HP box 16Gb RAM, a few Tb of disc space, Ubuntu Server 24.04.4 LTS
