Is there a limit of 50 zigbee devices using the Bridge with Homey Self Hosted Server?
1 Like
Are there any plans for you to use your own zigbee coordinator?
Iâve a usb sonoff adapter which Iâd like to use without the need of the bridge. That would be perfect setup - Homey OS hosted with your own zigbee/zwave coordinator.
5 Likes
Can we run both?
Set up Homey SHS on my NAS for most. Use my HP2023 (which is bursting at memory limits) for some things, join them with Homey Link app and use the bridge as intended so its all bridged around the house?
I was just about to buy a new HP2026 but i think i can pass now.
I take it app control and updates etc will be as is through the app
4 Likes
I was curious too, if i offload most/all to the NAS and use the link what effect will that have on routines/memory use?
Can we run all of it in one?
If i have bridge, will that âonlyâ server the SHS or will it bridge the shs and the Pro 2023?
Itâs most probably hardware related, not to the role it has (cloud extension / Pro sat / SHS sat).
Itâs no hard limit, but just like the Pro 2016-2019 series, itâs recommended to not exceed 40 devices to avoid performance issues, but some have reported to use 70 zigbee devices perfectly on a Pro 2019.
It all depends on the used devices, how many different brands and interference.
Donât build too big
Using Zigbee routers, you can create a stable Zigbee network of around 30-40 devices with Homey Bridge.
We do not recommend creating bigger Zigbee networks with your Homey. Adding more devices will put more stress on the network and might therefore negatively impact communication, reliability, and speed.
The limits of what is workable depend a lot on your specific situation.
If you notice Zigbee performance dropping after extending your network to a larger-than-recommended number of devices, you are probably pushing the limits of the Zigbee network in your home.
1 Like
Nice update. How can I pull a update from homey 2023 to homey self hosted?
Oh, that particular reply was about
as in âHome Assistantâ, Sven.
No issues with Homeyscript @ linux + Docker
Every platform has itâs dedicated topic now, Olivier. I think youâd best report here:
1 Like
(post deleted by author)
Yeah, sounds like it might be a Nuki quirk (âWorks with Home Assistantâ 
). I was planning a trip to the local IKEA somewhere in the upcoming days (Zigbee devices are getting cleared out) and pick up some of their new Thread devices.
EDIT: meh, just read that the new Thread devices will become available from Jan 1st.
1 Like
Does the connection between the Homey Self-Hosted Server and the Homey Bridge occur locally, given that the Homey Bridge was originally a cloud-based solution?
No everyone called Homey Cloud âHomey Bridgeâ, donâtask me why. So the Homey Cloud is the only cloud-based solution.
The actual bridge is just a device, connectable per local wifi to Homey Cloud, to Homey Pro or to Homey SHS.
One thing worth thinking about before deciding to use Homey SHS with Homey Bridge for Z Wave, Zigbee etc. devices is that if your Internet goes down, youâre fine as long as your Homey Bridge stays powered. If your Internet goes down and your Homey Bridge loses power even briefly then youâre stuck without access to any of your RF devices until the Internet is restored.
Wi-Fi with internet access is required
While Homey Bridge connects to Homey Pro directly on LAN, Homey Bridge needs Wi-Fi with internet access to connect to Homey Pro every time it powers on. Homey Bridge might pulsate red if your internet is offline until it can reconnect to Homey Pro.
Source: https://support.homey.app/hc/en-us/articles/7263667137052-Setting-up-Satellite-Mode-for-Homey-Pro
This kills the idea of Homey SHS as my primary solution at least for now.
So Iâm thinking Homey SHS might be a better option as a âbackup Homeyâ in the event something goes wrong with my Homey Pro that I cannot quickly fix. Obviously this use case wonât be viable until Homey SHS supports restore from backup (ideally cloud so that I have an automated nightly backup). And even then, itâs not clear that there would be a quick route to migrate RF devices from a Homey Pro to a Homey SHSâs Satellite Bridge.
So this leaves the only remaining use cases for Homey SHS right now:
-
Users who donât care about truly local (not sure how much overlap there is between these people and those contemplating Homey SHS)
-
Users who donât have (m)any RF devices. Similar caveat to the above.
-
Tinkering / dev system but not primary system (not sure how many people for whom this use case is worth the subscription fee)
In the cold light of day, Homey SHS is more limited than I first thought. And the addition of a restore from backup feature is even more critical IMHO. While youâre thinking about restore from backup, Athom, perhaps worth considering how RF devices could be migrated from Homey Pro to Homey Bridge operating as a Satellite for Homey SHS.
I just bought some yesterday in Groningen.. only the new air quality thing is not available
donât buy the scrol wheel button.. itâs bad
2 Likes
I think thatâs because Homey uses the homeylocal.com domain to reach your Homey via HTTPS (for me itâs 192-168-107-193.homey.homeylocal.com) and it needs DNS for that
Yeah I read your review, I will be skipping that (too bad because it sounded quite nice!).
âTLS Everywhereâ on a local network is just asking for problems. Not just because of this, but also having to turn off DNS rebinding protection in your router to make it work. I think itâs one of the main reasons why there are so many issues with âHomey Offlineâ errors.
But AFAIK the Homey app falls back to a cloud/relay connection when local access fails, right? When I block the â/pingâ URL in DevTools, the web app automatically uses the cloud/relay connection. So then you shouldnât have those Offline errors
They are already in stock in multiple Dutch stores. Picked up a TIMMERFLOTE temperature sensor in Haarlem last week.
2 Likes
