MeshCore v1.14.1 Brings Duty Cycle Control and New Device Support
MeshCore just released firmware v1.14.1 across repeater, room server, and companion platforms, and the changes reflect what the community has been asking for: better spectrum management, power efficiency, and support for emerging hardware.
The headline feature is token bucket-based duty cycle enforcement. For anyone running a repeater in Europe on 868 MHz, this matters directly—regulatory compliance just got easier. The token bucket algorithm ensures you stay within regional transmission limits without manual calculation or guesswork. If you’ve been nervous about exceeding duty cycle on a rooftop node, this update takes that anxiety off the table.
Power management got attention too. The nRF52-based RAK3401 now has dedicated power optimization, joining earlier fixes for the Heltec V4 and Heltec Tracker V2. On battery-powered nodes or solar repeaters, every milliamp counts. The SenseCAP Solar P1 picked up GPS support and long-press power-off functionality, making field deployment smoother for solar-powered setups.
New device support landed too. The GAT562 30S Mesh Kit and GAT562 Mesh Tracker Pro are now officially supported across all firmware variants. For operators looking to upgrade their mesh infrastructure, having fresh hardware ready out of the box means fewer firmware-flashing workarounds.
A smaller but useful addition: LNA toggle CLI commands (radio.rxgain on and radio.rxgain off) let operators fine-tune receiver sensitivity from the command line. Room servers now report MCU temperature in telemetry responses, which is handy for monitoring indoor server hardware during temperature swings.
Path Diagnostics Finally Get a Serious Upgrade
The v1.14.0 release a few weeks prior tackled a problem that’s been nagging the community for months: path hash collisions. The firmware now supports multibyte path hashes, replacing the single-byte prefixes that caused duplications when trying to trace packet routes through the mesh.
This matters if you debug routing issues or monitor network health. Single-byte hashes meant that two completely different paths could look identical on diagnostic output. With multibyte support, each route gets a unique fingerprint, making diagnostics and troubleshooting vastly more reliable.
The v1.14.0 update also shipped with new CLI commands for loop detection and path hash mode configuration, plus a discover.neighbors command for mapping local network topology on the fly.
Getting Updates Onto Your Nodes Just Got Simpler
Two new blog posts walk through the OTA (over-the-air) update process for the two most common MeshCore platform families. Updating nRF-based devices and ESP32 nodes are both straightforward now—no more climbing to the rooftop to manually reflash a repeater.
For operators running distributed repeater networks, this is a game-changer. Batch updates across multiple nodes happen wirelessly.
New Hardware: The T-Watch S3 Plus Joins the Roster
LilyGo’s T-Watch S3 Plus landed official MeshCore support. The device features GPS, an SX1262 LoRa radio, and a 1.5-inch color touchscreen. For someone building a portable mesh node or needing wearable situational awareness during field deployment, this fills a specific niche. The integrated GPS means location data without external hardware.
The broader trend across these updates is pragmatism: the project is shipping features operators actually need and supporting hardware that’s becoming available in the wild. Duty cycle compliance, power optimization, and wireless updates aren’t flashy, but they’re what make a mesh network deployable at scale.