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

Your clock settings are correct, I just want you to test the application on your DK to, to narrow down the source of the problem.

Comment out means that you add // in front of the function, so that it is no longer active in your code, as it is a comment. Could you please try, as this has solved some similar cases in the past.

Best regards,

Simon

[takashina hiroki]

Excuse me, it seems that the explanation was not enough.

I know about the meaning of commenting out itself.
In the sample of "ble_app_multirole_lesc", there is no processing for "BLE_GAP_EVT_SEC_PARAMS_REQUEST".
Therefore, there is no process to comment out.
What process should you comment out?