across 3 concrete floors
across 3 concrete floors
The 3-Floor Test: Real Data, Real Building
Late 2025. A 3-floor office building with approximately 60 smart LED downlights per floor — roughly 180 nodes total. Same driver hardware: Lifud Zigbee on one set, Lifud Matter/Thread on the other. This eliminated the driver as a variable. The only difference was the wireless protocol stack.
The building is typical commercial construction: concrete floors between levels, drywall partitions, metal studs, and standard office furnishings — metal shelving in storage rooms, suspended ceiling grids, the works. Not a lab. A real building.
Latency: Switch Press to Light Response
Measured from the instant a wireless switch sends its command to the moment the first photon hits the light meter. Lower is better. Every millisecond matters when you're standing in a dark hallway waiting for the lights.
| Scenario | Zigbee 3.0 | Matter Over Thread | Delta |
|---|---|---|---|
| Same room, clear line of sight | 120ms | 180ms | +50% (Matter slower) |
| Same floor, 1 wall | 150ms | 280ms | +87% |
| Same floor, 3 walls | 200ms | 450ms | +125% |
| Different floor, through concrete | 350ms | 950ms (sometimes drops) | +171%, inconsistent |
| 50 nodes all responding (scene recall) | 800ms | 2.2s with 3 dropouts | +175%, lost packets |
The scene recall result is the one that matters for commercial. 2.2 seconds with 3 fixtures that never turned on. In a 60-person open office, that's 3 dark spots. In a warehouse aisle, that's a safety issue. Zigbee delivered all 50 in under a second, every time.
Packet Delivery Rate — 7-Day Continuous Test
Each node sent a heartbeat packet every 60 seconds. 10,080 transmissions per node over 7 days. We counted how many arrived at the coordinator.
| Condition | Zigbee 3.0 | Matter Over Thread | Winner |
|---|---|---|---|
| Line of sight | 99.2% | 98.5% | Zigbee (+0.7%) |
| Through 2 walls | 94% | 88% | Zigbee (+6%) |
| Through 3 walls + metal shelving | 88% | 72% | Zigbee (+16%) |
| Cross-floor (concrete) | 85% | 65% | Zigbee (+20%) |
The gap widens as the RF environment gets tougher. Through a single concrete floor — something every multi-story commercial building has — Zigbee delivers 20% more packets. That's not a small difference. That's the difference between lights that work and lights that don't.
When Matter/Thread Actually Wins
This isn't a clean sweep for Zigbee. Matter/Thread has genuine advantages — they're just not in the domain of commercial reliability. Here's where Matter comes out ahead:
1. Consumer Installation: "Just Works"
For 5 smart bulbs in a living room, Matter/Thread is the better experience. No hub required. Your phone provisions the device. Done. Zigbee's hub requirement adds cost and complexity that a homeowner doesn't want.
2. Ecosystem Independence
This is Matter's real killer feature. A Matter-certified light works with Apple Home, Google Home, Samsung SmartThings, and Alexa — simultaneously. Zigbee ties you to a specific hub and ecosystem. For a specifier who doesn't know what control system the client will use in 3 years, Matter eliminates that risk.
3. Future Roadmap: Thread v1.4
Thread v1.4 (targeting late 2026) introduces improved routing algorithms and better mesh partition recovery. If Thread closes the 20% packet delivery gap, the interoperability advantage could make Matter the default choice even for commercial. But it hasn't happened yet.
The "Protocol Transition" Trap
Here's a cautionary tale I've seen play out at least three times in the past 18 months: a manufacturer starts a Zigbee product line, gets halfway through engineering, reads a blog post about "Matter is the future," and decides to pivot mid-project.
That number covers:
- MCU redesign: Thread's IPv6-based stack requires more flash and RAM than Zigbee's lightweight 802.15.4 MAC — your existing microcontroller may not cut it
- FCC/CE re-certification: Changing the radio stack invalidates your existing certification; you're back at the test lab for 4–6 weeks
- Hub integration testing: Matter's multi-admin commissioning path must be validated against every major ecosystem controller — Apple, Google, Amazon, Samsung
- Field upgrades: If you've already deployed Zigbee product, swapping to Matter means replacing coordinator hardware, re-commissioning every node, and retraining installers
The Smarter Move: Dual-Protocol
Don't bet on one protocol. Design with a dual-protocol module that supports both Zigbee 3.0 and Thread.
The two options worth considering today:
- Silicon Labs MG24: Single-chip SoC with concurrent Zigbee and Thread support. Proven in commercial deployments. ~$1.50 premium over single-protocol alternatives.
- NXP K32W: Multi-protocol wireless MCU supporting Zigbee 3.0, Thread, and Bluetooth LE. Slightly more expensive but adds BLE commissioning as a bonus.
At approximately $1.50 more per unit, dual-protocol hardware lets you ship Zigbee today, enable Thread via firmware update when the commercial ecosystem is ready, and avoid the $25K–50K re-engineering cost per SKU. That's the real commercial strategy.
Frequently Asked Questions
Is Thread dead because of Matter delays?
No, but the hype has deflated. Thread will win in the consumer market — Apple, Google, and Amazon are all-in on the Matter ecosystem, and Thread is the primary wireless transport for Matter devices. In commercial, Thread v1.4 (targeting late 2026) promises improved routing and mesh resilience that may close the gap with Zigbee. For now, Zigbee wins commercial reliability; Thread is the consumer play. The smart move is dual-protocol hardware.
Do I need a hub for Zigbee?
Yes, for most setups. Consumer products like Philips Hue require the Hue Bridge. Commercial installations use a central coordinator module — essentially an industrial-grade hub that manages the mesh network. This coordinator typically bridges Zigbee to the building's backbone (BACnet/IP, DALI gateway, or cloud IoT platform). The hub requirement is Zigbee's main disadvantage vs. Matter/Thread, but in commercial, you already have a building management system — adding a Zigbee coordinator to it is incremental, not a dealbreaker.
Bluetooth Mesh — where does that fit?
Don't use it for lighting control. Bluetooth Mesh was designed for beaconing, sensor data, and asset tracking — not time-sensitive lighting commands. Latency is 500ms+ per hop, scalability degrades past 50 nodes, and the flooding-based message propagation model wastes bandwidth in dense networks. Both Zigbee 3.0 and Matter Over Thread outperform Bluetooth Mesh by a wide margin for any lighting application beyond a single room. If someone pitches you Bluetooth Mesh for a 100-node commercial lighting installation, walk away.
What happens if I've already deployed Zigbee — can I migrate to Matter later?
You can, but it's not a software update. Zigbee and Thread share the same physical radio (IEEE 802.15.4 at 2.4 GHz), but the upper protocol stacks are incompatible. Migration requires: (1) hardware that supports both protocol stacks (dual-protocol modules), (2) a firmware update to switch the stack, (3) re-commissioning every node on the new Thread network, and (4) replacing or reconfiguring your coordinator. Field migration is expensive and disruptive — this is why starting with dual-protocol hardware from day one is so valuable.
Which protocol should I spec for a new commercial lighting project in 2026?
Zigbee 3.0, with dual-protocol hardware if budget allows. For a 50+ node commercial installation today, Zigbee delivers better reliability (88% vs. 72% packet delivery through concrete), lower latency (350ms vs. 950ms cross-floor), and proven field performance across thousands of deployments. If your project timeline extends into 2027 or beyond, dual-protocol modules (Silicon Labs MG24 or NXP K32W) give you the option to switch to Matter/Thread when the ecosystem matures — without re-engineering your product.
Sourcing smart LED drivers with Zigbee or dual-protocol support?
Compare2Best vets driver manufacturers for protocol compatibility, FCC/CE certification status, and real-world mesh performance. Filter by protocol (Zigbee 3.0, Thread, dual-protocol), wattage, and form factor to find drivers that match your commercial lighting spec.
Compare Smart LED Drivers →