Choosing Thread vs Zigbee for light bulbs

When you’re building a local-first smart home, the choice between Thread and Zigbee for your light bulbs affects reliability, how you integrate with your ecosystem, and how future-proof your kit is. Both are low-power mesh protocols that share the same underlying radio, but they differ in how they connect to the rest of your house. Here’s an honest breakdown for a Home Assistant, HomeKit, or Hubitat setup.

What the two protocols actually are

Zigbee has been around since the mid-2000s and has a huge device ecosystem - Philips Hue, IKEA, Sonoff, Aqara, Third Reality, and many more. It runs on 2.4 GHz using the 802.15.4 radio standard, draws very little power, and forms a self-healing mesh where mains-powered devices (bulbs, plugs) relay traffic for battery devices. To use Zigbee you need a coordinator - a radio that runs the network. In Home Assistant that’s a USB stick driven by ZHA or Zigbee2MQTT; in Hubitat or a SmartThings hub it’s the radio built into the hub.

Thread is newer and also runs on 2.4 GHz / 802.15.4 - it is the same kind of radio as Zigbee, not a different band. The big difference is that Thread is IP-based: every Thread device gets an IPv6 address and is reachable over your network. Thread is the transport that Matter most often rides on for low-power devices, which is why it matters for a future-proof setup. Instead of a coordinator, a Thread network needs a border router, which bridges the Thread mesh onto your home IP network. Mains-powered Thread devices act as routers within the mesh, just like Zigbee’s mains devices do.

So the honest framing: these are siblings, not opposites. The practical question is which one a given bulb speaks and how cleanly it lands in your ecosystem.

Zigbee: the established, deep ecosystem

If you already run Zigbee in Home Assistant, you’re on solid ground. The device selection is the largest in the smart home world, prices are low, and ZHA or Zigbee2MQTT control it all locally with no cloud.

A few ecosystem notes worth getting right:

• Hubitat has both a built-in Zigbee radio and a built-in Z-Wave radio, so it handles Zigbee bulbs natively.
• HomeKit has no native Zigbee support. To get Zigbee bulbs into Apple Home you go through a bridge - the Philips Hue Bridge exposes Hue’s Zigbee bulbs to HomeKit, or you can use Home Assistant’s HomeKit Bridge integration to expose any HA device.
• The Philips Hue Bridge is local - it does not require the cloud to control your lights on your LAN - but it is a closed Zigbee gateway. It only manages Hue and Hue-friendly devices and cannot act as a generic Zigbee coordinator for arbitrary brands. If you want one coordinator for everything, use a generic stick with ZHA or Zigbee2MQTT instead of (or alongside) the Hue Bridge.
• For a generic Zigbee coordinator, sticks like the ConBee III or the Sonoff Zigbee 3.0 USB Dongle Plus are common picks. (Note: Aeotec is best known for Z-Wave, but it now makes Zigbee gear too - its Z-Stick 10 Pro is a single USB dongle that runs both Z-Wave and Zigbee, usable with ZHA or Zigbee2MQTT.)

Zigbee’s main weakness is that network health depends on layout. The mesh routes around a failed node in most cases, but a poorly placed coordinator or too few mains-powered routers can cause dropouts. Good router placement matters.

Thread: the Matter-era option

Thread shines when you’re building around Matter. Because it’s IP-based, Matter-over-Thread bulbs can be commissioned into Apple Home, Google Home, SmartThings, or Home Assistant (via the Matter integration plus a Thread border router) without a brand-specific bridge. That’s the real “future-proof” appeal: one device, several ecosystems, all local.

For bulbs, your Thread/Matter options today include the Nanoleaf Essentials Matter-over-Thread bulbs and the Aqara LED Bulb T2, which is a dual-radio bulb - it can run as Matter-over-Thread (no hub, direct to a Matter ecosystem) or as Zigbee through an Aqara hub for Aqara-specific features. Even Philips Hue’s newest-generation bulbs have started adding Thread radios alongside Zigbee and Bluetooth, so a bulb can support more than one protocol.

To use Thread you need a border router. In a Home Assistant setup that’s commonly the Home Assistant Connect ZBT-2 (running Thread firmware) or a HomePod / most Apple TV 4K models / a recent Google Nest Hub acting as a border router. Make sure you actually have one before buying Thread bulbs.

Real-world tradeoffs

• Device availability. Zigbee still has a far larger catalog of bulbs and accessories. Thread/Matter bulbs are growing but remain a smaller selection.
• Maturity. Zigbee is battle-tested. Matter-over-Thread is solid and improving, but commissioning quirks and uneven manufacturer implementations still show up - check reviews for the specific bulb.
• Ecosystem reach. Thread/Matter reaches Apple Home, Google, and others without a brand bridge. Zigbee reaches HomeKit only through a bridge, but works natively in Home Assistant and Hubitat.
• Both are local. Neither protocol requires the cloud for on-LAN control. This is not a local-vs-cloud decision.

Quick verdict

If you already have a working Zigbee setup, there’s no urgency to switch - it’s local, deep, and cheap. Keep buying Zigbee bulbs.

If you’re starting fresh and want to lean into Matter across multiple ecosystems, Thread/Matter bulbs (with a border router in place) are the more future-proof choice. A dual-radio bulb like the Aqara LED Bulb T2 is a nice hedge: run it on Thread now, or fall back to Zigbee if that suits your hub better.

Either way, you’re staying local. Pick based on what your hub speaks, what your ecosystem needs, and which protocol the bulbs you actually want to buy support.