What is Bluetooth LE? (Low Energy)

Move small amounts of data at the right time with less energy
Hello everyone, Bluetooth Low Energy, commonly called Bluetooth LE or BLE, is a wireless technology introduced with Bluetooth 4.0 for devices with low energy requirements. Part of the Bluetooth family, it is particularly useful for intermittent measurements, status updates and control data. Much of its energy advantage comes from brief radio activity separated by sleep periods. Assess the complete operating cycle rather than the instantaneous current alone.
How do devices discover each other?
BLE uses the 2.4 GHz radio-frequency band. A device can announce its presence or short data using advertising; another device listens through scanning. Advertising here means a radio announcement, not commercial advertising. A beacon, for example, can broadcast an identifier or status without establishing a connection. Not every advertisement accepts connections: connectable and non-connectable advertising serve different purposes.
Legacy advertising uses the three primary channels numbered 37, 38 and 39. Its advertising data field holds up to 31 bytes, shared by the name and other included fields. Extended advertising offers different packet and secondary-channel capabilities, subject to device support. In Bluetooth operation, discovery, connection establishment and pairing are separate procedures; reading data does not always require a user-facing pairing dialogue.
Central, peripheral, client and server are different roles
In a typical connection, the phone is the central and the sensor is the peripheral. The central scans and initiates the connection. GATT client and GATT server describe data-access roles instead: the server exposes a database and the client initiates operations. These role pairs are not interchangeable. A device can be both a client and a server; simultaneous connection capacity depends on implementation. A device name alone does not reveal these distinctions when pairing Bluetooth devices.
How GATT carries measurements and settings
GATT organises data into services and characteristics. A service groups related functions; a characteristic represents a measurement, setting or status. A UUID identifies the type of an item. Products can use standard or custom services. If a custom temperature characteristic represents 23.50 °C as the number 2350, its scale, numeric type, byte order and unit must be documented. This example encoding is an application choice, not BLE's mandatory temperature format.
A read retrieves a value and a write changes one. Once enabled, a notification carries updates to the client without requiring an ATT-level confirmation for each notification. An indication requires ATT confirmation. Link-layer error checking and retransmission do not prove that the receiving application processed every measurement. Critical records can use sequence numbers, timestamps and application acknowledgements. Across Bluetooth applications, this distinction matters more than simply reporting that data was sent.
The settings that determine energy consumption
Bluetooth power consumption depends on advertising frequency, connection intervals, data volume, transmit power and processor sleep time. Advertising once a second instead of every 100 ms can reduce average radio activity while increasing discovery time. A gateway scanning continuously has a different energy budget from a sensor advertising intermittently. LEDs, regulators, sensor supplies and active debugging interfaces can outweigh savings in the radio itself.
For connected devices, the connection interval determines the spacing between communication events. Peripheral latency allows certain events to be skipped under appropriate conditions. The supervision timeout determines when a lack of valid communication causes the connection to be considered lost. For example, changing an interval from 30 ms to 300 ms can save energy with sparse traffic, while increasing command waiting time. Parameters must be mutually consistent and accepted by the peer. The longest interval is not the best setting for every application.
Battery-life calculation: include the whole device
A simplified estimate is operating time = usable capacity / average current. With a hypothetical usable capacity of 220 mAh and total average current of 20 µA, 220 / 0.020 gives 11,000 hours, about 458 days. If other circuits add 80 µA, the total becomes 100 µA and the estimate falls to 2,200 hours, about 92 days. This is not a product battery-life promise. Temperature, ageing, pulse loads and voltage limits affect the capacity that can actually be used.
Why maximum speed and maximum range require different trade-offs
Common PHY options include LE 1M at 1 Mbit/s, LE 2M at 2 Mbit/s and LE Coded at 500 or 125 kbit/s. These are physical-layer rates. On a suitable link, 2M can shorten radio airtime for the same data. Coded PHY uses error-correction coding to help communication at weaker signal levels, while increasing airtime per unit of data. Not every device supports every option; check version and feature support together.
Application throughput depends on ATT MTU, link-layer data length, packets per event, the phone's stack and retransmissions. These are distinct parameters. For example, with an ATT MTU of 23 bytes, a standard notification can carry up to 20 bytes of characteristic value. Larger MTUs are possible, so “BLE only sends 20 bytes” is not a universal limit. For large files or images, consider the differences between Bluetooth and Wi-Fi.
Bluetooth range depends on antenna placement, transmit power, receiver sensitivity and the environment. Closing a metal cover can disrupt a previously working connection; moving a sensor a few centimetres can change the result. RSSI indicates signal strength; it is not a precise distance measurement by itself. Traffic from 2.4 GHz Wi-Fi shares the environment. Test with machinery and networks operating, as well as in an otherwise quiet workshop.
Pairing, encryption and access control
Pairing establishes security keys, while bonding stores them for future connections. A connected status does not by itself establish encryption or user authorisation. Bluetooth security requires consideration of the pairing method, characteristic access permissions and peer identity verification. Just Works does not provide authentication against a man-in-the-middle attack. Advertising packets must not automatically be treated as confidential. Successfully writing a setting also does not prove that a physical action completed; read back the relevant result.
Are BLE, mesh and LE Audio the same thing?
No. Bluetooth Mesh is a separate networking approach built on BLE; a BLE sensor is not automatically a mesh node. LE Audio requires compatible audio profiles, isochronous transport and components such as LC3. An ordinary BLE data service does not turn a module into a wireless headset. Radio capability and application support must be checked separately.
Industrial example: from a battery-powered sensor to a PLC
Consider an IoT application in which a sensor sends temperature and battery status every five seconds. It communicates over BLE with a gateway, which converts the data into a form the PLC or server understands. BLE does not automatically become Modbus or Ethernet. Data mapping and failure behaviour require design. A gateway with an Ethernet connection faces different site conditions from one using Wi-Fi.
For example, a project could mark a reading as stale after 15 seconds without a new measurement. The display shows the last value and its measurement time; sensor timestamps and sequence numbers can also be transmitted where needed. Fifteen seconds is a hypothetical application decision, not a BLE requirement. Preventing old measurements from appearing current is more useful than relying on a connection icon alone. For industrial remote control and safety functions, assess the product's intended use and applicable standards separately.
When BLE fits and when to consider alternatives
Battery-powered measurements, nearby parameter configuration, diagnostics and wearable products are suitable candidates for BLE. Compare alternatives for continuous high data rates, demanding coverage conditions or strict timing requirements. Compare Wi-Fi power consumption with BLE under the same data workload and latency target. When selecting a remote control solution, a low-energy label alone is insufficient.
Connected, but no data: what should you check?
Start with the correct service and characteristic UUIDs, read permissions and notification subscription. Then check data encoding, application permissions, security requirements and reconnection behaviour. If scanning cannot find the device, inspect its advertising type, scan filters and advertising interval. Frequent disconnections call for checks of battery voltage, timing and antenna conditions. Distinguish Bluetooth connectivity issues from Wi-Fi-related environmental problems before increasing transmit power at random.
Related topics and further reading
Bluetooth fundamentals: What is Bluetooth?, How it works, Versions and features, Range, Energy consumption.
Connections and applications: Device pairing, Data security, Connection troubleshooting, Applications, Health questions.
Networks and industrial applications: Bluetooth versus Wi-Fi, Wi-Fi fundamentals, Internet of Things, Industrial remote control, Remote control standards, Remote control overview.
Sources
Bluetooth SIG: BLE architecture, advertising and data transport
Bluetooth SIG: Dual-mode and supported functionality
Silicon Labs: GATT client and server roles
Silicon Labs: Acknowledged and unacknowledged GATT operations
Silicon Labs: Throughput, MTU and packet size
Silicon Labs: Current consumption and sleep conditions
Nordic Semiconductor: Connection parameters and power trade-offs
Android Developers: BLE, services and application roles
Bluetooth SIG: Physical factors determining range