Meshtastic has published a new pre-release: v2.7.24.472b14c. This one looks worth tracking for Oklahoma operators because it lands a decent batch of radio, display, Wi-Fi, and device support fixes while we still haven’t seen a new stable in months.
Release name: Meshtastic Firmware 2.7.24.472b14c Alpha
Published: 2026-05-23T01:12:32Z
Type: Pre-release / alpha
What stands out
- New hardware and variant support, including ThinkNode M7, T-Echo-Card, and initial Station G3 support.
- Privacy and routing-adjacent fixes, including position precision handling and direct position packet clamping.
- Reliability improvements for Wi-Fi services, display geometry, heartbeat LED behavior, and battery/power logging.
- For Oklahoma mesh operators: anything that improves node stability, location privacy, and Wi-Fi/HTTP behavior is worth paying attention to on fixed nodes and test boxes.
Release highlights
Enhancements
- ThinkNode M7
- Implement rotating JSONL recorder for persistent logging
- Make power status logging less chatty and track battery presence transitions
- Add variantDefaultConfig and set eth_enabled to default true
- VSCode: Prepare for pioarduino transition
- Refactor virtual keyboard cell height for layout consistency
- Refactor position precision handling to honor explicit channel settings and prevent location leaks
Bug fixes and maintenance
- T-Echo-Card support
- Clamp direct position packets to channel precision (fixes #8640)
- Give ThinkNode-m4 a heartbeat
- Make heartbeat LED play nice with other LEDs
- Fix screen geometry update for SH1107 display
- Add initial support for Station G3 variant
- Fix WiFi TCP/HTTP services not starting without USB serial connected
- Enabled SX_LNA_EN by default
Dependencies
- Update NeoPixel to v1.15.5
- Update libch341-spi-userspace digest to 2e5ff75
Downloads
- GitHub release page
- Firmware manifest JSON
- ESP32-S3 devices
- nRF52840 devices
- ESP32 devices
- RP2040 devices
Operator note: This is still marked as a pre-release, so don’t blindly flash production backbone nodes just because GitHub got excited. Test on a spare node first, especially if you’re depending on stable routing across the Oklahoma mesh.