NTP time sync get random values

[gaelbenoit]

Describe the bug
Since I have upgraded my WLED builds to 2101130, the ntp client give random values. After a reboot the time is correctly synced, but 24h later it's absolutly random:

1st: ESP32 DevBoard
NTP: local ntp server
Current local time is 2061-9-8, 7:13:27.
board = esp32dev
platform = [email protected]
build_flags = ${common.build_flags_esp32}

2nd: ESP32 D1 MINI
NTP: pool.ntp.org
Current local time is 2006-5-16, 9:44:09.
board = esp32dev
build_flags = ${common.build_flags_esp32}
platform = [email protected]

3rd: ESP32 D1 MINI
NTP: 0.wled.pool.ntp.org
Current local time is 2061-9-8, 7:16:31.
board = esp32dev
build_flags = ${common.build_flags_esp32}
platform = [email protected]

4th: ESP8266 D1 MINI
NTP: pool.ntp.org
Current local time is 2017-6-24, 20:17:44.
board = d1_mini
platform = ${common.platform_wled_default}
build_flags = ${common.build_flags_esp8266}

To Reproduce
I just downloaded the release 2101130 and build it with PlatformIO and my historical platformio_override.ini file

Expected behavior
The correct time from NTP

WLED version

• Board: ESP8266 D1 MINI, ESP32 Dev Board, ESP32 D1 MINI
• Version 0.11.1 2101130
• Format self-compiled

[stale]

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs.
Thank you for using WLED!

[lodesmets]

Do you still have the problem? Because I have it too with v0.14.0

Only very infrequently

[jannic]

I also have this issue, with v0.14.0 on an esp8266. Usually happens after several days of uptime.

[softhack007]

@jannic @lodesmets please try latest source code from 0_14_1 branch (PR #3536).

More details are here: #3515 (comment)

[jannic]

Thanks for the update, the patch does look promising. Unfortunately the precompiled version didn't work. I get 30 green LEDs and it doesn't connect to my WiFi. I didn't have time to have a closer look yet.

[lodesmets]

I compiled it myself with the USERMOD_SSDR. For now it seems to work, but the problem only came after a long uptime. So let's hope this works too