LowMesh

Devices Guide

The Devices page lists hardware LowMesh tracks—radios, MCUs, antennas, and features—so you can compare boards before you buy or flash.

How to read a device card

Each entry is built from a spec sheet (chipset, RF front-end, GNSS, display, etc.). Use it to answer:

  • Which firmware families are realistic? (Meshtastic® and MeshCore™ do not support identical sets.)
  • Which flash method applies? (ESP32 serial vs nRF52 UF2 vs RP2040 UF2.)
  • What range class can you expect? (Antenna, power, enclosure, and environment dominate real-world results.)

Specs are informational—always confirm against current upstream device support for the firmware you plan to run.

MCU families (what matters)

ESP32 (including S3 and variants)

  • Pros: Wi-Fi/BT radio for apps, large ecosystem, many off-the-shelf boards.
  • Flashing: Serial bootloader via USB-UART or integrated USB; see Flashing Guide.
  • Watch for: USB-UART vs native USB wiring, revision-specific pin maps, PSRAM requirements for some builds.

nRF52840 / nRF52 series

  • Pros: Low power, strong BLE stack, common in compact trackers and keyboards.
  • Flashing: Often UF2 or DFU; vendor tools may supplement the web flasher.
  • Watch for: SoftDevice/bootloader interactions; follow Meshtastic® or MeshCore™ guidance for your exact board.

RP2040

  • Pros: Simple UF2 drag-and-drop for many Meshtastic® targets.
  • Flashing: BOOTSEL USB drive workflow; see Flashing Guide.
  • Watch for: Wi-Fi is not native on RP2040—Wi-Fi boards add separate modules.

Radio and antennas

  • Frequency band must match your legal region and antenna.
  • Connector type (IPEX/U.FL vs SMA) and ground plane affect real range.
  • Higher TX power increases heat and battery drain; it does not fix a bad antenna match.

Power and deployment

  • USB is fine on the bench; field use needs battery chemistry, charging, and enclosure planning.
  • Solar setups require charge control and realistic duty cycle expectations.
  • Weatherproofing matters for condensation and corrosion—especially at antenna ports.

Choosing a device (practical checklist)

  1. Firmware goal – Meshtastic® community path vs MeshCore™ features.
  2. Form factor – handheld, vehicle, fixed repeater, or sensor node.
  3. GNSS – needed for position features; adds power draw.
  4. Display – useful for standalone use; impacts UI firmware choice (MeshCore GUI builds, etc.).
  5. Certification – regulatory markings depend on region, antenna, and modifications—do not assume hobby boards are certified for every use.

After you choose

  1. Purchase from Shop or a trusted retailer.
  2. LowMesh hardware ships with Meshtastic®—you can skip to Device Setup and the Meshtastic mobile app. Use the Flashing Guide only to update Meshtastic®, switch to MeshCore™, or match a specific build.
  3. Complete Radio & mesh concepts as needed; use the MeshCore guide if you flashed MeshCore™.

Official compatibility references