What to record so a public node can be understood, maintained and honestly represented years later.
Documentation is operational equipment
A remote node without records becomes an archaeological project. Future maintainers need to know what was installed, why it was configured that way, how to reach it safely and what normal performance looked like. Documentation also protects the host: it defines responsibilities, approved mounting, public information and the process for removal.
Maintain public and private records
| Public node record | Restricted operational record |
|---|---|
| Node name and general area | Exact coordinates and access route |
| Approximate coverage and test date | Keys, credentials and administration method |
| Frequency band, preset and role | Host contacts and access conditions |
| General antenna and power type | Detailed photographs, serials and asset value |
| Maintaining organization | Safety, grounding and site documents |
Publish only what the host has approved. Approximate coordinates can make a node useful on a map without exposing a private rooftop, vulnerable solar box or access point.
Create an installation record
Record a stable site ID, node IDs and names, owner, maintainer, installation date, approximate and exact locations at their appropriate access levels, elevation, antenna height, antenna model and gain, coax type and length, radio board, enclosure, power components, sensors and mounting hardware. Add purchase or warranty information where it helps maintenance.
Record the configuration
Store the firmware version, hardware target, regional profile, modem preset, frequency slot, device role, hop limit, rebroadcast policy, public channel policy, position precision and automatic broadcast intervals. Save an export or reproducible configuration procedure. Do not place plaintext administration or private-channel keys in a broadly shared document.
Preserve commissioning evidence
Attach the completed checklist, photographs before enclosure closure, final overview images, voltage readings, direct two-way test results, RSSI/SNR observations, sent/received counts and coverage-test files. State which paths were direct and which were relayed. Record limitations and areas not tested.
Keep a maintenance log
Every visit or remote change should record date, person, reason, state found, work completed, components replaced, firmware/configuration changes and tests passed afterward. Photograph water ingress, corrosion, storm damage or cable movement before repair. A short accurate history is more valuable than a perfect document that is never updated.
Plan ownership and end of life
Name the person or organization responsible for routine checks, incident response, host communication and cost. Include access constraints, spare equipment and the safe removal process. If responsibility changes, update both private records and the public listing. Mark a node inactive when evidence no longer supports an operational claim.
A practical minimum
- Identity, purpose and responsible maintainer.
- Site, antenna, radio, power and enclosure inventory.
- Firmware and configuration snapshot.
- Installation and closed-enclosure photographs.
- Commissioning and coverage evidence.
- Host agreement and access/safety notes.
- Maintenance history and next inspection date.
Use stable names and versioned records
Give the site a stable identifier independent of the replaceable radio’s node number or display name. Date photographs and configuration exports. Mark the current approved version while retaining superseded records. A filename such as “final-new-2” does not reveal which configuration was actually commissioned.
Store records somewhere available to more than one trusted maintainer. Protect restricted data with access control and a recovery process; a private notebook owned by one volunteer is a single point of failure.
Document absence and uncertainty
Write down what was not measured: unknown coax loss, unverified lightning design, sectors not range-tested or a battery whose capacity is only nominal. This is not a weakness in the record; it tells the next maintainer what to verify. Date every coverage claim and distinguish prediction, observation and operational expectation.
Review the record during every site visit. If reality and documentation differ, correct the record before leaving or create a clear follow-up task.
Related deployment guideS
- Commissioning Checklist for a New Infrastructure Node
- How to Diagnose One-Way LoRa Links
- How to Install a Permanent Meshtastic Node
- How to Perform a Proper Meshtastic Range Test
- How to Test and Map Meshtastic Coverage
- RSSI, SNR and Packet Loss Explained
- Troubleshooting a Meshtastic Node That Cannot Be Heard
Official sources
- Meshtastic Range Test module
- Meshtastic signal meter: RSSI and SNR
- Meshtastic Site Planner
- Meshtastic antenna testing
- Meshtastic device configuration
- Meshtastic telemetry configuration
- Meshtastic documentation: software/python/cli/
- Meshtastic documentation: configuration/radio/position/
Firmware, applications and documentation change over time. Confirm current setting names and applicable regional rules before commissioning or changing live infrastructure.