Bonding occurs after incorrect Passkey entry.

[mbredes]

I am using a static passkey to set up pairing and after that the devices are supposed to bond. The issue I am encountering is that when the wrong passkey is entered or if the passkey entry is allowed to time out the central device acts like it has successfully bonded(which it shouldn't have done) but if services are discovered or enabled it will show that they all have insufficient authentication. Why is the bonding occurring when the passkey that is entered is incorrect/the passkey is never entered?

[Petter Myhre]

To me it sounds like bonding is not occuring, since you get insufficient aithentication.

It is up to the application to react when pairing fails.

You will get the BLE_GAP_EVT_AUTH_STATUS event.

With it you can check the auth_status field in the ble_gap_evt_auth_status_t struct to see the security status:

BLE_GAP_SEC_STATUS_SUCCESS (0x00)
BLE_GAP_SEC_STATUS_TIMEOUT (0x01)
BLE_GAP_SEC_STATUS_PASSKEY_ENTRY_FAILED (0x81)

Implement the reaction you want when pairing is not successful.

[jokii]

I think it was my fault, I've messed too much in example;/ now working as expected when introduced solution from here: devzone.nordicsemi.com/.../ Not see bonds left any more.