https://devzone.nordicsemi.com/f/nordic-q-a/57820/nrf52840-decilne-connectionI am developing a device based on nrf52840, this is peripheral. But I want to change the code so that I can only connect to my device using my application (in other cases, for example, using nRF Connect, my BLU device rejected the connection attempt)en-USTelligent Community 13Sun, 16 Feb 2020 18:19:25 GMThttps://devzone.nordicsemi.com/thread/234528?ContentTypeID=1Sun, 16 Feb 2020 18:19:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1ec95595-c562-4f3e-aaf7-032b6e249e07awneil<p>All BLE communications happens via Characteristics - so, yes.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/234525?ContentTypeID=1Sun, 16 Feb 2020 11:45:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5c3e0b72-883d-4bd6-90cb-6b88a5122236uchar<p>Thanks for the answer.<br />I understand correctly that this can only be done by writing to the characteristic? That is, a connection with the device will be established in any case, and then, if the <span>peripheral&nbsp;</span>does not receive a confirmation command (the application must write data to the characteristic), then it will disconnect. Is the algorithm like this?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/234385?ContentTypeID=1Fri, 14 Feb 2020 12:03:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8e62c069-75cd-4369-99a0-612f376f0c5cawneil<p>The connection at the BLE level neither knows nor cares anything about what app may or may not be used.</p> <p>So you are going to have to do this in your own protocol - some sort of authentication/authorisation between app &amp; peripheral.</p><div style="clear:both;"></div>