0.57.0: real-time clock, 2FA, and alerts that wait for the network

[dexif]

0.57.0 is out.

The ESP32-P4 forgets the time when it loses power. Until it reached an NTP server or a browser signed in, it did not know the date, and file names on the card and two-factor codes need it. Now a small clock module on the capture board's I2C bus keeps it. On the Function EV and the Waveshare boards with a 40-pin header, a "DS3231 for Pi" module plugs straight onto pins 1-9. I pulled the power cable on my Function EV several times, and each time the clock came back within a second.

The clock chips it knows:

Chip	Common modules	Found by itself	Tried on hardware
DS3231, DS3231M	ZS-042, "DS3231 for Pi", ChronoDot v2, Adafruit DS3231	yes	yes
PCF8563, BM8563, RTC8563	M5Stack Unit RTC	yes	not yet
PCF85063		no, name it in Settings	not yet
PCF8523	Adafruit PCF8523	no, name it in Settings	not yet

The modules now have their own pages, next to the status displays: https://espkvm.io/boards/#clocks

Also in 0.57.0:

• Two-factor sign-in: after the password, a six-digit code from an authenticator app, with eight recovery codes for a lost phone. Settings -> Security.
• Alerts that could not go out - network down, Telegram busy - now wait, up to 50, and are sent later with the time they really happened. With a microSD card they survive a restart. This came out of a Reddit thread about the dashcam.
• Updates come from fw.espkvm.io now. The old address keeps working for older firmware.
• The DFRobot FireBeetle 2 is confirmed on hardware, thanks to @Diego-fe in DFRobot FireBeetle 2 (DFR1172): C6 reports fw 0.0.0, SDIO falls back to streaming mode, data plane stalls under MJPEG #63.

The write-up: https://espkvm.io/blog/0-57-0-a-clock-2fa-and-alerts-that-wait/

Two fixes followed:

• 0.57.1: over Wi-Fi the H.264 picture no longer flashes "Cannot play this stream" every few seconds.
• 0.57.2: for a few hours devices on 0.56 and older could not see new releases, because their update address started to redirect and they did not follow it. That address answers directly again, and from 0.57.2 the device follows a redirect anyway. It also fixes a boot loop on Wi-Fi boards when the Wi-Fi chip did not answer at start-up. If your console did not offer 0.57, open the update panel again.

If you have a PCF8563, PCF85063 or PCF8523 module, or the M5Stack Unit RTC, I would like to hear whether it works. Those drivers are written from the datasheets, and one log line from a real board would move them to the tested list.