Skip to content

Search guides, devices and posts

Back to MeshCore

MeshCore Web Flasher and Firmware Updates

MeshCore installs from a web page. Plug the board into a computer, open the flasher in Chrome or Edge, pick your device and role, and press the Flash! button. An update takes a few minutes and keeps your settings.

This guide covers the web flasher step by step, which role to pick, over-the-air updates for nRF52 and ESP32 boards, what an update keeps, and how to recover a flash that went wrong.

Checked October 2026 against MeshCore 1.18.0.

Current Firmware

MeshCore releases come out every month or two. Our release tracker lists each one and what changed. The flasher always offers the latest release, plus older ones in its version list.

How to check your current version

  • Companion: in the MeshCore app, open Settings (the gear icon) and scroll to Device Info at the bottom. It shows the Firmware Version and Firmware Date.
  • Repeater or room server: log in as admin in the app, open the Command Line tab and send ver. It replies with the version and build date. The same command works over USB in the flasher's Console.
  • From a computer: with meshcore-cli, meshcli -s /dev/ttyUSB0 ver prints the companion's version.

How to Use the MeshCore Web Flasher

The flasher at flasher.meshcore.io works in Chrome or Edge on a computer. It talks to the board through the browser's Web Serial API, which Safari doesn't have. You need a USB cable that carries data; many phone charging cables only carry power.

  1. Open the flasher

    Open flasher.meshcore.io in Chrome or Edge on a computer and plug the device in with a USB data cable.

  2. Choose your device

    Pick your board from the device list. Use the Filter box to search, and match the exact model and version printed on the board or box.

  3. Choose the role

    Pick Companion (Bluetooth or USB), Repeater, Room Server or another role. When updating, pick the role the device already runs.

  4. Don't erase for an update

    On ESP32 boards, leave Erase device unchecked when updating; on nRF52 boards, skip the Erase Flash button. A full erase deletes the node identity, so contacts will see it as a new node.

  5. Flash

    Choose the version, press Flash!, pick the serial port in the browser prompt and wait for Flashing complete!

Erase device: leave it off when updating

The flasher's own warning: don't do a full erase if you're simply updating, because it erases the device's MeshCore identity. Your node gets a new public key, and everyone who had you as a contact has to add you again. A repeater's admins would have to find it again too.

Tick Erase device only for a fresh start: a board coming from Meshtastic or other firmware, a corrupted install, or a device you're giving away. On an ESP32 board, an erase writes the full "merged" image, including the bootloader. A normal update writes only the MeshCore app.

nRF52 boards (RAK, T114, T1000-E)

The flasher shows Enter DFU mode and Erase Flash buttons. Erase Flash loads a small formatter that wipes all user data. For a clean install the order is Enter DFU mode, then Erase Flash, then the Flash! button.

Other buttons on the flasher

  • Custom Firmware: flash a file from your computer (.bin for ESP32, .zip for nRF52).
  • Repeater Setup: a page for configuring repeaters and room servers over USB.
  • Console: a serial terminal for CLI commands.
  • Download: the raw firmware files, for flashing with other tools.

Which Role to Flash

Each MeshCore role is its own firmware. The flasher only lists the roles built for the board you picked.

Companion: Bluetooth

Your personal radio, paired to the phone app. This is what most people flash first. In 1.18 the Bluetooth builds for some boards (Heltec V3 and V4, Heltec Wireless Paper, RAK3112, Xiao S3) can also join Wi-Fi, set up from the app's WiFi Settings.

Companion: USB

The same companion, but it connects over a USB cable instead. It has no Bluetooth. Use it with the desktop or web app, meshcore-cli, or a phone that supports USB.

Repeater

Relays traffic for everyone around it. No chat of its own, and no Bluetooth app connection. You manage it through a companion in the app or over USB. See repeater setup.

Room Server

A shared message board. People log in and catch up on posts they missed while offline. It doesn't relay other traffic, so it doesn't replace a repeater. See the room server guide.

On some boards you'll also see KISS Radio Modem (turns the radio into a modem for packet radio software over USB) and Ripple GUI (standalone firmware with its own screen interface, for devices like the T-Deck).

Downloading files by hand: release files are named after the board, role and version, for example Heltec_v3_companion_radio_ble-v1.18.0-81dbae5.bin. ESP32 releases come as a plain .bin (an update) and a -merged.bin (a full install with the bootloader). nRF52 releases come as a .zip (for DFU and OTA) and a .uf2 (for drag-and-drop).

MeshCore OTA Updates (Over the Air)

Over-the-air updates let you update a repeater on a mast without taking it down. How it works depends on the chip. Test it once on a node you can reach before relying on it for one you can't.

nRF52 boards: Bluetooth OTA

For RAK4631, Heltec T114, Xiao nRF52 and similar boards, using Nordic's free nRF Device Firmware Update app (Android and iPhone). You need to be within Bluetooth range of the board.

  1. On the flasher, download the .zip file for your board and role, and save it to your phone.
  2. In the MeshCore app, log in to the repeater as admin, open the Command Line tab and send start ota. It replies OK with its Bluetooth MAC address.
  3. In the DFU app's Settings, turn on Packet receipt notifications and set Number of Packets to 8 (10 also works on RAK). If the board doesn't show up later, turn on Force Scanning.
  4. Select the .zip, select the device, and tap Upload. It takes a few minutes.
  5. When it finishes, log in again and check ver and clock. Run clock sync if the time is wrong.

Companions on firmware 1.15 or newer can update the same way, without start ota: the update service runs alongside the normal Bluetooth connection.

If the DFU app keeps failing at "Enabling Bootloader", toggle Bluetooth or reboot your phone. If that doesn't work, forget the board in your phone's Bluetooth settings and pair it again through the DFU app.

Install the OTAFIX bootloader first

MeshCore strongly recommends the OTAFIX bootloader for nRF52 boards. It drops back into update mode when an update fails, instead of leaving a node you have to climb up to. Some boards' factory bootloaders can't do OTA at all, and the flasher warns about those. To install it, double-press reset so the board appears as a USB drive, drag the OTAFIX update-*.uf2 file onto it, and check that INFO_UF2.TXT on the drive mentions OTAFIX. get bootloader.ver shows the version on a repeater.

ESP32 repeaters and room servers: Wi-Fi OTA

For Heltec V3 and V4, Station G2, T-Beam and other ESP32 boards running repeater or room server firmware.

  1. On the flasher, download the plain .bin for your board and role (not the -merged one).
  2. Log in to the repeater as admin and send start ota. It replies Started: http://192.168.4.1/update.
  3. Within Wi-Fi range of the repeater, join the open hotspot named MeshCore-OTA from a phone or laptop.
  4. Open http://192.168.4.1/update in a browser and upload the .bin.

ESP32 companions can't update over the air. The Wi-Fi update only exists in firmware that has an admin password (repeaters, room servers and sensors). Update an ESP32 companion over USB with the flasher.

What an Update Keeps, and How to Back Up

A normal update (no erase) keeps your settings, contacts, channels and identity. Back up anyway; it takes a minute.

Companion backup

In the app's Settings, tap Export Config, choose Select All and confirm. That saves your node's configuration to a file. Import Config restores it after a reset or erase.

Repeater identity backup

Over USB only, get prv.key prints the repeater's private key. Store it somewhere safe. After an erase, set prv.key <key> and a reboot bring the same identity back. Anyone with that key can impersonate the repeater, so treat it like a password.

Release changes that affect upgraded nodes

  • 1.17 moved settings to a new file format and converts the old one automatically on first boot. The old file is left in place, so you can still go back to 1.16.
  • Receive gain: radio.rxgain defaults to on, but a node upgraded to 1.14.1 without an erase was left with it off. On an older repeater, check get radio.rxgain and run set radio.rxgain on if needed.
  • 1.16 added extended (6-byte) acknowledgements, and its release notes say repeaters have to be updated first.
  • 1.18 lets companions accept CLI commands from contacts you allow. Only grant that to people you trust.

Troubleshooting a Failed Flash

The flasher doesn't see the device

Most often it's the cable: many USB cables only carry power. Try one you know moves data, and plug straight into the computer rather than a hub. Make sure no other app (the MeshCore desktop app, a serial monitor, another browser tab) has the port open.

"Failed to open serial port" on Linux

The full error is NetworkError: Failed to execute 'open' on 'SerialPort': Failed to open serial port. Your user doesn't have access to the USB port. Grant it, then try again:

sudo setfacl -m u:$USER:rw /dev/ttyUSB0

The device won't boot after flashing

Check that you picked the exact board. Similar boards need different builds (Heltec V3 and V4, for example, or the Wio Tracker L1 Pro, which is nRF52, and the L2 Pro, which is ESP32). Flash again with the right one. If an update over the old install still won't boot, do a clean install with Erase device ticked. That gives the node a new identity unless you restore a repeater's key afterward.

Recovering an nRF52 board

Double-press the reset button within half a second. The board shows up as a USB drive, which means the bootloader is running even if MeshCore isn't. Drag the board's .uf2 file from the flasher's Download menu onto the drive, or use the flasher's Enter DFU mode and Erase Flash buttons for a full wipe. With the OTAFIX bootloader, a failed OTA update falls back to update mode on its own, so you can retry from the DFU app.

Rescue mode when you can't connect

Since 1.7.0, boards with a user button (some RAK boards, the T114) have a CLI rescue mode. Hold the user button within 8 seconds of boot, then open the flasher's Console to send commands, such as setting a new six-digit Bluetooth PIN with set pin followed by the PIN.

The phone won't reconnect after an update

An erase clears the board's Bluetooth pairing, but your phone still remembers the old one. Forget the device in your phone's Bluetooth settings, then connect again from the app and enter the PIN. More connection errors are covered in our MeshCore app error guide.

Flashing Without a Browser

On a Raspberry Pi or any computer without Chrome, download the file from the flasher's Download menu and use the chip vendor's tool. These are the commands from the MeshCore FAQ:

ESP32 (esptool), update with the plain .bin:

esptool.py -p /dev/ttyUSB0 --chip esp32-s3 write_flash 0x10000 firmware.bin

or a full install with the -merged.bin:

esptool.py -p /dev/ttyUSB0 --chip esp32-s3 write_flash 0x00000 firmware-merged.bin

nRF52 (adafruit-nrfutil), with the .zip:

adafruit-nrfutil --verbose dfu serial --package firmware.zip -p /dev/ttyACM0 -b 115200 --singlebank --touch 1200

The --chip esp32-s3 value fits S3 boards like the Heltec V3 and V4. Use your board's chip if it's different. meshcore-cli manages a running node but doesn't flash firmware. More detail is in the MeshCore FAQ.

MeshCore Firmware FAQ

What is the MeshCore web flasher?

It is the official browser tool at flasher.meshcore.io. It installs MeshCore over USB from Chrome or Edge on a computer, with no software to install. It lists every supported board, every role (companion, repeater, room server and more) and every release, and it can also open a serial console and a repeater setup page.

Does updating MeshCore erase my settings or contacts?

Not if you skip the erase (the Erase device checkbox on ESP32 boards, the Erase Flash button on nRF52). A normal update keeps your settings, contacts and identity. A full erase wipes the identity, so other nodes see a new node. Export your settings from the app first anyway, so you can restore them if anything goes wrong.

Can I update MeshCore over the air?

Yes, on nRF52 boards and on ESP32 repeaters and room servers. nRF52 boards update over Bluetooth with Nordic's nRF Device Firmware Update app (companions need firmware 1.15 or newer). ESP32 repeaters and room servers start a Wi-Fi hotspot with the start ota command and take the file in a browser. ESP32 companions have no OTA, so update them over USB.

Which browsers work with the MeshCore flasher?

Chrome and Edge on a desktop or laptop. The flasher uses the Web Serial API, which Safari does not support. On Linux, if flashing fails with "Failed to open serial port", give your user access to the port with: sudo setfacl -m u:$USER:rw /dev/ttyUSB0.

Companion Bluetooth or Companion USB: which should I flash?

Flash Companion Bluetooth to use the phone app. The USB build has no Bluetooth and is for connecting to a computer or the app over a cable. If you pick the wrong one, flash the other; it is the same process.

Do all nodes need the same MeshCore version?

No, but keep repeaters current. Repeaters older than 1.14 drop packets that use the larger 2- and 3-byte path hashes, and the 1.16 release notes say to update repeaters before companions. Running one release behind on a companion is fine.

Can I go back from MeshCore to Meshtastic?

Yes. Both run on the same LoRa boards. Flash Meshtastic with its own web flasher at flasher.meshtastic.org and you can switch back later. Your MeshCore identity and contacts do not carry over to Meshtastic.