https://devzone.nordicsemi.com/f/nordic-q-a/15198/ble-lesc-multirole-dhkey-reply-confusionI&#39;m trying to under the ble_app_multirole_lesc project and I&#39;m a bit confused about calling sd_ble_auth_key_reply and sd_ble_lesc_dhkey_reply. If you are using Just Works Unauthenticated, then I would think that the BLE_GAP_EVT_PASSKEY_DISPLAY event shouldnen-USTelligent Community 13Tue, 19 Jul 2016 09:11:08 GMThttps://devzone.nordicsemi.com/thread/58014?ContentTypeID=1Tue, 19 Jul 2016 09:11:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6fb90608-a53c-4d8e-9dd5-22077b021110Hung Bui<p>Hi,</p> <p>It was due to one of the bug we had (DRGN-7235) in the S13x v2.0.0 that the sd_ble_gap_lesc_dhkey_reply can&#39;t be called before sd_ble_gap_auth_key_reply() that we need to put the call in BLE_GAP_EVT_PASSKEY_DISPLAY . And this affects when you don&#39;t use PASSKEY but Justwork.</p> <p>However the issue is fixed on S13x v2.0.1. So you can actually update the new softdevice, and then move the call sd_ble_lesc_dhkey_reply to BLE_GAP_EVT_LESC_DHKEY_REQUEST() event instead. And that should fix the issue you have with Justworks bonding.</p><div style="clear:both;"></div>