Closed MikeyMoMo closed 2 years ago
BigBird0000
commented
2 years ago Perhaps adding an RTC (like the DS1307 or DS3231) option, and use the RTC instead of millis(), continue to use millis if no RTC, or if RTC is invalid. Then maybe depending on the accuracy of the RTC, maybe get NTP time once every couple of days.
MikeyMoMo
commented
2 years ago That is not the point. I use NTP time, not the crappy RTC modules. The library default for queering NTP is too short and needs to be changed, either by the author or by the user.
On Mon, Mar 7, 2022, 8:39 AM BigBird0000 @.***> wrote:
Perhaps adding an RTC (like the DS1307 or DS3231) option, and use the RTC instead of millis(), continue to use millis if no RTC, or if RTC is invalid. Then maybe depending on the accuracy of the RTC, maybe get NTP time once every couple of days.
— Reply to this email directly, view it on GitHub https://github.com/ropg/ezTime/issues/141#issuecomment-1060079539, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYPSIJOLMCE25M5B2GTCJLU6VF3NANCNFSM5OHBXZ6Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
You should, by default, only fetch time from NTP.org once per day. Their guidelines request that and be sure to avoid on the hour and half hour calls and surely avoid midnight calls. I would suggest using 86578 (or something quite similar) as that is slightly over a day and will cycle through the day, slowly, not sitting on one of the hotspot time for NTP.org.
This line:
#define NTP_INTERVAL 86578 // default update interval in seconds