Built-in setup page
Backup / restore every user file on the config partition
(settings, theme, events, MQTT, layout, station list) together with the pin map as a
single file — import it here after a web flash to re-provision the device in one step.
The Wi-Fi password is not included (it is stored separately, outside
settings.json) — set Wi-Fi above. Same file format as
Settings → System in the web UI, so a backup made there imports here and the
other way round. A full power cycle is needed after import.
Upload an application image — atlascube.bin, or
AtlasCube-<display>-ota.bin for your display from
atlascube.net/flash.
It is written to the inactive slot and the device reboots into it; settings and
pin map are kept. Works from this built-in page even if the web UI partition is wiped.
Don't power off during the upload.
www_version.txt in the selection to clear this warning.
Get the matching files (AtlasCube-www.zip) from the
latest release, then extract and
upload them below.
Optional / recovery only — the web UI ships inside the firmware, so a normal flash already includes it. Use this just to patch or restore individual files without reflashing.
Pick the files from spiffs_image/www/ (raw, uncompressed) —
get the matching set (AtlasCube-www.zip) from the
latest release.
The device gzips HTML/CSS/JS on upload. Icons (.ico) are not supported here.
Include www_version.txt to clear the "web UI out of date" warning.
Loading…
Allowed pins (in use / free):
GPIO number per signal, or -1 to disable. The display
driver is fixed in this firmware — only the wiring is configurable here.
The device refuses pins the chip or the firmware already owns (on the ESP32-S3: 19/20 native USB, 26–32 SPI flash,
33–37 octal PSRAM, 43/44 UART0 console); duplicates are blocked too.
The strapping pins 0 (BOOT button) and 45 (flash
voltage) are flagged but allowed. 3 and 46 are strapping pins as well, but
only matter with an eFuse burnt or BOOT held, so they count as ordinary
pins. Saved values take effect after the restart.