Set up your first MeshCore node
Guide · updated July 2026
From a bare board to messaging on the mesh in about 15 minutes. This covers a companion node — the kind you pair to your phone. (Setting up a repeater is a separate, more involved job — that’s a guide of its own.)
Before you start
- A supported LoRa board — not sure which? Pick your hardware below breaks down the common companion boards. A Heltec V3 is the cheap, easy default.
- The matching antenna for your band, plus a USB cable.
- A phone for the companion app (Android or iOS — desktop/web also work).
- About 15 minutes.
Antenna first, always. Screw the antenna onto the board before you power it up. Transmitting without one can damage the radio.
Pick your hardware
Any supported LoRa board gets you on the mesh — here’s how the common companion boards differ, and which to grab first.
Two questions decide almost everything. First, which chip: nearly every companion board is either an ESP32-S3 or an nRF52840. They run the same Semtech LoRa radio (an SX1262 on most boards), so range comes down to your antenna and where you mount it — not the chip. What differs is power: an ESP32 board is cheap and easy but thirsty — happy on USB, weak on a small battery. An nRF52840 board sips power — the one to pick for real battery life or solar.
Second, screen or no screen. A “companion” node is normally just the radio — your phone is its screen and keyboard, paired over Bluetooth. That’s every board below except one: the LilyGO T-Deck has its own keyboard and screen and runs MeshCore’s on-device app, so it texts on the mesh with no phone at all.
| Board | Chip | Screen | GPS | Battery life | Best for |
|---|---|---|---|---|---|
| Heltec LoRa 32 V3 | ESP32-S3 | 0.96″ OLED (status) | – | Modest | Cheapest first node |
| LilyGO T-Deck Plus | ESP32-S3 | LCD + keyboard | ✓ | Charge daily | No phone needed |
| Seeed T1000-E | nRF52840 | – (LED) | ✓ | Excellent | Sealed pocket tracker |
| Heltec T114 | nRF52840 | Optional TFT | Optional | Very good | Tiny low-power node |
| RAK WisBlock (RAK4631) | nRF52840 | – | Add-on | Excellent | Modular; grows into a repeater |
| LilyGO T-Echo | nRF52840 | 1.54″ e-paper | ✓ | Very good | Finished e-paper handheld |
These six are common picks, not the whole list — the flasher supports dozens more (the tiny Seeed Xiao / Wio-SX1262, Station G2, RAK WisMesh and others). ESP32 boards flash over USB serial; the nRF52840 boards drag-and-drop a firmware file — the web flasher walks you through either.
Just tell me which to buy
- Cheapest way in — a Heltec V3. The most-documented board there is; you message through your phone. ~$20
- Smallest, with GPS — a Seeed T1000-E: a sealed, credit-card-sized tracker with built-in GPS. Nothing to assemble, no case to print. ~$40
- No phone, all-in-one — a LilyGO T-Deck Plus: keyboard, screen and GPS, texting on the mesh by itself. ~$70
- Best battery, or going further — an nRF52840 board like the RAK4631 or Heltec T114: low power for battery/solar, and the RAK grows into a repeater later. ~$30–40
Two things to get right when you buy. Order the 915 MHz (US) version — these boards also sell in 433/868 MHz for other regions, and the wrong band won’t reach anyone here (or be legal). And mind the generation: a Heltec “V3” and the newer “V4” both work — just know which you’re buying. Then match it with the right antenna and connector (many boards use a small u.FL/IPEX pigtail to SMA).
Five steps onto the mesh
-
Flash the Companion firmware
Open the MeshCore web flasher in Chrome or Edge. Plug your board in, pick the right port/board, choose the Companion role, then enter DFU, erase, and flash. No command line needed.
-
Pair the app over Bluetooth
Install the MeshCore companion app (Android, iOS, desktop, or web), and pair it with your freshly-flashed node over Bluetooth. Give the node a name while you’re in there.
-
Set your region
In the app, set the Region / Preset to “US (Recommended)”. That puts you on the right frequency (915 MHz) and channel so you’re legal and talking to everyone else.
-
Stay on 1-byte IDs (our convention)
You’ll see advice elsewhere to flip on 2-byte paths under Experimental Settings — skip that here. Our area standardizes on 1-byte companions and 3-byte repeaters, so leave your companion at the default 1-byte. Curious why bytes matter? See MeshCore IDs & avoiding collisions.
-
Send your first message
Tap a contact and send a test. New nodes and repeaters announce themselves with adverts that take a little while to propagate — patience is key. If you only ever see “Sent” (never delivered), move somewhere higher with fewer obstructions, or get within range of a repeater.
Back up your identity. Your node’s private key is its Public ID — a reset or full re-flash regenerates it. Once you’re set up, save a backup so you can restore it later. See MeshCore backup & key security.
Stuck? The #meshcore channel in the RF Lab Discord is full of people running these exact boards. Ask away.
You’re on the mesh — now what?
Watch your node and the rest of the local network light up on MeshMapper and CoreScope. Want to extend coverage rather than just use it? That’s a repeater — a headless node you mount up high, configured with 3-byte IDs in our area (here’s why). Ready to build one? Follow Set up a MeshCore repeater.
Tools & sources
Get on the mesh with us.
Flash it, pair it, and say hi in #meshcore.