Batteries, Solar and Power Systems for Meshtastic

A practical method for sizing batteries, panels, regulators and backup power for infrastructure nodes.

Meshtastic infrastructure is a complete site: radio, antenna, feed line, power, enclosure, mounting, configuration and a plan for maintenance. This guide concentrates on one part of that system while showing how it affects the others. Product availability and firmware support change, so confirm the exact device revision and current documentation before purchasing or installing equipment.

Quick comparison

Option	Type or characteristic	Best use
Li-ion / 18650	High energy density	Compact temperate installations
LiFePO4	Long cycle life and stable chemistry	Larger outdoor systems with correct charger
LiPo pouch	Compact and easy to integrate	Protected indoor or mild-environment nodes
USB or DC mains	Continuous power	Homes, offices and equipment rooms
PoE	Power and data over one cable	Rooftop and Ethernet gateway sites

Measure before sizing

Solar design begins with average and peak current measured on the actual configured node. MCU family, GPS, Wi-Fi, display, sensors, telemetry intervals and traffic all change consumption. A data-sheet sleep figure is irrelevant if the firmware rarely sleeps. Meshtastic’s solar guidance correctly starts with measurement. Log current over representative hours and include cold starts, transmissions and charging losses.

For this part of the installation, write down the assumption, test it at the intended site and retain the result with the node record. Infrastructure becomes reliable through repeatable measurements and maintainable choices, not through a single impressive component.

Convert load into daily energy

Average current multiplied by 24 hours gives daily amp-hours at a stated voltage. Add margin for regulator inefficiency, battery aging and unexpectedly busy radio periods. Battery autonomy should cover the intended number of sunless days without exceeding the chemistry’s safe depth of discharge. Designing to use the full nameplate capacity makes the system fragile, especially in winter when both solar input and some battery performance decline.

Battery chemistry is a system choice

Li-ion cells offer excellent energy density but need protection and must not be charged below their safe temperature. LiFePO4 is robust and has a flatter voltage curve, but requires a compatible charger and may not work correctly with a board designed only for a single-cell Li-ion profile. Pouch cells need mechanical protection from puncture and swelling. Never mix unknown used cells or place unprotected cells directly in a sealed hot enclosure.

Panel and controller sizing

A panel’s rated watts are measured under favorable test conditions. Real output falls with poor angle, cloud, dirt, heat, shade and cable loss. Size from the worst relevant season, not an annual average. Ensure the controller accepts the panel voltage and implements the correct charging profile. WisBlock baseboards have specific solar-input limits; exceeding them is not made safe by using a small panel. Larger systems may use an external controller and regulated output to the node.

Mains, PoE and backup

At a building, mains power is simpler but should still be resilient. A DC UPS or appropriately managed battery keeps the node alive through outages. PoE reduces the number of rooftop cables and can carry Ethernet to a gateway, but voltage conversion near the radio must be quiet enough not to raise the noise floor. Fuse conductors at the source, provide surge protection and avoid improvised chargers that remain permanently hot inside the roof space.

Telemetry and maintenance

Monitor battery voltage, charge current where possible and internal temperature. Set alerts for a declining daily high voltage or repeated brownouts; these often reveal panel shading, water damage or an aging cell before total failure. Record battery type and installation date. Remote telemetry does not replace inspection: swollen cells, corroded terminals and UV-damaged wiring may not appear in a voltage graph until the site becomes unsafe.

Planning and commissioning

Begin with the purpose, users, expected coverage, legal region, site access and acceptable outage time. Draw the power and RF paths before assembly. Confirm that every radio and antenna is the correct frequency version. Configure a conservative hop limit and telemetry rate, then bench-test power failure and reboot recovery. At the site, test communication in both directions from representative user locations rather than relying only on the signal shown beside the infrastructure node.

Record the hardware model and revision, firmware version, region and modem preset, antenna, coax length, power source, battery chemistry, mounting date and responsible operator. Photograph the finished installation and cable entries. Label anything another maintainer could disconnect. For public or shared sites, avoid publishing exact sensitive coordinates unless the owner has approved it.

Establish a baseline after commissioning: battery high and low values, normal enclosure temperature, typical channel utilization, neighboring nodes heard and several repeatable test paths. Future observations are useful only when they can be compared with healthy behavior. A gradual fall in received signal may indicate water in a connector or a moving antenna long before the node disappears entirely. Store the baseline with the site record and repeat it after any material hardware or firmware change.

Common mistakes

Buying for advertised range or transmit power before surveying terrain and antenna placement.
Ignoring receiver performance, feed-line loss, power noise, condensation or winter energy production.
Using a specialized node role merely because the device is fixed or elevated.
Assuming a vendor enclosure, antenna or maximum output is automatically legal in every country.
Installing equipment that cannot be safely reached, opened, updated or recovered after a failure.

Procurement and standardization

Do not order a fleet from a product title alone. Confirm the exact MCU, LoRa transceiver, supported frequency, antenna connector, board revision and firmware target on a sample unit. The same commercial name may cover regional or hardware variants. Flash the current stable firmware, export a known-good configuration and run the sample continuously before buying more. For an outdoor product, inspect the real gasket, glands, mounting pieces and battery arrangement rather than judging only the radio specification.

Standardization is valuable even when another board is marginally cheaper. A small network that uses one radio platform, one connector family, one battery type and a limited set of fasteners needs fewer spares and fewer field tools. Keep at least one tested replacement for inaccessible or important sites. If a product becomes unavailable, qualify its replacement on the bench and on one non-critical site before changing the rest of the network.

Testing before permanent installation

Run a staged test. First verify programming, charging and recovery on the bench. Next operate the complete assembly outdoors at reachable height through several temperature and weather cycles. Finally test it at the intended site using the intended antenna, cable and power system. Send acknowledged direct messages in both directions and observe neighboring nodes over time. A single successful packet is not evidence of dependable coverage.

Simulate failure while the node is still accessible. Remove input power, partially discharge the battery, interrupt the network connection where relevant and verify that the node returns without manual intervention. Check that a firmware update does not erase the legal region or restore an unsafe power setting. Measure receiver behavior while nearby chargers, network devices and other transmitters are active. Quiet bench conditions can conceal site-generated interference.

Lifecycle and responsible operation

Every installation needs an owner and a retirement plan. Record who may change the configuration, how faults are reported and when the site will be inspected. Remove dead batteries and abandoned hardware instead of leaving them on roofs or hills. Respect property access, protected areas and visual-impact requirements. A community node should have a recognizable name or contact route without exposing personal details unnecessarily.

Review the configuration when firmware, regulation or local network practice changes. More relaying, more telemetry and more internet bridging are not automatically improvements; they consume shared spectrum. Use the minimum traffic and complexity that achieve the site’s purpose. When evidence shows that a node adds collisions or duplicates coverage without benefit, change its role, reduce traffic or relocate it. Good infrastructure is cooperative as well as technically functional.

Sources and further reading

What to read next

This article is technical guidance, not electrical, structural or legal certification. Follow national radio and building rules, equipment instructions and site-owner requirements. Use qualified installers for tower climbing, mains wiring, grounding and lightning-protection work.