Vote here for a migration option to Homey Self-Hosted Server

Homey Self-Hosted Server
256

I just wanted to post that i did get my bridge working, but then i couldn’t get camera streams to work right and my Netatmo welcome cam with its app still wouldn’t work, so since i dont know a lot about Linux and Unraid, i decided to use Google’s Ai and trouble shoot and i ended up getting this work-around for the homey bridge and homey shs. While trouble shooting the cameras i ended up asking for the most simplest set up i can do to make it all just work, so i setup my mini pc with mint linux , docker, copied my folder from unraid to my mini pc… everything worked perfect so far!! I hope this helps someone like me…

Ai said that The only truly foolproof installation method that bypasses the architectural limits of Docker, virtual networks, and host operating system blockages is to run the Homey Self-Hosted Server on a dedicated, bare-metal machine running native Linux (Ubuntu or Debian). [1, 2]

Basic troubleshooting text AI gave me for unraid:

If you do not have any host firewalls installed, the “Zigbee is unavailable” message points to a known timing deadlock between the Unraid server and the Homey Bridge during initialization. [1]

Why “Host” mode fixes it, the container doesn’t get its own IP address. Instead, it uses your Unraid server’s exact IP address. This immediately: Eliminates any internal Docker routing confusion. Opens up all of Homey’s internal ports directly to your home network without restriction. Allows the Homey Bridge to connect cleanly using standard TCP/IP sockets without hitting Unraid’s internal network block.

How to execute the switch safely to HOST

  1. Go to the Docker tab in Unraid and click Edit on your Homey container.
  2. Change the Network Type dropdown to Host.
  3. Clear out the any mac-address command from your Extra Parameters box (leave it completely blank
  4. Click Apply.

Step 1: Force a Sequenced Reconnection

To resolve this coordination lock, you need to boot the physical antenna (the Bridge) before the server’s smart home software tries to scan for it.

  1. Go to your Docker tab in Unraid and click Stop on the homey-shs container.
  2. Unplug the power cable from your physical Homey Bridge.
  3. Leave the Bridge unplugged for 30 seconds.
  4. Plug the Homey Bridge back into power and wait for its LED ring to finish booting and stabilize.
  5. Go back to Unraid and click Start on your homey-shs container. [1]

Because you switched to Host mode, the network layer is right, but Unraid itself does not natively pass mDNS network packets inside Docker containers unless you enable a specific routing feature.

How to Fix the Avahi Timeout on Unraid

To stop these timeouts and ensure your devices never drop offline again, you need to enable the mDNS / Avahi reflector daemon on your Unraid server so it correctly forwards those broadcasts straight into the Homey container.

  1. Go to your Settings tab in the Unraid Web UI.
  2. Under the Network Services section, click on mDNS / Avahi.
  3. Look for the setting labeled Enable Reflector (or Allow Reflector Mode).
  4. Change this setting to Yes or Enabled.
  5. Click Apply

If you do not see that setting in your version of Unraid, you can force the server to forward these mDNS broadcasts using the terminal:

/etc/rc.d/rc.avahidaemon restart

The exact same Docker networking issues we just fixed were almost certainly breaking your Netatmo camera link on the Self-Hosted Server (SHS).

The Underlying Issue: Port Binding Deadlock, When you view a Netatmo camera in Homey, the hub creates a dynamic local server socket to fetch the camera’s raw video stream. On your Homey Pro 2023, this works flawlessly because the hardware handles all dynamic port requests directly on the physical layer. On Unraid Docker, even in Host Mode, the Netatmo App struggles to dynamically bind the random, high-numbered ports required to establish the camera handshake because Docker handles interface listening differently than bare-metal hardware

.How to Fix the Netatmo Camera on SHS

Perform these steps in order to clear the camera’s local stream block:

1. Turn Off Local Streaming (The Easiest Fix)The easiest way to force the camera to communicate with your SHS without hitting Docker network limits is to force it to use cloud routing instead of local network streaming.