Please tell me how to achieve re-pairing.

RE: Please tell me how to achieve re-pairing.

Joakim Jakobsen — Tue, 13 Dec 2022 09:32:27 GMT

Thanks for sharing the solution!

Br,
Joakim

RE: Please tell me how to achieve re-pairing.

sdi_kei — Mon, 12 Dec 2022 11:20:52 GMT

Hello.
Sorry for the late reply.

I found the reason why my code did not re-pair.
When PM_EVT_CONN_SEC_CONFIG_REQ occurred, it was not processed in the event handler, but was stored as a task and processed after some time had passed.

As you taught us, we implemented PM_EVR_CONN_SEC_CONFIG_REQ and were able to re-pair.

Thank you!

RE: Please tell me how to achieve re-pairing.

Joakim Jakobsen — Thu, 03 Nov 2022 14:03:53 GMT

Thanks!

Before looking at your logs, I tested this in an example myself, to check if I would reproduce the issue.

static void pm_evt_handler(pm_evt_t const * p_evt)
{
    pm_handler_on_pm_evt(p_evt);
    pm_handler_disconnect_on_sec_failure(p_evt);
    pm_handler_flash_clean(p_evt);

    pm_conn_sec_config_t conn_sec_config;

    switch (p_evt->evt_id)
    {
        case PM_EVT_PEERS_DELETE_SUCCEEDED:
            advertising_start(false);
            break;
        
        case PM_EVT_CONN_SEC_CONFIG_REQ:
            conn_sec_config.allow_repairing = true;
            pm_conn_sec_config_reply(m_conn_handle, &conn_sec_config);
            break;

        default:
            break;
    }
}

Paired the device to my phone. Then I deleted the bond on the central (phone) side, and tried to re-pair. Works as expected.

BR,
Joakim

RE: Please tell me how to achieve re-pairing.

sdi_kei — Tue, 01 Nov 2022 12:33:40 GMT

Hello.

I have re-logged the re-pairing.
I have changed the log level to Debug to output a more detailed log.
Can you tell the cause of the error from this information?

00> <debug> nrf_sdh_ble: BLE event: 0x10.
00> <debug> peer_manager_handler: Event PM_EVT_BONDED_PEER_CONNECTED
00> <debug> peer_manager_handler: Previously bonded peer connected: role: Peripheral, conn_handle: 0, peer_id: 0
00> <debug> peer_manager_handler: Event PM_EVT_CONN_SEC_PARAMS_REQ
00> <debug> peer_manager_handler: Security parameter request
00> <debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
00> <debug> peer_manager_handler: Event PM_EVT_LOCAL_DB_CACHE_APPLIED
00> <debug> peer_manager_handler: Previously stored local DB applied: conn_handle: 0, peer_id: 0
00> <info> app: Connected, handle 0x0.
00> <debug> nrf_sdh_ble: BLE event: 0x21.
00> <info> app: PHY update request.
00> <debug> nrf_sdh_ble: BLE event: 0x22.
00> <debug> nrf_sdh_ble: BLE event: 0x23.
00> <debug> nrf_ble_gatt: Peer on connection 0x0 requested a data length of 251 bytes.
00> <debug> nrf_ble_gatt: Updating data length to 27 on connection 0x0.
00> <debug> nrf_sdh_ble: BLE event: 0x24.
00> <debug> nrf_ble_gatt: Data length updated to 27 on connection 0x0.
00> <debug> nrf_ble_gatt: max_rx_octets: 27
00> <debug> nrf_ble_gatt: max_tx_octets: 27
00> <debug> nrf_ble_gatt: max_rx_time: 2120
00> <debug> nrf_ble_gatt: max_tx_time: 2120
00> <debug> nrf_sdh_ble: BLE event: 0x55.
00> <debug> nrf_ble_gatt: Peer on connection 0x0 requested an ATT MTU of 185 bytes.
00> <debug> nrf_ble_gatt: Updating ATT MTU to 23 bytes (desired: 23) on connection 0x0.
00> <debug> nrf_sdh_ble: BLE event: 0x50.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_FLASH_GARBAGE_COLLECTED
00> <debug> peer_manager_handler: Flash garbage collection complete.
00> <debug> nrf_sdh_ble: BLE event: 0x13.
00> <debug> peer_manager_handler: Event PM_EVT_CONN_SEC_START
00> <debug> peer_manager_handler: Connection security procedure started: role: Peripheral, conn_handle: 0, procedure: Bonding
00> <debug> peer_manager_handler: Event PM_EVT_CONN_SEC_PARAMS_REQ
00> <debug> peer_manager_handler: Security parameter request
00> <debug> peer_manager_handler: Event PM_EVT_CONN_SEC_CONFIG_REQ
00> <debug> peer_manager_handler: Security configuration request
00> <info> app: PM_EVT_CONN_SEC_CONFIG_REQ
00> <debug> nrf_sdh_ble: BLE event: 0x19.
00> <debug> peer_manager_handler: Event PM_EVT_CONN_SEC_FAILED
00> <info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133
00> <debug> peer_manager_handler: Error (decoded): BLE_GAP_SEC_STATUS 0x85
00> <info> app: Connection Security Failed. procedure: 0x1, error: 0x85, error_src: 0x0.
00> <info> app: No Bonding Infomation for Central.
00> <debug> nrf_sdh_ble: BLE event: 0x50.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_FLASH_GARBAGE_COLLECTED
00> <debug> peer_manager_handler: Flash garbage collection complete.
00> <debug> nrf_sdh_ble: BLE event: 0x50.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_FLASH_GARBAGE_COLLECTED
00> <debug> peer_manager_handler: Flash garbage collection complete.
00> <debug> nrf_sdh_ble: BLE event: 0x50.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_ble: BLE event: 0x50.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> nrf_sdh_soc: SoC event: 0x2.
00> <debug> peer_manager_handler: Event PM_EVT_FLASH_GARBAGE_COLLECTED
00> <debug> peer_manager_handler: Flash garbage collection complete.
00> <debug> nrf_sdh_ble: BLE event: 0x11.
00> <info> app: Disconnected. conn_handle: 0x0, reason 0x13.

Best regards and thank you in advance for your help.

RE: Please tell me how to achieve re-pairing.

sdi_kei — Tue, 01 Nov 2022 11:11:05 GMT

I didn't communicate it well, my apologies.

When I said when disconnected, I meant when BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP occurs and disconnection occurs.

Central (phone) does not remember pairing information because it is manually deleted.
This is because it wants to perform a re-pairing action.

Thank you in advance for your cooperation.

RE: Please tell me how to achieve re-pairing.

Joakim Jakobsen — Tue, 01 Nov 2022 10:59:11 GMT

[quote user="sdi_kei"]This is because we currently do not delete bonding information when disconnecting.[/quote]

You don't delete bonding information on when disconnecting, but you are unable to reconnect due to the bonding information is missing?

But on the phone side, you choose to disconnect and "forget" the device, thus deleting the bond information?

Br,
Joakim

RE: Please tell me how to achieve re-pairing.

sdi_kei — Tue, 01 Nov 2022 10:56:56 GMT

Thank you. Please confirm.

This is because we currently do not delete bonding information when disconnecting.

Best regards, and thank you in advance for your cooperation.

RE: Please tell me how to achieve re-pairing.

Joakim Jakobsen — Tue, 01 Nov 2022 10:40:49 GMT

I'll take a closer look at the error you get.

I would like to note that if you perform bonding; the best way to avoid this would be not to delete bond information upon disconnection.

Br,
Joakim

RE: Please tell me how to achieve re-pairing.

sdi_kei — Tue, 01 Nov 2022 10:35:48 GMT

Hello!
Thanks for the answer!

I have it set to true because I want to update the pairing request instead of rejecting it.

For the central device only bonding information is being deleted, PM_EVT_CONN_SEC_CONFIG_REQ is being called, but it is being errored by BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP.

Why am I getting an error even though I have set up an update?

Also, you say that re-pairing is only done if the central does not have bonding information, how can I update it if the peripheral does not have bonding information?

Best regards, and thank you in advance for your help.

RE: Please tell me how to achieve re-pairing.

Joakim Jakobsen — Tue, 01 Nov 2022 10:16:16 GMT

Hi.

What you are seeing is to be expected. Re-pairing is used for when the peripheral already have a bond for the central that is trying to connect. If the bond information is deleted on the central device and tries to pair with the peripheral that already has a bond with the central, you can use the allow_repairing to either reject the request or update the bond with the peripheral.

Using allow_repairing = false:

A connected peer (central) is trying to pair, but the Peer Manager already has a bond for that peer. Setting allow_repairing to false rejects the pairing request.

[quote user=""]re-paired when there is no pairing information for either peripheral or central.[/quote]

If there is no bonding information on either the peripheral or the central, there wouldn't be a reason to re-pair. Then you can simply pair the devices as normal.

Br,
Joakim

RE: Please tell me how to achieve re-pairing.

sdi_kei — Tue, 01 Nov 2022 07:12:22 GMT

I logged it thinking that PM_EVT_CONN_SEC_CONFIG_REQ may not have been called.

Logs where only pairing information for peripherals was deleted and re-paired.

00> <info> app: Connected, handle 0x0.
00> <info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102
00> <info> app: Connection Security Failed. procedure: 0x0, error: 0x1006, error_src: 0x0.
00> <info> app: No Bonding Infomation for Peripheral.
00> <info> app: Disconnected. conn_handle: 0x0, reason 0x13.

Logs where only central pairing information was deleted and re-paired.

00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
00> <info> app: Connected, handle 0x0.
00> <info> app: PHY update request.
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <info> app: PM_EVT_CONN_SEC_CONFIG_REQ
00> <info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133
00> <info> app: Connection Security Failed. procedure: 0x1, error: 0x85, error_src: 0x0.
00> <info> app: No Bonding Infomation for Central.
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
00> <info> app: Disconnected. conn_handle: 0x0, reason 0x13.

As a result, PM_EVT_CONN_SEC_CONFIG_REQ was done only when the central pairing information was deleted.

I still don't know why I can't re-pair.
If anyone can figure it out, please let me know!