Pre-Deployment Checklist

The single most important rule for emergency mesh communications: configure and test your equipment before you need it. A device configured under stress, in the dark, during an emergency will have errors. Do this work now.

Hardware Preparation

☐ Flash current firmware from flasher.meshcore.io (MeshCore) or the Meshtastic flasher
☐ Set node name to something identifiable (your callsign or neighborhood)
☐ Set GPS coordinates (lat/lon)
☐ Change all default passwords (admin: “password”, guest: “hello”) on room server firmware
☐ Apply correct radio preset (USA/Canada for most North American MeshCore networks)
☐ Attach and secure external antenna
☐ Verify the node appears on a network map (map.meshcore.dev or meshmap.net)

Connectivity Testing

☐ Confirm channel/preset matches your local network
☐ Test two-way communication with at least one other known node
☐ Test from multiple locations (indoors, outdoors, vehicle)
☐ Confirm room server (if deployed) accepts messages from client nodes
☐ Verify MQTT gateway (if present) is publishing to broker

Infrastructure

☐ Consider a permanent rooftop or elevated repeater for neighborhood coverage — install before an emergency while conditions are normal
☐ Ensure permanent repeaters have reliable power (ideally with UPS or battery backup)
☐ Document all node locations, hardware, and configurations in a shared document accessible to your emergency team

Team Preparation

☐ Train all team members on the companion app before deployment
☐ Establish and communicate channel names and passwords to all participants in advance
☐ Assign a “mesh coordinator” role responsible for network status during an event
☐ Export config backup and store separately from the device

Realistic Range Expectations

Scenario	Typical Range
Urban direct (street level)	1–5 km
Suburban rooftop-to-rooftop	5–15 km
Rural / hilltop-to-hilltop	20–50+ km
With mesh hops through repeaters	Multiply coverage area substantially