NTP / timestamps suddenly wrong

pimoroni / enviro

MIT License

101 stars 79 forks source link

NTP / timestamps suddenly wrong #124

Closed joshkopecek closed 1 year ago

joshkopecek commented 1 year ago

I just managed to get the enviro working, but in the last day the timestamps jumped. I think this may have been since I upgraded to v0.0.9 of the firmware? It now seems to think it's Christmas day…

I'm running the Enviro Weather
I upgraded to v0.0.9 firmware (the link in the release description to the uf2 file returns 404, so I used the '...filesystem-only.uf2' one)
I tried reporting direct to Adafruit.io, but this started jumping to the 24th December.
The exact difference between now and the reported timestamp is 19 days, 12 hours and 22 minutes.
I tried reporting to a custom http endpoint locally, and exactly the same happens.
It's connecting to WiFi fine and reporting via the internet to Adafruit fine, so connection isn't an issue.

Should I post the log?

ZodiusInfuser commented 1 year ago

Hi @joshkopecek. It's possible that local time of your board got set wrong somehow. If you check the log.txt and that too has times with the same date, then that would confirm it.

Currently the only way to change the time is to disconnect all power from your board for 1 minute or more. Then when you reconnect power it will have forgotten the previous date and will attempt to connect to your wifi to acquire a new date. This will appear in your log as a date in the early 2000's before the time sync has occurred.

If the log looks fine but the upload dates are still wrong then I am not sure. Perhaps you can try the pimoroni-picow_enviro-v1.19.10-micropython-v0.0.9.uf2 file (you'll need to re-enter your config details).

ZodiusInfuser commented 1 year ago

Thanks for the note about the link being wrong on the release. I have now corrected this

joshkopecek commented 1 year ago

@ZodiusInfuser thanks for the tip. I'll try to reset the time, but I have no idea how it could have got offset like that. Will report further.

joshkopecek commented 1 year ago

That did it – powering off for > 1 min. When I upgraded to v0.0.9, that's when the offset occurred (and stuck). I may not have completely powered it off for more than a minute.

ZodiusInfuser commented 1 year ago

Thanks. I'm glad to hear that worked. I'll close this issue, but if it occurs again and cannot be resolved with power cycling please let me know.