I tried the same if ((rtc.alarmFired(2) == true) ) code on the breadboard version and get the same results (crash on form submission).
Changed true to 1 and it is not crashing.
Also, even though I get stuff like this, the RTC time seems to be right:
Writing file: /inputMsg.txt
- file written
yourInputTime:…It's this bit that's causing the i2cCheckLineState() error and reboot:
if ((rtc.alarmFired(2) == true) ){
// Print current time and date
DateTime now = rtc.now(); //…I'm getting weird dates again. I will look at the hardware connections tomorrow.
It's also worth considering using the SQW pin: https://garrysblog.com/2020/07/05/using-the-ds3231-real-time-clock…
RTC alarms seem to fire at the next opportunity, even if they happened when ESP32 was off. This is a problem I wanted to avoid.
Reset the alarm in setup() if it's in the past?
OK, so it looks like arduino-timer .at() uses the millis() clock. Are there timers that use real time?
Still not working. May need to try AsyncIOScheduler, which I think is where the error is coming from.
Going to wait and see if this error causes any problems or not. Although I'm not sure why this would happen if I'm calling ki.stop().
2023-09-07 08:31:32,558 - Scheduler started
2023-09-…Replaced BlockingScheduler with BackgroundScheduler per https://apscheduler.readthedocs.io/en/3.x/userguide.html#choosing-the-right-scheduler-job-store-s-executor-s-and-trigger-s.
It looks like the reconnections have been happening, but didn't record this packet:
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…Closed in afe5b9338d6385e23004eaf815ade8a873531617 (at least for the fields I already have).