Time sync doesnt seem to happen any longer

[pepperm2]

For some reason, both of my Marquee scrollers have lost the ability to sync their time with TimeZoneDB. Has their time format changed or something?

I have tried reconfiguring and getting a new API key all without effect. WIFI connection works because weather information is collected but after reboot the time always starts at 12:00.

I am running V2.17 and here is the serial output from the ESP on boot (just the time and weather bits)...

Getting Weather Data GET /data/2.5/group?id=2636841&units=metric&cnt=1&APPID=a1d9191c3ebeea047d01bf0d6ad6d6e8 HTTP/1.1 Waiting for data Response Header: HTTP/1.1 200 OK lat: 53.0042 lon: -2.1854 dt: 1634807354 city: Stoke-on-Trent country: GB temp: 7.28 humidity: 78 condition: Clear wind: 3.20 direction: 308 weatherId: 800 description: clear sky icon: 01d timezone: 1

Updating Time... News Data for Getting Time Data for 53.0042,-2.1854 GET /v2.1/get-time-zone?key=4LF2K49NG3KE&format=json&by=position&lat=53.0042&lng=-2.1854 HTTP/1.1 Waiting for data {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=l%2FjwYMn17%2FP8ajBET03MxV29F%2FLNNh4X9UTYVN%2BMWGM74aWat%2B7kf%2BulSx3heZacyPKIA6iarIBeq6d2DKWT1znmLc49KA0yPyjCK4dVJGme5m9aC2jHeV9WD%2FbX5XexnKvzk6Y%3D"}{"success_fraction":0,"report_to":"cf-nel","max_age":604800}{"status":"OK","message":"","countryCode":"GB","countryName":"United Kingdom","zoneName":"Europe\/London","abbreviation":"BST","gmtOffset":3600,"dst":"1","zoneStart":1616893200,"zoneEnd":1635642000,"nextAbbreviation":"GMT","timestamp":1634814316,"formatted":"2021-10-21 11:05:16"}

firstEpoch is: 20 Version: 2.17

I note that the data stream above shows the correct time (11:06:16) but this does not get displayed on the scroller.

Has anyone any clues why this has started to happen (a couple of weeks now).

Mark

[geemac]

Update toV2.18 it fixes TimeZoneDB issue.

[pepperm2]

Interesting, thanks for that. I was just looking at the update but cant get past the Sign-In requirement to get to the firmware update option. I must have done previously to get to 2.17 but just cant figure it out again today.

Cracked the admin/password combination and updated to 2.18 now and everything works as expected. The display seems to have gone from 3x4 LED arrays to 2x4 for some reason, but that is another challenge.

[pepperm2]

Well everything worked for a day or so, now I am getting errors connecting to the weather and time services again. This is wierd, is the code (V2.18) having issues again does anyone know?

[G6EJD]

I think it's because uniquely this year there are 5 Sunday's in October and the time server used can't cope

[pepperm2]

Really!

[G6EJD]

Well with the last build it ran flawlessly for about 2-years, then this Sunday morning the time was not correct, so a power cycle showed the time was being set to Thu, 01-Jan 1970 00:00, so all that was different was the time services had tried to implement DST changes that were clearly wrong as uniquely this Oct has 5-Sundays not the usual 4… That’s the only plausible reason I can see.

[Qrome]

The real reason is the TimeDB service changed so the response was failing to parse. There is a new 2.18 version of the software out that fixes this. You can use the web interface to upgrade.

[G6EJD]

Thanks

[corkymork]

Had the same issue with mine, v2.15. Time is wrong, but weather and news OK. Power cycle resets time to 12:00. Upgraded to v2.18, now it's OK.