diff --git a/CHANGELOG.md b/CHANGELOG.md index 816ae1e5a..d949d468b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,11 @@ upstream MeshCore `dev` branch, which generally pulls in a new MeshCore software ### August 2026 +- **New** — Analytics dashboard on the Heltec V4 R8 Expansion Kit V2 TFT: 20-minute rolling RF activity with a packets-per-minute graph, on a dark padded layout that repaints only the rows that changed 2026-08-28 +- **New** — `display.timeout` (blank after N seconds, 0 = always on) and `display.flip` (rotate 180 degrees), both applied live 2026-08-28 +- **New** — Tap the Expansion Kit V2 panel or press USER to blank/wake the display; hold USER 3 s to power off 2026-08-28 +- **Fix** — Power-off on the V4 R8 armed an RF wake, so a node in live traffic rebooted seconds after showing "Turning OFF" 2026-08-28 +- **Fix** — The V4 R8 TFT could not be woken once blanked, because waking re-ran a full panel init that also reset the touch controller 2026-08-28 - **New** · `platformio` — MQTT observer repeater and room-server configs for Heltec V4 R8 (OLED and TFT) 2026-08-20 ### June 2026 diff --git a/docs/cli_commands.md b/docs/cli_commands.md index 057fc0e2a..0c4ddf6ac 100644 --- a/docs/cli_commands.md +++ b/docs/cli_commands.md @@ -662,6 +662,37 @@ Elsewhere it replies `Err - neighbors not enabled in this build`. If a --- +#### View or change the display timeout +**Usage:** +- `get display.timeout` +- `set display.timeout ` + +**Parameters:** +- `seconds`: `0` to keep the display on permanently, or `1-3600` seconds of inactivity before it blanks + +**Default:** `60` + +**Note:** Observer builds with a display only. The change applies immediately and restarts the +countdown. Tap the panel or press the USER button to wake or blank it by hand. + +--- + +#### Rotate the display 180 degrees +**Usage:** +- `get display.flip` +- `set display.flip ` + +**Parameters:** +- `state`: `0`/`off` (as built) or `1`/`on` (rotated 180 degrees) + +**Default:** `0` + +**Note:** Observer builds with a display only, for a board mounted the other way up. This is +persisted config, so it survives a firmware update - a node that looks upside down after an +update may simply still be carrying `display.flip 1`. The boot log reports the current state. + +--- + #### Enable or disable Multi-Acks support **Usage:** - `get multi.acks`