MeshCore Low-Power · Releases

from GitHub · updated 2026-08-02

19 releases

v1.16.dev_0802 # 3 days ago · 2026-08-02 08:16 UTC

View release ↗
v1.16_0802
- New: standby mode and GNSS mode selection for a confirmed ATGM336H-6N quick-link GPS module. (Companion, Repeater, Room Server — E213, V3, E290)
  
  Both take effect only once the attached module is confirmed to be an ATGM336H-6N — detected from the module's own hardware-info reply (tested via M5Stack's Unit GPS v1.1); other modules are left alone.
  - Standby mode: the quick-link GPS module is externally, continuously powered — the board has no wire to cut its power directly. Turning GPS off (or between fixes, while duty-cycling) now sends the module into its own low-power standby mode instead of leaving it running at full power the whole time.
  - GNSS mode selection: the same GNSS Mode setting already available on V4 and T096 (CLI get/set gps.mode, Companion Portal dropdown, shown read-only on the on-device GPS page) is now available on E213, V3, and E290 too: GPS / GPS+BDS / GPS+BDS+GLONASS+Galileo / GPS+BDS+GLONASS+Galileo+QZSS.
- New: GPS-on reminder icon in the header. (Companion — all platforms with GPS)
  
  GPS is easy to turn on and forget about, quietly draining the battery in the background. A small circle-with-center-dot icon now appears in the header whenever GPS is active, positioned just left of the battery icon. Shown on the Home page only on OLED (limited header space); shown on every page on T096 and e-ink, which have more header room.
- New: gps.minsat / gps.hdop — tune how many satellites and how accurate a fix needs to be before GPS reports it as valid. (Companion, Repeater, Room Server — all platforms with GPS)
  
  Previously fixed in firmware (minimum 6 satellites, HDOP ≤ 2.0). Now configurable via CLI (get/set gps.minsat, get/set gps.hdop) and the Companion/Repeater/Room Server portal, so it can be tuned for different sky conditions without a rebuild. Companion's GPS page also now shows current HDOP next to satellite count (sat / hdop).
Heltec V3 GPS wiring: module RX → GPIO47, module TX → GPIO48. Heltec E213 GPS wiring: module RX → GPIO43, module TX → GPIO44. Heltec E290 GPS wiring: module RX → GPIO43, module TX → GPIO44.
- New: configurable default channel for Quick Send. (Companion — all platforms)
  
  Quick Send previously always sent to the Public channel. It now targets a configurable channel instead, settable via Qk.Ch. in on-device Settings, CLI (get/set quick.channel), or a new Default Channel dropdown in the Companion Portal's Quick Send Presets section — and included in portal backup/restore.
Heltec T096 antennas wear out easily with just light usage.
v1.16.dev_0726 # 10 days ago · 2026-07-26 06:36 UTC

View release ↗
v1.16_0726
- New: GPS support for Heltec Vision Master E213 via the quick-link UART header. (Companion, Repeater, Room Server — E213)
  
  E213 exposes its native UART0 pins on the board's quick-link connector. Wire any NMEA GPS module's TX/RX there (crossed), with the module connected and powered at boot/reset so the firmware can confirm it's present — GPS then works as usual. Its baud rate doesn't need to be known in advance: it's auto-detected in software on first use, and re-detected automatically if a different module is swapped in while GPS is off.
- Fix: a GPS module that stops responding mid-session is now detected. (Companion, Repeater, Room Server — V4, T096, E213)
  
  Previously, if a working GPS module died or was unplugged after startup, the device had no way to notice — the GPS page just kept showing "no fix" forever. It now shows "Lost GPS module" after about a minute of silence while GPS is on, and recovers automatically once the module (or a replacement) starts responding again, no reboot needed.
- Fix: Quick Send presets not saved on NRF52 boards. (Companion — T096, RAK4631)
  
  Presets were only ever written/read via an ESP32-only SPIFFS path, so on NRF52 they silently reset to defaults on every reboot. Now uses the cross-platform store, like Saved Locations.
v1.16.dev_0719 # 17 days ago · 2026-07-19 05:04 UTC

View release ↗
v1.16_0719
- New: Sensors screen. (Companion — all platforms)
  
  A new Sensors page on the Home screen. Battery shows a 24-hour rolling battery-percentage history as a bar chart, one bar per hour. If an environment sensor is attached, long press cycles through its readings — temperature, humidity, pressure, altitude, voltage, current, power, distance, or gas resistance — as a plain value+unit grid (°C, hPa, V...). The header shows the sensor's actual name (e.g. "BME280") while viewing its page, and precise Vbat voltage while viewing "Battery". With only one sensor attached, the page title just reads "SENSOR"; with more than one, pages are numbered by detection order ("Sensor 1", "Sensor 2"...) rather than the raw LPP channel number.
- Message Persist setting now available in the WiFi Companion Portal, and included in backup/restore. (Companion — WiFi transport, V3, V4, E213, E290, Wireless Paper, XIAO S3)
  
  The Message Persist toggle (added in v1.16_0714) was previously only reachable via CLI or the on-device UI. It's now also a checkbox under General Settings in the Companion Portal, and its value round-trips through the portal's Backup/Restore.
v1.16.dev_0714 # 23 days ago · 2026-07-14 01:38 UTC

View release ↗
v1.16_0714
- New setting: choose whether unsynced messages are saved to flash. (Companion — all platforms)
  
  Companion → Settings → Message Persist, or CLI get/set msg.persist. Off by default — unsynced messages only live in RAM until the app syncs them. Turn on to also persist them to flash so they survive a crash, reboot, or dead battery before the app catches up. Turning off immediately clears any already-persisted copy from flash.
  
  On NRF52 boards (T096, RAK4631), each persisted message costs one physical flash-page erase, on a small 100KB partition shared with contacts — fine for normal personal use, but sustained heavy traffic (hundreds to 1000+ msgs/day) wears against that partition's erase-cycle lifetime faster than typical usage. ESP32 boards aren't affected: SPIFFS appends into already-erased space and only erases a block during garbage collection, not on every message write.
v1.16.dev_0712 # 24 days ago · 2026-07-12 04:44 UTC

View release ↗
v1.16_0712
- New: reach Companion via mDNS hostname instead of typing an IP. (Companion — WiFi transport, V3, V4, E213, E290, Wireless Paper, XIAO S3)
  
  When connected over WiFi, the node is now reachable at meshcore-xxxx.local (xxxx = the first 2 bytes of its public key, unique per node) instead of needing to know its DHCP-assigned IP. Confirmed working with the official MeshCore app.
- New: unsynced messages now survive a crash or reboot. (Companion)
  
  Previously, any message received while the app wasn't connected only lived in RAM — a crash, reboot, or dead battery before the app had a chance to sync meant it was gone for good. Unsynced messages are now also saved to flash and restored automatically on boot, along with the on-device unread indicator. USB-connected companions are covered too, since USB has no reliable way to detect whether the app is actually listening — messages are saved as they arrive rather than waiting for a disconnect that may never be seen in time.
- New: e-ink ghost-clearing. (Companion, Repeater, Room Server — E213, E290, Wireless Paper)
  
  Each boot now runs a quick black/white flush to prevent ghosting from building up, Companion adds a Settings → Clear Ghost action for a deeper manual clean, and a static screen gets an automatic full refresh every 5 minutes of idle to prevent burn-in.
v1.16.dev_0705 # 1 month ago · 2026-07-05 07:23 UTC

View release ↗
v1.16_0705
- New setting: WiFi static IP configuration. (Companion — V3, V4, E213, E290, Wireless Paper)
  
  When using WiFi transport mode, you can now assign a fixed IP address instead of relying on DHCP. Configure via CLI (get/set/clear wifi.ip) or the config portal (Static IP + Subnet Mask fields in the App Transport Connection section). Blank Static IP = DHCP. Included in backup/restore.
- New setting: Message Font — Normal or Large now available on all displays. (Companion — V3, V4, T096, E213, E290, Wireless Paper)
  
  On OLED (V3/V4): Message Normal Font with transliteration; Message Large Font with native UTF-8 (Latin, Cyrillic, and Greek). On TFT (T096): both Normal and Large render native UTF-8 — only the size changes. On e-ink: as before — Normal or Large, both native.
- Fix: incoming message alert sometimes silently missed, bouncing to the Home screen instead. (Companion)
  
  If the app had synced messages off the device (draining the offline queue) and later disconnected, the next incoming message could fail to show its on-device alert — the screen would wake but land on Home instead. Caused by a stale internal "unread" marker left behind after the queue was drained. Fixed.
- Fix: WiFi STA could get stuck associated with no IP after reconnect. (Companion — WiFi transport)
  
  If no valid IP is held for 30s, the node now forces a WiFi reconnect to retrigger DHCP, instead of staying stuck until a manual reboot. Static IP config is preserved.
- Fix: restoring a large backup could crash the node. (Companion — config portal)
  
  Backups grow past 100 KB with many contacts; restore now streams the file instead of loading it all into RAM, so it no longer overflows and crashes.
- Backup/restore now covers all passwords. (Companion, Repeater, Room Server — config portal)
  
  Passwords are now part of the backup, so a restore fully re-provisions the node with nothing left to re-enter by hand: WiFi and portal login on Companion; Admin and Guest on Repeater and Room Server.
v1.16_0706 pre-release for e-ink devices
- New: e-ink ghost-clearing. (Companion, Repeater, Room Server — E213, E290, Wireless Paper)
  
  E-ink screens gradually accumulate faint ghosting from partial refreshes that a normal full refresh doesn't fully remove. Each boot now runs a quick black/white flush to keep this from building up, and Companion adds a Settings → Clear Ghost action that runs a deeper multi-cycle clean to clear stubborn ghosting on demand.
v1.16.dev_0628 # 1 month ago · 2026-06-28 03:34 UTC

View release ↗
v1.16_0628
- Portal: out-of-range numeric inputs are now blocked before saving. (Companion, Repeater, Room Server)
  
  Save is blocked if any numeric field is out of range; a red error message lists which fields need fixing (e.g. Spreading Factor (5-12): >= 5). Covers SF, CR, TX Power, interference threshold, timezone offset, duty cycle, flood max, channel hop limits, and all other bounded numeric fields.
- Fix: Portal Password and WiFi Password fields now show ******** when already set. (Companion)
  
  The Repeater and Room Server portals already had this behaviour; the Companion portal was missing it. Both fields now pre-fill with ******** when a password is stored. Submitting without changing the value leaves the password untouched; submitting blank clears it.
- E-ink font bumped from 13 px to 15 px. (Companion — E213, E290, Wireless Paper)
- New setting: Message Font — Normal (15 px) or Large (18 px) for message body. (Companion — E213, E290, Wireless Paper) Large is useful for Cyrillic/Greek where glyphs are taller.
- Fix: newest contacts were invisible on the Contacts screen. (Companion) Index offset bug from upstream PR #2763 (anon-contact slots) — contacts now display correctly.
- Fix: companion clock stuck in the future. (Companion) If a stored contact had a future-dated timestamp from a mis-clocked peer, the app's correct time sync was refused because it appeared to go backwards. Now accepted; affected contact timestamps are clamped to the corrected clock.
v1.16.dev_0621 # 2 months ago · 2026-06-21 07:24 UTC

View release ↗
v1.16_0621
- Configuration portal for Companion, Repeater, and Room Server — configure, back up, restore, and update firmware without the CLI. (ESP32 devices only)
  
  Open it the same way as before — start ota in the CLI, or Start OTA from the companion Settings menu. Previously this landed on a firmware-only upload page; it now opens the full configuration portal where you can configure, back up, restore, flash firmware, and reboot — all from one page in the browser.
  
  The companion backup covers custom preferences (Quick Send presets, saved locations, channel hop limits, display settings, WiFi credentials,...) that upstream MeshCore doesn't have — handy when moving to a new device. For the Repeater and Room Server, this is the first time backup and restore are available at all — no more re-entering everything from scratch after a node failure or hardware swap.
  
  The portal is password-protected. Companion: set one with set portal.password in the CLI. Repeater / Room Server: the existing admin password is used automatically.
  
  The backup format is compatible with the official MeshCore app — upstream preferences in the backup can be restored by the app. Passwords are never written to backup files.
- Config portal AP: open network, login page, 1-client limit, 10-minute idle auto-shutdown.
  
  The WiFi AP is open (no AP password); access is gated by a browser login page using the portal password described above. Only one device can associate with the AP at a time. If no device connects within 10 minutes of the AP opening, it shuts down automatically.
- Fix: full-flash (_merged.bin) images for Vision Master E213 and E290 were built with the wrong flash size.
  
  Both boards have 16 MB of flash, but their merged full-flash images were generated with an 8 MB flash-size header. The pre-merged images are now built with the correct 16 MB size. If you previously flashed an E213 or E290 using a _merged.bin, re-flash with the corrected image. OTA (.bin) updates were not affected.
v1.16.dev_0614 # 2 months ago · 2026-06-14 04:15 UTC

View release ↗
v1.16_0614
- New devices: Heltec Vision Master E213, Wireless Paper, and Vision Master E290 — full e-ink companion support (Companion, Repeater, Room Server).
  
  Three e-ink boards are now fully supported with the complete companion UI — Quick Send, Contacts, Settings, Saved Locations, GPS Trace, and message preview. Repeater and Room Server firmware are provided for all three.
  - Heltec Vision Master E213 (author-tested, v1.1.1) — ESP32-S3 with a 2.13" e-ink display (250×122 px), SX1262 LoRa, and a QuickLink I2C port. Has a second user button (GPIO21): press to scroll up in any list, or to go back — faster than double clicking the main button.
  - Heltec Wireless Paper — ESP32-S3 with the same 2.13" e-ink panel as the E213 in a more compact form factor. Shares the same companion UI and firmware variants as the E213. Single button only.
  - Heltec Vision Master E290 — ESP32-S3R8 with a larger 2.9" e-ink display (296×128 px), SX1262 LoRa, and a QuickLink I2C port. Also has a second button (GPIO21) like the E213. The companion UI adapts automatically to the wider panel — more message lines and a larger clock on the Home screen.
  Common characteristics across all three e-ink boards:
  - Always-on display — e-ink retains content indefinitely without power; no screen timeout.
  - Native multilingual text — Latin, Cyrillic, and Greek scripts render natively.
  - Font Weight setting — choose between Thin and Bold via Settings → Font Weight. Preference is saved to flash.
  - I2C sensor support — environment sensors can be connected via the QuickLink I2C port.
- Companion: unified BLE / USB / WiFi connection mode for all ESP32-S3 boards.
  
  All ESP32-S3 companion builds (Heltec V3, V4, E213, Wireless Paper, E290, XIAO S3) now ship as a single unified firmware image that supports all three connection transports: BLE, USB serial, and WiFi TCP. The active mode is saved to flash and selected at boot — no per-mode build is needed.
  
  Switching is done via Settings → Connection Mode, which opens a direct selection screen listing all three modes with the current one marked *. Navigate to the desired mode and confirm — the device reboots into the new mode.
  
  Alternatively, switch via TerminalCLI: set conn.mode wifi|ble|usb. WiFi credentials are configured with set wifi.ssid / set wifi.password, or from the OTA update page which now includes a WiFi credentials form alongside the firmware upload button.
  
  In WiFi mode, the node connects as a STA to your router and the Home screen shows the IP address and port. All three modes meet the low-power criteria of this repo.
- Companion UI: Home screen always shows a large clock; message count shown in the header.
  
  The center of the Home screen now always shows the current time (HH:MM) in a large font — MSG: N is gone. If there are messages stored in memory, their count and a small envelope icon appear in the header (where the small clock used to be); the header is left empty when count is zero. The header clock is visible again on all other pages as before.
  
  On e-ink displays (E213, Wireless Paper, E290), the clock is rendered in a large font; pairing pin or connection status appears at the bottom-left, and the date at the bottom-right. On OLED and T096, the layout is: large clock → date → connection status, stacked top to bottom.
  
  Before the clock is synchronized with the app or GPS, the display shows uptime counting up from 00:00 since boot, consistent with the small header clock.
- Repeater/Room Server: flood hop limits now correctly ignore leading-zero path padding.
  
  Some senders limit how far a packet propagates by pre-filling the path with zero entries — a TTL trick used by custom firmware, and by companions in this firmware via ch.hops. Previously, repeaters counted these zeros as real relay hops, causi …
pre-release-Heltec-E213-Wireless-Paper-E290 # Pre-release 2 months ago · 2026-06-11 11:45 UTC

View release ↗
v1.16_0611 pre-release for Heltec E213, Wireless Paper and E290
- New device: Heltec Vision Master E213 — full support (Companion, Repeater, Room Server).
  
  The Heltec Vision Master E213 is now fully supported. It is an ESP32-S3 based board with a 2.13" e-ink display, SX1262 LoRa radio, and a USB-C port. The complete companion UI runs on the e-ink display — Quick Send, Contacts, Settings, Saved Locations, GPS Trace, and message preview. Repeater and Room Server firmware are also provided.
  
  Notable characteristics:
  - Always-on e-ink display — no screen timeout; the display retains its content indefinitely without power.
  - Native multilingual text — Latin, Cyrillic, and Greek scripts render natively.
  - I2C sensor support — environment sensors (temperature, humidity, pressure...) can be connected via the QuickLink I2C port.
  - Two user buttons — the second button (GPIO21) makes navigation faster: press it to scroll up in any list, or to go back/exit any menu.
- New devices: Heltec Wireless Paper and Heltec Vision Master E290 — full support (Companion, Repeater, Room Server).
  
  Two new e-ink boards are now supported:
  - Heltec Wireless Paper — ESP32-S3 with a 2.13" e-ink display (same resolution as E213), SX1262 LoRa radio, and a compact form factor. Shares the same companion UI and firmware variants as E213.
  - Heltec Vision Master E290 — ESP32-S3R8 with a larger 2.9" e-ink display (296×128), SX1262 LoRa radio, and a QuickLink I2C port for external sensors. The companion UI adapts automatically to the wider, taller display — showing more message lines and better-spaced layouts compared to the 2.13" boards.
v1.16.dev_0607 # 2 months ago · 2026-06-07 05:01 UTC

View release ↗
v1.16_0607
- Companion UI: Native multilingual display on Heltec T096 (ST7735S)
  
  Node names and messages now render natively on the T096 color TFT — characters are displayed as-is instead of being converted to ASCII equivalents. Supported languages include all 31 from v1.14 plus additional scripts:
  
  Latin-based: Catalan, Croatian, Czech, Danish, Dutch, Estonian, Finnish, French, German, Hungarian, Icelandic, Italian, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish, Swedish, Turkish, Vietnamese, Welsh
  
  Cyrillic: Belarusian, Bulgarian, Macedonian, Russian, Serbian, Ukrainian
  
  Greek: Greek
- Companion UI: Contacts screen now includes room servers; request telemetry from any contact.
  
  Room servers appear in the contact list tagged [R]. Selecting any contact — chat node or room server — and long pressing opens an action menu: Send message or Request telemetry. Requesting telemetry displays the node's battery voltage and GPS coordinates (if present); long press to open the GPS Trace screen for that location.
  
  GPS coordinates follow the Pos. Format selected in Settings (DD, UTM, or MGRS).
  
  The message inbox group list now tags group/channel entries with [G] and room server entries with [R] for consistent visual distinction. Each room message shows the original author's name. When viewing a room message, long press to open the popup and select Reply to post back to the room (visible to all subscribers).
  
  Private room servers: messaging requires a prior login. Public rooms (no password) work without any login. For private rooms, log in once via the MeshCore app — if your account has admin rights on that room server, the session persists across reboots. Regular user sessions are not saved to flash and will require re-login after the room server reboots.
- Companion: switch the app connection between BLE and USB serial without reflashing.
  
  In USB mode the node behaves like a standard usb build — the PC app connects over the USB serial port directly. Toggle via Settings → Connection Mode on the display, or via TerminalCLI: set conn.mode usb / set conn.mode ble. The setting persists across reboots. BLE toggle is hidden in the Settings menu while USB mode is active.
- Repeater, Room Sever: hold user button 5 seconds to power off.
  
  Hold the user button for 5 seconds to power off the node — faster than reaching for the CLI when you're standing next to it. The LED blinks 5 times as a warning before shutdown.
- Repeater, Room Server: advert.hops.max default changed to 8; room server support added; flood.max.advert alias.
  
  advert.hops.max now defaults to 8 instead of flood.max — advert relay limiting is active out of the box without any configuration. Room servers now also enforce this limit (previously repeater-only). The command flood.max.advert is accepted as an alias for compatibility with upstream firmware.
v1.15.dev_0531 # 2 months ago · 2026-05-31 02:29 UTC

View release ↗
v1.15_0531
- Full support for Heltec T096 — companion, repeater, and room server
  
  The Heltec T096 is now fully supported across all node types. The hardware is an nRF52840-based board with an SX1262 radio, KCT8103L FEM, UC6580 GPS, and a 0.96" 160×80 color TFT display (ST7735S).
  
  The complete companion UI — Quick Send, Contacts, Settings, GPS, Saved Locations, GPS Trace, and message preview — runs on the color TFT.
  
  Differences from other supported boards:
  - Color TFT display. All companion pages render in color on the 160×80 ST7735S — unlike other supported boards which use a monochrome OLED.
  - Brightness control. A Brightness item in the Settings page adjusts the TFT backlight intensity: 25 → 50 → 75 → 100. Setting is saved to flash.
  - KCT8103L FEM — same as Heltec V4.3. set radio.rxgain on / off works identically.
  - UC6580 GPS. gps.interval works the same as on Heltec V4. Constellation selection (gps.mode) uses a different set of options:
    
    Value Constellations
    
    1 GPS L1 only
    
    2 All-system L1 (GPS+BDS+GLO+GAL)
    
    3 All-system + QZSS dual-band (default)
- AGC auto-reset improvements (all node types).
  
  Coordination between AGC auto-reset and channel busy detection has been improved. While the noise floor baseline is being re-established after a reset, channel sensing falls back to hardware CAD only.
- Fix: excessive flash writes on nRF52 Companion (T096, RAK4631).
  
  Each received advertisement previously triggered an immediate flash write — both to the advert blob store and to the contact list. In areas with high advert traffic this caused unnecessary flash wear, and a malicious node spamming adverts could wear out ExtraFS in hours. Advert blobs are now buffered in RAM and flushed to flash at most once every 10 minutes. Auto-discovered contacts use the same 10-minute pattern instead of a short debounce timer.

Value	Constellations
`1`	GPS L1 only
`2`	All-system L1 (GPS+BDS+GLO+GAL)
`3`	All-system + QZSS dual-band (default)

v1.15.dev_0524 # 2 months ago · 2026-05-24 01:53 UTC

v1.15_0524

Fix: radio deafness recovery in noisy environments (all node types).

When strong in-band interference causes the SX1262 AGC to become overwhelmed, the radio can go deaf — severely degraded in receive sensitivity. The firmware now detects this condition automatically and triggers an immediate hardware recalibration, restoring sensitivity without waiting for the scheduled agc.reset.interval. The agc.reset.interval setting remains available but is now unnecessary.

Two new commands let you monitor and reset the AGC reset counter:

Command Effect

get agc.resets Show how many times the AGC has been auto-reset since boot or last clear

clear agc.resets Reset the counter to zero

Real-world validation: A repeater installed near a periodic in-band interference source (confirmed via RTL-SDR) accumulated 918 auto-resets over 8.5 hours (~1.8/min), matching the observed interference sweep cycle. A second repeater at a clean location recorded 0 resets over the same period, confirming no false positives. Without this feature, the first repeater was unreachable remotely due to persistent deafness.

Command	Effect
`get agc.resets`	Show how many times the AGC has been auto-reset since boot or last `clear`
`clear agc.resets`	Reset the counter to zero

GPS update interval configurable at runtime on Heltec V4 (all node types).

A new gps.interval setting controls the sleep time between GPS position updates. After each fix, GPS powers down for the configured interval, then wakes and acquires a new fix. Set it to 0 to keep GPS always on. Default is 10 seconds.

Available on Companion via TerminalCLI and on Repeater / Room Server via the Command Line:

Command	Effect
`get gps.interval`	Show current interval (`always on` if 0)
`set gps.interval 0`	GPS always on — maximum accuracy, highest power draw
`set gps.interval 30`	GPS sleeps 30s after each fix, then re-acquires
`set gps.interval 300`	GPS sleeps 5 minutes after each fix

Setting is saved to flash and takes effect immediately — no reboot needed.

GPS constellation selection for L78K on Heltec V4 (gps.mode) (all node types).

Choose which satellite constellations the L78K module tracks. Average current draw is essentially the same across all configurations in duty cycle mode with gps.interval greater than 10 (~23 mA mean current measured on Heltec V4.3 Companion with gps.mode = 4 and gps.interval = 10). Leave at the default 4 for the most robust fix; adjust only if you have a specific coverage reason.

Value Constellations

1 GPS only

2 GPS + BeiDou

3 GPS + GLONASS

4 GPS + BeiDou + GLONASS (default)

Available on Companion via TerminalCLI and on Repeater / Room Server via the Command Line:

Command Effect

get gps.mode Show current constellation selection

set gps.mode 4 GPS + BeiDou + GLONASS (default)

set gps.mode 1 GPS only

Setting is saved to flash. Change takes effect on next GPS on.
Companion: GPS screen shows interval and constellation when GPS is off.

When GPS is off, the GPS page now shows the configured update interval (intv) and constellation selection (mode, Heltec V4 only), so you can verify settings before enabling GPS.

Value	Constellations
`1`	GPS only
`2`	GPS + BeiDou
`3`	GPS + GLONASS
`4`	GPS + BeiDou + GLONASS (default)

Command	Effect
`get gps.mode`	Show current constellation selection
`set gps.mode 4`	GPS + BeiDou + GLONASS (default)
`set gps.mode 1`	GPS only

v1.15.dev_0517 # 3 months ago · 2026-05-17 03:19 UTC

View release ↗

v1.15_0517

Companion: per-channel outgoing hop limit (ch.hops).

Limit how far your outgoing messages travel on a specific channel, without affecting any other channel or any other node in the network. Useful for keeping a private or local-area channel confined to a small radius — for example, a home-to-nearby-relay link — without touching the rest of the city mesh.

Configure via TerminalCLI:

Command	Effect
`set ch.hops <channel> <N>`	Limit outgoing messages on `<channel>` to at most N hops
`set ch.hops <channel> off`	Remove the limit
`get ch.hops <channel>`	Show current limit
`ch.hops status`	List all channels with an active limit
`ch.hops clear`	Remove all limits

set ch.hops Public 2         # Public channel messages travel at most 2 hops
set ch.hops My Local Net 3   # My Local Net channel travel at most 3 hops
set ch.hops Public off       # remove the limit
ch.hops status

The limit applies to your outgoing messages only — other nodes sending on the same channel are unaffected. No repeater configuration or network coordination required.

The repeater's group.hops.max algorithm has been updated to correctly account for sender-side pre-fill, so ch.hops and group.hops.max work together without conflict — update repeater firmware to get full compatibility.

Settings are stored in flash and persist after reboot.

Companion: toggle RxGain directly from the Radio screen.

Long press on the Radio page cycles through RxGain modes (OFF → ON → Auto) and shows a popup confirming the new mode. The current mode is now also displayed on the Radio page itself (RxG: OFF / RxG: ON / RxG: Auto), so you can check it at a glance without going into Settings. (Auto is available on Heltec V4.2 only.)
Fix: noise floor stuck at -120 in noisy environments (all node types)

In environments with strong in-band interference, the noise floor could remain at -120 dBm for a long time instead of updating to reflect actual conditions. Fixed.

v1.15.dev_0510 # 3 months ago · 2026-05-10 02:47 UTC

View release ↗

v1.15_0510

Repeater: per-type relay hop cap (advert.hops.max / group.hops.max).

Two new settings let you independently limit how far advertisement packets and group messages are relayed across the mesh, without affecting direct messages, ACKs, or path discovery.

Setting	Controls	Default
`advert.hops.max`	Max hops to relay node advertisement (ADVERT) packets	= `flood.max`
`group.hops.max`	Max hops to relay group messages (GRP_TXT / GRP_DATA)	= `flood.max`

These are repeater-only settings. Configure via the Command Line in the MeshCore App:

set advert.hops.max 3    # relay adverts at most 3 hops from sender
set group.hops.max 5     # relay group messages at most 5 hops
get advert.hops.max
get group.hops.max

Setting either value to 0 completely suppresses that packet type — no relay at all, while everything else (DM, ACK, path) continues to work normally.

Why this matters — advert storm reduction:

Each repeater periodically broadcasts an advertisement that every other repeater in range relays, up to flood.max times (default 64). In a network of 35 repeaters and 35 companions, advert traffic alone consumes roughly 4% of airtime. Limiting to 3 hops brings that down to under 0.5% — a 7× reduction — with no loss of communication capability.

No coordination required. Each repeater applies its own cap independently. You do not need all repeaters to agree on the same value — even a partial deployment reduces airtime. No region configuration, no App UI changes needed.

Recommended profiles:

Profile	`advert.hops.max`	`group.hops.max`	Airtime (35R / 35C)	Use case
Default	= `flood.max`	= `flood.max`	~4%	No change
Optimized	3	5	~0.5%	Most deployments
DM-focused	0	3	~0.2%	Prioritise direct messages
EU compliance	0	3	~0.2%	Large EU networks (legal requirement)

Relationship with flood.max and path hash size: flood.max is the master hop cap for all flood payloads. Its default of 64 is calibrated for 1-byte path hash mode. With larger hashes the packet fills up sooner — 2-byte hash caps at 32 hops, 3-byte hash caps at 21 hops — so flood.max is typically set to match. advert.hops.max and group.hops.max are automatically clamped to flood.max and work correctly with all hash sizes. If you want to suppress adverts entirely while keeping everything else unrestricted, set advert.hops.max 0 — leave flood.max untouched.

Repeater: combining hop caps with region scope for full community isolation.

advert.hops.max and group.hops.max work standalone — no coordination needed. For operators who also want to restrict which community's group messages get relayed, combine them with region rules and the companion's scope settings:
1. Each companion sets a region scope — either per-channel via the burger menu, or globally via Settings → Experimental → Default Region Scope. All outgoing flood packets (including DM path discovery) are tagged with the community name.
2. Each repeater: denyf * + allowf <community> — only relay community-tagged traffic.
3. Add set advert.hops.max 0 to also suppress advert relay.
With a global Default Region Scope, DM path discovery is tagged and passes through denyf * repeaters — direct messaging works normally inside the community.

Default Region Scope is in the App's Experimental Settings and is opt-in. Per-channel scope (burger menu) only tags group messages for that channel, not advertisements or DM path discovery.
Companion: GPS coordinate display formats — DD / UTM / MGRS.

A new Pos. Format item in the Settings page lets you choose how GPS coordinates are shown on the GPS page, GPS Trace screen, and Quick Send status bar.

Format Example

D

…

Format	Example
D
…

v1.15.dev_0427 # Pre-release 3 months ago · 2026-04-27 09:32 UTC

View release ↗

v1.15_0427

Repeater: per-type relay hop cap (advert.hops.max / group.hops.max).

Two new settings let you independently limit how far advertisement packets and group messages are relayed across the mesh, without affecting direct messages, ACKs, or path discovery.

Setting	Controls	Default
`advert.hops.max`	Max hops to relay node advertisement (ADVERT) packets	64 (unchanged)
`group.hops.max`	Max hops to relay group messages (GRP_TXT / GRP_DATA)	64 (unchanged)

These are repeater-only settings. Configure via the Command Line in the MeshCore App:

set advert.hops.max 3    # relay adverts at most 3 hops from sender
set group.hops.max 5     # relay group messages at most 5 hops
get advert.hops.max
get group.hops.max

Setting either value to 0 completely suppresses that packet type — no relay at all, while everything else (DM, ACK, path) continues to work normally.

Why this matters — advert storm reduction:

Recommended profiles:

Profile	`advert.hops.max`	`group.hops.max`	Airtime (35R / 35C)	Use case
Default	64	64	~4%	No change
Optimized	3	5	~0.5%	Most deployments
DM-focused	0	3	~0.2%	Prioritise direct messages
EU compliance	0	3	~0.2%	Large EU networks (legal requirement)

Relationship with flood.max: flood.max (long-standing setting, default 64) is the master hop cap for all flood payloads — DMs on first send, path discovery, group messages, adverts. It applies regardless of payload type. advert.hops.max and group.hops.max add finer per-type control on top: they can only be equal to or stricter than flood.max, never looser. Setting flood.max lower automatically clamps both values to match. If you want to suppress adverts entirely while keeping DMs unrestricted, lower advert.hops.max to 0 — leave flood.max untouched.

v1.15.dev_0426 # 3 months ago · 2026-04-26 04:49 UTC

View release ↗
v1.15_0426
- Companion: redesigned message preview.
  
  Messages are now grouped by sender or channel so you can read a conversation in one place instead of hunting through a mixed list.
  
  From the group list you can scroll back through older messages from any sender or channel, including ones you've already read. Long press a group to open it.
  
  When new messages arrive, you go straight to a new messages view that shows only the unread ones — from all senders and channels — one by one. Once you've read them all, a single click takes you home.
  
  Long messages scroll one full page at a time with no overlap. Small arrows (▲ / ▼) appear at the corner of the screen to let you know there is more content above or below.
- Companion: reply directly from message preview.
  
  While reading any message, long press to open the menu. A new Reply option lets you send a preset message back without leaving the screen:
  - If the message came from a contact, the reply goes to that contact as a private direct message.
  - If the message came from a channel (Public, #SOS, or any other), the reply goes back to that same channel.
  Note: The Quick Send page always sends to the Public channel. Use Reply from the message preview when you want to respond to a specific contact or a non-Public channel.
- Companion: Contacts page and direct messaging.
  
  A new Contacts page sits between Quick Send and Saved Locations. Long press it to open the contact list, only chat-capable nodes are listed (repeaters, room servers and sensors are excluded — they cannot receive direct messages). Select a contact and long press to send them a direct message using your Quick Send presets.
- Companion: configurable Screen Off timeout in Settings.
  
  A new Screen Off item in the Settings page lets you choose how long the display stays on after the last button press: 15s → 3min → Never. Setting is saved to flash and persists after reboot.
- Companion: Flip Screen setting in Settings.
  
  A new Flip Screen toggle in the Settings page rotates the display 180°. Setting is saved to flash and persists after reboot.
- fix bugs
v1.15.dev_0419 # 4 months ago · 2026-04-19 04:50 UTC

View release ↗

bump to 1.15.dev
v1.14_0417 # 2 variants 4 months ago · 2026-04-17 13:57 UTC

RAK4631 low power RAK4631-low-power-v1.14_0417 View ↗
XIAO S3 Wio low power XIAO-S3-Wio-low-power-v1.14_0417 View ↗
v1.14_0417
- Hybrid RSSI + hardware CAD channel sensing (all node types).
  
  isChannelActive() now performs a two-stage check before transmitting:
  1. RSSI check (fast, single SPI register read) — defers if signal is above noise_floor + int.thresh.
  2. Hardware CAD (scanChannel()) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).
  RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.
  
  int.thresh=0 disables both RSSI and CAD. int.thresh=1 enables full hybrid at maximum sensitivity.
  
  On repeaters (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, txdelay=2, 100 messages):
  - Repeaters close together / strong inter-repeater signal: RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → 9% collision rate.
  - Spread-out repeaters, some pairs below noise floor: RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD 8% vs RSSI-only 17%.
  - Many hidden node pairs: neither RSSI nor CAD helps. Only txdelay reduces the floor. Example: ~20–24% regardless of sensing method.
  On companions (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):
  - int.thresh=3: 53–64% of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)
  - int.thresh=0 (no sensing): 0–1% relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back
  Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.
- Companion: get/set txdelay, get/set direct.txdelay, get/set int.thresh via TerminalCLI.
  
  Relay timing and interference threshold are now configurable without reflashing.
- Companion: "Heard N Repeats" alert after Quick Send.
  
  After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. "Heard 3 Repeats"). The counter updates in real time as each relay is heard.
- Companion: local time and date on the display.
  
  All pages now show the current time (HH:MM) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. 14 Apr 2026).
  
  Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via TerminalCLI:
```
set tz.offset 7    # UTC+7
set tz.offset -5   # UTC-5
get tz.offset
```
  Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.
- Companion: Metric / Imperial units.
  
  A new Units item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.
  
  Display Metric Imperial
  
  GPS Trace distance 150m / 1.2km 492ft / 0.7mi
  
  GPS page altitude 245m 804ft
  
  Home page date 14 Apr 2026 Apr 14 2026
- Companion: GPS Privacy mode.
  
  A new GPS Privacy item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me …

Display	Metric	Imperial
GPS Trace distance	`150m` / `1.2km`	`492ft` / `0.7mi`
GPS page altitude	`245m`	`804ft`
Home page date	`14 Apr 2026`	`Apr 14 2026`

MeshCore Low-Power · Releases

v1.16_0802

v1.16_0726

v1.16_0719

v1.16_0714

v1.16_0712

v1.16_0705

v1.16_0706 pre-release for e-ink devices

v1.16_0628

v1.16_0621

v1.16_0614

v1.16_0611 pre-release for Heltec E213, Wireless Paper and E290

v1.16_0607

v1.15_0531

v1.15_0524

v1.15_0517

v1.15_0510

v1.15_0427

v1.15_0426

v1.14_0417