Do not send security request as peripheral if bonded to peerhttps://devzone.nordicsemi.com/f/nordic-q-a/63222/do-not-send-security-request-as-peripheral-if-bonded-to-peerI have a requirement that my peripheral device should only rely on the central to start any security operation. Right now I see a problem when the central side removes the bonding but my side still has the bonding information. The peripheral still sendsen-USTelligent Community 13Thu, 02 Jul 2020 09:25:37 GMTRE: Do not send security request as peripheral if bonded to peerhttps://devzone.nordicsemi.com/thread/258025?ContentTypeID=1Thu, 02 Jul 2020 09:25:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0598ff50-32e1-4cb2-a2ed-9d5b7a73515dVidar Berg<p>Hello,</p> <p>I can&#39;t foresee any problems with the change you made. Other options you could consider is to not call <span><a title="pm_handler_on_pm_evt" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/group__pm__handler.html?cp=7_5_1_6_2_15_2_3#ga87b3d3ebdd6d878ba4360bd9b98c303e">pm_handler_on_pm_evt</a></span>() from your PM callback, or to delay the peripheral pairing request (with PM_HANDLER_SEC_DELAY_MS config setting) enough to give the Central time to issue the request first.</p><div style="clear:both;"></div>