Bluetooth 6.2: what the new core specification changes

ReportedPublished 10 January 20264 min read

A development board with an exposed antenna trace clamped in a vice beside fine probes on a grey bench mat

Bluetooth 6.2 arrived on 4 November 2025, according to the Bluetooth SIG's own Core 6.2 feature overview, and the trade coverage that followed described it mostly in terms of latency. For anyone who owns a finding tag the useful question is narrower: does any of it reach the coin-cell device on your key ring? The short answer is no, and the reasons are worth setting out, because they explain how specification releases relate to the hardware already in circulation.

What the release contains

Writing on 5 November 2025, Nordic Semiconductor's Joel Kauppo summarised the release as five groups of changes. They are, in the order the specification presents them:

Feature	What it does	Relevance to a finding tag
Shorter Connection Intervals	Allows connection intervals below the previous 7.5 ms floor, down to 375 µs, supporting report rates above 2 kHz	None — tags broadcast rather than hold a connection
Channel Sounding attack resilience	Adds an amplitude-based Normalized Attack Detection Metric to the ranging feature	Only for devices that implement Channel Sounding
HCI USB LE Isochronous support	A Bulk Serialization Mode for carrying isochronous packets over USB	None — this is a host-side audio concern
LE test mode enhancements	A Unified Test Protocol for radio measurements	Manufacturing and certification only
Security and privacy errata	Four corrections to passkey generation, mitigating reflection attacks on legacy pairing	None — a finding tag does not use legacy pairing

TechPowerUp's coverage of the release framed the headline feature as responsiveness for latency-sensitive peripherals such as gaming keyboards and stylus input, which is a fair reading of where Shorter Connection Intervals will be used.

Why none of it touches the tag on your key ring

A finding tag does not maintain a Bluetooth connection in the ordinary sense. It advertises: it transmits short packets into the air at intervals and never establishes a session with the devices that hear them. Connection-interval improvements are therefore irrelevant to it by construction — there is no connection whose interval could be shortened.

The Channel Sounding change is the one that sounds closest to the subject, and it is worth being precise about what it is. It does not introduce ranging; Channel Sounding was introduced in Core Specification 6.0, adopted on 3 September 2024. What 6.2 adds is a defence: a metric for detecting attacks that manipulate signal amplitude to spoof a distance measurement. That matters enormously for keyless vehicle entry and access control, where a falsified distance opens a door. It matters not at all to a tag that never measures distance in the first place.

Our earlier piece on what the Bluetooth specification says about tags sets out the advertising model that makes this so.

The gap between a specification and a product

This is the general point, and it recurs with every release. The Bluetooth SIG publishes a specification; silicon vendors then implement the parts their customers want; module makers then design those chips into products; and manufacturers then ship them. Each stage adds months.

Coverage at the time of the 6.2 release suggested the first chipsets supporting it were expected around the middle of 2026, with finished devices later in the year. For a category as cost-sensitive as finding tags, the lag is longer still: a tag sells for a few pounds, so it uses mature, cheap, well-understood silicon rather than the newest part in the catalogue.

Two consequences follow for buyers. First, a box that says "Bluetooth 5.3" or "Bluetooth 6.0" tells you almost nothing about how well a tag will find your keys — the finding behaviour comes from Apple's Find My protocol running on top, not from the core version underneath. Second, there is no upgrade path. A specification release cannot be installed on a device that shipped before it; the radio is fixed in hardware.

What would actually change a finding tag

Only one thing on the current roadmap would: Channel Sounding reaching low-power, low-cost silicon and being adopted by the platform owners. That is a real prospect rather than a speculative one, and it is moving. But it requires the feature at both ends — in the tag and in the phone — and it requires the operating system to expose it. Until all three line up, the last few metres of a search are closed by a map and a buzzer.

How BlueTag sits against all this

BlueTag is a broadcast-only Bluetooth Low Energy device, which is why nothing in the 6.2 release alters it and why nothing in a future release will either. It advertises a rotating, anonymous identifier; any passing Apple device that hears it reports an encrypted position that only your Apple Account can decrypt.

The specification that governs what it can do for you is Apple's, not the core release number. Within roughly 60 m / 200 ft your iPhone holds the link and can sound the 80–100 dB buzzer; past that the Find My network carries the sightings. There is no Ultra Wideband and no Channel Sounding in it, so there is no on-screen arrow — a limitation we would rather state than let you infer from a version number on a box. iOS 14.5 or later, iPhone and iPad only, IP67, a CR2032 that runs up to two years and twists out when it does not. Two tags in a box, free UK delivery, under £15. The full specification is here.

Sources

From the desk of Bluetooth Tracker Last revised 10 January 2026

Related notes

← All workbench notes