Quite a few community members have more than one SmartThings hub,for different reasons. This is becoming even more true with the “hub everywhere” initiative already mentioned above that intends to put a built-in Zigbee/thread/matter hub (But not zwave) into many different Samsung smart devices, from televisions to soundbars, and eventually refrigerators and washing machines.
But even without the “hub everywhere” initiative, you can use multiple SmartThings hubs right now.
you can add multiple SmartThings hubs to one SmartThings account.
you can also now add multiple SmartThings hubs to one SmartThings “location.“ That didn’t used to be true, so if you’re looking at something written before 2022 it may tell you that you can’t do it. But you can now.
right now, with the exception of thread on a SmartThings station or one of the WiFi mesh models, Each hub on the account maintains its own Zigbee, thread, and zwave (If it supports zwave) networks. So when you add a new end device like a sensor or a light switch, you will be asked to select which hub on your account you want to add that device to.
Eventually, Samsung intends the thread networks from different hubs on your account to be available to merge. At the time of this posting, that can only be done with the SmartThings station hubs.
We should note that this is way easier to do technically with thread than with Zigbee, so while Samsung has made some statements indicating that they would like to eventually also offer this option for Zigbee, it may take longer, and be limited to specific models.
Because the current networks belong to a specific hub, they don’t share repeaters.
- right now, if you create a routine That includes devices that belong to different hubs, that routine will have to run in the cloud. The hubs do not speak directly to each other in most cases.
(As always, the Wi-Fi mesh models are an exception, but those appear to be end of life devices, and they are updated less frequently than the other models, and don’t have all of the same features, particularly with regards to matter.
So while You can still buy them new, I would not recommend those Specific models until there is a firm commitment from SmartThings that they will be continued in the future and until they are updated to match the functionality of the other models, particularly with regard to matter.)
If the issue is that you are running out of memory for Edge drivers (a common symptom of this is that the hub keeps shutting down and rebooting), you might find that adding a second smartthings hub of any model helps if you can then limit the number of edge drivers on each. A common way to do this is to put Zigbee devices on one hub and zwave devices on another.
Note that SmartThings still uses a new architecture version of “superLAN connect”, Which means it will download a bunch of LAN drivers that you may not need, like for Sonos. If you delete these, they will just be added again The next time it does a LAN scan, probably within an hour or two.
You also cannot permanently delete stock drivers for zwave or Zigbee— they will get added back again with the next hub firmware update.
But at least you have control over how you distribute your custom edge drivers and that can be helpful as some of them are quite large.
Another popular reason for having more than one hub is local communication issues due to architecture, such as in Adobe or cement buildings. In that case, you may need a hub on each floor just to communicate with the devices in those rooms.
Some people will also put a separate hub in an outbuilding to reach Zigbee/Z wave/thread devices there, communicating to the cloud by internet.
In all these cases, you can write a routine that has, for example, a sensor connected to one hub and a light switch connected to another. Just remember that that routine will run in the cloud and therefore will need an active Internet connection.
So that’s what’s currently available. We may see more multi hub options in the future at both the RF protocol layer and the application layer, but we aren’t there yet.