Adjustable NTP polling interval

[rodhammond]

Sorry if I missed a config but assume NTP is used to set the internal HW time IRQ. I've noticed my animations briefly pause/freeze when NTP is enabled (found tip to disable NTP from QuinLED). Is it possible to allow the user provides a recommended NTP background polling interval in the form of hh:mm? I assume, after device boots, a fixed number of NTP requests will set time, then the user's hh:mm interval would kink in to maintain time. This would prevent the need to disable NTP to prevent animations from freezing/pausing. Please let me know if there is a different solution. Thanks

[Aircoookie]

Indeed the NTP interval (once the time is successfully obtained once) is hard-coded to 11 hours and 40 minutes. I don't see how having this interval user-configurable would prevent the brief freezes. Perhaps it would be more useful to have NTP poll only when the LEDs are off to prevent freezes, unless the LEDs are on for an extended amount of time (> 24 hrs ?). As I would assume most setups not to be turned on 24/7 this would eliminate random freezing due to NTP in most practical scenarios.

On a related note, the retry interval if there is no network access or the NTP server is unreachable is quite aggressive, leading to frequent 7 second freezes if there is a connection problem. This would be a separate issue to address, with potential mitigations being longer retry intervals or even temporarily disabling NTP completely until the next reboot or change of relevant settings.

[rodhammond]

Thanks for the detailed response. I must somehow be in the second condition with aggressive NTP retry even when the device has the correct time and a network connection. For now, I manually enable after rebooting and disable once time is correct. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Christian Schwinne ***@***.***> Sent: Tuesday, July 11, 2023 10:28:38 AM To: Aircoookie/WLED ***@***.***> Cc: rodhammond ***@***.***>; Author ***@***.***> Subject: Re: [Aircoookie/WLED] Adjustable NTP polling interval (Issue #3285) Indeed the NTP interval (once the time is successfully optained once) is hard-coded to 11 hours and 40 minutes. I don't see how having this interval user-configurable would prevent the brief freezes. Perhaps it would be more useful to have NTP poll only when the LEDs are off to prevent freezes, unless the LEDs are on for an extended amount of time (> 24 hrs ?). As I would assume most setups not to be turned on 24/7 this would eliminate random freezing due to NTP in most practical scenarios. On a related note, the retry interval if there is no network access or the NTP server is unreachable is quite aggressive, leading to frequent 7 second freezes if there is a connection problem. This would be a separate issue to address, with potential mitigations being longer retry intervals or even temporarily disabling NTP completely until the next reboot or change of relevant settings. — Reply to this email directly, view it on GitHub<#3285 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE3U3F7SWJL5FXHPIIJSA7LXPV5LNANCNFSM6AAAAAA2FBDO74>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Aircoookie]

You can also do any main UI interaction (e.g. power on/off) to set the time from your client device, so NTP is not even required.