Yes, it did solve the issue.
But just wondering, why we need to restart the sntp. Can't we have an API which is just to sync time?

Thanks for the confirmation!

Thanks for the reply,
But if we do sntp_restart does it deinit the sntp and initialize again?
Do we need to again set the operating mode and NTP servers? Or it just uses the previous configurations?

Thanks for the reply! Yes, that would be the fixed interval of time when the time gets synced and callback is triggered. But how can I sync time at custom intervals i.e. suppose there is a event after which I need to re-sync the time regardless of the current drift. How can I achieve it? Which API w...

Sure, thanks for the insight. Got the point regarding the time sync first time. The issue I am facing seems to be with the re-sync. What will be the steps when we do want to resync to the ntp server? I am using "sntp_sync_time" API with default implementation, I have not overridden the API. But by u...

Thanks for the reply, However, the callback is called regardless of the time sync. Check the below logs for the reference. I (7348) sntp.c: Waiting for system time to be set... (1/10) I (9348) sntp.c: Waiting for system time to be set... (2/10) I (11348) sntp.c: Waiting for system time to be set... ...

Hello, I am performing sntp sync. However, I need to know how I can be aware of the time sync not done? When the device is failing to update the ntp time, it fetches the device time and sets the status as SNTP_SYNC_STATUS_COMPLETED. I can check the timestamp which is updated and can compare it with ...