BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Samuel Keller — Thu, 18 Apr 2024 12:39:29 GMT

I faced the same issue. Seems like this problem still not resolved.
I could test my application using the example "central_nfc_pairing" and adjusted it to use a fixed temporary key. So i did not have to use a real NFC antenna.

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Sreejith Sundh — Mon, 10 Oct 2022 08:46:20 GMT

Does anyone found solution for this thread, I am facing the same issue.? Looks for valuable suggestions,

Thanks and Regards,

Sreejith

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Jeffe — Mon, 22 Aug 2022 16:45:05 GMT

Hi, thank you for your reply.

I was unaware of the Android App OOB pairing is not supported for means outside of NFC. This caused me to do further research and also led me to realize that on IOS, OOB pairing is pretty much completely unsupported. Since my application at the end needs to work with a mobile APP, this means that using OOB for pairing is unviable for my application. Thank you for your answer.

As for the nrf connect for Desktop BLE_GAP_SEC_STATUS_CONFIRM_VALUE error, I have indeed tried to enter the data in either direction to no avail. As for the sniffer trace, in the past I have tried getting the sniffer working to no avail since on my development computer, wireshark always freezes and I don't want to spend more time on this issue considering now that I have decided to not use OOB. I guess this ticket can be considered solved considering that OOB turned out to be an unsuitable form of pairing.

Again, thank you a lot for your reply, it was most enlightening

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Simonr — Mon, 22 Aug 2022 08:23:57 GMT

Hi again

Have you tried typing the OOB request data the other way around. Most data in BLE is little-endian, and it depends on the application if this is taken care of already or not. Could you also upload a sniffer trace so we can see what is going on over the air, as we need data on that to see what exactly is going wrong. My guess is that the data you enter is either in the wrong format (that's the only thing the BLE_GAP_SEC_STATUS_CONFIRM_VALUE error points to). If you can provide a sniffer trace, I'll ask the development team to take a look so we can see what's going on.

A sniffer trace can be gotten by using either a dedicated BLE sniffer (like the Ellisys sniffers), or if you have a spare nRF52 DK or Dongle, you can use the nRF Sniffer and Wireshark to sniff the connection and pairing method.

Regarding the Android app, this was discussed some time back, and as far as we know, the only OOB pairing supported in Android is over NFC, and you'll need to use a different pairing method to provide a PIN or passcode like this.

Best regards,

Simon

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Jeffe — Fri, 19 Aug 2022 16:18:08 GMT

Hi, a quick update:

I just used an mostly unmodified ble_app_hrs_nfc_pairing example, but instead of using NFC for the OOB I just had the DK under a debugging so I can directly look at the generated OOB value from the default code, and entered into nrf connect, with no luck. Same issue, still gives me the error BLE_GAP_SEC_STATUS_CONFIRM_VALUE even though I'm positive that I entered it in correctly.

I still have no idea how to initiate OOB pairing on the nrf connect app for android

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Jeffe — Fri, 19 Aug 2022 15:37:18 GMT

Hi, I think you misunderstood my question.

I am trying to get my example working with nrf Connect for Desktop and nrf Connect for Android. I already created a ble_app_hrs_c example that worked using OOB pairing with my modified ble_app_hrs peripheral example. I'm just posted to code in case if I did something wrong.

I can try making another example starting from ble_app_hrs_nfc_pairing but in the meantime I was hoping to get an answer that touches on my current troubles with the nrf Connect for Desktop and nrf Connect for Android

RE: BLE legacy pairing with OOB but not through NFC, using nrf connect Desktop and/or nrf connect mobile

Simonr — Fri, 19 Aug 2022 13:26:15 GMT

I still think the ble_app_hrs_nfc_pairing example can be a good starting point. nfc_ble_pair_lib.c shows the API calls used to manage OOB pairing with NFC tag and Peer manager and I think you can replace the NFC APIs with the OOB transport you have.

Also, it may be useful to have a look at message sequence chart for LESC OOB bond procedure in the SDS (link) and in core spec. 5, vol. 3, part H, Appendix C, section 2.2.2.10.

Best regards,

Simon