The question behind the question
When a contractor proposes a wireless lighting control system, you will hear a radio name: Bluetooth, Zigbee, Thread, sometimes Matter. Owners reasonably ask which one is best. For commercial lighting, that is slightly the wrong question.
The radio decides how messages travel. What decides whether a system meets your needs is the layer on top: the application profile that defines what an occupancy sensor says, how a fixture responds, how energy is reported, and how all of it is configured and maintained. This post compares the four names you are most likely to hear, at the level an owner, facility manager or IT lead needs, and ends with the questions that actually decide the choice.
Three layers, not one
It helps to separate three things that sales conversations tend to blur:
- The radio. The physical wireless link: 2.4 GHz for most of these, sub-GHz for some newer options. Range, penetration through walls and racking, and interference live here.
- The network. How devices form a mesh, route messages and join securely. Thread is a network. Bluetooth Mesh and Zigbee each define their own.
- The application profile. What devices say to each other: this zone is occupied, dim to 30%, here is my energy reading. Without a shared profile, two devices on the same radio still can’t cooperate.
Commercial lighting needs all three to be solid. It also needs the third layer to cover commercial behavior: occupancy with time delays and partial-off, daylight response, high-end trim, scheduling, energy monitoring and integration with HVAC.
Bluetooth Mesh with NLC profiles
Bluetooth Mesh builds a managed mesh network on Bluetooth Low Energy radios. For lighting, the important development is the set of networked lighting control (NLC) profiles published for Bluetooth Mesh. They define standard behavior for occupancy sensors, ambient light sensors, energy monitoring and HVAC integration, among other device roles.
In practice, that makes Bluetooth Mesh the wireless option with the most complete standard definition of commercial lighting behavior today. Profiles don’t guarantee that every pair of products interoperates perfectly, so we still bench-test combinations, but they give a specification something concrete to require.
Watch for the practical details: how many devices a network can hold before it needs splitting, how devices are provisioned and keys are managed, and whether the gateway exposes data openly. Adoption figures for Bluetooth NLC that circulate in marketing mostly come from vendors. Judge on products you can test.
Zigbee 4.0 and Suzi
Zigbee has a long history in lighting, mostly in residential products and some commercial ones. The Connectivity Standards Alliance (CSA) announced Zigbee 4.0 in November 2025, along with Suzi, a sub-GHz option. Sub-GHz radios generally reach farther and get through obstacles better than 2.4 GHz, which is interesting for large buildings, metal structures and exterior lighting.
The honest caveat is timing. A specification announcement and a shelf of certified commercial lighting products are different things. For projects designed in 2026, we treat Zigbee 4.0 and Suzi as worth watching, and we verify product availability, certification status and commercial lighting behavior before specifying them.
Thread
Thread is an IP-based mesh network built on the same low-power radio standard that Zigbee uses, with border routers connecting the mesh to the building’s IP network. It is well engineered and increasingly common in homes, largely because Matter runs on it.
The key point for commercial lighting: Thread is a network, not a lighting control standard. It moves packets between devices reliably. It does not define what an occupancy sensor or a dimming zone does. Something above it has to, and for commercial lighting that something is not yet standardized on Thread.
Matter
Matter is an application layer from the CSA that runs over Wi-Fi, Thread and Ethernet. The CSA has begun to list commercial buildings as a target market, but Matter has no commercial lighting device types yet. It can’t currently express the sequences a commercial lighting specification requires, and it is not a replacement for BACnet or for networked lighting controls. We look at it in more depth in a separate post.
Proprietary meshes
Many of the most established wireless luminaire-level systems use a manufacturer’s own mesh rather than any of the four names above. That is not automatically a problem. Several of them are mature and well supported. The risk is concentration: one company controls the radio, the profile, the tools and the gateway. If you go this way, insist on an open data path and a written answer about what happens if the product line ends.
Side by side
| Bluetooth Mesh (NLC profiles) | Zigbee 4.0 / Suzi | Thread | Matter | |
|---|---|---|---|---|
| What it is | Mesh network plus application profiles | Mesh network plus application layer | IP mesh network | Application layer over Wi-Fi, Thread or Ethernet |
| Commercial lighting profiles | Yes: occupancy, ambient light, energy monitoring, HVAC integration and more | Verify per product | None of its own | No commercial lighting device types yet |
| Radio | 2.4 GHz | 2.4 GHz, plus sub-GHz with Suzi | 2.4 GHz | Depends on transport |
| Maturity for commercial lighting | Mainstream | Emerging | Infrastructure only | Not ready for commercial lighting |
| Watch out for | Gateway openness, provisioning, network size | Product availability and certification | Needs a profile on top | Missing device types, enterprise management |
Our Protocol Explorer puts these alongside wired and building-automation protocols, filterable by what you need.
What matters more than the logo
Whatever the radio, these are the questions we ask before recommending a wireless system:
- Data out. Can occupancy, energy and fault data leave through BACnet, a documented API or MQTT, without an add-on nobody mentioned?
- Local control. Do occupancy and daylight sequences keep running in the mesh if the gateway, head-end or internet connection is down?
- Gateways. How many per area, where do they mount, and what fails when one does?
- Commissioning tools. Can a qualified technician other than the manufacturer commission and change the system? Can the configuration be exported?
- Firmware. How are updates delivered, tested and rolled back?
- Keys. How are network keys managed, and who holds them after closeout?
- Radio survey. Has anyone checked performance in your actual building, with racking, metal decking and stock in place?
- Exit plan. If the product line ends, what can be reused?
Metal buildings and other Mid-South realities
Much of the building stock in our region is metal: pre-engineered warehouses, plants with steel decking, schools with metal-stud additions. Wireless works in these buildings, but it needs density and a survey. Full racking changes radio behavior compared with the empty building at commissioning, and a warehouse that worked fine in March can develop dead spots when peak-season inventory arrives. We test with stock in place where we can and design mesh density with margin.
A representative scenario: a school retrofit
Consider a representative middle school in North Mississippi: a 1970s block building with a later metal-stud addition, existing LED troffers with 0-10V drivers, and a district that wants occupancy control, daylight response in classrooms with windows, and an easier way to find failures across several campuses. Pulling new low-voltage runs through block walls during the school year would be slow and disruptive.
Wireless is the right family here. We would favor a system with standard NLC profiles or a proven commercial mesh, add sensor and controller kits to the existing troffers, place gateways after a radio walk, and require BACnet or API export so the district’s BMS sees occupancy. We would skip anything whose commercial lighting behavior depends on device types that don’t exist yet.
What we’d do
- Write requirements as behaviors and data, not radio names. The specification says what the system must do and what data must come out.
- Prefer standard profiles where they exist. Accept a proprietary mesh only with an open data path and a written exit plan.
- Bench-test the combination. Sensors, fixtures and gateways go on the bench in our Lab together before anything is ordered.
- Survey the real building. Radio performance is measured, not assumed.
- Bring IT in early. Gateways, keys and remote access get reviewed before installation, not after. Our cybersecurity service runs that review.
- Commission and document. Every sequence tested, every setting recorded.
Where to start
If you are planning a wireless controls retrofit, our wireless retrofit and LLLC service starts with a site walk and a protocol recommendation tied to your building, your data goals and your IT team’s rules. If you are not sure controls are worth it yet, a Baseline Assessment will tell you which spaces pay back first.
Filed under: Bluetooth Mesh · Zigbee 4.0 · Thread · Matter · wireless lighting controls
