MeshCore firmware release image
MeshCore firmware release image Photo by MeshCore

MeshCore Firmware v1.15.0 Is Live (Plus Default Scope Notes)

by John Cornelison

MeshCore 1.15.0 is available now, with Default Scope support and several new device additions.

MeshCore Firmware Release Default Scope

MeshCore v1.15.0 Is Available

MeshCore firmware v1.15.0 is now available via the official flasher: https://flasher.meshcore.io/

This release includes the new Default Scope capability plus a wide set of protocol, radio, device, and stability updates.

Major Features

  • Default Scope support
  • Support for new GROUP_DATA (binary) packets
  • Radio rxgain now ON by default
  • Radio frequency range now supported down to 150 MHz
  • New CLI command: get|set dutycycle
  • nRF companion support for OTA updates

New and Added Devices

Grouped from the v1.15.0 release notes:

New Device Support

  • Heltec V4.3 support
  • Heltec nRF Tracker (T096) support
  • GAT562 Mesh EVB Pro support (repeater + room server)
  • Muzi Works R1 Neo support
  • GAT562 Watch support

Added Companion Support

  • Heltec Wireless Paper companion support added

Fixes and Reliability Improvements

  • GPS preference persistence fix
  • BME680 sensor initialization fix
  • Heltec Wireless Paper battery read fix
  • WiFi companion fixes for Heltec V4 and T-Beam 1W
  • Waveshare RP2040 RXEN fix
  • Xiao C3 bootloop fix

Default Scope: Why It Matters

The Default Scope feature (introduced with v1.15.0) helps meshes that rely on regional filtering and reduced un-scoped flood traffic.

Mobile App (Companion Nodes)

In MeshCore App v1.43.0, Experimental Settings include a default scope region option. When set, companion flood packets (like adverts and unknown-path DM/login/request traffic) are scoped to that region.

Group channel scope still overrides default scope when a channel-specific scope is set.

Repeater and Room Server

There is a new CLI command:

  • region default {name | <null>}

This sets or clears the default region and auto-creates the region if needed. It also performs an implicit region save.

For request/response behavior in v1.15.0:

  • If request scope can be resolved, the reply uses the same scope.
  • If request scope cannot be resolved, the reply is un-scoped.

This is intended to reduce lockout risk while admins transition scoped configurations.

Also Notable

region put ... now defaults newly created regions to allow flood, so admins usually do not need a follow-up region allowf ....

Official Sources