addr_id_peer after pairing process seems to always be 0 even if peer device has a random resolvable address

[jm_laird]

I am seeing an issue when, after the pairing process is complete, during the BLE_GAP_EVT_AUTH_STATUS event, that the peer addr_id_peer field is always 0. For testing, I am using two nRF52840's with softdevice 7.2.0, SDK 17.0.2. Once device has a public address and a random resolvable address (central device), the other has a public address (peripheral device). The peripheral device begins advertising to which the central device connects to it using a random resolvable address - I can see that the address begins 02 from the peripheral side, the central device then pairs (and bonds) with the peripheral device and the various events fire, on the BLE_GAP_EVT_AUTH_STATUS event, I output all the fields of the pairing information structure and I see the peer device's real public address, address type is 0 indicating that it is a public address, but addr_id_peer is 0 which suggests that the device does not have a private resolvable address, however this is incorrect. Is this a bug in the softdevice?

[Sigurd]

Hi,

The addr_id_peer field is used in subsequent connections to identify if the peer used the resolvable address or the identify address during connection setup, and if the SoftDevice resolved the address from the device identity list that has been set.(sd_ble_gap_device_identities_set()). See this message sequence chart:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s140.api.v7.2.0/group___b_l_e___g_a_p___p_e_r_i_p_h___c_o_n_n___p_r_i_v___m_s_c.html

[jm_laird]

Hi Sigurd,

The documentation on this is confusing but that cleared it up, thank you.

Thanks,
Jamie