A Matter hub and a Thread border router are not the same device, and nothing on the box tells you which one you’re buying. Most people asking this question already own something that qualifies. The problem is figuring out which thing, and whether it’s already doing the job.
The distinction that causes the confusion
Three separate jobs get lumped under “smart home hub,” and a single device can do one, two, or all three.
- A Matter controller is the app or device that commissions a Matter accessory, holds its credentials, and issues commands to it. Apple Home, Google Home, Amazon Alexa, and SmartThings are all Matter controllers.
- A Thread border router is a piece of hardware that bridges a Thread mesh network to your Wi-Fi or Ethernet network. It has nothing to do with which app controls your devices – it just gets Thread traffic on and off your regular network.
- A Zigbee or Z-Wave hub is neither of the above. It’s a bridge for an older mesh protocol, and it only touches Matter if the manufacturer has built a translation layer, the way Philips Hue exposes existing Zigbee bulbs to Matter through the Hue Bridge.
A device can be a controller without being a border router – an Alexa app on your phone controls Matter devices but doesn’t route Thread traffic. A device can be a border router without being much of a controller – a bare Thread border router with no companion app is just plumbing. And a device can be both at once, which is what a HomePod mini, an Echo Hub, or an Aqara Hub M3 actually is: one box doing two jobs that get sold as if they were one.
The confusion is the industry’s fault, not yours. Product copy calls all of it “hub,” and most boxes don’t say which of the two jobs they do.
None of this touches Zigbee or Z-Wave devices you already own. Those still work through their own hubs exactly as before – Matter and Thread are additions to the smart home, not replacements for what was already running. For the full protocol lineup, see our smart home automation protocols guide; for what “Matter” itself actually is, see our Matter explainer.
What you probably already own
Thread border routers ship quietly inside products sold for something else – a speaker, a streaming box, a Wi-Fi mesh point. If you’ve bought any smart home hardware in the last few years, there’s a decent chance one of these is already sitting in your living room.
| Device | Thread border router? | Notes |
|---|---|---|
| HomePod mini (any generation) | Yes | Built in since it launched in 2020. Becomes a home hub automatically once set up in the Home app. |
| HomePod (2nd generation, 2023) | Yes | The original 2018 HomePod does not have the Thread radio. |
| Apple TV 4K, Wi-Fi + Ethernet models | Yes | Confirmed on Apple’s own support pages for the 3rd-generation (2022) Wi-Fi + Ethernet model, and on the 2nd-generation (2021) unit. |
| Apple TV 4K, Wi-Fi-only 3rd generation (2022) | No | Same box, same year, no Thread radio. This is the single most common wrong assumption in this whole category – two Apple TV 4K units sold side by side, and only one of them can route Thread. |
| Amazon Echo (4th generation) | Yes | Ships with a Thread 1.1 radio per Amazon’s own developer documentation. |
| Echo Hub | Yes | Thread 1.3, per the same Amazon documentation. Also the newer Echo Show and Echo Studio models and several eero mesh Wi-Fi units – Amazon has the longest hardware list of any ecosystem. |
| Google Nest Hub (2nd generation) | Yes | Added Thread border router support via a firmware update, alongside Nest Hub Max. |
| Google TV Streamer | Yes | Built in from launch, and picked up Thread 1.4 credential sharing in a 2026 firmware update – the first consumer device to get it. |
| SmartThings Station | Yes | Samsung’s compact hub puck. Along with the Aeotec Smart Home Hub, it’s one of only two SmartThings-family devices with a native Thread radio. |
| SmartThings Hub v3 (Aeotec) | Yes | Got Thread border router functionality added via firmware in late 2022, confirmed on the Thread Group’s own compatibility list. |
| Aqara Hub M3 | Yes | Aqara’s first Matter controller and Thread border router in one box. |
| Aqara Hub M2 | No | Stays a Zigbee-only hub. A firmware update lets it expose existing Zigbee devices to Matter over Wi-Fi, but it does not gain a Thread radio and cannot route Thread traffic. If you own an M2 and want Thread, you need an M3 alongside it, not instead of it. |
| Homey Pro and Homey Pro mini | Yes | Both create or join a Thread network and handle Matter-over-Thread onboarding without extra setup. |
The Apple TV row is worth reading twice. Apple sold two versions of the 3rd-generation Apple TV 4K in the same year with the same name on the box – one with Ethernet and Thread, one Wi-Fi-only and without. If you’re checking what you own, look at the port on the back, not the model name on the box or the receipt.
Check the box or the settings menu for your specific unit before assuming – firmware-gated Thread support changes as manufacturers roll out updates, and this table reflects what’s shipped and documented as of September 2026. For the wider list of what’s HomeKit compatible beyond just border routers, see our full HomeKit compatible devices list.
When you actually need to buy something
Skip this section if a device from the table above is already running in your home – it’s already a border router, and Thread devices will find it automatically during setup with no separate purchase or configuration step.
You need to buy dedicated hardware in three situations:
- You own none of the above. Older ecosystem hardware – a 1st-generation Apple TV, an original 2018 HomePod, an Echo Dot from before the 4th generation – doesn’t have a Thread radio and never will, no matter how many firmware updates ship.
- Your existing border router is out of range of where you want to put a Thread device. Thread is a mesh, so range extends hop by hop once you have two or more Thread-capable devices talking to each other, but a single border router in a back office won’t reach a sensor on the far side of the house on its own.
- You want a dedicated, ecosystem-neutral controller, not a speaker or streaming box doing double duty. This is the case for the Aqara Hub M3 and Homey Pro – both are purpose-built Matter controllers and Thread border routers with no other job, aimed at people who want a home automation setup that isn’t tied to Alexa, Google, or Apple staying in business the way they are today.
When you do need to buy, the decision is simpler than the lock or camera categories: match the ecosystem you already use for everything else. If your phone and your other smart devices already live in Apple Home, a HomePod mini is the cheapest way to add Thread coverage to a room, and it does double duty as an actual speaker. If you’re in Google’s ecosystem, a Nest Hub does the same job with a screen attached. If you don’t want to commit to a single ecosystem, Homey Pro or an Aqara Hub M3 will talk to more than one at once.
What breaks, and what doesn’t
A border router from one ecosystem will happily serve another. Thread is a shared, IP-based mesh network, not an Apple network or a Google network. A HomePod mini creating a Thread mesh will route traffic for a Thread device you’ve commissioned into Google Home or SmartThings just as readily as one commissioned into Apple Home. The border router moves packets; it doesn’t check whose app is asking.
Multi-admin lets more than one ecosystem control the same device, but it doesn’t merge your Thread networks by itself. A Matter device supports multi-admin commissioning, meaning the same light can be added to Apple Home and Google Home at once, each tracked as a separate “fabric” on the device. Historically each border router also formed its own separate Thread network, so a home with a HomePod mini and a Nest Hub could end up running two Thread meshes side by side instead of one. Thread 1.4 introduces credential sharing specifically to fix this – border routers from different manufacturers exchanging network credentials so they cooperate on a single mesh instead of each building its own – and Google has already shipped it to the Google TV Streamer, with more devices expected to follow as manufacturers adopt it.
If a border router disappears, the Thread devices it was routing for don’t just die – but they do stop being reachable off your local network. Local automations that don’t need a cloud round trip generally keep working, since Thread and Matter are built for local control. What you lose is remote control, notifications, and any device that was relying specifically on that one border router with no other route to a mesh. This is the practical lesson from Starling Home Hub, the third-party bridge that let Nest devices show up in Apple Home: Starling discontinued the Home Hub in September 2025, citing tariff costs on the hardware. Existing units kept working with continued support promised, but the product was gone from shelves – a reminder that a single-purpose bridge box from a small company is a different bet than a border router built into hardware you’d own anyway, like a speaker or a streaming box you were buying regardless.
Matter over Wi-Fi vs. Matter over Thread
Matter itself isn’t a radio – it’s a shared language devices use to describe themselves and take commands, and it runs on top of Wi-Fi, Thread, or Ethernet. Which transport a given device uses depends on what it’s built to do, and that decision was made by the manufacturer, not by you.
Matter over Wi-Fi is what you’ll find in anything that’s mains-powered and doesn’t care about battery life: smart plugs, switches, and most mains-powered lighting. These join your Wi-Fi network directly, exactly like a laptop or a phone, and need no border router at all.
Matter over Thread is for anything battery-powered where power draw matters: door and window sensors, battery-powered locks, some battery-powered lighting controls. Thread’s low-power mesh radio is why a coin-cell sensor can run for a year or more instead of weeks, but it only works if there’s a border router nearby to get that traffic onto your regular network.
This is why the buying decision comes before the border router question, not after. A Matter smart plug needs nothing extra regardless of what hub hardware you have. A Matter door sensor needs a border router in range, which is the entire reason this page exists. Check which transport a specific product uses before assuming a border router is required – the packaging or spec sheet will say Wi-Fi or Thread, and it changes what else you need to buy.
For the underlying radio-layer comparison – how Thread’s mesh recovery and range compare to Zigbee and Z-Wave at scale, with real measured numbers, not marketing claims – see our Z-Wave vs. Zigbee vs. Wi-Fi guide. And if what you actually have is a Zigbee device that needs to reach HomeKit, not a Thread device that needs a border router, that’s a different piece of hardware entirely – see our HomeKit bridge guide.
Frequently asked questions
Do I need a smart home hub at all?
Not necessarily, and for a lot of people the honest answer is no. Wi-Fi-based Matter devices – plugs, most switches, many bulbs – need nothing but your existing router. You only need a hub-shaped device once you own a battery-powered Thread device or want an ecosystem-neutral controller. Check what you already have from the table above before buying anything.
What is a Thread border router?
It’s the piece of hardware that connects a Thread mesh network – the low-power wireless network your Thread-based smart home devices form with each other – to your regular Wi-Fi or Ethernet network. Without one, Thread devices can talk to each other but can’t reach your phone, your voice assistant, or the internet.
What’s the best Matter hub?
There isn’t a single best one – it depends on which ecosystem you’re already using for everything else. A HomePod mini is the natural pick inside Apple Home, a Nest Hub or Google TV Streamer inside Google Home, an Echo Hub or Echo 4th generation inside Alexa. If you want one controller that talks to more than one ecosystem at once, Homey Pro and the Aqara Hub M3 are the two purpose-built options.
Does Matter work with HomeKit?
Yes. Matter has been a first-class citizen in Apple Home since Matter 1.0 launched in late 2022, and Apple Home is one of the ecosystems every Matter device is required to support if certified. A Matter device sits in the Home app the same way any other HomeKit accessory does.
Does a border router need to be from the same brand as my devices?
No. A Thread border router routes traffic for any Thread network in range regardless of manufacturer, and Thread 1.4’s credential sharing is making it easier for border routers from different brands to cooperate on a single shared mesh instead of each building its own. What has to match is the Matter controller – the app that’s commissioning and controlling the device – not the border router underneath it.
What happens to my Thread devices if I get rid of my border router?
Devices that only needed local control generally keep working with each other since Thread doesn’t depend on a cloud connection for that. What breaks is anything routed through that specific box: remote access away from home, push notifications, and voice control through whichever app was paired to it. If you have more than one border router in the house, the mesh usually keeps functioning through the others.