Bluetooth LE Connections: Roles, Events, and the Parameters That Keep a Link Alive
Bluetooth LE's connection model is full of subtle distinctions that routinely cause mismatches, reconnection bugs, and silent data failures in mobile and IoT apps. Knowing exactly what a connection does and does not guarantee saves hours of debugging and prevents designs that misuse roles or parameters.
Connecting a phone to a smart lock is not a single handshake; it is an agreement on timing, channels, and failure detection. This guide walks through the core mechanics of a Bluetooth LE ACL connection, starting with the distinction between broadcast and connection, and the four GAP roles (Broadcaster, Observer, Peripheral, Central). It stresses that roles are not fixed labels: a phone can act as Central in one connection and Peripheral in another, and Central does not mean GATT Client.
The connection flow itself is precise: a peripheral sends connectable advertising, the central responds with CONNECT_IND, and the two sides then meet in repeated connection events. There is no extra acceptance packet in the traditional path, unlike extended advertising which uses AUX_CONNECT_REQ and AUX_CONNECT_RSP. The guide explains how connection events alternate sends, how channel hopping works, and why link-layer acknowledgment is not the same as business success.
Three parameters determine the rhythm and durability of a connection: connection interval, peripheral latency, and supervision timeout. Their relationship is captured by the constraint that supervision timeout must exceed 2 * (latency + 1) * interval. Newer features like Shorter Connection Intervals (down to 0.375 ms with Core 6.2) and connection subrating add flexibility but require support on both sides. The guide closes with the post-connection tasks: service discovery, pairing vs bonding, and what reconnection actually requires.
The common mental model of Bluetooth pairing conflates connection, pairing, and bonding; this guide separates them cleanly, which is exactly where many Android and Flutter bugs originate.
The distinction between legacy connectable advertising and extended advertising is not just a spec detail; it changes the protocol state machine, and apps that assume a confirmation packet after CONNECT_IND will misread the sequence.
Connection subrating solves a real tradeoff: instead of choosing between a slow idle interval and a fast one, a device can keep a fast base schedule and simply skip events, which is more responsive when burst data arrives.
The supervision timeout formula is a practical constraint that most developers never reason about until they see intermittent disconnects; knowing the math helps set parameters that do not contradict the link layer.