https://devzone.nordicsemi.com/f/nordic-q-a/15155/overwriting-bond-information-reliablyHi, I have a situation where our central device needs to be paired atmost with 1 peripheral. I can put a central device into repairing mode for 3 minutes. Within this time if another peripheral is found it shud connect and store bond information. Ifen-USTelligent Community 13Wed, 10 Aug 2016 12:47:06 GMThttps://devzone.nordicsemi.com/thread/57866?ContentTypeID=1Wed, 10 Aug 2016 12:47:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5ed2a578-965c-4c05-8bd8-17f208d7fbd7bjorn-spockeli<p>You will have to use <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk51.v10.0.0/group__dm__cntxt__mgmt__api.html#gaf267e34f237c41665fd9df15dd32c531">dm_device_delete</a> or <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk51.v10.0.0/group__dm__cntxt__mgmt__api.html#ga677524b3230bd620c91a83e4f68e3e01">dm_device_delete_all</a> to delete the old bonding information, then wait for the <code>DM_EVT_DEVICE_CONTEXT_DELETED</code> event and then call <code>dm_security_setup_req()</code> to to bond with the new device.</p> <p>Alternatively, you could increase <code>DEVICE_MANAGER_MAX_BONDS</code> to 2 so that you can bond to both devices. After the new device has bonded successfully you can delete the bonding information to the old device. This requires some “bookkeeping” as you will have to make sure that you only allow two devices to be bonded to the central when it’s in “repair-mode” and only one when it’s in its normal operating mode.</p> <p>I suggest that you take a look at <a href="https://github.com/NordicSemiconductor/nRF51-ble-peripheral-bond-handling">this</a> GitHub repo, it contains an example on how to delete the oldest bond information.</p> <p>-Bjørn</p><div style="clear:both;"></div>