Bluetooth Low Energy (BLE)

Executive summary

• BLE IoT — Bluetooth Low Energy, also called "Bluetooth Smart" — is the low-power variant of Bluetooth, introduced in Bluetooth 4.0 (2010) and maintained by the Bluetooth SIG. If you're new to the ecosystem, first review what IoT is to understand the context of short-range communication protocols.
• It operates in the 2.4 GHz band with a design optimized for sending small amounts of data sporadically with minimal power: a coin cell can last months or years.
• Its data model is GATT (Generic Attribute Profile): devices expose services and characteristics that a client reads, writes, or receives by notification.
• It's the dominant protocol in wearables, proximity sensors, beacons, medical devices, locks, and anything that pairs with a smartphone, because it's built into every phone.
• BLE 5.x (2016+) added greater range (Coded PHY), more speed (2M PHY), extended advertising, and, with Mesh, multi-node networks.
• Don't use it when: you need long range with no phone nearby (use LoRaWAN), sustained high bandwidth, or a mature home mesh for lighting (ZigbeeProtocolZigbeeVeteran 2.4 GHz mesh — backbone of many smart home hubsView profile/Thread usually fit better).

What BLE is and how it differs from classic Bluetooth

Bluetooth Low Energy shares its brand with the Bluetooth we've always known, but it's a different protocol. "Bluetooth Classic" (BR/EDR) is designed for continuous streaming: headphone audio, car hands-free. BLEBTermBluetooth Low Energy (BLE)Bluetooth Low Energy (BLE) is the low-power variant of Bluetooth, for sending small amounts of data intermittently with minimal battery. It dominates wearables and proximity. Maintained by the Bluetooth SIG.View profile is designed for the opposite: sending a small data point (a temperature reading, a heart rate) and going back to sleep.

What made BLE ubiquitous in IoTITermIoT (Internet of Things)The IoT (Internet of Things) is the network of physical objects with sensors, software and connectivity that collect and exchange data and act autonomously.View profile isn't any single technical feat, but the fact that it's in every smartphone. Any BLE device has a potential gateway in its user's pocket. That makes it the natural choice for consumer products configured or read from an app.

How BLE works

Roles: central and peripheral

• Peripheral: the small device (a sensor, a wristband, a beacon). It advertises its presence and exposes data.
• Central: the one that scans and connects (typically the smartphone or a gateway).

Advertising and connection

A peripheral broadcasts advertising packets over three reserved channels. There are two paths:

1. Connectionless (broadcast): the peripheral only broadcasts data in the advertising. This is what beacons do (Apple's iBeacon, Google's Eddystone). There's no connection; anyone listening can read it.
2. Connection-oriented: the central sees the advertising, connects, and from then on they exchange data reliably over GATTGTermGATTGATT (Generic Attribute Profile) is BLE's data model: it organizes information into services and characteristics a client reads, writes or is notified about.View profile.

GATT: services and characteristics

Once connected, the data is organized hierarchically:

Profile
 └── Service (e.g. Heart Rate Service, UUID 0x180D)
      └── Characteristic (e.g. Heart Rate Measurement, UUID 0x2A37)
           ├── Value (the data bytes)
           └── Descriptors (metadata, e.g. notifications on/off)

The central can read, write, or subscribe to notify/indicate to receive updates when the value changes (for example, on every heartbeat). The SIG defines standard services (heart rate, battery, temperature) and allows custom 128-bit UUIDs for custom data.

GAP: discovery and security

The GAP (Generic Access Profile) governs how devices advertise and connect, and security: pairing, bonding (remembering the pairing), and AES-128 encryption. BLE supports LE Secure Connections with ECDH to protect against eavesdropping during pairing — an improvement over the more vulnerable legacy methods.

BLE 5 PHYs

BLE 5 introduced several physical layers that are selected based on the goal:

• 1M PHY: the classic one, 1 Mbps, the default balance.
• 2M PHY: 2 Mbps, more data in less time (saves battery through faster transfer).
• Coded PHY (LE Long Range): sacrifices speed for range, reaching hundreds of meters in line of sight.

Real-world use cases

When NOT to use BLE

• Autonomous long range: even with Coded PHY, BLE is for proximity. For kilometers without a nearby gateway, use LoRaWAN or NB-IoTProtocolNB-IoT3GPP-standardized cellular LPWAN — carrier coverageView profile.
• Mature home-lighting mesh: BLE Mesh exists and works, but the fixed-home-automation ecosystem is still dominated by Zigbee and Thread. If your case is smart home, Zigbee or Thread offer a more mature ecosystem.
• Many devices publishing to a central backend without a phone in the loop: that's where the MQTT-over-Wi-Fi/cellular pattern fits better.
• Sustained high-throughput streaming: that's what Bluetooth Classic or Wi-Fi are for.

BLE Mesh: multi-node networks

Bluetooth Mesh (2017) is a specification on top of BLE for creating networks of many nodes, designed mainly for commercial lighting and buildings. It works through managed flooding: messages are relayed by relays rather than along calculated routes as in Zigbee. It's robust and simple, but less traffic-efficient than a routed mesh. It competes with Zigbee and Thread in the smart-building space, with the advantage of being able to interact with smartphones that already carry BLE.

BLE compared with the alternatives

Against Zigbee, BLE wins on phone integration and on wearables/proximity, while Zigbee has a more mature home-automation mesh. Against Wi-Fi, BLE uses far less power but offers less bandwidth and range. Against LoRaWAN, they play in different leagues: BLE is proximity (meters), LoRaWANProtocolLoRaWANOpen long-range, low-power LPWANView profile is long range (kilometers) with very little data.

Getting started: reading a BLE sensor with an ESP32

The ESP32 has an integrated BLE radio, which makes it ideal for prototyping both peripherals and centrals. This ArduinoCompanyArduinoOpen source hardware and software platform for makersView profile example creates a peripheral that exposes a temperature characteristic via notification.

#include <BLEDevice.h>
#include <BLEServer.h>
#include <BLEUtils.h>
#include <BLE2902.h>

#define SERVICE_UUID        "180A"   // Device Information (example)
#define CHAR_UUID           "2A6E"   // Temperature

BLECharacteristic *tempChar;

void setup() {
  BLEDevice::init("ESP32-Sensor");
  BLEServer *server = BLEDevice::createServer();
  BLEService *service = server->createService(SERVICE_UUID);

  tempChar = service->createCharacteristic(
      CHAR_UUID,
      BLECharacteristic::PROPERTY_READ | BLECharacteristic::PROPERTY_NOTIFY);
  tempChar->addDescriptor(new BLE2902());

  service->start();
  BLEDevice::getAdvertising()->start();
}

void loop() {
  int16_t tempCenti = 2150;  // 21.50 °C in centigrade x100
  tempChar->setValue((uint8_t*)&tempCenti, 2);
  tempChar->notify();
  delay(2000);
}

From the phone, an app like nRF Connect (Nordic SemiconductorCompanyNordic SemiconductorSpecialist in low-power wireless connectivityView profile) scans, connects, and shows the characteristic notifying every 2 seconds. It's the fastest way to inspect and debug any BLE peripheral.

Pros and cons

Pros

• Ubiquitous: built into every smartphone and most modern MCUs (ESP32, nRF52).
• Minimal power draw: ideal for coin cells and devices that sleep almost all the time.
• A standard with defined profiles: standard GATT services for health, battery, etc.
• Versatile: connectionless (beacons), connection-oriented (sensors), or mesh.
• Excellent tooling ecosystem (nRF Connect, libraries on every platform).

Cons

• Proximity: limited range, no substitute for long-range networks.
• Saturated 2.4 GHz band: coexistence with Wi-Fi and Zigbee.
• Modest throughput: no heavy multimedia.
• Profile fragmentation: outside the standard services, every vendor invents custom UUIDs.
• Security depends on the implementation: the legacy "Just Works" pairing doesn't authenticate; you have to use LE Secure Connections.

Primary sources

• Bluetooth SIG — Specifications — the body that maintains the standard (accessed: 2026-05)
• Bluetooth Core Specification 5.4 (accessed: 2026-05)
• Nordic Semiconductor — nRF Connect — the reference tool for debugging BLE
• Bluetooth Mesh Networking (accessed: 2026-05)