https://devzone.nordicsemi.com/f/nordic-q-a/103574/sd_ble_gatts_hvx-returns-13313-after-a-second-device-connects-no-bondingHello, My device uses SDK 17.0.2. I&#39;m connecting to it from my mobile app and enable notifications. Notifications are sent and everything works. Until my device connects to some other device - BLE led driver in my case. Once the connection to the seconden-USTelligent Community 13Fri, 08 Sep 2023 07:20:08 GMThttps://devzone.nordicsemi.com/thread/445062?ContentTypeID=1Fri, 08 Sep 2023 07:20:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c292e841-8410-4b45-a397-b64bdef6c936dragilla<p>Ok. I know what the problem was. This post was unnecessary. The problem was unrelated to what I was asking about. I was using a wrong variable to get my connection handle. Sorry about that. Closing this.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/445024?ContentTypeID=1Thu, 07 Sep 2023 23:27:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:deda3bd2-3b1b-44be-9543-735833ab9dacdragilla<p>Ok. Now after some changes the situation is as followe:</p> <p>1. When the led driver gets connected&nbsp;<span>sd_ble_gatts_hvx&nbsp;returns 13313</span></p> <p><span>2. When I reenable the notifications from the mobile app side, the&nbsp;sd_ble_gatts_hvx&nbsp; starts returning 8.</span></p> <p><span>This is because of the&nbsp;sd_ble_gatts_sys_attr_set(p_abc-&gt;conn_handle, NULL, 0, 0); in on_write.</span></p> <p><span>If I comment that out I keep getting 13313.</span></p><div style="clear:both;"></div>