ESP32 vs nRF52840: Which Platform?

Two microcontroller platforms dominate the LoRa mesh hardware landscape: Espressif's ESP32 family and Nordic Semiconductor's nRF52840. Both are capable, both are well-supported by Meshtastic and MeshCore firmware, and both commonly pair with the SX1262 (and related Semtech LoRa transceivers such as the SX1276/SX1268/LLCC68). But they are optimized for fundamentally different use cases, and choosing the wrong one has real consequences.

Platform Comparison at a Glance

Figures above are approximate typical ranges, not single datasheet values; cite per-mode datasheet figures where precision matters. Per Nordic, the nRF52840 draws ~4.8 mA peak in TX (0 dBm), ~4.6 mA peak in RX, and ~52 µA/MHz running from flash; its System OFF floor is ~0.4 µA (no RAM retention) and ~1.5 µA in System ON with wake-on-RTC. The ESP32-S3 and nRF52840 are both rated -40 to +85 °C per their respective datasheets.

Power Consumption: The Real Numbers

For battery-powered mesh nodes, power consumption is frequently the deciding factor. Here are approximate figures for a LoRa mesh node in active listening mode (radio on, MCU active, no WiFi). Exact values depend heavily on board design and firmware sleep strategy:

Note on transmit current: LoRa TX draw is dominated by the SX1262 power amplifier, which draws ~118 mA at +22 dBm and ~45 mA at +14 dBm per the Semtech datasheet (the RAK4631 module measures ~125 mA at +20 dBm). With MCU overhead, a node transmitting at +20-22 dBm draws roughly 120-160 mA total — not the 350-500 mA sometimes quoted, which reflect WiFi TX bursts rather than LoRa.

Practical implication (illustrative estimate): A node that spends 95% of its time in light sleep will consume roughly 3 - 5 mA on ESP32-S3 vs 0.6 - 1 mA on nRF52840. On a 2000 mAh 18650 cell, that is approximately:

• ESP32-S3: ~400 - 650 hours (~17 - 27 days)
• nRF52840: ~2000 - 3300 hours (~83 - 137 days)

This 4 - 5x difference is why nRF52840 is the correct choice for battery-powered or solar nodes, and the ESP32 is acceptable only when AC power is available.

Sleep Modes Explained

ESP32 Sleep Modes

• Active: Full operation, both cores running, radio on
• Modem sleep: WiFi/BT radio off, CPU running - not useful for mesh nodes since the LoRa radio is external
• Light sleep: CPUs paused, memory retained, peripheral clocks gated. ~0.8 mA total system is achievable (board/firmware dependent) for an ESP32-S3 with the LoRa radio in sleep
• Deep sleep: Most of chip off, only RTC domain active. ~10 - 150 µA depending on which RTC peripherals/ULP are enabled
• Minimal deep sleep (RTC timer only): ~5 µA but loses non-RTC GPIO state. This is the lowest-current deep-sleep configuration rather than a separately named mode

Key limitation: the ESP32's sleep modes interact poorly with external peripherals. Bringing WiFi up from deep sleep takes 200 - 400 ms - during which messages can be missed.

nRF52840 Sleep Modes

• System On (active): Full operation, up to 64 MHz CPU
• System On (idle): CPU halted, peripherals running - ~1 - 3 mA (config-dependent)
• System On (low power): Aggressive clock gating via automated low-current modes - ~0.5 - 1 mA (config-dependent)
• System Off: Only GPIO wakeup retained - ~0.4 µA with no RAM retention, rising to ~1.5 - 2 µA with RAM retention / wake sources enabled

The nRF52840's architecture allows the BLE radio and application code to be active simultaneously in time-division, with very efficient power management built into the SoftDevice BLE stack.

WiFi: ESP32's Biggest Advantage

The ESP32's integrated 802.11 WiFi is a genuine capability that the nRF52840 lacks entirely. This matters for:

• MQTT bridging: An ESP32 node can connect directly to a WiFi network and forward mesh messages to an MQTT broker without any additional hardware
• OTA firmware updates: WiFi-based OTA is reliable and convenient; no cable required
• Web configuration interface: Meshtastic's web UI is served over WiFi from the node itself
• NTP time sync: WiFi-enabled nodes can sync accurate time without GPS

If your deployment scenario requires WiFi connectivity from the node itself - for example, a Meshtastic MQTT gateway or a node that serves as both a mesh device and a WiFi access point - the ESP32 is the better choice.

BLE Capabilities

Both platforms support BLE 5.0 and use it for phone-to-node configuration and message viewing via the Meshtastic and MeshCore apps. In practice, BLE performance is similar between the platforms. The nRF52840 additionally supports Bluetooth Mesh natively, but this is not used in current Meshtastic/MeshCore deployments.

Community and Software Support

Decision Guide