with the upgrade of 4 units to ESPEasy_v2.0.0-dev12 I discovered a NTP problem.
At boot, the time/date is not set to the NTP time but something with 1970 .... (that sounds Unix)
After a number of cold and warm boots and NTP On/Off and changing NTP servers .... I was able to get the 4 units back on the right time.
So happy with that, that I'm afraid to reboot now.
My NTP setting:
I also used-
- an empty field (empty defaults to pool.ntp.org)
- nl.pool.ntp.org
- europe.pool.ntp.org
What I could catch from the log at boot:
Don't know the clock resolution but I see only 10, 12, or 13 ticks between request and the "No Reply" message.
Is that long enough for a NTP response?
If I ping those IP's: The ping times look reasonable to me.
I have seen this problem for the first time when I upgraded one unit to ESPEasy_v2.0.0-dev11 some time ago.
Could this, as a side effect, be related to dev11 improvements?
I see in dev11 release notes ..
- cleaned up RTC initialisation.
- large changes to wifi handling. code cleanup, more efficient connecting,
Is the code too fast now?
TD-er made a comment here:
wrong systime with DST / Timezone enabled #592 https://github.com/letscontrolit/ESPEasy/issues/592
Any toughts?perhaps the timeout of the NTP is also too short.
Do more people have this problem?