how can i initiate unbonding on the peripheral side?

RE: how can i initiate unbonding on the peripheral side?

kruenheck — Fri, 31 Oct 2025 14:18:35 GMT

I got it by eliminating the call to bt_conn_auth_cb_register() in main().

RE: how can i initiate unbonding on the peripheral side?

kruenheck — Wed, 29 Oct 2025 21:46:03 GMT

Daniel,

Thank you for this information. Lesson 5 Exercise 2 did the trick. Unfortunately I recently found out that my peripheral will need to pair and bond without access to the terminal, so I can't use the six digit key. So what's needed is the pairing method of Exercise 1 (through Step 7) with the bonding and white listing capabilities of Exercise 2.

I attempted to accomplish this by changing the characteristics (in exercise 2) from

BT_GATT_PERM_WRITE_AUTHEN to

BT_GATT_PERM_WRITE_ENCRYPT, but I'm still getting the passkey display on the terminal and request on my phone. Is there something I can remove from Exercise 2 that will make it only require security Level 2 but still perform bonding and whitelisting?

Thank you

RE: how can i initiate unbonding on the peripheral side?

DanielNG — Mon, 27 Oct 2025 18:58:37 GMT

Hi are you using nRF Connect SDK or nRF5 SDK?

Assuming that you are using ncs, you can take a look at lesson 5 exercise 2 on our Dev Academy BLE Fundamentals course and the associated github to see how bt_unpair() is implemented to perform unbonding.

Please note that if only the peripheral deletes the bond, the next connection attempt will typically fail (the link cannot be re-encrypted) until the central also forgets the device in its Bluetooth settings. This is a limitation of how Bluetooth bonding works: both sides must remove the bond for a new pairing to the same device to succeed.

Please give me more details if you still have questions (what sdk are you using, version,...)