peerManager and Legacy Pairing

[Stephane Masson]

Hello,

I am trying to use the peer manager on a nRF52832 acting as a peripheral  with both bonding and legacy pairing on SDK 16.0.0.

The application configured with bonding works fine (tested with Android phone on nRF connect), but when I configure the security parameters as pairing and no bonding I get some issues. The securitty process and the conenction are succeeding, however when I look in the peer manager it seems nothing is stored (pm_peer_count returns 0, while in bonding it returns 1 as expected). Also reconnecting the same host to my device does not trig the PM_EVT_BONDED_PEER_CONNECTED event. 

Did I misunderstood something on the peer manager? is it supposed to store information about the peers that are not bonded but only paired ? Is the legacy pairng supported ? Or did I forgot to do something?

Securtity parameters used: Pairing, no bonding:

sec_param.bond = false ;
sec_param.mitm = false;
sec_param.lesc = 0;
sec_param.keypress = 0;
sec_param.io_caps = BLE_GAP_IO_CAPS_KEYBOARD_ONLY;
sec_param.oob = false;
sec_param.min_key_size = 7;
sec_param.max_key_size = 16;
sec_param.kdist_own.enc = 0;
sec_param.kdist_own.id = 0;
sec_param.kdist_peer.enc = 0;
sec_param.kdist_peer.id = 0;

Thanks for your help !

Stéphane

[Edvin]

Hello,

The Peer Manager will only store information from bonded devices, and not paired devices. Bonding is actually exactly that, that you store the keys for later use, so that you don't need to perform the pairing again every time you connect. 

So it is expected that the Peer Manager doesn't store anything on devices that are only paired, and not bonded. Likewise, you will not get the PM_EVT_BONDED_PEER when a device is not bonded. 

BR,

Edvin

[Stephane Masson]

Thank you!

It was not clear for me wether or not legacy pairing was supposed to store data or not!