Meshtastic Power: Battery, Solar, and Remote Deployments

A Meshtastic node can run from USB power, a rechargeable battery or a solar installation. The correct choice depends less on the radio’s advertised range than on its processor, role, accessories, radio traffic and how often someone can reach the site.

The most important distinction is between ESP32-based boards and nRF52-based boards. ESP32 hardware is flexible, especially when Wi-Fi is needed, but normally consumes considerably more energy. An nRF52840 board is usually the better starting point for an unattended solar node.

Battery-life figures in this guide are planning estimates, not guarantees. Firmware, screen use, Bluetooth connections, Global Navigation Satellite System (GNSS) receivers such as GPS, sensors, transmit power, traffic and temperature can all change the result. Measure the finished node before sizing a remote installation.

Why power matters in Meshtastic

LoRa (Long Range) is a low-data-rate radio modulation designed for long-range communication with relatively little energy. That does not make the complete device equally efficient. Its processor, display, GPS, Wi-Fi, Bluetooth and power circuitry all consume energy.

A portable node only needs enough energy for a walk or a weekend. A home node can remain on a good USB supply. A rooftop or mountaintop node must survive nights, cloudy periods, winter, battery ageing and maintenance delays.

ESP32 and nRF52 power profiles

ESP32 boards, including the LILYGO T-Beam and Heltec WiFi LoRa 32 families, provide Wi-Fi, Bluetooth and ample processing power. A normal awake node commonly requires several times the average energy of an nRF52 design, although the ratio varies by board and configuration.

The Nordic nRF52840 is designed for low-power Bluetooth devices. Boards such as the RAK4631, LILYGO T-Echo and Seeed XIAO nRF52840-based kits are therefore popular for portable and solar Meshtastic nodes. Meshtastic’s supported-device list identifies the processor and integrated features of current boards. Meshtastic supported hardware

Do not confuse a datasheet’s deep-sleep figure with normal Meshtastic consumption. RAK specifies 2 microamps for the RAK4631 module in sleep, while its RAK19007 base-board documentation says a core-and-sensor combination can sleep below 10 microamps and may reach 130 milliamps while transmitting. Those figures describe operating states, not the 24-hour average of a configured mesh node. RAK4631 datasheet RAK19007 datasheet

Platform or example board	Relevant published figure	Practical whole-node planning range	Power suitability
RAK4631 with nRF52840 and SX1262	2 µA module sleep; under 10 µA for a sleeping core/base combination; transmission may reach about 130 mA	About 5–15 mA average for an awake, receiving Meshtastic node; less is possible with application-specific sleep	Excellent starting point for battery and solar
LILYGO T-Echo, nRF52840	Manufacturer and Meshtastic documentation identify a low-power MCU, e-ink display, GPS and included battery	Often plan around 8–20 mA depending strongly on GPS and position interval	Good portable choice; GPS use matters
Seeed XIAO nRF52840 with Wio-SX1262	Seeed specifies less than 5 µA standby for the kit	About 5–15 mA as a normal receiving node; custom sleep workloads may be much lower	Very good for compact DIY and solar builds
LILYGO T-Beam, ESP32 family	Integrated GPS, power-management circuitry and 18650 holder; exact consumption depends on version	Roughly 30–80 mA average with Bluetooth and periodic GPS; active GPS or Wi-Fi can raise it	Convenient portable tracker; use a larger solar budget
Heltec WiFi LoRa 32 V3/V4, ESP32-S3	ESP32-S3, SX1262, Wi-Fi, Bluetooth and OLED; V4 datasheet quotes under 20 µA in its low-power condition	Roughly 25–60 mA as a configured receiving node, depending on display, Bluetooth and sleep settings	Fine for USB and accessible battery installations; less forgiving on solar

These broad ranges combine hardware-state figures with community measurements, including an ESP32 test near 0.1 watt without GPS or a screen. Solar Meshtastic measurements Use them only for initial planning: the official guide recommends measuring energy over time because transmit current and traffic vary. Meshtastic power-measurement guide

Battery options and built-in support

18650 lithium-ion cells

An 18650 is a cylindrical rechargeable lithium-ion cell. It is mechanically robust and easy to replace when an enclosure has room for a holder.

The LILYGO T-Beam has an integrated 18650 holder and charging/power circuitry, making it convenient for a portable GPS node. LILYGO T-Beam product information Use a reputable protected cell unless the complete device provides all required protection, observe polarity, and never assume that every 18650 holder includes safe charging.

LiPo pouch batteries

A lithium-polymer pouch, commonly called LiPo, is light and fits compact handheld enclosures. It is easier to damage and replace than a cylindrical cell. Voltage, polarity and charger chemistry must match the board.

The T-Echo is an example of an integrated portable nRF52840 device supplied with a case and battery. Meshtastic T-Echo hardware page RAK WisBlock base boards instead provide battery and solar connections for custom builds; follow the exact connector-polarity and input specifications for the selected base board. RAK WisMesh battery and solar connection example

AA and AAA packs

AA or AAA packs offer easy field replacement. Primary alkaline cells are not rechargeable; nickel-metal hydride cells are rechargeable but have a different nominal voltage. Packs are bulky and need the correct cell count and regulator. Verify the board’s permitted input rather than connecting a pack because its measured voltage looks close.

How long will a battery last?

A useful first estimate is:

runtime in hours = usable battery capacity in mAh ÷ average current in mA

For planning, use only about 80% of the labelled capacity. Conversion losses, cold weather, ageing and voltage cut-off make the full rating unavailable. A 3,000 mAh cell therefore provides a planning capacity of approximately 2,400 mAh.

Example configuration	Planning current	Estimated life from one 3,000 mAh cell
nRF52 CLIENT or CLIENT_MUTE, no GPS, normal receiving	5–10 mA	About 10–20 days
nRF52 ROUTER or ROUTER_LATE, active mesh	8–15 mA	About 7–12 days
nRF52 TRACKER with periodic GPS fixes	10–25 mA average	About 4–10 days
ESP32 CLIENT with Bluetooth, display mostly off	25–50 mA	About 2–4 days
ESP32 tracker with frequent GPS or an always-active display	50–100 mA	About 1–2 days

These are calculated examples, not guarantees. Traffic and repeated GPS searches can raise consumption. Measure at least 24 hours in a representative configuration before buying the final battery or panel.

Power saving and sleep behavior

Meshtastic power saving disables Bluetooth, serial, Wi-Fi and the screen, then lets the processor enter a low-power state. On a sleeping ordinary node, the LoRa radio remains in standby and an incoming radio packet can wake the device. Configuration changes may then require waking the node with its user button, resetting it or using remote administration. Meshtastic Power Configuration

Most users should select an appropriate device role before changing advanced power timers. In the clients, enable power.is_power_saving; with the command-line client, the command is:

meshtastic --set power.is_power_saving true

Role behavior is not identical:

All roles except TRACKER and SENSOR can use the traditional sleep behavior.
For ROUTER, power-saving sleep is automatically enabled and cannot be disabled.
An ESP32 can use light or deep sleep; the power.ls_secs light-sleep interval setting applies only to ESP32 boards.
With power saving, TRACKER sleeps for its position-broadcast interval, wakes, obtains a valid GPS location, transmits it and repeats.
With power saving, SENSOR sleeps for its environmental-telemetry interval, wakes, measures, transmits and repeats.
During the special TRACKER and SENSOR sleep cycles, the LoRa radio does not remain listening for packets that could wake the node.

These current rules are documented in the official role guide. Meshtastic Device Configuration Read Node roles explained before assigning infrastructure roles merely to improve perceived range.

Solar power fundamentals

A dependable solar node has four power components:

A panel that produces energy in the available sunlight.
A solar-aware charge controller compatible with the battery chemistry.
A battery large enough to run the node overnight and through cloudy days.
A regulated, protected connection to the Meshtastic board.

The battery powers the node continuously; the panel replenishes it. Do not depend on the panel directly because cloud and shade make its output unstable.

A solar input does not accept every panel. Observe its maximum voltage, polarity, charge current and battery chemistry. Use a solar-aware controller rather than assuming a generic USB charger will work efficiently from varying input. Panel output must also remain within the cell and controller’s charging limits. Solar controller and charging notes

Sizing the panel and battery

Work in watt-hours (Wh), because this allows batteries, USB measurements and panels at different voltages to be compared.

Measure the node’s average power for at least 24 hours.
Multiply average watts by 24 to obtain watt-hours per day.
Multiply daily energy by the desired number of sunless days.
Increase battery capacity for usable depth of discharge, cold, ageing and conversion losses.
Divide daily watt-hours by the site’s worst-month peak-sun-hours and system efficiency to find the minimum panel rating.
Add margin so the panel can both run the node and recharge after bad weather.

Example: an nRF52 installation averaging 0.04 W consumes 0.96 Wh per day. Three sunless days require 2.88 Wh of usable storage. A 3,000 mAh cell is about 11.1 Wh nominal at 3.7 V, leaving theoretical margin after derating.

If the site receives only two peak-sun-hours in its worst month and the charging system is assumed to be 70% efficient, the break-even panel is 0.96 ÷ (2 × 0.70), or about 0.69 W. That is only the mathematical minimum. A 3–5 W panel is a more defensible starting point because it can recover from cloudy days, dirt and imperfect orientation.

An ESP32 node averaging 0.15 W consumes 3.6 Wh per day. Under the same two-hour assumption, its break-even panel is about 2.6 W; a practical starting point may be 8–10 W with a larger battery. A GPS-heavy or busy node may require more. This is why ESP32 should not be the default choice for a difficult solar site.

Peak-sun-hours are not hours of daylight. They express the day’s solar energy as an equivalent number of hours at the panel’s rated irradiance. Use a reputable solar resource for the exact coordinates and design for the worst season, not the annual average. The European Commission’s PVGIS calculator covers much of the world, while the US National Renewable Energy Laboratory provides PVWatts for locations covered by its dataset.

Solar deployment in practice

Orientation: point the panel toward the equator—generally south in the northern hemisphere and north in the southern hemisphere. Use a steeper angle when optimizing for low winter sun.
Shade: inspect the site across the day and season. A branch, mast or antenna shadow can reduce charging precisely when the system has little margin.
Winter: shorter days, lower sun, cloud and snow can reduce production drastically. High-latitude sites may need a much larger panel and battery, another energy source or seasonal maintenance. Solar cannot be assumed to work everywhere.
Temperature: confirm the cell’s charging range. For example, Panasonic specifies +10°C to +45°C for its NCR18650B; another cell may differ. Use appropriate chemistry and low-temperature protection. Panasonic lithium-ion specification example
Weatherproofing: use an outdoor-rated ultraviolet-resistant enclosure, sealed cable glands and a downward-facing drip loop. A pressure-equalizing waterproof vent can reduce condensation caused by temperature cycling.
Heat: do not leave a lithium battery pressed against the back of a sun-heated panel. A sealed box in direct sun may become much hotter than the surrounding air.

A documented community build shows practical use of a weatherproof enclosure, bulkhead antenna connection, cable sealing and a breather vent, but it should be treated as one build example rather than a universal parts prescription. Community solar-node build

USB power banks

A USB power bank is fine for tests, events, travel or an accessible home node. It includes charging and regulated 5 V output.

It can be inefficient for a permanent low-power node. The bank’s voltage converter consumes its own quiescent current—the current used while doing almost no useful work—and some models switch off when the node draws less than their minimum-load threshold. Converting a cell from about 3.7 V to 5 V and then regulating it again on the board also wastes energy.

Test the exact bank and node for several days. Confirm that any “always-on” mode survives charging interruptions. A direct battery system is normally more predictable remotely.

Remote deployment checklist

Measure average and peak power with the final firmware, role and accessories.
Size for the worst month and several days without useful sun.
Use the correct charger and protection for the battery chemistry.
Confirm polarity before connecting the battery, panel or board.
Use a weatherproof, ultraviolet-resistant enclosure and sealed cable glands.
Add drip loops and strain relief so cables cannot pull on small board connectors.
Keep antenna coaxial cable short; mounting the node near the antenna usually loses less signal than a long cable run. See Antennas, placement, and real-world range.
Mount the antenna vertically unless the intended network uses another polarization, and keep it clear of the panel and metalwork.
Provide a safe maintenance method: Bluetooth access, a reachable USB connector or tested remote administration.
Test the sealed system outdoors before placing it somewhere difficult or dangerous to reach.
Obtain permission for the site and use safe, structurally appropriate mounting hardware.

Measuring your node’s actual power draw

A normal multimeter shows instantaneous current, but a node alternates between receiving, transmitting, using GPS and sleeping. For solar sizing, use a USB energy meter, source meter, power profiler or bench supply that records accumulated milliamp-hours or watt-hours and has enough resolution for low-current devices.

Assemble the final board, display, GPS, sensors and antenna.
Install the intended firmware and select the final role and intervals.
Place the node on a mesh with representative traffic.
Reset the energy meter and run the test for at least 24 hours; several days is better.
If the meter reports mAh, multiply amp-hours by the measured supply voltage to obtain Wh.
Divide accumulated Wh by elapsed hours to obtain average watts.
Repeat with GPS, Bluetooth, screen or power saving changed so you know which feature matters.

The official measurement guide includes worked conversions and explains why an integrated measurement over time is preferable to adding receive and transmit datasheet values. How to measure Meshtastic device power consumption

Use ESP32 when you need its capabilities and can supply the energy; use nRF52 when battery life and solar resilience are priorities. Measure the finished node and design for the worst season.