Differences in communication using nRF Connect for Mobile and for Desktop

RE: Differences in communication using nRF Connect for Mobile and for Desktop

Sigurd — Wed, 22 Mar 2023 13:43:39 GMT

Hi,

You could e.g. use the nRF sniffer

https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le

Catch a sniffer trace for the connection between the mobile app and the nRF52833, then between the desktop app and the nRF52833, and then compare the logs to find the difference.

RE: Differences in communication using nRF Connect for Mobile and for Desktop

Hamilton Woods — Wed, 22 Mar 2023 13:38:35 GMT

Thank you for your reply. Based on the guide you linked, I have walked through many combination of security parameter settings. Every time I try to pair with the peripheral, regardless of the security settings applied, I get the error message, "Authentication failed with status BLE_GAP_SEC_STATUS_UNSPECIFIED".

I am trying to understand what to do to have nRF Connect for Desktop BLE encryption operate like nRF Connect for Mobile. Can I interrogate the encryption settings that nRF Connect for Mobile is using and then apply those settings in nRF Connect for Desktop BLE? If so, how do I interrogate the encryption settings that nRF Connect for Mobile is using?

RE: Differences in communication using nRF Connect for Mobile and for Desktop

Sigurd — Wed, 22 Mar 2023 13:03:38 GMT

Hi,

[quote user=""]nRF Connect for Desktop has several options for pairing: IO capabilities, Authentication, Keypress notifications, and Bonding. I have not found a combination of selections that allows me to pair with the device. When I attempt to read a value from a characteristic, the error, ATTERR_INSUF_ENCRYPTION (0x010F) is returned.[/quote]

Looks like you need to encrypt the link. We have a guide on how to do this with nRF Connect Desktop BLE app here: https://infocenter.nordicsemi.com/topic/ug_nrfconnect_ble/UG/nRF_Connect_BLE/nRF_Connect_Pairing_devices.html