Node IDs now follow public keys
Node numbers are derived from public key identity instead of the hardware MAC address. Maps, databases and MQTT tools should be checked for duplicated or changed node records after migration.
Mesh News • September 7, 2026
BIG CHANGES ARE HITTING BOTH MESHES.
Meshtastic 2.8 changes identity, privacy, traffic management and the default US preset. MeshCore 1.17 improves collision handling and adds support for more hardware. Here is what builders and community operators should know.
Reporting and release information credited throughout to the original project teams, developers and issue reporters.
Important: Meshtastic 2.8 is currently an alpha release. Test it on one noncritical device before considering it for permanent or remote infrastructure.
Meshtastic 2.8 changes the default US preset
New US nodes selecting their region for the first time now default to LongTurbo instead of LongFast. The two presets cannot communicate with each other. A freshly configured node may therefore look completely isolated until its preset is changed to match the local mesh.
Source: Meshtastic firmware team, Firmware 2.8.0 alpha release notes, released September 1, 2026.
This is much bigger than a normal firmware update
Position and telemetry become opt in
Position and telemetry broadcasts are disabled by default. Public mesh position precision is also more tightly controlled, which may change what maps and dashboards receive.
Traffic management is redesigned
Packet deduplication, rate limiting, role aware forwarding and variable hop limits are intended to improve performance on busy meshes.
Source: Meshtastic contributors, official 2.8 alpha changelog.
The first 2.8 build was revoked
The initial 2.8 release was withdrawn after LR1110 initialization problems appeared, including on freshly flashed SenseCAP T1000 E devices. The replacement is build 2.8.0.47db0e3, but it remains an alpha and should be treated accordingly.
Source: Meshtastic firmware maintainers, official firmware release history.
A mesh and MQTT position bug was reported and patched
A 2.8 issue could leave a stationary node showing a correct live GPS fix in its connected app while the mesh and MQTT continued receiving an older position. The problem was reported on September 5. A related fix was merged into the development branch on September 6 so failed or skipped position sends no longer consume the broadcast timing window. Builders should wait for that work to appear in a published build before assuming every 2.8 image includes it.
Reported by: @garthvh in issue #11748. Fix merged by: @caveman99 in pull request #11751.
Meshtastic Android is improving everyday messaging
Recent Android work includes swipe to reply, message reactions, per contact drafts, full timestamp options, node database export and clearer connection warnings. The September 7 snapshot is an automated debug build and is not intended for production use.
Source: Meshtastic Android contributors, official Android release notes.
MeshCore 1.17 targets real network performance
MeshCore 1.17 introduced major listen before talk and preamble detection changes intended to reduce packet collisions without the long lockups associated with hardware CAD. It also moved configuration storage to JSON and laid groundwork for companion devices supporting multiple interfaces such as BLE and USB.
Source: MeshCore team, official MeshCore 1.17.0 announcement, published August 9, 2026.
More hardware now has official MeshCore support
MeshCore 1.17 added support for the Elecrow ThinkNode M9 and M7, SenseCAP MeshTracker X1, Heltec V4 R8, Heltec RC32 and RAK Ethernet modules. That is especially useful for builders testing fixed infrastructure, Ethernet connected nodes and newer companion hardware.
Source: Individual contributors credited in the MeshCore 1.17.0 changelog.
MeshCore 1.17.1 fixes receive gain and device problems
The follow up release corrected FEM receive gain persistence and fixed a Heltec T096 transmit failure. Repeater administrators using FEM equipped hardware should verify both radio.fem.rxgain and radio.rxgain after updating.
Source: MeshCore team and credited contributors, official MeshCore 1.17.1 announcement, published August 14, 2026.
No Bars Club takeaway
Open the 2.8 survival guide →UPDATE ONE NODE. VERIFY EVERYTHING.
Before changing permanent infrastructure, back up the configuration, confirm the local preset, test map and MQTT behavior, and keep one known good node untouched.
Editorial and attribution note
No Bars Club independently summarized these developments for community education. No Bars Club did not create the cited firmware, discover the cited bug or author the cited fixes. Follow each source link for the complete original work and contributor history.