The MeshCore Companion App receives a substantial update with version 1.50.0, significantly enhancing interaction within the decentralized mesh network. This release focuses on advanced management functionalities and an optimized user experience.
Enhanced CLI Management Options
A key new feature is the ability to remotely manage other companion nodes via the command line. A dedicated button has been integrated into the contact details of the Companion App, providing direct access to a remote CLI. To utilize this, the remote CLI permission must be explicitly enabled within the contact permissions. This serves as a security measure to prevent unauthorized access.
Local Command Line Interface
In addition to remote management, version 1.50.0 introduces a local command line interface (CLI) within the settings screen. This allows for direct configuration of your own companion node. The local CLI is available for Companion Firmware Version 1.18.0 or higher, offering a powerful tool for advanced users to fine-tune detailed settings.
CLI
set radio.rxgain on
reboot
Managing Region Scopes and Wi-Fi Configuration
The app now supports importing and exporting region scopes within the Companion configuration JSON file. This simplifies sharing and applying specific frequency band settings relevant for LoRa communication. Also new is a dedicated Wi-Fi settings screen, which streamlines the configuration of SSID and password. Users can now more easily verify their connection types, as the currently used connection type is displayed at the bottom of the settings screen.
Improvements to Path Tracing and Ping Functionality
For the Path Trace Map Tool, a button has been added to cluster repeater markers, improving clarity for complex network paths. A long press on the ping button now configures the default path hash size for all future pings, increasing the efficiency of recurring diagnostic queries. When tracing 3-byte paths, which are not directly supported by the protocol, the app automatically converts them to 2-byte paths to ensure compatibility. Ping failure messages now display the repeater name and prefix, facilitating troubleshooting.