PeerManager error (error: 133)

[takashina hiroki]

I have a question about PeerManager.

SDK: 15.3.0
example: ble_app_multirole_lesc (I changed the source from the sample)
using device: EYSHJNZWZ (nRF52832)
connection device: Android (Bluetooth v5.0)

When trying to connect with LESC security level using PeerManager, the following error occurred.
Please tell me the cause.

<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133
<warning> peer_manager_handler: Disconnecting conn_handle 0.

I know that this error means "BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP".
The connection partner supports pairing.
I confirmed that I could connect many times.
However, this error may occur.
Also, after this error occurs, the same error will occur no matter how many times you try to connect.
This error does not occur after reset.

[Simonr]

Hi

Yes, the clock configuration seems correct. So as long as you've connected it correctly that should not be the problem. Do you have a Development Kit to test your application on to, so that we can confirm this?

You could also try commenting out BLE_GAP_EVT_SEC_PARAMS_REQUEST in the ble_evt_handler, as bonding/pairing should be handled by the peer manager.

Best regards,

Simon

[takashina hiroki]

Yes, I have a development kit to test the application.
Please tell me how to confirm that the clock setting is correct.

In the sample of "ble_app_multirole_lesc", nothing is processed when "BLE_GAP_EVT_SEC_PARAMS_REQUEST" occurs.
What does "comment out" mean?