This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

(re)bonding with nRF Connect v2.3.0

Hi!

I may have found a bug/problem with nRF Connect v2.3.0.

I'm developing an BLE peripheral device based on nRF52832 and using nRF Connect (with PCA10040) as central for testing.

(SDK 15, SD6, SES V3.34)

The device uses privacy, bonding with LESC and directed advertising.

Bonding (and undirected advertising) needs to be started manually.

The Problem:

- nRF Connect discovers the device correctly (while in bonding/fast advertising mode)

- connecting and bonding also works as expected

- after disconnection, directed advertising is also correctly discovered

- reconnection works, and the device-name is also displayed correctly again

- the device detects a previously bonded peer

- BUT when I try to "pair" in order to re-encrypt the link based on stored LTKs, nRF Connect always starts procedure 1 (pairing & bonding) instead of procedure 0 (just encrypt with stored keys).

I tried the same with a Cypress Dongle and CySmart 1.2 - with that it works as expected

Did I miss something? Or is there a different way to re-encrypt the link without rebonding?

Thanks and best regards!

Related