https://devzone.nordicsemi.com/f/nordic-q-a/122345/how-does-ble-peripheral-s112-use-supervision-timeoutI&#39;m working on an nRF device (S112 SoftDevice) that acts as a connectable peripheral to an iOs central. The application only has data to transfer every 5 minutes, so I&#39;m trying to lengthen the connection parameters to reduce the power consumption whileen-USTelligent Community 13Wed, 18 Jun 2025 12:43:58 GMThttps://devzone.nordicsemi.com/thread/539708?ContentTypeID=1Wed, 18 Jun 2025 12:43:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c7f07877-08bd-43eb-a9ad-61bb2450c24cKenneth[quote user=""]I was expecting to see 3 empty connection events before timeout, but it looks like after the first unacknowledged event the peripheral skips the latency and starts trying at the actual connection interval. It does this for the next `&lt;supervision_timeout&gt; - &lt;first_interval=connection_interval*(peripheral_latency+1)&gt;` duration. Is that the expected behavior?[/quote] <p>Yes, this is how it&#39;s defined should occur according to the Bluetooth core spec.</p> [quote user=""]The nrf_sdh is polling for BLE events and I was expecting to see&nbsp;BLE_GAP_EVT_TIMEOUT but instead see&nbsp;<span>BLE_GAP_EVT_DISCONNECTED. Is that the right event for a peripheral supervision timeout?</span>[/quote] <p>Based on what happens here it&#39;s also correct and according to the Bluetooth core spec.</p> [quote user=""]I noticed that if I block the connection right <em>before</em> a planned connection interval, it still disconnects 18s after the previous connection event, even though the connection has only been interrupted ~12 seconds.[/quote] <p>I don&#39;t remember all the details from the Bluetooth core spec, but I assume this is also according to it.</p> <p>Kenneth</p><div style="clear:both;"></div>