Audit the user docs for accuracy against the code, enrich them with
component-level screenshots, and separate the doc-screenshot generation
path from the visual-regression gate so doc framing no longer churns test
baselines.
Veracity fixes (claims verified against code):
- connections: removed 3 screenshots that were from the unrelated mPWRD/nymea
WiFi-provisioning app and rewrote the TCP/IP section to match the real
Network transport flow (mDNS scan + manual IP:4403); replaced the BLE
"scan" image (it was the wifi-provision splash) with the real device list.
- nodes: online window is 2h (not 15min); binary online/offline, no "away" tier.
- map: markers are identity-colored node chips, not online-status colors.
- node-metrics & signal-meter: signal quality is preset-relative SNR, not
fixed thresholds.
- messages: max message length is 200 bytes (not 237/230).
- telemetry: CO2 bands aligned to Co2Severity (Good/Stuffy/Poor/Unsafe/Evacuate).
- translate: locale dirs use {lang}-r{REGION}.
New pages: Home Screen Widget, Help & In-App Docs (Chirpy on-device AI).
Screenshot enrichment + tighter framing: added IAQ scale, firmware verifying,
TAK local server, quick-chat dialog; cropped firmware states and connections
panes to component-level views instead of full-screen frames.
Pipeline split (new :docs-screenshots module, generate-only, not CI-gated):
holds doc-framed compositions so reframing a doc image never moves a regression
baseline; :screenshot-tests stays the gate. copyDocsScreenshots aggregates
both modules. Updated CI filter, governance advisories, dev docs, and the
testing-ci skill.
Translated docs re-sync from the English source via the scheduled Crowdin job.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
:feature:firmware
Firmware Update System
The :feature:firmware module provides a unified interface for updating Meshtastic devices across different platforms and connection types.
Supported Platforms & Methods
Meshtastic-Android supports three primary firmware update flows:
1. ESP32 Unified OTA (WiFi & BLE)
Used for modern ESP32 devices (e.g., Heltec V3, T-Beam S3). This method utilizes the Unified OTA Protocol, which enables high-speed transfers over TCP (port 3232) or BLE. The BLE transport uses the Kable multiplatform library for architectural consistency and modern coroutine support.
Key Features:
- Pre-shared Hash Verification: The app sends the firmware SHA256 hash in an initial
AdminMessagetrigger. The device stores this in NVS and verifies the incoming stream against it. - Connection Retry: Robust logic to wait for the device to reboot and start the OTA listener.
- Automatic MTU Handling & Fragmentation: The BLE transport automatically detects the negotiated MTU and fragments data chunks into packets that fit. It carefully manages acknowledgments for each fragmented packet to ensure reliability even on congested connections.
sequenceDiagram
participant App as Android App
participant Radio as Mesh Node (Admin)
participant OTA as ESP32 OTA Mode
Note over App: Phase 1: Preparation
App->>App: Calculate SHA256 Hash
Note over App, Radio: Phase 2: Trigger Reboot
App->>Radio: AdminMessage (ota_request = mode + hash)
Radio->>Radio: Store Hash in NVS & Reboot
Note over App, OTA: Phase 3: Connection & Update
App->>OTA: Connect (TCP:3232 or BLE)
App->>OTA: Handshake & Version Check
App->>OTA: Start OTA (Size + Hash)
loop Streaming
App->>OTA: Stream Data Chunks
OTA-->>App: ACK
end
App->>OTA: REBOOT Command
2. nRF52 BLE DFU
The standard update method for nRF52-based devices (e.g., RAK4631). Uses a pure KMP Nordic Secure DFU implementation built on Kable — no dependency on the Nordic DFU library. The protocol stack (SecureDfuTransport, SecureDfuProtocol, SecureDfuHandler) handles DFU ZIP parsing, init packet validation, firmware streaming with CRC verification, and PRN-based flow control.
sequenceDiagram
participant App as Android App
participant Radio as Mesh Node
participant DFU as nRF DFU Bootloader
App->>Radio: Trigger DFU Mode
Radio->>Radio: Reboot into Bootloader
App->>DFU: Connect via BLE
App->>DFU: Initialize DFU Transaction
loop Transfer
App->>DFU: Stream ZIP Segments
DFU-->>App: Progress
end
DFU->>DFU: Verify, Swap & Reboot
3. USB / UF2 (RP2040, nRF52, STM32)
For devices supporting USB Mass Storage updates. The app triggers the device into its native bootloader mode, then guides the user to save the UF2 firmware file to the mounted drive.
sequenceDiagram
participant App as Android App
participant Radio as Mesh Node
participant USB as USB Mass Storage
App->>Radio: rebootToDfu()
Radio->>Radio: Mounts as MESH_DRIVE
App->>App: Prompt User to Save UF2
App->>USB: Write firmware.uf2
USB->>USB: Auto-Flash & Reboot
Key Classes
FirmwareUpdateManager.kt: Top-level orchestrator for all firmware update flows.FirmwareUpdateViewModel.kt: UI state management (MVI pattern) for the firmware update screen.FirmwareRetriever.kt: Handles downloading and extracting firmware assets (ZIP/BIN/UF2) with manifest-based ESP32 resolution.Esp32OtaUpdateHandler.kt: Orchestrates the Unified OTA flow for ESP32 devices.WifiOtaTransport.kt: Implements the TCP transport logic for ESP32 OTA.BleOtaTransport.kt: Implements the BLE transport logic for ESP32 OTA using Kable.UnifiedOtaProtocol.kt: Shared OTA protocol framing (handshake, streaming, acknowledgment).SecureDfuHandler.kt: Orchestrates the nRF52 Secure DFU flow (bootloader entry, DFU ZIP parsing, firmware transfer).SecureDfuProtocol.kt: Low-level Nordic Secure DFU protocol operations (init packet, data transfer, CRC verification).SecureDfuTransport.kt: BLE transport layer for Secure DFU using Kable (control/data point characteristics, PRN flow control).DfuZipParser.kt: Parses Nordic DFU ZIP archives (manifest, init packet, firmware binary).UsbUpdateHandler.kt: Handles USB/UF2 firmware updates across platforms.
Dependency Graph
graph TB
:feature:firmware[firmware]:::kmp-feature
:feature:firmware -.-> :core:ble
:feature:firmware -.-> :core:common
:feature:firmware -.-> :core:data
:feature:firmware -.-> :core:database
:feature:firmware -.-> :core:datastore
:feature:firmware -.-> :core:di
:feature:firmware -.-> :core:model
:feature:firmware -.-> :core:navigation
:feature:firmware -.-> :core:network
:feature:firmware -.-> :core:prefs
:feature:firmware -.-> :core:service
:feature:firmware -.-> :core:resources
:feature:firmware -.-> :core:ui
:feature:firmware -.-> :core:testing
classDef android-application fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef android-application-compose fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef compose-desktop-application fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef android-feature fill:#FFD6A5,stroke:#000,stroke-width:2px,color:#000;
classDef android-library fill:#9BF6FF,stroke:#000,stroke-width:2px,color:#000;
classDef android-library-compose fill:#9BF6FF,stroke:#000,stroke-width:2px,color:#000;
classDef android-test fill:#A0C4FF,stroke:#000,stroke-width:2px,color:#000;
classDef jvm-library fill:#BDB2FF,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-feature fill:#FFD6A5,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-library-compose fill:#FFC1CC,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-library fill:#FFC1CC,stroke:#000,stroke-width:2px,color:#000;
classDef unknown fill:#FFADAD,stroke:#000,stroke-width:2px,color:#000;