3 min read meshtastic

How to Update Your Meshtastic Firmware (and Why You Should)

Old Meshtastic firmware breaks direct messages and misses security fixes. Here's how to check your version and update, by device type.
Close-up of a teal circuit board showing a u-blox GPS radio module with STATUS, GPS, and RADIO labels in the silkscreen
Photo: M2R / CC BY-SA 2.0

Firmware updates are easy to skip. The node is running, it's on the map, messages are getting through. Why touch it?

Here's why: if your node is running firmware older than 2.5, direct messages from newer nodes fail silently. Firmware 2.7.15, released November 2025, removed legacy unencrypted DMs entirely. A node on 2.4 or earlier can no longer exchange direct messages with anyone who has updated. It can still relay traffic and use channels, but one-to-one messaging is broken until you update.

That's the current live consequence. There are also ongoing bug fixes, new hardware support, and security improvements that accumulate across releases. Running firmware from 2024 on a 2026 network is like running a browser from 2024: it mostly works until it doesn't.

Check your current version

In the Meshtastic app, tap your node name to open node details. The firmware version is listed there. On Android you can also find it under Settings > About. If you're on anything below 2.5, update now. If you're on 2.5 to 2.6, updating is still worth doing. Current release is 2.7.x.

How to update: ESP32 devices

ESP32-based hardware (Heltec V3, T-Beam, T-Deck, most budget nodes) updates via the web flasher.

  1. Connect your node to your computer with a USB data cable.
  2. Open flasher.meshtastic.org in Chrome or Edge. Firefox and Safari don't support Web Serial.
  3. The flasher detects your device automatically. Select your firmware version and flash.

The web flasher preserves your settings by default. If you want a clean slate, there's a Full Erase option before flashing. Use it if you're troubleshooting or if the update instructions for your firmware version recommend it. The 2.7.15 release notes specifically warned that some devices needed a full erase due to BLE pairing changes.

After a full erase you'll need to reconfigure everything from scratch: node name, channels, MQTT settings, position config. Export your config first if you can (see below).

How to update: nRF52 devices

nRF52-based hardware (RAK4631, T-Echo, Heltec T114) uses a drag-and-drop method that's simpler than it sounds.

  1. Download the firmware for your device from meshtastic.org/downloads. You want the .uf2 file.
  2. Connect your node via USB while double-tapping the reset button to enter bootloader mode. The device appears as a USB drive named something like RAK4631.
  3. Drag the .uf2 file onto that drive. The node reboots and comes up on the new firmware.

Settings survive this process on most nRF52 devices. Check your channels and MQTT config after updating to confirm.

nRF52 devices also support Over-the-Air (OTA) updates over Bluetooth, which is useful for nodes that are mounted somewhere inconvenient. Use it only when USB isn't an option. Bluetooth firmware transfer is significantly more failure-prone than USB: a dropped connection, a screen timeout, or a low battery on either end can leave the device in a non-working state that requires USB recovery to fix. If OTA is your only option, the Meshtastic app has built-in support for most RAK devices under Settings > Firmware Update. Plug your phone in, disable auto-lock, keep the app in the foreground, and don't touch anything until the node reboots on its own. If the transfer fails repeatedly, reduce the packet size in the OTA settings to give the Bluetooth link more room to recover between chunks.

Before you update

Export your configuration. In the Android app: Settings > Export Config. This saves a file with your channels, radio settings, and module config. After updating, you can import it back rather than re-configuring manually.

Write down your channel PSKs separately. The export file contains them, but having them on paper means you can reconfigure even if the import fails. If you're on NEPAMesh's MQTT server, note your server address, username, and password from Settings > MQTT Module before flashing or just refer to the MQTT setup post.

After you update

Check the basics: node name is correct, channels are intact, MQTT is connecting, position is reporting. On Android you may need to re-pair Bluetooth after a full erase. Forget the device in your phone's Bluetooth settings and pair fresh.

Send a direct message to another node to confirm PKI DMs are working. If the recipient is also on current firmware, you should see a lock icon indicating the DM used PKC encryption rather than channel encryption.

Keep your app updated too. The Meshtastic Android and iOS apps track firmware releases closely. Some features in newer firmware require a matching app version to configure.

NEPAMesh is a community Meshtastic network covering Northeastern Pennsylvania's Wyoming Valley. Live map at map.nepamesh.com. Questions in the Discord.

Meshtastic is a registered trademark of Meshtastic LLC. No warranty is provided. Use at your own risk. This post is not endorsed by or affiliated with Meshtastic LLC.

You might also like...

10
Aug
The NEPAMesh live map showing Meshtastic node markers scattered across the Wyoming Valley region of Northeastern Pennsylvania.

NEPAMesh's Four Dashboards, Explained: Map, View, Monitor, and Propagation

NEPAMesh runs four Meshtastic dashboards, and each one answers a different question. Here's a plain English walkthrough of what each shows and how to read it.
7 min read
07
Aug
The silhouette of a jet airliner seen head-on against a sunset sky, with its contrail glowing orange in the last light.

July Follow-Up: What's New in MeshShadow

A passenger jet exposed a bug in NEPAMesh's node count. Here is the fix, plus what else is new in MeshShadow this month: proactive router health warnings and a way to claim your own node before it goes dark.
7 min read
01
Aug
A self-supporting amateur radio tower with antennas mounted on a mountain ridge at over 4,000 feet elevation, similar to the ridge-top router sites NEPAMesh depends on for coverage.

July on the Mesh: A Coverage Drop, a Silent Router, and Numbers That Don't Agree

A cat knocked loose an antenna connection at BMBF, and we thought that solved it. It didn't. Two routers are still missing, and the mystery is still open.
5 min read
30
Jul
Polar diagram comparing vertical radiation patterns of quarter-wave, half-wave, and 0.625-wavelength monopole antennas, showing longer elements flattening toward the horizon.

Antenna Gain vs. Takeoff Angle: Why Bigger Isn't Always Better in NEPA's Hills

A 9 dBi collinear sounds like a straight upgrade over a 2 dBi dipole, but in NEPAMesh's ridge-and-valley terrain it can make your node hear less, not more. Takeoff angle decides which antenna actually helps.
4 min read
25
Jul
Assortment of battery types on a workbench: lead-acid 12V 18Ah, 12V 7Ah, 18650 lithium cells, LiPo packs, and a small 3.7V LiPo

How Long Will Your Meshtastic Node Last on Battery?

The biggest factor in Meshtastic battery life isn't your battery size. It's your chip platform. Here's what the numbers actually look like.
4 min read