https://devzone.nordicsemi.com/f/nordic-q-a/98304/nrf5340---getting-started-a-new-limited-adv-sessionHi, In our BLE peripheral application (NCS 2.2.0, Zephyr 3.2.99) the advertising window is limited to 30 sec (limited advertising with BT_LIM_ADV_TIMEOUT = 30). Now I want give user the chance to launch another 30 sec advertising window by pressingen-USTelligent Community 13Tue, 04 Apr 2023 15:35:27 GMThttps://devzone.nordicsemi.com/thread/419086?ContentTypeID=1Tue, 04 Apr 2023 15:35:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:788bd321-49a8-4235-a7e1-8872146efa83Gabriele<p>Hi Hung,</p> <p>I&#39;ve solved&nbsp;by awaiting the pushbutton k_event outside the ble module.&nbsp;The event detection calls an api for restarting the advertising if CONFIG_BT_AUTORESTART&nbsp;_ADVERTISING is n. Otherwise the bluetooth disconnection&nbsp;gets advertising restarted automatically. Thank you&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/418639?ContentTypeID=1Fri, 31 Mar 2023 13:49:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:73677845-5f1e-465e-ba8f-bf8b4ef8589eHung Bui<p>Hi Gabriele,&nbsp;<br />I tried to look into the host stack but couldn&#39;t find any callback to the application.&nbsp;<br />If you have a look in the adv.c you can find where the&nbsp;k_work for adv_timeout is scheduled inside&nbsp;bt_le_adv_start() with&nbsp;BT_LIM_ADV_TIMEOUT. But there is no callback to the application when the&nbsp;adv_timeout() is triggered.&nbsp;</p> <div>So I afraid you will have to start a timer in the application to keep track of that.&nbsp;<br />If you want to launch another 30 sec before the first 30sec advertising is timed out, you would need to stop advertising, then the k_work scheduling for <span>adv_timeout&nbsp;()&nbsp;</span>will be cancelled.&nbsp;</div><div style="clear:both;"></div>