MeshApp v2.2.0

Release notes v2.2.0

Device settings

The device configuration screen now has contextual help for Meshtastic settings. Help is available next to configuration fields and explains what the setting does, when it is useful, what values are expected, and whether the option is deprecated or list-based.

Saving configuration is also more robust. MeshApp now detects modules that are not available in the device firmware before sending changes, and handles reconnects more reliably when a setting causes the device to reboot.

Remote administration

MeshApp can now administer remote Meshtastic nodes when this client’s public key is present in the remote node’s Admin Key.

From a node’s details screen, you can load the remote configuration over the mesh network, search and edit settings, and save changes back to the node. The loading process shows which sections were requested, received, or failed.

Remote administration also includes commands for reboot, shutdown, time sync, connection status refresh, backup and restore from Flash or SD, backup removal, NodeDB reset, configuration reset, factory reset, and DFU mode.

Firmware updates

A new Firmware tab is available in Settings. It shows the active connection, device information, and current firmware version. Firmware files can be selected as .bin, .uf2, or .zip; MeshApp validates the file and shows its SHA-256 hash before starting.

For ESP32 devices connected over TCP, MeshApp can perform Wi-Fi OTA upload: it requests OTA mode, waits for the bootloader, connects to it, and uploads the firmware.

BLE OTA and DFU/UF2 modes are recognized and validated, but full firmware upload through those modes is not yet handled by MeshApp.

Application updates

The About dialog now includes manual update checking.

On supported non-Flatpak installations, MeshApp can prepare application updates from inside the app: it downloads the update archive, verifies it, stages the new version, and applies it after restart. If automatic installation is not available or fails, the update dialog falls back to manual download.

Flatpak installations are not updated directly by MeshApp; the dialog shows the flatpak update app.privatepractice.meshapp command instead.

Application settings

A memory limit setting was added for the Java heap size. The value is configured in megabytes and takes effect after restarting the application.

Fixes

• Fixed a memory leak in telemetry charts.
• Fixed Store & Forward handling.
• Fixed version display in the About dialog.
• Fixed version detection for installations launched through the self-update mechanism.
• Fixed several issues in update preparation, archive verification, restart handling, and update manifest publication.
• Long dialogs and modal windows now scroll instead of cutting off content.