Intermittent bad times reported after browser time refresh #27

New Issue

W1CDN · 2023-09-06T21:57:04-05:00

W1CDN commented

2023-09-06 21:57:04 -05:00

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 ```

W1CDN commented

2023-09-06 22:07:03 -05:00

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)); } ```

W1CDN referenced this issue

2023-09-08 14:21:30 -05:00

Set RTC alarm (run program) more than a month in advance #33

W1CDN referenced this issue

2023-09-17 16:32:13 -05:00

RTC not keeping time #50

W1CDN changed title from ~~Intermittent bad times reported~~ to Intermittent bad times reported after browser time refresh

2023-10-01 11:34:52 -05:00

W1CDN commented

2023-10-01 11:36:20 -05:00

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

Sign in to join this conversation.