v3.13.1 — 2026-09-25

A bug-fix release. If you use a Quiet Time schedule, take this one.

Fixed

• A Quiet Time schedule could reboot the gateway — and with Restore on Boot enabled, loop. The schedule was evaluated on the RTC task, which has a 2 KB stack that already peaks at about 1.4 KB just reading the clock. Asserting Quiet Time from there sends bus frames through a call chain that needs roughly 1.5 KB more: a stack overflow, a panic, a reboot. Reported as "quiet time does not work with restore on boot: it goes blank, after a minute it loads the backup, and loops" — exactly that sequence: power-up homing (blank), the boot restore, the schedule asserting quiet the moment the restore released the bus, the crash, and round again. The schedule now runs on the network task, which has the stack for it. Verified on hardware: asserting quiet from the schedule now costs 1.8 KB of that task's 6 KB and the gateway carries on.
• Restore on Boot now takes the bus before any task starts, so the schedule can no longer assert Quiet Time in the gap before the restore is armed.

---

Board: Waveshare ESP32-S3-RS485-CAN (16 MB flash).

• SplitFlapGateway-3.13.1.bin — the application image. Upload it from the dashboard (Settings ▸ Open Firmware Updater), push it with espota, or flash it over USB at 0x10000 together with boot_app0.bin at 0xE000.
• boot_app0.bin — the boot selector for a USB flash of the app image.
• SplitFlapGateway-3.13.1.factory.bin — the complete image for a blank board, over USB at 0x0 (erases WiFi/MQTT settings).

If the web update fails, see the README's recovery without developer tools.