https://devzone.nordicsemi.com/f/nordic-q-a/96172/bluetooth-cachingHi, I am using nRF Connect SDK, 2.2.0. I am developing a Central device, which performs the following, in this order: Enables Bluetooth (bt_enable()) Starts scanning (bt_le_scan_start()) looking for a specific Peripheral Once the Peripheralen-USTelligent Community 13Wed, 01 Feb 2023 21:07:23 GMThttps://devzone.nordicsemi.com/thread/407650?ContentTypeID=1Wed, 01 Feb 2023 21:07:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:dd510ed7-1374-4aba-a512-8791f9fde3b0D0023<p>Never mind. There was error in my code.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/407430?ContentTypeID=1Tue, 31 Jan 2023 19:52:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:53fa7257-c990-4069-a1ef-fe27ca8066fcD0023<p>Some more information:</p> <p>Just for testing, I tried steps 1, 2 and 3, only. What I see is that, when scan is started again, later, and the Peripheral is not there, I still get ADV report, with some random address for the Peripheral - an address that the Peripheral never used.</p> <p>If the Peripheral comes back online, I still get some random address (in the ADV report) - not the correct Peripheral address.</p> <p>I also noticed that, when I get the random address, I invoke&nbsp;bt_le_scan_stop(), which completes without error. But after that, the scan callback is invoked again, even though I stopped scanning. And the second invocation contains the correct Peripheral address.</p> <p>Any idea why this is happening?</p> <p>Maybe it is related to the fact that bt_disable() is not really implemented, based on this:</p> <p><a id="i1" href="https://devzone.nordicsemi.com/f/nordic-q-a/93896/how-to-disable-bt-in-ncs2-1-2">https://devzone.nordicsemi.com/f/nordic-q-a/93896/how-to-disable-bt-in-ncs2-1-2</a></p><div style="clear:both;"></div>