Idle time before the screensaver starts. 0 = OFF.

Keeps the screen on while radio, SD or Bluetooth audio is active.

This screensaver shows the widgets defined in the MQTT settings. Configure the broker connection and widgets on the 📨 MQTT tab.

The display brightness while the screensaver is on. It never goes above the normal brightness, so 100 leaves it as it is. Any tap or encoder turn brings the normal brightness back.

The Dim style keeps the current screen and only lowers the brightness to this level.

💡 For clock-based dimming (dim at 22:00, brighten at 07:00), make a pair of time rules on the rules page.

Polls a JSON endpoint and renders one value. Active when screensaver style is "Dashboard".

When off, the 10-band EQ is bypassed entirely. Volume is unaffected. Changing any band (here, in the app, on the screen or from the remote) turns it back on automatically.

Mono sums left and right into both channels — for single-speaker builds. This affects the output only, not the stream itself: the CHANNELS readout on the device and in the web player keeps showing the source format (so a stereo stream still reads STEREO), and the VU meters keep their stereo image. Bluetooth playback is unaffected (it bypasses the DSP).

How the 0–100 % number maps to actual output gain. Tapered (default) raises the position to the fourth power, so the quiet end of the scale is fine-grained and usable. Gentle squares it instead — half as steep in dB, for amplifiers that already taper in hardware. Both reach full output at 100 %. Gentle is louder at low settings: 20 % is −28 dB against −56 dB tapered, so turn the volume down before switching. Applies instantly. Bluetooth is unaffected (the module scales in hardware, outside the DSP).

Percent, 100 for no limit. Every slider stays 0–100 — on the screen, here, in the app and in a rule. What changes is how much of the amplifier full deflection asks for: at 50, a volume of 100 is half power, and the whole travel spreads over the half the speakers can take. For a box that distorts or bottoms out near the top, this is the setting, not a smaller number on the slider.

Applies instantly, and to the fade-in of a wake-up rule and the level of a spoken notification as well. Bluetooth is not covered: that volume is the module's own, set over its own link.

Evens out the volume jump between radio stations. The device learns how loud each station is and turns the loud ones down, by up to 9 dB — it never boosts a quiet one, so nothing can distort at full volume. A new station plays as it is for about 15 seconds, then glides to its level; a station heard before gets its correction the moment it starts. Radio streams only: files, podcasts, Network Music, notifications and Bluetooth play unchanged.

When on, if the radio was playing before a restart, it resumes the last station automatically after boot.

When on, starting playback on the phone takes over the output — it stops the radio or the SD player — and starting the radio pauses the phone. Starting SD playback always pauses the phone, regardless of this setting.

Plays a signal on the left channel, then the right — a quick way to verify the wiring, amp and speakers without an SD card or stream. Uses the current volume.

Any remote will do — the radio learns the codes rather than shipping a key list: NEC (including the cheap LED-strip remotes), Samsung, RC5 and Sony are decoded. Point the remote at the receiver, press a key, and it appears below; then bind it to an action. Up to 20 keys, changes apply immediately.
On the playlist and SD browser screens, Next and Previous move the selection, and any of Play, Play / stop or Pause / resume opens what is selected — so those keys double as navigation and you need no separate ones. Stop still stops.

No receiver is wired yet. Assign a GPIO to ir_rx on the pin setup page and restart, then come back here.

The remote talks to the radio over ESP-NOW, not Wi-Fi — this button only opens a 60-second window during which the radio accepts a pairing request. Press it, then start pairing from the remote's own menu. Pairing again replaces the stored remote.
The remote sleeps between button presses, so “last contact” is the age of the last frame it sent — hours of silence is a healthy remote on battery, not a broken link.

When disabled, the device does not connect to the broker.

Leave blank to keep the existing password.

Must be unique per broker — two devices sharing one ID disconnect each other in a loop. Leave blank for an ID derived from this device's MAC.

Device topics will be: <base>/state/* and <base>/cmd/*. Publishing any action string to <base>/cmd/action runs it, including macro:N, which fires the rules waiting on that number.

Announces the radio to Home Assistant, which then adds it as a device with volume, brightness, source, transport buttons, now playing and the wired I/O slots — no YAML. Sent once per connection (one retained message under homeassistant/device/). Needs Home Assistant 2024.11 or newer. Turning it off removes the device from Home Assistant. If you added the radio's entities to Home Assistant by hand, remove those, or you will have each one twice.

Up to 6 widgets (toggle / slider / label) shown on the MQTT screen.

Lets a rule send you a message through a bot — add a Telegram block to a rule in the rules editor.

Off means no task, no connection and no cost.

Seconds. 0 turns receiving off; below 5 is raised to 5. A /command written in the chat runs the rule whose trigger is Telegram command named command — make one in the rules editor.

Cheaper than it reads. The connection is kept open and Telegram is asked to hold each check for up to 15 s, so checking every 15 s is one handshake rather than four a minute. The cost of a check is the handshake, not the question.

Only messages from the chat id below are obeyed — a bot's name is public, so without that anyone who finds it could drive the radio. Anything that is not a command is ignored, and nothing from Telegram is ever shown on the screen.

Talk to @BotFather to create a bot and get its token. Kept in NVS, never sent back to this page — leave the field empty to keep the stored one.

One reader per bot. Telegram lets a single client hold getUpdates, so a token already being polled by Node-RED, a script or another device cannot also be read here — checks come back 409 and the log says so. Give this device a bot of its own if something else already has one. Sending is unaffected; only reading collides.

Where a message with no chat of its own goes. Your own id comes from a bot such as @userinfobot; a group id starts with a minus.

Shows current conditions on the device's home screen. Widget position is set in the layout editor.

Get a free key at openweathermap.org. Stored in weather.json, so it exports with the rest of the configuration.

Search powered by Open-Meteo, or enter coordinates manually. Saving remains a separate step.

Display only — the device always fetches the data in °C.

Text shown next to the icon on the device. Pick a language preset or type your own — the device stores exactly what you enter. An empty box falls back to the English name. Keep them short: a long name widens the widget and can run off a narrow screen.

—

Remap GPIO pins for display / touch / SD / encoder / Bluetooth, stored on the device. Advanced — wrong pins can blank the display (recoverable here). Opens the built-in setup page.

Drive the free GPIOs yourself — a relay, an LED, a fan — or read one as an input (switch, PIR, reed contact) and let it run any action a button can. Assign the pins under pin setup first.

Configure audio VU, volume feedback and system-status overlays for every WS2812B strip. Set its GPIO, length and colour order on the I/O page first.

"When this happens, do that" — a trigger (a time, a device state, a button bound to macro:N), conditions that have to hold, and a sequence of actions. Built as blocks on a canvas, with a live trace of what fires.

Live device health, refreshed every 2 s while this tab is open — the same snapshot as Settings → System → Diagnostics on the device. Copy report puts it on the clipboard as plain text, every task stack included, ready to paste into a bug report.

Every error and warning the radio has logged, kept on the device across restarts and crashes — no serial cable needed. Download it and attach it to a bug report.

Extra log lines on the serial console (115200 baud), per subsystem — for hunting a problem on a device that is already flashed, without a debug build. Off by default; the choice is saved, so an armed flag also covers the next boot. Leave it off in normal use: the busiest flags print several lines per second.

Saved in this browser. System follows your device's light or dark appearance. The AtlasCube screen theme is configured separately.

Re-upload the web UI after an app-only OTA left it behind (the warning above). Pick the raw files from spiffs_image/www/ — get the matching set (AtlasCube-www.zip) from the latest release. Include www_version.txt in the selection to clear the warning. HTML/CSS/JS are gzipped on the device; .ico isn't supported here.

Opens the wiring builder on atlascube.net with this radio's pins, display and I/O slots already filled in, to see or print how everything is connected. Opening it changes nothing. The builder's Send to radio comes back to this page, lists what would change and saves only once you confirm. The diagram counts as the whole radio: a part left off it is disconnected.

Download every user file on the config partition (settings, events, MQTT, layout and the station list) plus the hardware pin map as a single .json — a snapshot to keep before a full USB flash, which erases them. Wi-Fi/MQTT passwords live in a separate secure store and are not included. Same file format as the built-in setup page — a backup made there imports here and the other way round.

Restore a backup made above or on the setup page. Existing files are overwritten; everything takes effect after a restart (a restored pin map, if a part misbehaves then, after a full power cycle).

A software restart: playback stops and the device is back in a few seconds. Settings are kept, and so is the error log — unlike the reset button or a power cycle.