The 1.14.1 release expands hardware support, introduces token-bucket-based duty cycle enforcement, and fixes two packet transmission bugs. Here's a breakdown of what's new for repeater, room-server, and companion node operators.
Two New GAT562 Devices
The GAT562 30S Mesh Kit and GAT562 Mesh Tracker Pro join the list of officially supported hardware. Both devices extend the ecosystem with ready-to-deploy mesh-capable hardware options.
SenseCAP Solar P1: GPS and Power Management
The SenseCAP Solar P1 now has full GPS support, enabling location-aware operation straight out of the box. A long-press power-off switch has also been added for cleaner shutdowns in the field — useful when the device is mounted in hard-to-reach solar-powered installations.
nRF52 Power Management for RAK3401
The RAK3401 — a compact LoRa module built around Nordic's nRF52 microcontroller — now benefits from dedicated power management. Sleep states are handled more efficiently, which translates to meaningful battery savings in low-traffic deployments.
Token Bucket Duty Cycle Enforcement
A token bucket algorithm now enforces duty cycle limits on transmissions. The concept works like a bucket that refills at a fixed rate: each transmission consumes tokens, and sending stops when the bucket runs dry. This keeps nodes compliant with regulatory limits for unlicensed LoRa spectrum without any manual configuration.
LNA Toggle via CLI
The LNA (Low Noise Amplifier — a receive-path preamplifier that improves sensitivity) can now be switched on or off directly from the command line:
This is especially handy for comparing reception with and without the amplifier active in your specific antenna setup.
GPS Time Sync and MCU Temperature Telemetry
Nodes with GPS enabled will now automatically synchronize their system time every 30 minutes, keeping the network clock consistent without manual intervention. Room servers now also include MCU temperature in their telemetry responses — handy for monitoring nodes installed in enclosures or exposed outdoor locations.
Bug Fixes
Two bugs have been resolved: queued packets were occasionally dropped instead of transmitted, and automatic advertisements were ignoring the configured multibyte path setting — a routing parameter that controls how path information is encoded in packets. Both issues are now fixed.