Pairing failed with BT_SECURITY_ERR_PIN_OR_KEY_MISSING error.

[jhc]

Hi all

I have two units, one acts as Central and the other one acts as Peripheral.

I erase chip of one of the units, and then always failed to pairing, with a BT_SECURITY_ERR_PIN_OR_KEY_MISSING error.

Are there any settings or APIs to make the pairing successfully completed even if the PIN or KEY has been erased?

My development environment:

SDK: ncs v1.9.1,

CHIP: nrf52840

As a reference, when developing with legacy SDK sdk15.2, I always use the following codes to get the units successfully repaired:

Thank you very much!

[Jared]

Hi there,

Have you tried to delete the bonding on the other device and re initiate the pairing process.

regards

[jhc]

I use bt_unpair to delete the bonding data once the error comes out, but this will lead to a disconnection first, which is not what I expect.

[Jared]

Hi,

Are you calling it while you're already in a connection? Are you deleting the bonding information after the secure connection has already been established?

jhc said:

I use bt_unpair to delete the bonding data once the error comes out, but this will lead to a disconnection first, which is not what I expect.

What did you expect instead?

regards

Jared 

[jhc]

I want it could be repaired during the connection without reconnecting again by after deleted bonding data.

[Jared]

Hi,

If you're deleting the bond while in a connection, then I think it's expected that it will disconnect.

I'm wondering why you're deleting the bond while in a connection? What is the purpose of this?

regards

Jared 

[jhc]

Back to the question of this thread, how to let the pairing continue smoothly (without any reconnection) when I get a BT_SECURITY_ERR_PIN_OR_KEY_MISSING error during the pairing phase.

That is what I expected originally.

[Jared]

I understand,

Can you try to enable this and this in your kconfig?

Could you also double check in your kconfig from the build folder that this is already enabled?

regards
Jared 

[jhc]

Sure, these three CONFIGs are all already enabled, but cann't work.