IoT and Edge AI

Wi-Fi vs Bluetooth LE vs LoRa vs Zigbee: Choosing a Wireless Link for IoT

Compare Wi-Fi, Bluetooth LE, LoRa and Zigbee for IoT by range, data rate, power, topology and cost, with a step-by-step method for picking the right radio.

On this page
  1. Quick answer
  2. Comparison table
  3. Wi-Fi
  4. Bluetooth Low Energy
  5. LoRa and LoRaWAN
  6. Zigbee
  7. Where Thread and Matter fit
  8. Other options worth knowing
  9. How to choose: a step-by-step process
  10. Example scenarios
  11. Practical considerations
  12. Common mistakes
  13. FAQ

Quick answer

  • Wi-Fi: choose it when the device has mains power or a large battery, needs to send a lot of data, and can reach an existing access point. It connects directly to the internet without a special gateway.
  • Bluetooth Low Energy (BLE): choose it when the device is battery-powered, short-range, and especially when it needs to talk to a phone.
  • LoRa / LoRaWAN: choose it for small amounts of data over long distances (often kilometres outdoors) on very little power, such as farm, utility and city sensors.
  • Zigbee: choose it for low-power mesh networks of many devices in a building, such as lights, switches and sensors, especially in smart home and building automation.

There’s no universally best option. Each one trades off range, data rate, power and infrastructure differently.

Comparison table

The figures below are typical ranges. Real performance depends heavily on antennas, walls, interference, transmit power, regional rules and configuration.

Wi-Fi Bluetooth LE LoRa / LoRaWAN Zigbee
Frequency 2.4 GHz, 5 GHz (and 6 GHz on newer standards) 2.4 GHz Sub-GHz ISM bands (e.g. 868 MHz in Europe, 915 MHz in North America) Mostly 2.4 GHz
Typical range Tens of metres indoors Roughly 10 to 50 m indoors; more with long-range (Coded) PHY Kilometres outdoors with line of sight; less in dense urban areas Tens of metres per hop, extended by mesh
Data rate Megabits per second and up Up to 2 Mbps PHY rate; real throughput lower Roughly 0.3 kbps to a few tens of kbps 250 kbps at 2.4 GHz
Power use High Very low Very low Low
Battery life (sensor) Days to months, depending heavily on duty cycle Months to years Years possible Months to years for end devices
Topology Star (access point) Point-to-point, broadcast, mesh Star-of-stars (devices → gateways → network server) Mesh
Needs a special gateway? No, uses a standard router Phone or BLE gateway for internet access LoRaWAN gateway (yours or a network’s) Zigbee coordinator / hub
IP-native? Yes No (IP is possible but uncommon) No No
Phone can talk directly? Yes Yes No No
Typical uses Cameras, appliances, plugs, gateways Wearables, beacons, phone accessories, medical sensors Agriculture, metering, environmental and city sensors Lights, switches, home and building sensors

Wi-Fi

Strengths: Wi-Fi is everywhere, it carries IP traffic natively, and it gives high throughput. A Wi-Fi device can talk to a cloud service with standard protocols like MQTT or HTTPS without any translation. Wireless microcontrollers such as the ESP32 family make it cheap and easy to use, which is why so many hobby and commercial IoT devices use it.

Weaknesses: Power. Joining a network, keeping a connection alive and running TCP/IP and TLS all cost far more energy than BLE or Zigbee. A Wi-Fi sensor can sleep between readings, but reconnecting and doing a TLS handshake on each wake-up adds up. Coverage is limited to where access points reach, and setting up credentials on a device without a screen needs a provisioning flow (often over BLE or a temporary access point).

Newer developments: Wi-Fi 6 (802.11ax) adds Target Wake Time (TWT), which lets a device and access point agree on sleep schedules. It can cut power use considerably, though only if the access point supports it. Wi-Fi HaLow (802.11ah) uses sub-GHz bands for longer range and lower power, but chip and access-point support is much less common than for regular Wi-Fi.

Good fit: mains-powered devices, cameras, appliances, anything streaming data, and gateways that bridge other radios to the internet.

Bluetooth Low Energy

Strengths: BLE was designed for low power. Devices can run for months or years on a coin cell if they transmit occasionally. Its biggest practical advantage is that every smartphone supports it, so a device can be set up and controlled from a phone app without any extra hardware.

How it works: BLE devices can advertise, broadcasting small packets that anyone can receive (this is how beacons work), or form connections and exchange data through GATT services and characteristics. Bluetooth 5 added a 2M PHY for higher throughput and a Coded PHY for longer range at lower data rates. Bluetooth Mesh allows many-to-many networks for applications like commercial lighting.

Weaknesses: Short range with the standard PHY, and getting data to the internet needs a phone or a BLE-to-IP gateway. Throughput is modest compared with Wi-Fi.

Good fit: wearables, medical and fitness sensors, beacons and asset tags, phone accessories, and devices that need a phone for setup.

LoRa and LoRaWAN

First, an important distinction:

  • LoRa is a radio modulation technique (a form of chirp spread spectrum) developed by Semtech. It’s the physical layer.
  • LoRaWAN is a networking protocol built on top of LoRa, maintained by the LoRa Alliance. It defines how devices join a network, how messages are encrypted and how gateways forward them to a network server.

You can use plain LoRa point-to-point (for example, a sensor talking directly to a receiver in your house), or use LoRaWAN with gateways and a network server.

Strengths: Very long range and very low power. LoRa trades data rate for range. Higher spreading factors reach further but transmit more slowly and spend longer on air. A battery sensor sending a few bytes every 15 minutes can run for years. LoRa uses unlicensed sub-GHz bands, so there’s no SIM or carrier contract, and you can run your own gateway or use a public or community network.

Weaknesses:

  • Tiny payloads and low data rates: messages are typically from about a dozen to a couple of hundred bytes, depending on region and data rate.
  • Duty-cycle and dwell-time rules: in Europe, many sub-bands limit each device to 1% airtime. Other regions have different rules. This limits how often you can transmit.
  • Limited downlink: LoRaWAN is designed mostly for device-to-network traffic. Sending commands to devices is possible but constrained, and large transfers such as full firmware updates are slow and need special techniques.
  • Gateway dependency: if there’s no coverage, you need to install a gateway.

Good fit: agriculture, water and gas metering, environmental monitoring, parking and waste sensors, and remote buildings.

Zigbee

Strengths: Zigbee is a low-power mesh protocol built on the IEEE 802.15.4 radio standard. Mains-powered devices like smart bulbs and plugs act as routers that relay messages, while battery-powered end devices like sensors sleep most of the time. The network can route around a failed node. Zigbee is mature, widely used in smart homes and lighting, and Zigbee 3.0 unified earlier application profiles to improve interoperability between brands.

How it works: Every Zigbee network has a coordinator, usually inside a hub or a USB dongle on a home automation server, which forms the network and manages security. Devices communicate using standard clusters, such as “on/off” or “temperature measurement,” so a switch from one brand can control a bulb from another.

Weaknesses: It needs a coordinator or hub to reach the internet, and it isn’t IP-native. It shares the 2.4 GHz band with Wi-Fi, so channel planning can matter. Data rates are low (250 kbps raw), which is fine for control messages but not for large data.

Good fit: smart lighting, switches, door and motion sensors, and building automation with many devices.

Where Thread and Matter fit

Thread uses the same IEEE 802.15.4 radio as Zigbee, but it’s an IPv6-based mesh network. Devices get IP addresses, and a Thread border router (often built into smart speakers, hubs or some Wi-Fi routers) connects the mesh to your home network.

Matter isn’t a radio at all. It’s an application-layer standard from the Connectivity Standards Alliance that runs over Thread, Wi-Fi or Ethernet, with BLE used during setup. Its goal is that a certified device works with the major smart home ecosystems.

For new consumer smart home products, many developers now look at Matter over Thread or Wi-Fi alongside, or instead of, Zigbee. Many chips (such as the ESP32-C6 and ESP32-H2, Nordic’s nRF52840/nRF54 series and Silicon Labs’ EFR32 parts) support 802.15.4 radios that can run either Zigbee or Thread firmware.

Other options worth knowing

  • Cellular IoT (LTE-M and NB-IoT): wide-area coverage through mobile networks, low power, with carrier subscriptions. LTE-M supports mobility and higher data rates, so it suits trackers. NB-IoT favours stationary devices with deep indoor coverage, though availability varies by country and carrier.
  • Z-Wave: a sub-GHz smart home mesh protocol, popular in some markets.
  • Proprietary sub-GHz radios: simple point-to-point links used in many remote controls and sensors.
  • Ethernet and wired buses: still the most reliable choice when you can run a cable, and common in industrial settings (RS-485/Modbus, CAN).

How to choose: a step-by-step process

  1. How is the device powered? Mains or a large rechargeable battery keeps Wi-Fi on the table. A coin cell or a small battery that must last a year or more points to BLE, Zigbee, Thread or LoRa.
  2. How far must it reach, and through what? Within one room: BLE. Across a house or building: Wi-Fi, Zigbee or Thread mesh, or BLE Mesh. Across a farm, campus or town: LoRaWAN or cellular.
  3. How much data, and how often? Video or audio streams: Wi-Fi. Periodic readings of a few bytes: any of the low-power options. Large, frequent firmware updates are much harder on LoRaWAN.
  4. Where does the data need to go? To a phone: BLE. Straight to the cloud with no extra hardware: Wi-Fi or cellular. Into a smart home hub: Zigbee, Thread/Matter or Wi-Fi.
  5. Is a gateway or hub acceptable? If not, Wi-Fi or cellular. If yes, Zigbee, Thread, BLE gateways and LoRaWAN open up.
  6. How fast must commands reach the device? Sleeping LoRaWAN devices may only receive downlink messages shortly after they transmit, so they’re unsuitable for “turn on now” control. Zigbee, Thread, Wi-Fi and connected BLE respond much faster.
  7. What will it cost per device and in total? Include modules, certification, gateways and any subscription fees, not just the chip.

Example scenarios

Device Likely choice Why
Video doorbell Wi-Fi High bandwidth, mains or large battery
Fitness band BLE Phone connection, tiny battery
Field soil sensor on a large farm LoRaWAN Kilometres of range, years on a battery
Smart light bulb Zigbee, Thread/Matter, or Wi-Fi Always powered; mesh helps coverage
Door/window contact sensor Zigbee, Thread or BLE Coin-cell power, small messages
Shipping container tracker LTE-M Moves between regions, needs wide coverage
Hobby weather station in the garden Wi-Fi (or LoRa if far from the house) Simple setup with an ESP32

For more device ideas, see examples of IoT projects using embedded systems.

Practical considerations

  • Certification: Radios need regulatory approval (such as FCC in the US or the Radio Equipment Directive in the EU). Pre-certified modules simplify this a lot, but the final product still needs testing, and changing the antenna can affect the module’s approval. Using a protocol’s logo (Bluetooth, Zigbee, Matter, LoRaWAN) typically also requires that standard body’s qualification process.
  • Antennas and enclosures: A poor antenna layout or a metal enclosure can cut range dramatically. Follow the module vendor’s layout guidelines and test in the real enclosure.
  • Coexistence: Wi-Fi, BLE, Zigbee and Thread all share 2.4 GHz. Combo chips manage this internally, but busy environments still need testing.
  • Measure power, don’t estimate it: Battery-life calculations from datasheets are often optimistic. Measure actual current across sleep, wake-up, sensing and transmission with a power profiler.
  • Security: Each protocol has its own security model (WPA2/WPA3 for Wi-Fi, LE Secure Connections for BLE, AES-based encryption in Zigbee and LoRaWAN). Application-level security such as TLS and secure firmware updates still matters on top. See Over-the-Air (OTA) Firmware Updates for IoT Devices.

Common mistakes

  • Choosing Wi-Fi for a coin-cell sensor and then fighting battery life
  • Treating LoRa like a slow Wi-Fi: it’s built for tiny, infrequent messages, not general data transfer
  • Ignoring duty-cycle rules in the region where the device will be used
  • Forgetting the setup experience: how will a user give the device Wi-Fi credentials or pair it with a hub?
  • Testing only on the bench: range and reliability in a real building, field or factory can be very different
  • Skipping the gateway question until late, when it changes the product’s cost and installation story

FAQ

Which is best for battery-powered IoT devices? BLE, Zigbee, Thread and LoRa are all designed for battery operation. BLE suits short range and phones, Zigbee and Thread suit mesh networks in buildings, and LoRa suits long range with small data. Wi-Fi can work on batteries if the device wakes rarely, but it’s usually the most power-hungry option.

Can one chip do several of these? Yes. Many modern wireless SoCs combine Wi-Fi and BLE (like most ESP32 variants), or BLE with 802.15.4 for Zigbee and Thread. LoRa normally needs a separate sub-GHz radio, though some chips such as the STM32WL integrate one.

Is LoRa better than Zigbee? They solve different problems. LoRa reaches much further with very low data rates. Zigbee covers a building with a mesh of many devices and responds faster, but needs routers spread around to extend range.

What should I use for my first ESP32 project? Wi-Fi with MQTT is the easiest place to start. Our ESP32 MQTT tutorial walks through it step by step. To see how the radio fits into a full system, read IoT System Architecture.

The complete guide to iot and edge ai

Embedded Systems and the Internet of Things
Read the guide

Keep exploring

Guides from other topics

All topics →