Unpairing from central from nRF52

[TREvans]

I have an nRF52 paired to a central device. In order to delete the pairing on the nRF52 I clear the persistent data (dm_init_param_t).

I notice, however, that even though the pairing data is gone, the central device is still connecting with the nRF52. This makes sense because the central device does not know that the nRF52 (peripheral) has deleted the pairing information.

Is there a way to notify the central device that the unpairing has occured from the nRF52?

[Jørgen Kvalvaag]

In this scenario the central must already know that the bond is missing. Most likely, it will create a new bond to replace the old one.

When the central initiates the security procedure, it first asks the peripheral to encrypt the link using stored keys. If no known bond exists in the peripheral, it will reply that the keys are missing.

The central is then free to start a new bonding procedure, which Device Manager by default will accept.

The SoftDevice documentation contains some nice message sequence charts that describe these procedures in detail. Link s130 docs