SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Sigurd — Mon, 10 Jun 2024 14:59:15 GMT

Hi!

I was able to reproduce the issue. In order to find a workaround, could you explain in more details why this is an issue for you? How does it affect your application?

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Sun, 21 Apr 2024 15:59:56 GMT

There is no response received for this Issue.

I appreciate the support of any of the respected Nordic Support Engineers.

Thanks in advance for your support and fast response.

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Mon, 11 Mar 2024 15:12:23 GMT

Are there any updates regarding this issue?

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Mon, 04 Mar 2024 12:42:51 GMT

Sigurd
The issue i'm talking about will appear when you take the action from the peripheral side only (DK) and no action is taken from the central side (Mobile).

If you need any more details regarding the generation scenario. Kinly let me know.

Thanks

Mina

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Wed, 28 Feb 2024 09:21:25 GMT

The issue will appear when you are not taking any action on the phone. And reject the bonding on the DK only

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Sigurd — Tue, 27 Feb 2024 14:49:14 GMT

Hi!

When I'm testing this with a nRF52840-DK, nRF5 SDK v17.1.0 , S140 v7.2.0, ble_app_multirole_lesc example, I'm getting the Pairing Failed:

On the Phone side, I'm using nRF connect for mobile app.

I start the pairing from the phone, then reject with the button 2 on the DK, and when I see the numeric number on the phone side, I press connect on the phone.

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Mon, 19 Feb 2024 13:49:40 GMT

I tried the same example on both SDK 16.0.0 and 17.1.0, After Making it work as per this ticket [(+) BLE Multirole LESC Example Doesn't work on SDK 17.1.0 - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)]. And it seems that the SMP Pairing Rejected Message is not sent over the air in both examples. Attached The Logs, Sniffing Session for the example behavior

devzone.nordicsemi.com/.../8726.LESC-SDK-17.1.0-Native-Example.pcapng

devzone.nordicsemi.com/.../4606.LESC-SDK-17.1.0-Native-Example.log

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Sun, 18 Feb 2024 09:36:10 GMT

[deleted]

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Sigurd — Mon, 12 Feb 2024 09:00:11 GMT

Hi!

I tried pressing button 2 to reject the bonding. Using SDk 17.1.0

I see Numeric Comparison Failed sent from slave to master. And then Slave disconnects.

PS: If you are starting a new project, I recommend using nRF Connect SDK instead.

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Tue, 06 Feb 2024 15:05:57 GMT

Hello
I didn't modify the Native SDK Example of ble_app_multirole_lesc. The illustrated sequence diagram is actually what is done in the SDK Native Example. Kindly find attached screenshots for the calling of the API.

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Sigurd — Tue, 06 Feb 2024 10:24:43 GMT

Hi!
ref the message sequence charts you linked to:

Are you calling sd_ble_gap_auth_key_reply(BLE_GAP_AUTH_KEY_NONE,NULL) ?

RE: SMP Pairing Failed message is not sent from Peripheral to Central in Numeric Comparison Bonding

Mina Aziz — Thu, 01 Feb 2024 15:58:16 GMT

I noticed that the peripheral initiates a disconnection in case of the bonding failed in the BLE_GAP_EVT_AUTH_STATUS event if the error code doesn't equal to BLE_GAP_SEC_STATUS_SUCCESS. I commented this action and noticed that the central initiates the disconnection due to BLE operation timeout. So why the SMP Pairing failed message is not propagated by the soft device to the master? Note: I tried the same example with both soft device hex files with version 7.0.1 and SD 7.2.0 and the same behavior occurred. Attached the Sniffing Session after removing the peripheral side disconnection on Auth Status Failure.

devzone.nordicsemi.com/.../LESC_5F00_CANCEL_5F00_PER_5F00_DISCON_5F00_SD_5F00_7_5F00_2_5F00_0.pcapng