peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

Edvin — Mon, 20 Jan 2020 10:00:06 GMT

On the nRF, the easiest is to run the Nordic Command Line Tools command:
"nrfutil --eraseall"

and the reprogram your application. Let me know if you are having trouble doing this. If so, what IDE do you use?

What is your other device? If it is a phone, you must enter your bluetooth settings and select something like "Forget Device". If it is another nRF52810 you are trying to connect to, then you should erase that chip and reprogram it like the other one.

Best regards,

Edvin

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

kfcube — Mon, 20 Jan 2020 09:27:03 GMT

How to erase the bonding information?

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

Edvin — Mon, 06 Jan 2020 14:18:07 GMT

I don't know what numbers the events are coming from, but what I am interrested in is the log messages coming from the peer_manager_handler.

Now. Did you try to erase the bonding information both on the nRF and on the connected device? Please let me know if you are not sure how to do that. Also, please let me know what you are trying to connect to.

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

kfcube — Sun, 22 Dec 2019 00:11:31 GMT

From the log below:

<debug> nrf_ble_gq: Registering connection handle: 0x0000

<info> app: Connected.

<info> app: start timer here

<info> app: pm_evt_handler, event id: 0x1

<info> app: pm_evt_handler, event id: 0x3

<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

<info> app: ble_cube_on_ble_evt, evt: 0x14

We can see that the error happened after the ble connected. When the p_evt ->evt_id is 0x3, it reported this error.

Please give me some hints on how to fix it.

Thanks,

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

Edvin — Fri, 20 Dec 2019 13:30:51 GMT

This event is coming after a BLE_GAP_EVT_CONNECTED event, right? Are you trying to connect to it?

Regarding the LOG LEVEL 4, please check that app_timer_init() is called before log_init() in your main() function. I believe that there is a bug in some of the SDK examples from SDK16.0.0 that has this in the reverse order.

Best regards,

Edvin

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

kfcube — Fri, 20 Dec 2019 12:21:09 GMT

Sorry my bad. Now I can see my log. bug there is only one debug info. I put it here:

<debug> nrf_ble_gq: Registering connection handle: 0x0000

<info> app: Connected.

<info> app: start timer here

<info> app: pm_evt_handler, event id: 0x1

<info> app: pm_evt_handler, event id: 0x3

<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

I don't see its helpful. Maybe as you said, its just because other device. Anyway it doesn't stop the mobile connect to the app.

Thanks,

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

kfcube — Fri, 20 Dec 2019 11:54:03 GMT

There is NO other device connecting my DK. Maybe its the USB driver coz I keep receiving msgs says that the disk is not ejected properly. Anyway, I change the LOG LEVEL to 4 by changing sdk_config.h, and now I see nothing in the RTTClient. I don't know what's happened. You sure the level 4 work?

Thanks,

RE: peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102

Edvin — Fri, 20 Dec 2019 11:32:31 GMT

Hello,

Searching though this forum, it seems like most of these error messages with error code 0x4102 comes from one of the devices that already has stored bonding information, while the other one does not.

Can you please try to delete the flash entirely (you can use "nrfjprog -e"), and reprogram it, and then delete the bonding information on your other device. What sort of the device is your other device? And the device that print this error message, is that the central or the peripheral?

If that doesn't work, please try to set the log level to debug by changing:

#define NRF_LOG_DEFAULT_LEVEL 3

#define NRF_LOG_DEFAULT_LEVEL 4

What does the log say then?

Best regards,

Edvin