Zigbee vs Bluetooth Mesh for Smart Lighting Projects

TL;DR — the short answer

Choose Zigbee when the project is large or control-dense: hundreds of luminaires and sensors, multiple floors, scenes and automations managed through a professional gateway. Choose Bluetooth Mesh when the project is small to mid-size and you want phone-first commissioning without a dedicated hub — showrooms, single-floor retail, restaurant and small-hospitality fits. Both run on low-cost 2.4 GHz radios and both form self-extending meshes; the difference is the network logic inside. Zigbee routes each message along computed paths and stays fast at scale. Bluetooth Mesh floods every message to all listening nodes, which is brilliantly simple for a phone to join and progressively heavier as the node count grows.

Two mesh philosophies: routing versus managed flooding

Zigbee, built on IEEE 802.15.4, is a routing mesh. Mains-powered luminaires act as routers; the coordinator maintains a routing table so each command travels along an efficient path to its target. That is why a 400-node retail lighting installation can still respond in a fraction of a second, and why adding sensors and switches barely disturbs the network. The cost of this intelligence is infrastructure: the network needs a coordinator — in practice, a gateway or hub that also bridges to apps and clouds.

Bluetooth Mesh takes the opposite approach: managed flooding. There is no routing table. Every relay node re-transmits each message, and TTL limits plus message caching keep the storm under control. The design buys two real advantages. First, a standard Bluetooth Low Energy radio in a phone can talk to the network directly — provisioning and control need no hub. Second, node roles are flexible: relay nodes extend range, proxy nodes bridge phone-to-mesh, friend and low-power nodes let battery sensors sleep for years. The price is architectural: as the network grows, flooding overhead grows with it, and worst-case response time becomes less predictable than in a routed network.

Sensor strategy exposes the philosophies, too. Zigbee's sleepy end devices have run occupancy and daylight sensors on coin cells for years, and the routing mesh treats them as first-class citizens. Bluetooth Mesh achieves similar battery life through friendship packets, but battery-device support in mid-market product lines arrived later and remains more uneven — a practical point when the controls scope includes sensors rather than luminaires only.

Scale, latency and where each one starts to strain

In field practice, Zigbee comfortably carries multi-hundred-node commercial installations; its limits appear in extreme 2.4 GHz congestion, which channel planning addresses. Bluetooth Mesh performs well at the scale of a shop, a restaurant or a hotel floor — think tens to low hundreds of nodes. Beyond that, commissioning discipline matters: node grouping, relay placement and TTL settings determine whether scenes respond crisply or with visible lag. Neither protocol needs the cloud to function; both run their core switching and scene logic locally, which matters for projects where internet reliability is not guaranteed.

For context at the top end of the market: where a tender specifies certified response behavior, emergency integration and audit trails, wired DALI or DALI-2 still wins the backbone role. Zigbee and Bluetooth Mesh compete for the wireless layer — retrofits, decorative zones, and spaces where pulling control cable is the expensive part.

Interference, coexistence and what fails in the field

Both protocols live in the same crowded 2.4 GHz band as Wi-Fi, and most field complaints trace to coexistence rather than to the protocol itself. Zigbee mitigates by channel selection at commissioning — picking a Zigbee channel offset from the building's busiest Wi-Fi channels — a one-time decision a careless installer can skip. Bluetooth counters with adaptive frequency hopping, which re-maps congested channels continuously, making it more forgiving of messy radio environments at the cost of less predictability in dense deployments. In practice: both are reliable in a disciplined installation, and both get blamed for problems that belong to ceiling steel, wet-wall plumbing, or a microwave oven in the back office.

Field failure modes differ in character. Zigbee networks degrade when routing nodes are removed — a luminaire swapped out by an electrician can briefly orphan the devices behind it until routes heal. Bluetooth Mesh degrades gracefully but visibly: response times lengthen as hop counts grow. Commissioning discipline — recording node locations, keeping gateway firmware current, labeling relay roles — matters more to long-term satisfaction than the protocol logo.

Side-by-side comparison

Scale figures describe common field practice reported by cluster factories; they are directional guidance, not certified limits. Validate with a site pilot.

What the radio choice costs

Structure the quote as four lines and the comparison becomes honest. Module delta per luminaire: smart modules in either protocol price above non-smart drivers, with Zigbee and Bluetooth Mesh modules typically within a small margin of each other (illustrative — confirm per platform and volume). Gateway hardware: Zigbee needs one per project or floor; Bluetooth Mesh often needs none. Commissioning labor: phone-native provisioning can undercut gateway-based commissioning on small sites and lose to it on large ones. And support: whichever path is chosen, the app or gateway vendor's update window is part of the purchase price, whether or not it appears on the invoice.

A pattern worth copying from mature buyers: price the same mid-size project both ways every year or two. Module prices, gateway capabilities and app licensing all move, and the break-even node count between "hub-free convenience" and "hub-based scale" drifts with them. A ten-minute desk exercise keeps the program on the cheaper side of a moving line — and gives the sales team a current answer when clients ask which mesh is "cheaper" as if the answer were permanent.

How to choose — three decision rules

• More than roughly 150-200 control points, or multiple floors with scenes: specify Zigbee behind a professional gateway (illustrative threshold — confirm with a layout study).
• No IT infrastructure wanted and the end client will run scenes from a phone: Bluetooth Mesh keeps the bill of materials free of hubs.
• Uncertain between them: price both with the same luminaire platform. Many export-ready product families ship identical hardware in Zigbee and Bluetooth Mesh variants, so the decision stays at the controls layer.

Advice for procurement teams and dealers

Demand stack clarity in writing. "Smart" on a Chinese factory datasheet can mean Zigbee 3.0, Bluetooth Mesh, Tuya's implementations of either, or a proprietary protocol. Ask for the exact stack and certification IDs, the gateway or app it is validated against, and the over-the-air update policy. For multi-ecosystem tenders, also ask how the line bridges to Matter — the comparison that increasingly matters commercially is not Zigbee versus Bluetooth Mesh but "either" versus native Matter, covered in our related guide.

For dealers: a shared-platform strategy de-risks inventory. One luminaire platform offered in both radio variants lets you serve hub-based commercial projects and hub-free retail customers from the same stock, with differences only in module and app support. Sample validation should include a real-building test — commission ten nodes through the actual app, trigger scenes across floors, and measure response before committing a program. Cost-wise, module delta per luminaire and gateway cost per project are quoted per project; treat any per-unit premium you hear informally as illustrative until your own schedule is priced.