Advanced Search
Search Results
727 total results found
Regional Scoping with ISO Codes (MeshCore)
Regional Scoping (MeshCore Region Filtering) MeshCore region scoping (region filtering) lets repeater operators tag flood traffic with a region so that repeaters only forward scoped packets within their configured region, reducing cross-country network congest...
MeshCore CLI Reference
Connecting to Your Device
The MeshCore CLI (meshcore-cli) supports three connection methods. Choose the one that matches your hardware and situation. Serial (USB) The most reliable method. Connect your device via USB and specify the serial port with -s: meshcore-cli -s /dev/ttyUSB0 Th...
Full Command Reference
MeshCore has two command surfaces. The device-side serial CLI (canonical reference: docs.meshcore.io/cli_commands) uses bare get/set verbs and is used to configure repeaters and room servers over USB serial. The host tool meshcore-cli (invoked as meshcore-cli/...
Key Repeater Settings
These settings are most critical for deploying and maintaining MeshCore repeater and room server nodes. AGC Reset Interval - Fix Receiver Deafness set agc.reset.interval 4 Problem it solves: If a high-power transmitter (such as a nearby ham radio or commercia...
Troubleshooting & Known Issues
Common Issues and Fixes
Quick Reference Table ProblemSolution Repeater goes deaf after nearby RF transmissions set agc.reset.interval 4 - resets AGC periodically (value in seconds) to recover from desensitization Heltec V3 Bluetooth dropouts Community modification (not ...
EasySkyMesh: Third-Party Power-Optimized MeshCore Fork
Important clarification: EasySkyMesh is a third-party derivative project based on MeshCore firmware, maintained by IoTThinks at github.com/IoTThinks/EasySkyMesh. It is not an official MeshCore firmware variant and is not available through the official MeshCore...
MeshCore Ecosystem Notes
Planning Your Network
Device Roles — All 12
Is There Already a Network in Your Area?
Is There Already a Network in Your Area? Before starting a new mesh network, check whether an existing network already covers your area. Joining an established network is almost always better than starting from scratch - you immediately have more repeaters, a ...
Personal Device Roles
Personal roles are designed for individual users who want to send and receive messages. They vary in how aggressively the device relays messages for others. Important: Your role choice affects everyone on the network. The Meshtastic project's guidance is clea...
Choosing Your Protocol and Channel
Choosing Your Protocol and Channel The two dominant LoRa mesh protocols for community networks are MeshCore and Meshtastic. They are not interoperable - nodes must use the same protocol to communicate. Protocol Comparison FeatureMeshCoreMeshtastic Infras...
Infrastructure Roles: Router and Repeater
Infrastructure roles are for fixed, well-placed nodes that genuinely improve mesh coverage for others. They should only be assigned to nodes that meet strict criteria. Misuse of these roles is a common cause of network congestion and poor performance. Prerequ...
Growing Your Community
Specialized Roles
Specialized roles optimize node behavior for specific use cases: tracking, sensing, and tactical operations. Each role adjusts transmission priority and sleep/retransmit behavior to match its intended function; telemetry cadence is configured separately in the...
Finding Volunteers and Repeater Sites
Finding Volunteers and Repeater Sites The practical limit on any mesh network's coverage is the number and location of repeaters. Growing a community mesh means finding both people willing to host hardware and locations with good RF exposure. Identifying Good...