https://devzone.nordicsemi.com/f/nordic-q-a/43557/48-bit-bluetooth-address-changes-after-ota-dfuHi, we&#39;ve noticed that after performing an OTA DFU, the Bluetooth Address of the device changes as follows: new_address = old_address - 1 Example: Address before OTA DFU: C7:4B:F6:07:74:0C Address after OTA DFU: C7:4B:F6:07:74:0B Is it a regularen-USTelligent Community 13Mon, 11 Feb 2019 13:04:54 GMThttps://devzone.nordicsemi.com/thread/170358?ContentTypeID=1Mon, 11 Feb 2019 13:04:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fdd382b5-35db-4c03-aa64-9c0323668f5fSimonr<p>Hi</p> <p>Yes, this is a default setting. We do this to solve the issue that central devices (phones/tablets etc.) may try to re-encrypt the connection if the address stays the same. This is the simplest way to do DFU without worrying about re-encryption and termination from the central device (Known issue with Android devices).&nbsp;</p> <p>If you want the DFU process to be encrypted you should send the bond information from the application to the bootloader. There are several ways to do this, one approach is detailed in <a href="https://developer.nordicsemi.com/nRF51_SDK/nRF51_SDK_v8.x.x/doc/8.0.0/s110/html/a00079.html">this link</a>. Note that this solution only works if you start with your application first, and then enter bootloader. You can use flash to share bond information with the application, and that will make it possible to start bootloader from reset.</p> <p>For more information on DFU, please visit our <a href="https://devzone.nordicsemi.com/b/blog/posts/common-faqs-on-dfu">DFU FAQ post</a>.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>