Estou usando SHS no Raspberry Pi 4B Pendrive 3.0 64gb uma Dongle SONOFF ZB Dongle-E Zigbee 3.0 USB Plus Zigbee2MQTT e um mini Nobreak Para Raspberry PI. Funciona perfeito com um custo beneficio ótimo $4,90 mês. Só acho caro a ativação ilimitada $150. E ainda utilizo a GPIO do Raspberry PI para controlar 8 relés e sensor de umidade e temperatura.
+1
+1
+1
My SHS + Bridge has had zigbee network reliability issues since the beginning and still does with 13.2.1
+1
Mental that this has just been ignored by Athom for six months
+1
As well as the backup and restore from the cloud, it would also be really great if you could also backup to a local SMB share (either a NAS or a server) That you could run daily without having to take your smart home off-line every time like you do with the USB backup (worst backup method EVER!) It would also afford you the check-box of having multiple daily backups, including off-site and local (again, in case your internet went down for an extended period for example)
+1 - As a homey pro user, who is starting to push the limits of my homey pro device with my advanced automations, I was looking into running my own SHS version on a Mac mini for the house, to continue to grow my system with homey it is important that I do not have to start over and should be able to migrate from my pro or my cloud backup of my existing homey pro system. I also think existing homey pro users that are in the same boat as me should be able to use their existing homey pro device as the bridge device instead of needing a a homey bridge.
It’s possible for over 6 months now, albeit a(nother) splendid community initiative, not Athom’s:
+1
+1 for out of the box migration of settings, flows etc.
Also think it is crucial to have the opportunity to use custom antennas as the bridge is way too limited for many use cases (e.g. too weak Zigbee-capability limited n of devices, no matter) or at least provide the possibility to use the antennas of HP2023 or HP2026.
+1
Would be great to be able to move on to s SHS Homey as my Early 2023 is crashing app all the time due to low memory 
+1
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
- Go to the Docker tab in Unraid and click Edit on your Homey container.
- Change the Network Type dropdown to Host.
- Clear out the
any mac-addresscommand from your Extra Parameters box (leave it completely blank - 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.
- Go to your Docker tab in Unraid and click Stop on the
homey-shscontainer. - Unplug the power cable from your physical Homey Bridge.
- Leave the Bridge unplugged for 30 seconds.
- Plug the Homey Bridge back into power and wait for its LED ring to finish booting and stabilize.
- Go back to Unraid and click Start on your
homey-shscontainer. [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.
- Go to your Settings tab in the Unraid Web UI.
- Under the Network Services section, click on mDNS / Avahi.
- Look for the setting labeled Enable Reflector (or Allow Reflector Mode).
- Change this setting to Yes or Enabled.
- 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.
I don’t quite see how this post belongs to this topic, but wanted to note that I have no issues running Homey SHS on Unraid and connecting my Homey Bridge to it.
Edit: I have not tried to connect any Netatmo devices, just a Sonoff camera via ONVIF streaming URL and that works fine for me (also has nothing to do with the Homey Bridge). So for apps that require lots of ports perhaps a bare metal setup or an advanced Unraid Docker network configuration with a dedicated IP on the host network may help as well.
+1 I need to migrate dvices so i dont have to do all of them AGAIN
There’s a community built tool
