https://devzone.nordicsemi.com/f/nordic-q-a/64339/nrf-connect-for-mobileHi , In order to capture and get the data from the external BLE beacons, I am trying to simulate this using nrf connect Advertiser option instead of using Beacons for testing purposes. However, see that the advertised packets from the nrfen-USTelligent Community 13Fri, 31 Jul 2020 07:33:59 GMThttps://devzone.nordicsemi.com/thread/262505?ContentTypeID=1Fri, 31 Jul 2020 07:33:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:169ce639-640f-4897-891e-6e9c0feeaaceviveknath<p>Hi,</p> <p></p> <p>Thanks a lot for your inputs.</p> <p>I will check in this direction.</p> <p></p> <p>Best Regards,</p> <p>Viveknath</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/262492?ContentTypeID=1Fri, 31 Jul 2020 06:04:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0931f4fa-2567-4c1f-a04d-d7e7862d3fc0Simonr<p>Hi</p> <p>The nRFConnect advertiser uses RandomPrivateResolvable address type, and there&#39;s no way to edit this in the nRFConnect app I&#39;m afraid. In order to confirm that this is the phone, you&#39;ll have to whitelist the IRK in your scanning device. This is used to resolve the address so that you can know that it is the same device even though the address changes. You can refer to the HID Keyboard application to see how whitelisting is implemented there. Essentially, the peer manager library that handles bonding also takes care of the IRK, so it&#39;s quite straightforward. Please check out the<a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/ble_sdk_app_hrc.html"> ble_app_hrs_c example</a> for instance to see how you can do this in your central.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>