https://devzone.nordicsemi.com/f/nordic-q-a/15607/how-to-get-own-private-address-with-softdevice-v3-0-0With softdevice version 2.0.0, the sd_ble_gap_address_set is used to set the address to one of the four address types, and sd_ble_gap_address_get is used to get our own current BT address. This would work even when the address type is random resolvableen-USTelligent Community 13Wed, 10 Aug 2016 16:42:24 GMThttps://devzone.nordicsemi.com/thread/59536?ContentTypeID=1Wed, 10 Aug 2016 16:42:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d3e17b04-9983-4394-b647-60901c1938e3Youssif<p>According to the <a href="http://nfciop.readthedocs.io/en/latest/ch/bluetooth_simple_pairing.html#static-handover-with-bluetooth-le-device">NFC Static Handover specification</a> I think the device address should be given, and there is no way to add the IRK. Even if there is a way to add the IRK, if the devices haven&#39;t paired we cannot get the remote address using NFC static handover. Moreover, the handover should occur almost instantaneously, so as long as the address cycle is 5 seconds or greater this shouldn&#39;t be a probelm with random addresses.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/59535?ContentTypeID=1Mon, 08 Aug 2016 15:32:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:733011e3-c0d6-4a14-9113-7c2503dd50efOle Bauck<p>I see your problem. You should only need the IRK to identify the device and connect. Is there some way to include the IRK in the record so that the other device can automatically connect?</p> <p>Even with the previous SoftDevice the method of receiving the address with sd_ble_gap_address_get(..) when using random resolvable or random non-resolvable is not safe as the address may change at any time, see here: <a href="https://devzone.nordicsemi.com/question/859/bonding-difference-between-irk-and-address-in-whitelist/">devzone.nordicsemi.com/.../</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/59534?ContentTypeID=1Mon, 08 Aug 2016 14:48:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:50f8ed33-c13c-44f6-9b27-4bb698b3b9c6Youssif<p>I need the address so that I can include in the NFC tag for connection handover. Please see sample NFC app which gets the mac address so that it can include in the OOB tag.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/59533?ContentTypeID=1Mon, 08 Aug 2016 14:30:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2da487aa-d8eb-4fb1-911a-f18971379c17Ole Bauck<p>There is no way to get the current address with SD132 v3 if it is random resolvable or random non-resolvable. The underlying link layer will generate the addresses so the application will be entirely unaware of it.</p> <p>Why do you want to get the current address?</p><div style="clear:both;"></div>