Customer:
I just bought an Inkplate 10 and cannot get the Inkplate10_RTC_Alarm_With_Deep_Sleep example sketch to work. It only displays the time once and then never wakes up again. I also put in a battery for the RTC.
Originally submitted via email support on 27 October 2024. Migrated to the forum for community visibility.
Soldered Support:
RTC issues were being investigated and a software patch was in development.
Soldered Support:
Testing found that RTC_Alarm worked alone with a time difference of ~2 mins, but the RTC deep sleep example had issues. The year wasn’t displaying correctly when printed. A working version of the sketch was created:
Output from the working sketch:
RTC data:
rtc_seconds: 0
rtc_minutes: 5
rtc_hour: 12
rtc_day: 6
rtc_weekday: 4
rtc_month: 11
rtc_year: 24
epoch:
RTC set alarm data:
rtc_alarm_seconds: 14
rtc_alarm_minutes: 37
rtc_alarm_hour: 5
rtc_alarm_day: 1
rtc_alarm_weekday: 4
The data written to the RTC is correct and can be read back. However, the epoch received is not correct and thus the alarm time is also incorrect because it’s being set via the epoch. At that time, the reason was unclear.
Setting the alarm time via another function worked: https://pastebin.com/raw/sm9RmyQ8
The epoch printed is still incorrect, but setting it manually seems to work. Investigation into the two epoch functions was needed. The working example should be usable in the meantime for creating something temporarily useful.
Soldered Support:
If interested, try running this code on Inkplate to check if any of these times get incorrectly read:
This worked on both Inkplate 10 and Inkplate 5 - unable to recreate the issue anymore, so feedback from users who reported RTC issues would help.