“Light is the first element of design; without it, there is no form, no space, no texture.”
Walk into any smart home showroom and ignore the spec sheets for a moment. Forget the logos, the protocols, the buzzwords printed on tiny cardboard boxes. Just look at the room. What you feel first is not “Matter 1.2” or “Thread mesh network.” What you feel is rhythm. A lamp that fades up without a jerk. Shades that lower in one smooth line. A hallway that brightens just before you step into it. When the technology recedes and the behavior of the space feels calm and predictable, that is when compatibility has actually done its job.
The tension people feel around hubs and Matter is not really about silicon or firmware. It is about whether their home will still “behave” in five years. Whether a light switch will still talk to a bulb after a company rebrands an app. Whether their living room scene still works when they change phones. The “hub dilemma” is just the latest way of asking a very old question: how do you keep a space simple while the infrastructure gets more complex underneath?
I tend to think of it like planning the electrical layout in a renovation. You do not start with “How many breakers can I add?” You start with “How should this room feel at 7pm on a winter night?” Warm, even, no glare, no hunting for switches in the dark. From there you work backward to circuits and code requirements. Smart home design works the same way. Begin with the emotional brief: “I want my home to feel coordinated, not chaotic.” The rest is scaffolding.
Matter promises a world where your devices speak a shared language. No brand fiefdoms, no fragile bridges that stop working when a company loses interest. That promise sounds clean on paper. In the real house, it is messier. There is the old Zigbee hub in the closet, the Wi-Fi cameras, that one Bluetooth lock that never quite cooperates, the smart TV with its own ideas. Then a box says “Matter compatible” and the natural question is: does this finally mean I can get rid of all these hubs?
Design is subjective, but the answer lives somewhere between “yes,” “not yet,” and “it depends what you mean by hub.” The trick is to separate what the standards bodies say from what your living room actually needs. A good home feels legible. You should be able to point to one mental center of gravity, even if there are several silent brains doing background work.
The myth of the single hub
“Form follows function.”
For over a decade, the consumer smart home has been hub-centric. One plastic puck in the corner, wired into your router, advertised as the “brain” of it all. In practice, many homes ended up with several brains: a Zigbee bridge for bulbs, a proprietary bridge for shades, another box for cameras, a mesh router that wants to be a hub on the side. The result: a hardware junk drawer that happens to have Ethernet ports.
Matter tries to flip that script. Instead of one monolithic hub, it treats the network itself as the structure, and each capable device as both client and contributor. Your smart speaker, your TV, your router: each can discover and coordinate devices. The hub becomes more of a role than a box.
That shift is powerful, but it also creates new categories that sound abstract when you first meet them: “Border routers,” “controllers,” “bridges.” They are easy to confuse, and marketing does not help. So let us ground them in a room.
Picture a modest apartment: one living room, a bedroom, small kitchen, maybe a hallway. Right now, you might have:
– Wi-Fi bulbs that talk straight to your router
– A Zigbee hub for a few older sensors
– Two smart speakers
– A smart lock on the front door
– A thermostat over by the hallway
On the coffee table, your phone acts as the remote for most of this. Sometimes the automation lives in the hub. Sometimes in the cloud. Sometimes in the app that came with a device. The intelligence is scattered.
Matter says: “Pull the intelligence into a shared standard. Let many things act as controllers. Give each device a common dictionary.” So your living room speaker can set a scene that includes a plug from one brand, a lamp from another, and a future blind you have not bought yet, provided they all speak Matter.
The psychological dilemma appears right here. If all of these devices can speak Matter, do you still “need” a hub, or has everything quietly become a hub? The answer depends on your tolerance for complexity and what you want your home to remember when you are not actively thinking about it.
What Matter actually is in your house
“Architecture is the thoughtful making of space.”
Marketing talks about Matter like a logo. From a design point of view, it is more helpful to treat it as a building code. When you renovate an old warehouse, the code does not tell you how your living room should feel; it sets rules for structure, fire safety, and circulation. Matter does the same thing for devices: a shared way to describe a light, a lock, a sensor, a scene.
Three concepts are worth separating, because they show up in the hub dilemma again and again:
1. Controllers: who holds the memory
A Matter controller is a device that can pair, configure, and control other Matter devices. It also often holds your automations and scenes. Today, this is usually:
– Your phone
– A smart speaker or display
– A home hub built into an OS (HomePod, certain smart speakers, some TVs, some routers)
In practice, the controller is where your home’s “habits” live. When the sun sets and your lights fade up, the logic for that behavior is usually stored in a controller device. From a design perspective, you want that memory to feel anchored. There should be a clear answer to “Where do my scenes live?”
If you think visually, imagine a subtle diagram: circles for devices, one or two darker circles for controllers. You do not want a dozen dark circles, one for each brand. Matter allows consolidation, but it does not enforce it. You still choose a “primary brain,” even if other devices can also send commands.
2. Border routers: Thread’s quiet bridges
Matter supports several transport layers: Wi-Fi, Ethernet, and Thread. Thread is the one that confuses people. It is a low-power mesh for small devices, designed so battery sensors and switches can talk reliably without each one needing Wi-Fi. A “border router” connects a Thread mesh to your main IP network.
Many products now include a Thread border router alongside other roles: a smart speaker, a TV, a plug-in hub. So suddenly you have three border routers without trying. That feels like the old hub sprawl all over again, only with nicer acronyms.
The key difference is that multiple Thread border routers can coexist and cooperate. You do not have to pick a single physical hub. But from an architectural mindset, you still want a clean mental model: one or two fixed devices in stable locations acting as your main Thread anchors. Treat them like structural columns. They may be hidden, but their placement sets the tone for reliability.
3. Bridges: the translators for your old gear
Bridges sit between Matter and older ecosystems. A Zigbee bridge, for example, can expose your existing bulbs and sensors as Matter devices to the rest of your home. That is where the hub dilemma gets subtle. A bridge is a hub in disguise. It may not say “hub” on the label, but it hosts older protocols and makes them look modern.
This is not a bad thing. From a sustainability point of view, keeping older products alive through a bridge is often better than throwing everything out for the sake of purity. But it does mean you will probably keep at least one “legacy brain” around if you have a lot of pre-Matter gear. The trick is to keep that role quiet and well-defined, not scattered across competing boxes.
Material thinking for invisible infrastructure
When you design a kitchen, you do not choose marble only because it is pretty. You look at patina, maintenance, how much you cook, how you feel about staining. You ask what this surface will look like on a Tuesday night in bad light. Smart home protocols deserve the same material thinking. They are invisible, but they age, they gather technical patina, they show their quality when something fails.
Here is a way to think about the “materials” of your smart home network in simple, physical terms:
| Layer / “Material” | What it feels like in daily use | Strengths | Weaknesses |
|---|---|---|---|
| Wi-Fi devices | Direct, often quick to respond, live on your main network | Easy setup, wide support, no extra hubs | More radio noise, higher power draw, can feel fragile during router glitches |
| Thread devices | Quiet, stable, fade into the background once set up | Low power, strong mesh, built for small sensors and switches | Needs Thread border routers, tooling is still maturing |
| Zigbee via bridge | Older but proven; works well when the bridge is solid | Large existing catalog, inexpensive devices | Relies on a single bridge, integration varies by brand |
| Cloud-only devices | Can feel laggy or inconsistent, break when the vendor has issues | Rich features from vendor apps, remote access by default | Dependent on internet and vendor support, privacy questions |
Matter’s role is to sit over Wi-Fi and Thread, and in some cases over bridges for Zigbee, and give you a single design language. When you dim a light from a phone, you should not care which “material” it uses. You care that it responds smoothly and predictably.
In architecture, mixing materials thoughtfully creates depth. Concrete for structure, wood for touch points, glass for light. In a smart home, the combination of Wi-Fi, Thread, and a few bridges can create similar depth, if it is intentional. The home feels composed instead of accidental.
The realistic future of hubs
The phrase “hub-free” sounds tempting. A house where every device just appears, speaks Matter, and follows your routines. No bridges hidden behind televisions, no panels on the wall that stop working when a company gets acquired.
The reality is closer to “fewer hubs” and “clearer roles.” The future looks like this in a typical home:
– Your router or mesh system includes Matter controller functions and often Thread
– Your main smart speaker or display is also a Matter controller and Thread border router
– A few legacy bridges stay for blinds, older bulbs, or cameras
Functionally, you still have hubs. Psychologically, you do not have to think of them as separate purchases. They arrive embedded in devices you already want to own for other reasons: better Wi-Fi, better sound, a better screen on the wall.
From a design standpoint, what matters is where your routines live and how many apps you actually need to touch. If you can open one primary app to adjust 90 percent of your home behavior, you experience harmony. The remaining 10 percent can live in specialist apps without ruining the composition, just as a single accent chair can break the rules of an otherwise minimal room.
Shadow hubs vs. intentional hubs
The real danger going forward is not owning “too many hubs” as hardware. It is letting “shadow hubs” take over. These are the hidden brains you never intentionally chose: a camera cloud running its own notifications, a TV’s built-in automation engine, a lighting app that tries to schedule its own sunrise effects.
You end up with layers of partially overlapping automations. A hallway light that turns on because your motion sensor told Matter to do it, and also because the bulb’s own app still has a legacy schedule running from last year. The behavior feels haunted. Not in an interesting way.
So while Matter makes technical hubs less visible, it forces a more architectural discipline. You choose:
– One main place where schedules and scenes live
– One or two devices that act as permanent structural hubs (router, speaker, maybe a dedicated box)
– Clear boundaries for what brand-specific apps are allowed to control
The goal is not zero hubs. The goal is a small, intentional core, with everything else stripped of “brain” responsibilities and reduced to texture: sensors, actuators, surfaces.
Planning a Matter-first smart home like a floor plan
Imagine you are sketching a floor plan instead of a wiring diagram. Start with zones and feelings:
– Entry: clarity, security, welcoming
– Living: soft ambient light, simple media controls
– Kitchen: task lighting, predictable ventilation, maybe presence-aware lights
– Bedroom: quiet, warm, no harsh status LEDs, gentle wake-up
Now translate that into Matter and hubs, but in plain language:
1. Decide your “center of gravity”
You need one anchor platform where your scenes and automations live. That might be:
– The native home platform on your phone
– The ecosystem around your smart speakers
– A dedicated automation platform that now speaks Matter
From a design perspective, this is like picking the dominant material in a room. You can mix others, but one should set the tone. Once you choose, commit. Pair new Matter devices through that lens whenever you can.
2. Establish structural devices
Pick the few devices that will always be present and powered:
– Main router or mesh nodes in stable locations
– A couple of speakers or displays in central rooms
– Any dedicated hub you are willing to hide and forget for five years
These become your “columns” for Thread and your main controllers. If you have a choice, prefer gear that:
– Has reliable power, not on a wall switch
– Sits roughly central in the home for better radio coverage
– Comes from brands that tend to support products for longer cycles
I tend to prefer routers or speakers with integrated Thread, because they already want to be central objects in a tech sense. That keeps the mental model clean.
3. Treat legacy hubs as transition joints
If you own a pile of Zigbee bulbs or older sensors, use their bridge as a transitional joint between the old world and Matter. But strip it of extra features when your main platform supports Matter bridges. Turn off duplicate schedules and routines in the old app once you re-create them in your main Matter-aware system.
In architecture, a good transition joint is one you do not notice. The material changes under your feet, but the path feels continuous. Your smart home should do the same thing when a bulb silently goes from “Zigbee-only” to “Zigbee behind a Matter bridge.”
Compatibility as a design constraint, not a checklist
When people ask “Will Matter fix compatibility?” they usually mean “Can I stop worrying about things breaking when I mix brands?” The honest answer: it will reduce random breakage, especially for basic functions. A Matter light will turn on and off reliably from a Matter controller, across vendors. A Matter lock will expose a similar set of controls to various platforms.
Where things stay messy is at the edges:
– Complex features that exceed the basic “shape” Matter defines
– Vendor-specific behaviors like advanced video analytics
– Timing and quality of firmware updates
Think of it like building a house with a shared drawing standard. The doors all have standardized sizes and swing directions. That helps coordination immensely. But one manufacturer may still offer a nicer closer mechanism, or a special hinge your platform cannot yet control in full.
For your home, the result is:
– Simple behavior (on/off, dim, lock/unlock, open/close, temperature setpoint) becomes fairly safe to mix and match.
– More complex behavior (special color scenes, custom camera zones, vendor AI features) often still lives inside the vendor app or special integrations.
Once you accept that, the hub dilemma softens. You stop asking “Can Matter solve everything so I never think about hubs again?” and start asking “Can Matter cover the quiet, everyday 80 percent, so the remaining 20 percent is a conscious design choice, not a pile of hacks?”
Comparing “hub futures” the way you compare finishes
When clients look at two pieces of stone, they rarely ask “Which one is technically better?” They ask “How will this make the kitchen feel after it has been lived in?” You can apply the same mindset to how you intend to structure your home around Matter.
| Hub Strategy | What it looks like | Upsides | Tradeoffs |
|---|---|---|---|
| “Hubless” (everything in speakers/TV/router) | No separate boxes; controllers and Thread live in multi-function devices | Less visible clutter, fewer wires, simpler inventory | Reliant on consumer gear lifecycles, occasional vendor lock-in feelings |
| “Hybrid spine” (one dedicated hub plus embedded ones) | One neutral automation hub, plus Matter/Thread in other gear | More control, often deeper automation features, flexibility to switch ecosystems | One extra box to maintain, slightly higher complexity |
| “Brand archipelago” (many vendor hubs) | Separate boxes for lighting, blinds, security, appliances | Full access to each brand’s advanced features | More apps, higher mental load, harder to maintain scenes across systems |
Matter gently nudges you away from the “archipelago.” It does not completely kill it, because some categories still want their own logic. But it gives you enough shared ground that a hybrid spine or a hubless model becomes realistic.
From a design point of view, I prefer the hybrid spine in most homes. A quiet central brain for complex automations, with Matter to tie in vendor devices, and a couple of visible consumer objects that double as controllers and border routers. It is similar to exposing one structural beam on the ceiling: you acknowledge the system, but you do not let it dominate the room.
Practical cues for choosing Matter devices now
Design is subjective, but when picking hardware in this period of transition, a few cues can keep your future options open without turning your home into a lab.
1. Favor native Matter support where it covers your needs
If a light, plug, or basic sensor offers Matter out of the box, that is often the cleanest route. Native Matter support means:
– Fewer proprietary bridges
– Better chance of working across phone platforms
– A simpler pairing story in a few years when apps and ecosystems shift
You will give up some brand-specific extras sometimes, like elaborate lighting scenes or experimental features, but for core behaviors, native Matter usually feels more “architectural” and less “gadget.”
2. When something uses a bridge, verify its Matter bridge roadmap
For devices that almost always come with a hub or bridge, such as certain shades or older lighting systems, check whether:
– The bridge already exposes Matter endpoints
– Or the vendor has a clear timeline and track record for updates
This is less about “future-proofing” in a marketing sense and more about giving your home a stable wiring diagram in your head. If the bridge turns its devices into Matter participants, you can treat that brand as another material in your palette, not a separate island.
3. Avoid stacking clouds for critical functions
Security, door locks, and primary lighting behave better when the control path stays local as much as possible. Matter is good at that: controller to device, on your own network. When you chain several cloud services on top, you introduce a sort of digital echo. From a tactile point of view, you start to feel lag and uncertainty in the switches you touch each day.
So for these categories, lean toward devices that:
– Offer strong local Matter control
– Keep cloud features as optional extras rather than the only path
This way, the home’s daily rhythm does not depend heavily on someone else’s server uptime.
The “feel” of a Matter home
Strip the logos off every device and just walk your future Matter home:
– You speak to a room, not a brand, and the lights respond in a coordinated way, even if they are from three manufacturers.
– You press a physical switch by the door, and the response is crisp. No roulette wheel of “Will this one sync with that one today?”
– Your phone changes, or your voice assistant allegiance shifts, and you rebuild your control surfaces without replacing half the hardware.
That feeling comes from a few simple architectural moves:
– Limit where intelligence lives
– Prefer shared standards for basic behavior
– Treat hubs as structure, not decoration
You still have a hub dilemma, but it is not the old “How many boxes should I hide in the media cabinet?” question. It becomes “Which devices am I comfortable trusting with the long-term memory of this house?” That is a nicer question to solve. It feels closer to choosing where to put a built-in bookshelf than deciding where an extension cord can reach.
In that sense, Matter is less a total reset and more like introducing concrete into a town of timber-framed houses. The old beams do not vanish overnight, and some are beautiful. But the new material gives you spans and shapes that were hard to achieve before. If you treat it thoughtfully, compatibility stops being a fragile trick and starts feeling like part of the building.