https://devzone.nordicsemi.com/f/nordic-q-a/65289/how-to-tell-central-devices-apartHello. I am running ble_app_uart altered to allow for connection of two central devices. The connection of two devices work fine. Upon each connected central, I can tell the connections apart if I make m_conn_handle into an array of 2, I guessen-USTelligent Community 13Thu, 27 Aug 2020 13:20:31 GMThttps://devzone.nordicsemi.com/thread/266759?ContentTypeID=1Thu, 27 Aug 2020 13:20:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3b52c947-d81c-4343-9d99-58275108a25dAndersF<p>Thanks very much.</p> <p>The proprietary characteristic seems the best way to go.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/266748?ContentTypeID=1Thu, 27 Aug 2020 12:48:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b96286bc-6b30-4c14-9a33-0ed5c4cf42faKenneth<p>Hi,</p> <p>You can separate peers with the connection handle as you describe yes.</p> <p>I am not aware of any built in feature in BLE that can identify a peer automatically, however you may for instance add a proprietary characteristic that the app running on the peer can write to after connection is established to identify itself. Think this would be the preferred option. Alternatively you can do a database discovery of the peer, however I would not expect that you could get any reliable information from this without doing this for many vendors and versions, this could also change if they update the peer.</p> <p>Kenneth</p><div style="clear:both;"></div>