Deployment and Testing

A practical field guide to turning Meshtastic hardware and configuration into verified public infrastructure.

Deployment is a process, not a mounting job

A permanent Meshtastic node is not finished when the enclosure is attached to a mast. It is finished when the site is safe, legal, weather-resistant, correctly configured, reachable in both directions, documented and assigned to someone who will maintain it. Deployment joins the subjects covered elsewhere on MeshAtlas: site planning, antennas, power, enclosures, radio configuration and community coordination.

The useful sequence is survey, bench preparation, installation, commissioning, coverage testing, documentation and scheduled review. Skipping a stage usually creates a remote fault that is much more expensive to investigate later.

What this section covers

The guides in this section follow the life of a new infrastructure node. The installation guide begins before the site visit and ends with a serviceable physical system. Coverage and range-test guides explain how to collect repeatable evidence rather than a single spectacular contact. The radio-metrics guide explains what RSSI, SNR and packet loss can—and cannot—tell an operator.

Two troubleshooting guides then separate one-way paths from nodes that appear completely silent. The commissioning checklist provides a formal acceptance gate, while the documentation guide creates the record future maintainers will need.

Three different kinds of evidence

Evidence	What it answers	Limitation
Prediction	Where coverage may be possible	Depends on terrain data and assumptions
Commissioning test	Whether the installed site works now	Usually samples selected paths
Operational history	Whether it remains reliable over time	Needs logging and comparable observations

The official Meshtastic Site Planner can help predict radio coverage, but a model is not proof. Trees, roofs, local noise, antenna pattern, feed-line loss and imperfect terrain data change real results. Conversely, one received packet proves only that one packet arrived under one set of conditions.

A public-network standard

A community should agree on a minimum commissioning record: node identity, hardware, firmware, regional profile, modem preset, antenna, power source, approximate site, installation date, test endpoints and responsible maintainer. It should also define what counts as operational. “Visible in somebody’s node list” is too weak; a useful infrastructure node should pass planned two-way tests and remain observable over a representative period.

Keep administration keys, private channel keys, access instructions and sensitive exact coordinates out of the public record. A public node can be transparently described without publishing information that endangers the host or installation.

The deployment loop

Good infrastructure work is iterative. Survey assumptions become an installation plan; commissioning reveals construction or configuration defects; coverage tests expose weak sectors; operational monitoring shows whether the result survives weather, traffic and time. Feed those observations back into the site record and the next deployment. A community that preserves this evidence improves with every node, while one that keeps only screenshots repeats the same mistakes.

Define who can accept a node, who can change it and who may update its public status. This prevents an experimental installation from being advertised as dependable public infrastructure and prevents undocumented remote changes from invalidating earlier tests.

Safety and legal limits remain outside the app

Meshtastic can enforce some regional radio parameters, but firmware cannot approve a mast, judge a roof, design lightning protection or obtain property permission. Those responsibilities remain with the operator and host. Stop work when weather, access, electrical conditions or working at height exceed the planned method. A radio node is not important enough to justify unsafe work.

Read the guides in order

Official sources

Firmware, applications and documentation change over time. Confirm current setting names and applicable regional rules before commissioning or changing live infrastructure.