Every once in a while it shows something like this in the serial connection, but that timestamp is right and the translation is wrong.
1694055231
UTC time from browser: 2158/50/122 (3) 23:9:0
Every once in a while it shows something like this in the serial connection, but that timestamp is right and the translation is wrong.
```
1694055231
UTC time from browser: 2158/50/122 (3) 23:9:0
```
I have added this as part of #24. Maybe it will let me know if something goes weird again. It could also be a bad solder connection; I still don't have this board in a case yet.
// Might work to fix random errors? If date is far in the future,
// try to update again.
while(rtc.now().year() > 2100){
Serial.println("RTC can't set time. Trying again.");
rtc.adjust(DateTime(yourInputTime));
}
I have added this as part of #24. Maybe it will let me know if something goes weird again. It could also be a bad solder connection; I still don't have this board in a case yet.
```
// Might work to fix random errors? If date is far in the future,
// try to update again.
while(rtc.now().year() > 2100){
Serial.println("RTC can't set time. Trying again.");
rtc.adjust(DateTime(yourInputTime));
}
```
I suspect this is somehow related to not waiting to call RTC, or something like that, after updating time. Or some other weirdness. See notes on #50 and how time is being kept now.
I suspect this is somehow related to not waiting to call RTC, or something like that, after updating time. Or some other weirdness. See notes on #50 and how time is being kept now.
W1CDN
added the bug label 2023-11-02 20:53:09 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every once in a while it shows something like this in the serial connection, but that timestamp is right and the translation is wrong.
I have added this as part of #24. Maybe it will let me know if something goes weird again. It could also be a bad solder connection; I still don't have this board in a case yet.
Intermittent bad times reportedto Intermittent bad times reported after browser time refreshI suspect this is somehow related to not waiting to call RTC, or something like that, after updating time. Or some other weirdness. See notes on #50 and how time is being kept now.