Which smart home hub should you choose?
What a smart home hub does and how Home Assistant, SmartThings, Apple Home, Google Home and Alexa compare on radios, Matter, local control and privacy.
Photo: James Yarema / Unsplash
After reading this article you will be able to:
- Explain what a hub, a Matter controller and a Thread border router each do
- Compare the five main platforms on radios, local processing, accounts and privacy
- Pick a platform from the devices, phones and time you already have
On this page
Use Apple Home if the household uses iPhones and wants the least setup. Use Google Home or Alexa if you already own their speakers or displays and voice is how you mostly control the home. Use SmartThings if you have recent Samsung TVs or appliances, which often contain a hub already. Use Home Assistant if you have devices from many brands and protocols, want automations that run without the internet, and accept looking after a small server. Since all five act as Matter controllers, a certified Matter device will work with any of them, so the choice is less permanent than it used to be.
What still separates the platforms is which radios they speak natively, how much runs on the hub rather than in the vendor’s cloud, how deep the automations go, and who holds your data. The table summarizes the differences; the sections below explain each one and how to weigh it.
| Home Assistant | SmartThings | Apple Home | Google Home | Alexa | |
|---|---|---|---|---|---|
| Hub hardware | Green, Raspberry Pi, mini PC | Samsung TVs, appliances, hubs | HomePod, Apple TV | Nest speakers, displays, Wifi Pro | Echo speakers, displays, eero |
| Thread border router | With a USB radio | Built into recent hubs | HomePod mini, HomePod, Apple TV 4K | Some models | Many Echo and eero models |
| Zigbee and Z-Wave | Both, with USB radios | Zigbee; Z-Wave on some hubs | Through vendor bridges | Through vendor bridges | Zigbee on some Echo models |
| Account needed | None | Samsung | Apple | Amazon | |
| Admin effort | High | Low to medium | Low | Low | Low |
What does a smart home hub actually do?
A hub, or controller, does three jobs. It speaks the radios your devices use, either directly or through a bridge. It keeps the state of the home (which lights are on, which doors are open) and runs automations on that state. And it connects the home to apps, voice assistants and remote access. The smart home guide describes these as the radio, controller and ecosystem layers.
The commercial platforms hide this behind a speaker or a TV: an Apple TV, a Nest Hub or an Echo is also the controller, as long as it stays powered and on the network. Apple says a home hub is what lets you control accessories away from home, share control and run automations, and HomePod and HomePod mini become hubs automatically when set up. Samsung builds a SmartThings hub into many of its TVs, monitors, soundbars and Family Hub refrigerators. Home Assistant is the exception: the controller is a computer you choose and run.
What are Matter controllers and Thread border routers?
Matter is the application standard that lets one device work with several platforms. A Matter controller is the software that commissions devices and sends them commands; all five platforms include one. Matter’s multi-admin feature lets a device join several controllers at once, so a lock can sit in Apple Home and Home Assistant at the same time. The Home Assistant Matter documentation notes that each device should support at least five such connections, called fabrics.
Thread is the low-power mesh many Matter devices use instead of Wi-Fi. A Thread device needs a border router to reach the rest of the network. Apple lists the HomePod mini, HomePod (2nd generation) and Apple TV 4K as Thread-enabled hubs. Google’s Matter hub list names the Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro, Google TV Streamer and the 2026 Google Home Speaker as Thread border routers. Amazon’s Matter page lists Thread border routers across many Echo and eero models, and Home Assistant becomes one with a Thread-capable USB radio.
One practical catch: each vendor tends to create its own Thread network with its own credentials, and the Home Assistant Thread documentation points out that devices cannot roam between those networks. Two border routers from different brands do not automatically make one stronger mesh. Whether a device should use Thread or Wi-Fi in the first place is covered in Matter over Thread vs Wi-Fi.
How much runs locally, and what needs the cloud?
Matter itself is local: it relies on IPv6 and mDNS on your home network, so once a device is commissioned its commands do not need to leave the house. Google says a Matter hub lets you control devices locally instead of over the cloud, and Amazon says its Echo connection lets Alexa control Matter devices locally. SmartThings runs hub-connected Zigbee, Z-Wave, Matter and LAN devices through Edge drivers on the hub, which also allows local automations.
Local commands are only part of it. On the commercial platforms, setup, the phone app, remote access, voice recognition and many automations depend on the vendor’s servers to some degree, and devices added through a cloud-to-cloud link (a vacuum, a car, many Wi-Fi plugs) stop responding when the internet drops. Home Assistant is designed the other way round: everything runs on the local machine, and cloud services are optional extras. If “still works when the internet is down” is a requirement, test it on whatever you choose by unplugging the router’s WAN cable for an evening.
How do the platforms differ on privacy?
All the commercial platforms tie the home to a vendor account, and the data they keep about your devices and voice requests depends on the vendor’s own policies. Apple states in its platform security guide that HomeKit data is synchronized with iCloud end-to-end encryption and is not accessible to Apple. Amazon and Google provide controls for voice recordings and activity history in the Alexa Privacy settings and My Activity; review them once the system is set up.
Home Assistant keeps state, history and automations on your own machine and needs no account at all. That is a real difference, but it moves responsibility to you: securing remote access, applying updates and protecting backups. A local system that is exposed to the internet carelessly is not more private than a cloud one.
How should you choose?
Start from what you already have rather than from feature lists:
- Phones. Apple Home works only from Apple devices. Google Home, Alexa, SmartThings and Home Assistant have apps for both iOS and Android, which matters in a mixed household.
- Existing devices. List the radios: Zigbee bulbs, Z-Wave switches, Thread sensors, Wi-Fi plugs. Alexa has a Zigbee hub in some Echo models; Apple and Google rely on vendor bridges for Zigbee devices; Home Assistant covers Zigbee, Z-Wave and Thread with USB adapters. Zigbee vs Z-Wave compares the two older meshes.
- Automation depth. The commercial apps handle “at sunset, turn on these lights” well. Conditions that combine several sensors, time windows and states are where Home Assistant pulls ahead.
- Time and interest. Home Assistant asks for setup time and ongoing maintenance. The others ask for almost none, in exchange for less control.
Platforms can be combined. A common pattern is Home Assistant as the main controller, with Matter devices also shared to Apple Home or Google Home through multi-admin so other family members can use the app and voice assistant they know.
Where to go next
- Home Assistant explained covers installation, hardware and the optional cloud.
- Matter explained covers how commissioning and multi-admin work under the hood.
- Thread explained covers the mesh and the role of border routers.
- The smart home, explained describes the three layers every platform is built on.
Topics: smart home, hub, Home Assistant, SmartThings, Apple Home, Google Home, Alexa, Matter, comparison, everyday questions