https://devzone.nordicsemi.com/f/nordic-q-a/5951/push-button-to-confirm-connectionHey, I noticed that most of the wearable ble devices (without keyboard and screen) on the market are using &#39;push to confirm connection&#39; authentication, when you have to push button on the device to confirm smartphone connection within given timeout. Allen-USTelligent Community 13Tue, 10 Mar 2015 12:28:20 GMThttps://devzone.nordicsemi.com/thread/20721?ContentTypeID=1Tue, 10 Mar 2015 12:28:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cc5ab024-f276-40cc-8bdc-1d229acb37adHung Bui<p>Hi Justin,</p> <p>Maybe I haven&#39;t tried the a device with that feature but by spec if you don&#39;t use whitelist or directed advertise when advertising, you won&#39;t be able to allow or discard a connection before it is made. The peripheral will accept any connect request from central.</p> <p>What I can suggest you to do is to have a state that you ignore any event from BLE and not putting any data into the characteristics on the peripheral. The device remains in that stat until the &quot;push to to confirm&quot; button is press after that you can return the normal functionality of the device.</p> <p>If the button is not pressed after a timeout, you can terminate the connection. You can also refuse to do pairing in that waiting state as well.</p><div style="clear:both;"></div>