https://devzone.nordicsemi.com/f/nordic-q-a/28593/processing-of-unexpected-handle-indication-messagesI am using PCA 10040 development boards with soft device version s132_nrf52_3.0.0 to investigate Central/Peripheral communications. A PCA 10040 acts as a Central making connections to two peripherals, one peripheral is another PCA 10040 board and theen-USTelligent Community 13Tue, 19 Dec 2017 12:53:20 GMThttps://devzone.nordicsemi.com/thread/113314?ContentTypeID=1Tue, 19 Dec 2017 12:53:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8ec4eecf-57a1-4cc2-8600-05160c383900Hung Bui<p>Usually you don&#39;t need to disconnect, just need to do service discovery again. But it&#39;s also fine if you disconnect and then connect again and then do service discovery.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/113313?ContentTypeID=1Tue, 19 Dec 2017 10:25:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:18882b6e-ec78-478f-b191-62c508bdc374kc<p>Thank you. For now Central firmware is disconnecting when unexpected indication data is received.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/113315?ContentTypeID=1Mon, 18 Dec 2017 12:09:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f4078f9f-95fc-4c6d-a578-440f4d49f4ccHung Bui<p>Hi kc,</p> <p>You can check what is at handle id = 0x03 using nRFConnect or other BLE central tool. Most likely it&#39;s the service changed characteristic. It&#39;s used when the peripheral wants to tell the central that the attribute table has been changed, and the range is from 0x0001 to 0xffff as you see in the data.</p> <p>It&#39;s up to the central to decide what to do with that. You can start another service discovery after you receive the indication. Usually, this service changed indication is only for bonded peers that don&#39;t do service discovery on every connection.</p><div style="clear:both;"></div>