Somewhere between “smart plugs work straight out of the box with just Wi-Fi” and “you need a hub for anything serious,” most people setting up a connected home in 2026 get stuck on one deceptively simple question: do I actually need a smart home hub, or is it a relic I can skip? The honest answer is that the hub did not disappear — it changed shape, hid inside devices you may already own, and split into two different jobs that people constantly confuse. Skip the wrong one and half your future devices will not work; buy the wrong one and you have spent money on a box you did not need. The real question is not “hub or no hub” but “which of the two hub jobs does my specific plan require, and do I already own something that does it?” This guide is the decision framework we wish someone had drawn for us before we bought — or wrongly skipped — anything. As an Amazon Associate I earn from qualifying purchases.
We are the Smart Home Guide Editors at smarthomeguide24.com. “Do I need a hub?” is one of the most common questions we answer, and it is genuinely hard to resolve from product pages, because manufacturers have strong incentives to either sell you a hub or claim you will never need one, and both messages are half-true. What follows is built from how the major protocols and ecosystems actually work in 2026, the real overlap between “hubs” and devices you likely already have, and the patterns that determine whether a hubless setup stays happy or hits a wall. We keep brand names general where the behavior is a property of the architecture rather than any one product, because the hub question is about plumbing, not logos.
The two jobs a “hub” actually does
The word “hub” is overloaded, and almost every argument about whether you need one is really two people talking about two different jobs. Separating them dissolves most of the confusion.
Job one: the controller (the brain). Something has to hold your automations, run your routines, respond to voice, and give you one app to control everything. In 2026 this job is almost always done by an ecosystem — Alexa, Google Home, Apple Home, or SmartThings — running on a device you already own or a cheap speaker. You essentially cannot avoid having a controller; the only question is which one. This is the job people mean when they say “you always need a hub” — and they are right, but the hub here is usually a smart speaker or your phone, not a dedicated box.
Job two: the radio bridge (the translator). Some devices do not speak Wi-Fi. Zigbee, Z-Wave, and Thread devices talk in low-power radio languages your router cannot hear, so something must translate between those radios and your network. That translator is a bridge or border router. This is the job people mean when they say “you don’t need a hub anymore” — because for Wi-Fi and some Thread devices, the translation is either unnecessary or already built into a speaker you own.
Once you see the two jobs separately, the whole decision becomes tractable: you always need a controller, and you need a radio bridge only if you buy devices that speak Zigbee, Z-Wave, or Thread. Whether that adds up to buying a dedicated hub depends entirely on what those two needs look like for your plan.
The decision matrix
Here is the framework in one place. Find the row that matches the kind of devices you intend to buy, and it tells you what you actually need.
| Your device plan | Controller needed? | Radio bridge needed? | Dedicated hub to buy? |
|---|---|---|---|
| Only Wi-Fi devices (many plugs, cameras, some bulbs) | Yes — an ecosystem app/speaker | No | No hub needed at all |
| Matter-over-Wi-Fi devices | Yes | No | No hub needed |
| Matter-over-Thread devices | Yes | Yes — a Thread border router | Often already in a speaker you own |
| Zigbee devices | Yes | Yes — a Zigbee bridge | Yes, unless a speaker has one built in |
| Z-Wave devices | Yes | Yes — a Z-Wave bridge | Yes — a dedicated hub, almost always |
The pattern that emerges: the more your plan leans on Wi-Fi and Matter-over-Thread, the more likely you already own everything you need. The more it leans on Zigbee and especially Z-Wave, the more likely you need a genuine dedicated hub. And the crucial middle case — Matter-over-Thread — is where “the hub you already own” quietly saves most people money, because a modern smart speaker or streaming device increasingly includes a Thread border router at no extra cost.
The hub you probably already own
This is the fact that changes the math for most households in 2026: the radio bridge is increasingly built into devices bought for other reasons. Many current smart speakers and smart displays include a Thread border router, and some include a Zigbee radio too. A streaming/TV device from a major ecosystem may act as a Matter controller and a Thread border router. If you already own one of these, you may have both hub jobs covered without ever having bought something called a “hub.”
The practical move is to inventory what you own before you buy anything. Check whether your smart speaker, display, or streaming box lists Thread or Zigbee support in its specs. If it does, a whole category of “you need a hub” advice simply does not apply to you — you can buy Matter-over-Thread devices and they will join through the border router already sitting in your living room. This is exactly why blanket answers (“you always need a hub” / “you never need a hub”) are both wrong: the right answer depends on which radios your existing devices already provide.
Where this breaks down is Z-Wave. Z-Wave is a mature, reliable, long-range protocol beloved for locks and sensors, but its radio is rarely built into general-purpose speakers, so a Z-Wave plan almost always means buying a dedicated hub that includes a Z-Wave radio. If your heart is set on specific Z-Wave gear, budget for that hub from the start rather than discovering the requirement after the devices arrive.
What you gain by adding a dedicated hub anyway
Even when you can technically go hubless, a dedicated hub can be worth buying for reasons that have nothing to do with radio translation. Understanding these helps you decide whether the box earns its place.
Local processing and speed. A dedicated hub often runs your automations locally, on the box itself, rather than round-tripping to a cloud. That means a motion-triggered light fires instantly and keeps working during an internet outage. A purely cloud-dependent, speaker-based setup can lag or stall when the internet does.
Protocol breadth in one place. A good hub speaks several radios at once — Zigbee, Z-Wave, Thread, Matter — so you can mix devices from any protocol and manage them in a single system. This is genuinely valuable if you expect to buy across protocols over time, because it removes the “which radio does this need” question from every future purchase.
Reliability and independence. A hub that processes locally is not at the mercy of a single ecosystem’s cloud uptime or business decisions. For households automating things that matter — security sensors, locks, climate — that independence is worth real money.
| Approach | Best for | Trade-off |
|---|---|---|
| Hubless (speaker/app as controller) | Wi-Fi + Matter-over-Thread homes, simple setups | More cloud-dependent; limited to built-in radios |
| Dedicated multi-protocol hub | Mixed-protocol homes, local automations, reliability | Upfront cost; one more box to manage |
| Hybrid (speaker + one hub) | Most growing homes | Slight complexity; but covers every case |
When you can confidently skip the hub
You can go fully hubless, and stay happy, if your plan fits a recognizable profile. You are buying mostly Wi-Fi devices and Matter-over-Thread devices. You already own a smart speaker or display that acts as a controller and, ideally, a Thread border router. Your automations are simple enough that occasional cloud dependence is acceptable — lights on a schedule, a plug on voice, a camera you check on your phone. And you are not planning to build security-critical automations that must survive an internet outage. If that describes you, buying a dedicated hub would be spending money to solve a problem you do not have.
The renter’s case is a strong version of this. Renters typically want minimal, non-permanent, Wi-Fi and Matter devices they can unplug and take with them, controlled by a speaker and a phone. For that profile, a dedicated hub is usually pure overhead, and a hubless setup is not a compromise — it is the correct architecture. The mistake renters make is not skipping the hub; it is buying Zigbee or Z-Wave gear that needs one, when equivalent Wi-Fi or Matter devices would have kept the setup hub-free and portable.
When you genuinely need one
Certain plans make a dedicated hub not optional but necessary, and recognizing yourself in these profiles early saves a frustrating false start. You need a hub if you are committing to Z-Wave devices, because the radio is almost never built into general-purpose gear. You need one if you want local automations that survive internet outages for anything important. You need one if you are building a large, mixed-protocol home where a single system managing Zigbee, Z-Wave, Thread, and Matter together is worth far more than juggling several apps. And you benefit from one if you want the fastest, most reliable automations, because local processing beats cloud round-trips every time.
There is also a subtler case: the home that starts hubless and grows into needing one. Many people begin with a few Wi-Fi plugs and a speaker, then discover the specific sensor or lock they want speaks Zigbee or Z-Wave, or that their cloud-based automations feel sluggish. Adding a hub at that point is perfectly fine — nothing you already own is wasted — but if you can see that trajectory coming, buying a capable multi-protocol hub earlier saves you from re-buying devices you chose only because they avoided a hub you were always going to need.
Zigbee, Z-Wave, and Thread: which bridge each really needs
Because the radio-bridge decision drives whether you buy a dedicated hub, it pays to understand how the three low-power protocols differ in what they demand of you. They are often lumped together as “the ones that need a hub,” but their requirements and payoffs are quite different, and matching your plan to the right one avoids buying a bridge you did not have to.
| Protocol | Bridge required | Strengths | Who it suits |
|---|---|---|---|
| Thread | Thread border router — often built into a speaker/streamer you own | Low power, self-healing mesh, native to Matter, no vendor lock-in | New builders who want Matter with the least extra hardware |
| Zigbee | Zigbee bridge — sometimes in a speaker, often a dedicated hub | Huge cheap device catalog, mature mesh | Budget-focused homes buying many inexpensive devices |
| Z-Wave | Z-Wave bridge — almost always a dedicated hub | Long range, quiet sub-GHz band, rock-solid for locks/sensors | Large or Wi-Fi-congested homes, security-focused setups |
The single most useful insight in this table is the Thread row: because a Thread border router is increasingly free inside devices you buy for other reasons, a Thread-based plan is the cheapest path to a capable, hub-light smart home. Zigbee sits in the middle — sometimes your speaker already bridges it, sometimes you need a hub — and its payoff is the sheer volume of cheap devices available. Z-Wave sits at the far end: you will almost certainly buy a dedicated hub, but you get range and reliability that genuinely matter in big or radio-noisy homes. None of these is “best”; they are different trades, and the bridge cost should be weighed as part of the total, not treated as an afterthought.
A common and costly mistake is buying a device purely because it advertises “no hub required” — which usually means it is Wi-Fi — without noticing that a house full of individual Wi-Fi devices strains a consumer router far faster than the same number of mesh devices sharing one bridge. “No hub” is not automatically simpler at scale; past a couple dozen devices, a mesh protocol behind one bridge is often the calmer, more reliable architecture even though it required a hub to start.
What it actually costs, three ways
Money is usually the real question hiding under “do I need a hub,” so it helps to see the three paths priced as whole systems rather than as individual boxes. The cheapest path is fully hubless: a smart speaker you may already own as the controller, plus Wi-Fi and Matter-over-Thread devices that need no separate bridge. Your only “infrastructure” spend is the speaker, and often that is already bought. The middle path is speaker plus one dedicated hub, which adds the cost of a multi-protocol hub but unlocks Zigbee, Z-Wave, and local automations — worthwhile the moment you want protocol freedom or outage-proof reliability. The most expensive mistake is the accidental path: going hubless, buying a few devices, discovering one needs a bridge, buying a single-protocol bridge for it, then later needing another — ending up with several partial boxes that a single capable hub would have replaced for less.
The lesson is to price the system you will likely grow into, not just the first three devices. If your honest trajectory is “a handful of plugs and a bulb, forever,” stay hubless and spend nothing extra. If your trajectory is “this is going to grow, and I care about reliability,” a single good multi-protocol hub bought early is usually cheaper over two years than the drip-drip of single-purpose bridges bought reactively. The trap is not spending too much or too little up front; it is buying reactively in a sequence that no one would have chosen on purpose.
Future-proofing the decision without overspending
The good news in 2026 is that the hub decision is far less permanent than it used to be, because Matter lets systems coexist. You can start hubless and add a hub later without stranding anything you already bought, provided you did not paint yourself into a single-vendor corner. A few habits keep your options open. Favor devices that support Matter where a good option exists, because a Matter device can be adopted by whatever controller and bridge you add later. Prefer a controller and any hub that still receive regular firmware updates, since an abandoned hub is the one component that can genuinely strand you. And if you do buy a dedicated hub, lean toward a multi-protocol one that speaks Thread, Zigbee, Z-Wave, and Matter together, so a future device from any protocol slots in without a second box.
What you are really future-proofing against is not “choosing the wrong hub” but scattering money across incompatible islands with nothing tying them together. The households that get stranded are not the ones who guessed wrong on hub timing; they are the ones who bought impulsively across three ecosystems and two orphaned single-protocol bridges. Buy deliberately, keep a coherent center of gravity, make sure whatever you own can bridge into Matter, and the specific hub decision becomes reversible and low-stakes — which is exactly how it should feel.
The mistakes that cost people money
A handful of avoidable errors account for most of the wasted spend we see around the hub question. The first is buying a hub before knowing which radios you need — purchasing an expensive multi-protocol hub for a home that will only ever run Wi-Fi plugs, where a free app would have done the whole controller job. The second is the mirror image: refusing any hub on principle and then buying a string of single-protocol bridges reactively, spending more in total than one good hub would have cost. The third is ignoring what you already own — buying a Thread border router when the speaker on the shelf already includes one. The fourth is scattering automations across a hub and an ecosystem so neither has the full picture, producing the flickering-light conflicts that make a home feel possessed.
Every one of these is prevented by the same two-step audit: separate the controller job from the radio-bridge job, then inventory what you already own against what your device plan actually requires. Do that once, honestly, and you will neither over-buy a box you do not need nor get stranded by a protocol you cannot bridge. The hub question only feels hard because the two jobs get blurred and the existing hardware gets overlooked; pull those apart and the answer is usually obvious.
A simple path for the undecided
If you are still not sure, here is a sequence that keeps costs low and options open. Start by using your phone and a free ecosystem app as your controller, and buy one or two Matter devices — a plug and a bulb — because Matter devices travel with you no matter what you add later. If you already own a smart speaker with a Thread border router, buy your next few devices as Matter-over-Thread and enjoy a hub-light home. Only when you hit a concrete wall — a specific Zigbee or Z-Wave device you want, or automations that feel too slow or too internet-dependent — add a single capable multi-protocol hub, at which point nothing you bought is wasted and everything gains local speed and protocol freedom. This path never spends ahead of a real need, never strands a device, and lets the home tell you when a hub has become worth it rather than guessing on day one.
Whichever way you go, keep the foundation boring and solid. A first device that doubles as infrastructure is the smart buy: a Matter smart plug gives you an easy win and a Thread repeater in one, and a multi-protocol hub, when you actually need it, future-proofs every purchase after it. Buy the controller you were always going to need, add the bridge only when a device demands it, and the hub question resolves itself into a short, cheap, reversible set of steps.
Frequently asked questions
Does Matter mean hubs are dead? No — Matter reduced the need for a hub as a controller monopoly, but it did not eliminate the radio-bridge job. Matter-over-Thread devices still need a Thread border router, which is a hub job even when it lives inside a speaker. Matter made hubs less visible and more shareable, not obsolete.
Is my smart speaker a hub? Often, partly. Most smart speakers act as a controller, and many modern ones also include a Thread border router and sometimes a Zigbee radio. Check your specific model’s specs — if it lists Thread or Zigbee, it is doing a radio-bridge job too, and you may need no other hub.
Can I use more than one hub? Yes, and larger homes often do — for example a speaker acting as a Thread border router plus a dedicated multi-protocol hub for Zigbee and Z-Wave. Multiple Thread border routers actually strengthen a Thread mesh. The thing to avoid is scattering your automations across multiple systems; keep the logic in one place even if the radios live in several.
Will a hub make my devices faster? Frequently, yes, if it processes automations locally instead of via the cloud. A local hub fires automations in milliseconds and keeps them running during an outage, whereas a purely cloud-based, speaker-only setup can lag or pause when the internet does.
I only want a few smart plugs and a bulb. Do I need anything? Just a controller, which your phone plus a free ecosystem app already provides, or a cheap smart speaker if you want voice. No dedicated hub, no bridge — Wi-Fi and Matter-over-Wi-Fi devices need nothing more. This is the majority case, and it is genuinely as simple as it sounds.
How a hubless home behaves during an internet outage
One factor decides more hub purchases than any spec sheet: what happens when your internet goes down. A purely hubless, cloud-dependent setup — Wi-Fi devices controlled through an ecosystem that processes automations in the cloud — can go partly or fully deaf during an outage. Voice commands that route to a cloud assistant stop working, and any automation that depends on that cloud pauses until service returns. For lights on a schedule this is a mild annoyance; for a lock, a security sensor, or a thermostat in extreme weather, it can matter a great deal.
The nuance is that not all hubless setups are equally fragile. Matter’s design pushes control local, so many Matter devices can still be operated directly from a phone on the same network even when the wider internet is down, and Matter-over-Thread devices controlled by a local border router are more resilient than old cloud-relay Wi-Fi gear. But automations — the “if motion then light” logic — are only as reliable as wherever they run. If that logic lives in a cloud, the outage takes it with it. This is the strongest single argument for a dedicated hub that processes automations locally: it is not about radios at all, it is about keeping your home’s reflexes working when the connection to the outside world does not. Households automating anything they would hate to lose during an outage should weigh this heavily, because it is precisely the scenario a local hub is built to survive.
Matching the decision to your home’s size and walls
Physical scale quietly pushes the hub decision, and it is worth factoring in before you buy. A small apartment with a handful of devices, all within easy radio range of a central speaker, is the ideal hubless candidate — short distances mean Wi-Fi and Thread reach everything, and there is little to gain from a dedicated box. A large or multi-floor house is a different animal: distances stretch, walls multiply, and the long-range, quiet-band strengths of Z-Wave (which requires a hub) start to look attractive precisely because Wi-Fi congestion and range limits bite harder. The bigger and more radio-hostile the building, the more a capable hub with strong low-power radios earns its place.
Construction matters as much as square footage. Brick, plaster-and-lath, and homes with lots of metal behave like they have extra walls, shortening every radio’s reach and making a robust mesh — and the hub that anchors it — more valuable. A sprawling single-story home with thin drywall may stay perfectly happy hubless, while a compact but brick-walled townhouse might benefit from a hub sooner than its size suggests. When in doubt, let the building vote: open, small, and modern leans hubless; large, old, or dense leans toward a dedicated multi-protocol hub.
More frequently asked questions
Can I run my whole smart home from just my phone? For control, largely yes — a free ecosystem app on your phone is a perfectly good controller for Wi-Fi and Matter devices, and it can trigger automations while it and the devices are on your network. The limits appear with automations that need to run when your phone is away or asleep, and with devices that need a radio bridge your phone cannot provide. For a simple home, though, phone-plus-app genuinely is the entire “hub” you need.
Is a dedicated hub more secure than a hubless setup? It can be, mainly because local processing means less of your home’s activity depends on and travels to a cloud. A hub that runs automations locally exposes a smaller cloud footprint. That said, security depends far more on strong passwords, keeping firmware updated, and buying reputable devices than on the presence of a hub. Do not buy a hub expecting security by itself; buy good habits alongside whatever architecture you choose.
If I already have a smart speaker, should I still buy a hub? Only if your device plan needs a radio your speaker lacks (commonly Z-Wave, sometimes Zigbee) or you want fast, outage-proof local automations. If your speaker already provides a Thread border router and you are buying Matter devices, a second hub is usually redundant. Check your speaker’s specs first — the answer is often “you already have what you need.”
Do hubs go obsolete and strand my devices? A hub that stops receiving updates is the one component that can genuinely strand you, which is why update longevity matters more than raw features when choosing one. Buying a Matter-capable, multi-protocol hub from a maker with a good update track record minimizes this risk, because even if you replace the hub later, Matter devices can be re-adopted by the new one. Single-vendor, cloud-locked hubs carry the most obsolescence risk.
What’s the single most common right answer in 2026? For a typical household starting today, it is: use a smart speaker or your phone as the controller, buy Matter devices (over Wi-Fi or Thread), lean on the Thread border router your speaker likely already includes, and skip a dedicated hub until a specific Z-Wave device or a reliability need forces the issue. That path covers the majority of homes at the lowest cost and the least complexity, and it never strands a purchase — which is why “you probably don’t need a dedicated hub yet, but keep the door open” is the honest default for most people.
Step back and the pattern is reassuring: the hub question feels intimidating only because the industry has strong incentives to answer it for you in whichever direction sells a box. Strip those incentives away and it reduces to a short, honest audit of two jobs and one inventory. Separate the controller from the radio bridge, look at what your speakers and streamers already provide, and match the gap against the protocols your device plan truly needs. Nine times out of ten the answer is cheaper and simpler than the marketing implied, and on the tenth — the Z-Wave lover, the outage-proof security build, the sprawling brick house — the case for a dedicated hub is clear enough that you will not second-guess it.
The bottom line
The “do I need a hub?” debate is really two questions wearing one coat. You always need a controller — a brain to run automations and give you one app — and in 2026 that is almost always an ecosystem running on a speaker or your phone, not a dedicated box. You need a radio bridge only if you buy Zigbee, Z-Wave, or Thread devices, and for Thread that bridge is increasingly built into a speaker you already own. Wi-Fi and Matter-over-Thread homes can very often skip a dedicated hub entirely; Z-Wave and mixed-protocol homes that want fast, outage-proof local automations should buy one on purpose.
So inventory what you already own, decide which protocols your plan really needs, and let those two facts — not a manufacturer’s slogan — make the call. When you do build, the cheap accessories that keep any setup stable are the same regardless of the hub decision: hardwire your controller or border router with a solid Ethernet cable so its connection is never the weak link, keep a mains-powered Matter smart plug around as a Thread repeater and easy first device, and label your hubs and cables so you always know which box is doing which job. Decide on purpose, and the hub question stops being intimidating and becomes a ten-minute audit.