zero out LESC and KEYPRESS fields in PAIRING REQUEST PDU if peer&#39;s BLE verison is not 4.2https://devzone.nordicsemi.com/f/nordic-q-a/18337/zero-out-lesc-and-keypress-fields-in-pairing-request-pdu-if-peer-s-ble-verison-is-not-4-2currently(sdk_12.1.0_0d23e2a, s132_nrf52_3.0.0_softdevice), nrf52832 can&#39;t pairing with windows 10.1607(build 14393.479), if we set lesc bit in ble_gap_sec_params_t. windows&#39; bluetooth stack does not support BLE4.2, it interprets the AuthReq byte inen-USTelligent Community 13Wed, 14 Dec 2016 14:51:14 GMTRE: zero out LESC and KEYPRESS fields in PAIRING REQUEST PDU if peer's BLE verison is not 4.2https://devzone.nordicsemi.com/thread/70813?ContentTypeID=1Wed, 14 Dec 2016 14:51:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cca0093d-7fa2-4ee5-814e-19d31e44863cJ&#248;rgen Holmefjord<p>Hi tiamo,</p> <p>Was this intended as information to other users, or did you have a question? As you say, this is a bug in Win10, and should be fixed by MS. This is not something we can easily workaround. Note that it is possible to have different versions on the different layers of BLE, so your fix might not always work for all hardware/drivers. LL_VERSION_IND is dependent on both drivers and hardware.</p><div style="clear:both;"></div>RE: zero out LESC and KEYPRESS fields in PAIRING REQUEST PDU if peer's BLE verison is not 4.2https://devzone.nordicsemi.com/thread/70814?ContentTypeID=1Tue, 13 Dec 2016 14:14:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5e961545-91f3-4379-84f3-f6ae6385cdfetiamo<p>currently we can call pm_sec_params_set in BLE_GAP_EVT_SEC_PARAMS_REQUEST event with lesc bit cleared if peer&#39;s lesc is not set.</p> <p>note that pm_sec_params_set should be called before pm_on_ble_evt</p><div style="clear:both;"></div>