What’s new in Bluetooth®︎ Core 6.2: An overview

RE: What’s new in Bluetooth®︎ Core 6.2: An overview

Murad — Sat, 11 Apr 2026 14:37:55 GMT

@Joel Kauppo or anyone from Nordic,

I have a question regarding Google Find My Device / Find Hub SDK access.

We are developing an ultra-small BLE tag (MicroTag) under SONYROID Co., Ltd. (Project ID: 59106960746) and I need to understand the exact process to obtain the Find My Device SDK and API from Nordic.

Specifically:
1. What is the approval process? Do we need Google's approval first, or do we request from Nordic directly?
2. Is there a public API for backend to fetch location data, or is the location data only available to the end-user on their phone?
3. I already submitted a private ticket. Will Nordic provide the SDK access through that, or do I need to contact someone specific (e.g., Brian Ha)?

Any guidance would be greatly appreciated. Thank you!

RE: What’s new in Bluetooth®︎ Core 6.2: An overview

Valon.Shen — Thu, 11 Dec 2025 03:40:53 GMT

Hello, I have some questions. If we update the interval to the minimum value （375us）, what is the maximum amount of ACL data we can send?

If the data is too long (such as sending a control packet), will we encroach on the next interval?

If not, does that mean we can never send overly long packets? For example, for a CONNECTIN RATE IND , would we be unable to update the interval to a larger value?

RE: What’s new in Bluetooth®︎ Core 6.2: An overview

Emil Lenngren — Tue, 11 Nov 2025 14:04:34 GMT

The changes about legacy passkey pairing can be found in Table 2.8 in the Security Manager specification.

Notably, legacy passkey pairing is no longer considered "authenticated", meaning that it no longer satisfies Security Mode 1 Level 3.