Here’s a log excerpt from the serial port. The first field is the timestamp returned by the system
time() function, the other fields indicate a sensor label and value(s).
1657548001,AM-4,0.012 1657548001,WL-1,0.649098,0 279b0 2 mDash.c:10988:sntpcb SNTP: setting time to 3985593123.385 -449836783,WL-1,0.649007,0 -449836782,AM-1,0.014
The device boots, connects to mDash, and sets its initial clock correctly. Apparently at random, after several minutes of normal operation, time is set to a nonsensical value, as reflected in the log message and subsequent timestamps returned by time().
In case it’s of any use, the initial clock-setting log messages are:
502 2 mDash.c:10988:sntpcb SNTP: setting time to 3992585258.385 10bd 2 mDash.c:10920:dev_cb connected to wss://mdash.net/api/v2/rpc 10c0 2 mDash.c:10347:info_cb Setting up system time to UTC Mon Jul 11 15:56:37 2022
but these are also weird because the timestamp reported in the first line is (as seconds relative to Jan 1, 1900) 2026-04-19 13:12:03 UTC, but the correct date/time appears in the third line.