🔧 Meshtastic Firmware v2.8.0.7239fe8 — Meshtastic Firmware 2.8.0.7239fe8 Alpha

Meshtastic has published v2.8.0.7239fe8 Alpha, a major pre-release with several protocol, privacy, and UI changes that Oklahoma mesh operators should review carefully before upgrading.

Important warning for Oklahoma operators: new US nodes now default to LongTurbo instead of LongFast. Those presets cannot hear each other. If you’re joining an existing Oklahoma mesh that is still on LongFast, switch the preset back after flashing or you may think the network is dead when it’s just speaking the wrong dialect.

Also important: if you hit a boot loop or repeated crashes after upgrading, Meshtastic recommends doing a full erase and flash. Export your config first if you need to preserve settings.

Why this release matters

• New packet signing with XEdDSA and broader mesh hardening
• Ground-up NodeDB and traffic management redesign for busy meshes
• Telemetry and position broadcasts are now opt-in instead of always on
• New LoRa region and preset allocation changes, including ham-oriented carve-outs
• Privacy changes that clamp public position precision more aggressively
• UI improvements across BaseUI, InkHUD, touch support, maps, and TFT devices

What Oklahoma operators should watch

• Preset mismatch risk: confirm LongFast vs LongTurbo before troubleshooting missing nodes
• Location sharing changed: telemetry and position are no longer on by default, so some nodes may appear quieter after upgrade
• Mesh behavior changed: the new traffic handling and NodeDB internals may improve dense-node reliability, but early adopters should expect a little weirdness because it is still an alpha
• Upgrade carefully on critical routers: backbone, relay, and hilltop nodes should probably wait for more field reports unless you like surprise debugging sessions

Release links

• GitHub release page and release notes
• ESP32 firmware download
• nRF52840 firmware download
• Meshtastic Web Flasher

The upstream release notes are extensive and worth reading in full before you upgrade. This is not a tiny bugfix build; it is a significant pre-release with behavior changes that can directly affect interoperability and node visibility.