Meshtastic Firmware 2.7.18.fb3bf78 Alpha: What's New

Meshtastic alpha 2.7.18.fb3bf78 is out. It’s a precursor to the next stable release, so this is the build for people who want to test the new features and are comfortable reporting issues back upstream.

We haven’t flashed this to our production nodes yet. The notes below come straight from the release changelog. If you’re running this in the field, we’d love to hear what’s holding up and what isn’t.

What’s New

Multi-message storage. Nodes can now batch multiple messages together before transmitting, which reduces the number of discrete packets hitting the channel. For congested meshes, this should shave off some of the chatter.

API port now configurable from the config file. Custom applications built against the Meshtastic API can now pin the port in config rather than relying on defaults. Useful if you’re running multiple services against the same device.

Rak3112 module support. The firmware now recognizes the Rak3112 as a build target. If you have one of these modules on a shelf waiting for official support, this is the release that unlocks it.

PMSA003I refactor and AQ telemetry update. Internal reorganization. Moving the PMSA003I air quality sensor to its own class makes the telemetry pipeline cleaner going forward. No user-visible impact unless you’re building against that sensor directly.

InkHUD joystick navigation for the Wio Tracker L1 e-ink. If you’re running a Seeed Wio Tracker L1 with an e-ink display, joystick input now drives the InkHUD UI. Cleaner standalone operation.

What to Test

If you flash this alpha, a few things worth watching:

• Does multi-message storage actually reduce repeat transmissions on your channel, or does it introduce delivery delays?
• Does API port reconfiguration survive reboots cleanly?
• Wio Tracker L1 users: does the joystick nav behave the way you’d expect it to, or are there rough edges?

The full changelog is on the Meshtastic GitHub releases page. Read it before flashing. Alpha builds aren’t meant for mission-critical nodes.

Who Should Flash This

If you run a dedicated test node or you have a spare device on the bench, this is the kind of release you pull down to help shake out regressions before they reach stable. The community feedback is what moves these fixes into the next stable release.

If your nodes are part of a live mesh your group depends on, wait for stable. Alpha means alpha.