What Your Matter Hub Actually Does (And What Breaks Without It)

“No hub required” is one of those smart home promises that is often technically defensible and practically incomplete. A Matter light bulb, plug, lock, or sensor may not need the old brand-specific box that earlier smart homes revolved around. But something in the home still has to add the device, manage it, expose it to an app or voice assistant, and—if the device uses Thread—connect it to the rest of the network.

That is why Matter devices need a hub in some setups and appear not to in others. The useful question is not whether Matter needs “a hub.” The useful question is which job you are asking that hub to do.

The word “hub” is hiding three different jobs

Matter did reduce dependence on proprietary hubs. It did not remove the need for smart home infrastructure. The confusion starts because manufacturers, app screens, and retailers use “hub” for several roles that are not interchangeable.

The Connectivity Standards Alliance says Matter devices need a Matter controller for commissioning and remote access, which is the first place the “hub-free” claim becomes too vague for actual setup work.[1] How-To Geek’s Matter explainer separates the controller, border router, bridge, and admin device roles for the same reason: each role solves a different problem.[2]

A single box can perform more than one role. A smart speaker might be both a Matter controller and a Thread border router. A legacy bridge might expose Zigbee bulbs into Matter but not provide Thread networking. The label on the box matters less than the role it actually supports.

The Matter controller is the part even Wi-Fi devices usually need

A Matter controller is the platform brain. It is the thing that receives the setup code, commissions the device onto your smart home, stores the relationship between that device and your chosen ecosystem, and keeps the device available through that ecosystem’s app, automations, scenes, voice assistant, and remote access.

This is where a lot of Wi-Fi Matter confusion comes from. A Wi-Fi or Ethernet Matter device uses your normal home network for communication. It does not need a Thread border router. It may even be capable of local network communication on the same LAN. But that does not mean it can be meaningfully used in a Matter smart home with no controller at all. Google’s Matter guidance and How-To Geek’s hub explainer both draw this narrower distinction: Wi-Fi or Ethernet Matter devices can communicate locally, but onboarding and remote access still depend on a controller.[3][4]

In practice, the missing controller shows up as an oddly familiar failure: the device has power, the phone can see something during setup, the Matter logo is on the packaging, and yet the device never becomes a normal member of the household’s smart home. Or it works only inside one app, without the expected platform automations, room assignments, shared control, or remote access.

For a Wi-Fi Matter bulb, plug, thermostat, or appliance, the short diagnosis is: you do not need a Thread border router, but you still need a Matter controller if you expect Matter setup, platform control, and remote use to work normally.

Thread devices need a border router, and there is no app-only workaround

Thread is different. A Matter-over-Thread device is not joining your Wi-Fi network. It is joining a low-power Thread mesh, and that mesh needs a Thread border router to connect it to the home’s IP network. Without that border router, a Thread lock, sensor, button, or bulb has nowhere useful to go.

Matter Alpha and matter-smarthome.de both describe the Thread border router as the required gateway between Thread devices and the broader home network.[5][6] This is not like skipping a nice-to-have accessory. If the device is Matter-over-Thread and the home has no compatible Thread border router, the device cannot function as intended.

That requirement matters most for the exact device categories people often buy Thread for: battery-powered sensors, locks, buttons, shades, and other devices where low power and mesh coverage are more attractive than Wi-Fi. It is also why a Matter smart lock can be “Matter-certified” and still fail the buyer’s expectation of universal compatibility. Certification tells you something important about the device’s protocol support; it does not mean your home already has the network role the device needs. For a closer look at that distinction, see what the Matter certification logo actually guarantees.

A Thread Matter device therefore has two infrastructure needs, not one: a Matter controller to commission and manage it, and a Thread border router to give it network reach. Many modern devices combine those roles, which is convenient. The roles are still separate.

A bridge is for older devices, not for every Matter device

A Matter bridge is the role people most often confuse with the older idea of a hub. It exists to bring certain non-Matter devices into a Matter environment. Think of legacy Zigbee bulbs, some proprietary sensors, or other devices that were designed around a manufacturer’s original bridge rather than around Matter itself.

Moving a home toward Matter does not magically rewrite the radios inside old devices. A Zigbee bulb remains a Zigbee bulb. If the manufacturer supports bridging, its bridge can present that device to a Matter controller in a more platform-neutral way. If not, the device may remain dependent on its original app or ecosystem.

This is why the sentence “Matter eliminates hubs” causes trouble in homes that already own years of Zigbee, Z-Wave, or proprietary gear. Matter may reduce the need to buy a new brand-specific hub for new Matter devices. It does not guarantee that every older device becomes native Matter hardware.

You may already own the missing role

The good news is that a Matter controller or Thread border router often is not a new purchase. It may already be sitting in the living room, kitchen, office, or network closet under a name that does not include the word “hub.”

Common examples include Amazon Echo devices such as the Echo 4th Gen, Echo Show devices, and eero 6-class routers; Google devices such as Nest Hub 2nd Gen, Nest Hub Max, Nest Wifi Pro, and Google TV Streamer; Apple devices such as HomePod Mini, HomePod 2nd Gen, and compatible Apple TV 4K models; and Samsung hardware such as SmartThings Hub v3, Aeotec Smart Home Hub, SmartThings Station, and select newer TVs.[3][7][8]

The exact role depends on the model and firmware. A device can be a Matter controller without being a Thread border router. Some devices are both. Some older smart speakers or displays may look similar to supported models but lack the necessary Matter or Thread support. That is why the model number matters more than the product family name.

If you want a practical inventory pass, start with Your Matter Smart Home Hub Might Already Be in Your Home. For a concrete example of one device that can cover both the controller and Thread border router roles, see the Google Nest Hub 2nd Gen device profile.

How to diagnose your own setup

Do not start with the word “hub.” Start with the device’s transport and age.

• If it is a Wi-Fi or Ethernet Matter device, you need a Matter controller for setup, platform control, remote access, sharing, scenes, and most automations.
• If it is a Thread Matter device, you need a Matter controller and a Thread border router.
• If it is an older non-Matter Zigbee, Z-Wave, or proprietary device, you may need a bridge that can expose it to Matter.
• If you already own a smart speaker, display, streaming box, mesh router, or SmartThings-class hub, verify which of these roles that exact model supports.

For a first Matter setup, this usually means choosing the controller before buying a pile of devices. The buying order is less exciting than the product packaging, but it prevents the hallway setup failure where the device is compatible in theory and stranded in practice. The step-by-step version is covered in Build Your First Matter Smart Home in 2026.

Why this question matters more in 2026

The Matter ecosystem is no longer a small early-adopter shelf. By early 2026, the Connectivity Standards Alliance had certified more than 750 Matter products, and matter-smarthome.de pointed to low-cost IKEA Matter products under $10 as one sign that the standard had moved into more accessible price ranges.[9]

That growth is useful context, not a guarantee of frictionless setup. More Matter products means more buyers will encounter the difference between a Wi-Fi Matter bulb, a Thread Matter lock, and an older Zigbee device that needs a bridge. It also means the Matter logo is doing only part of the communication job at the point of sale.

The Wi-Fi-versus-Thread choice is especially worth checking before purchase. A Wi-Fi Matter bulb can be simpler if your home already has strong Wi-Fi and you do not want to think about Thread. A Thread bulb or sensor can make sense in a home that already has a reliable Thread border router. If you are comparing bulbs specifically, Which Matter Smart Bulb Should You Buy? is the more device-focused place to make that trade-off.

Correct hardware still does not make every platform identical

Owning the right roles is necessary. It is not a promise that every ecosystem will expose every feature in the same way.

Thread compatibility across ecosystems is still uneven. Adam Dunkels’ device-type discussion notes that using a Thread border router from one ecosystem with a Thread device from another can still produce parallel Thread networks, even as Thread 1.4 aims to improve credential sharing.[10] For the person setting up a device, that can look absurd: there is Thread hardware in the house, but the new device still does not join the Thread network you expected.

Matter version support also varies by platform. As of early 2026, matter-smarthome.de reported that not all platforms supported Matter 1.5 features equally.[9] A controller can therefore be present, updated, and still not expose a newer device category or feature exactly as another ecosystem would.

So the practical checklist has two layers. First, confirm the required role: controller, Thread border router, or bridge. Then confirm the specific platform support for the device category and feature you care about. That second step is annoying, but it is less annoying than discovering it after the lock is mounted or the sensor is stuck to a door frame.

The plain answer

Matter has reduced the need for brand-specific hubs. It has not eliminated the need for home infrastructure.

A Wi-Fi Matter device needs a Matter controller for normal setup, remote access, sharing, and platform features. A Thread Matter device needs both a Matter controller and a Thread border router. An older non-Matter device may still need a bridge. In many homes, one existing smart speaker, display, router, streaming box, or smart home hub already covers one or more of those jobs. The part worth checking is which role is actually present, and which one is missing.

References

1. Matter FAQs — CSA-IOT
2. Matter Explained: Controllers, Bridges, Border Routers, and More — How-To Geek
3. Google Home Help — Google Home Help
4. Will I Need a Dedicated Hub? — How-To Geek
5. What is a Thread Border Router? — Matter Alpha
6. What is a Thread Border Router? — matter-smarthome.de
7. Matter standard — Wikipedia
8. Homey Wiki — Homey Wiki
9. The Matter Standard in 2026 – A Status Review — matter-smarthome.de
10. Device types article — Adam Dunkels