Dedicated smart home hub vs smart speaker or display as your controller

What a hub actually does

A hub does three jobs. It speaks the radios your devices use. It stores your rooms, scenes and automations. And it lets your phone and voice assistant reach everything. In some ecosystems a hub is a requirement for the second job: Apple says a home hub lets you control accessories when you are away, share control with others and run automations. A modern speaker, display or TV can take on one or more of those jobs, which is why many households never buy a separate hub.

The key question is which radios you own. Amazon says its Echo and eero devices have built-in smart home hubs, with Zigbee on the models it lists, and that the Echo device is the Matter administrator that connects Matter devices to Alexa locally. Google lists the Nest devices that function as Matter hubs. Samsung says TVs from the Q60 series up, released after 2022, include a built-in SmartThings hub that supports Matter, Thread and Zigbee. The list changes with each hardware generation, so read the maker’s page for the exact model you own.

When the speaker or display is enough

It is enough when your devices are Wi-Fi or Matter, when you have a handful of Thread sensors, and when voice and a wall display are how you control the house. In that case the speaker is already the Matter controller. If it also includes a Thread border router, Thread sensors need nothing else. Home Assistant’s Thread page notes that Google, Apple and Amazon all make border routers, and that for many of them border routing is only an auxiliary function of a smart home device.

Two habits keep this setup reliable. Leave the speaker plugged in and in one place, and add a second Thread-capable device later so the mesh does not depend on one unit. Home Assistant’s documentation points out that Thread can use several border routers in one network, which reduces the risk of a single point of failure. Different vendors often form separate Thread networks, so a second border router from the same ecosystem is the simpler way to add coverage.

When a dedicated hub earns its place

Choose a hub when you want more than a few Zigbee or Z-Wave devices, when you need locks or sensors to act even if the internet is down, or when speakers in your home come from different ecosystems. SmartThings’ developer documentation says hub-connected devices benefit from low latency, local execution and the reliability of the hub, with Edge drivers running on the hub itself. Devices connected through a cloud link, by contrast, depend on the brand’s cloud and your internet. For the practical side of the choice, read Do you need a smart home hub? and Do you need a SmartThings hub?

A dedicated hub also separates the smart home from the speaker’s life cycle. You can move, replace or remove speakers without touching your automations. Put the hub on Ethernet if it has a port, give it a battery backup if you want it to survive short outages, and keep it away from the router’s antennas.

Using both

Most mixed households end up with both. The speaker or display handles voice and the dashboard, and the hub handles sensors and locks. If the hub supports Matter bridging, Apple Home, Google Home and Alexa can all see its devices; the Matter bridge guide explains what is exposed and what you give up. If your hub and your speaker are on different Thread networks, do not try to merge them by hand. Pick one as primary, add devices there, and check the other app for duplicates.

Before you buy: a three-minute check

1. List the radios of the devices you own or plan to buy: Wi-Fi, Zigbee, Z-Wave, Thread.
2. Look up each speaker, display and TV you own on the maker’s page and note its Matter, Thread and Zigbee support.
3. Pick a hub only for radios nothing at home covers, and confirm it supports your ecosystem.