Security Connection Triggering Event Issues

RE: Security Connection Triggering Event Issues

Sigurd — Fri, 23 Jun 2023 10:56:25 GMT

Hi,

Based on the image posted, I don't see any issues with this.

RE: Security Connection Triggering Event Issues

Mikey — Wed, 10 May 2023 00:59:35 GMT

Hi,

Our past handling methods：

1、ble_evt_handler

2、pm_evt_handler

In the "BLE_GAP_EVT.CONNECTED" event, it is necessary to determine the UI to hide the pairing code. There is a situation that cannot be avoided. After the phone is connected to the product, the product information is deleted and the phone is paired with the product again. At this point, the pairing code will quickly disappear.

Current processing method:

1、ble_evt_handler

2、pm_evt_handler

The new way is to create the UI for this hidden pairing code in "BLE_GAP_EVT.CONN_SEC_UPDATE" and "PM-EVT_PEER_DATA_UPDATE_SUCCEEDED" to avoid the situation of rapid disappearance.

RE: Security Connection Triggering Event Issues

Sigurd — Tue, 09 May 2023 21:36:21 GMT

Hi,

[quote user=""]The customer provided us with a solution to hide the pairing code of the LCD in the "BLE_GAP_EVP_CONN_SEC_UPDATE" event of secure information exchange, and our testing is also possible. I hope Nordic can confirm if this is possible.[/quote]

Could you add some details about what this "pairing code" you moved from BLE_GAP_EVT_CONNECTED event to PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event does explicitly? Does it call any peer_manger functions or Softdevice functions?