Search Results

Step 1 - Flash Room Server Firmware Use the MeshCore web flasher at flasher.meshcore.io. Select your hardware (e.g., Heltec V3) and choose the Room Server firmware variant. Step 2 - Connect via Serial or Bluetooth Connect via USB serial at 115200 baud using a ...

Dual Deployment: Separate Repeater and Room Server The recommended best practice for any fixed site is to deploy two separate devices rather than enabling repeat mode on the room server. Why Two Devices? A repeater and a room server have conflicting placement...

Meshtastic MQTT Gateway Overview MQTT allows Meshtastic nodes to bridge the local LoRa mesh to the internet, enabling mesh messages to travel between physically separated mesh islands and feeding data into monitoring dashboards. Hardware Requirements A device...

Home Assistant & Grafana Integration Once your Meshtastic node is publishing to an MQTT broker, that data stream can feed home automation and monitoring platforms. Home Assistant Integration Home Assistant has a built-in MQTT integration that can subscribe to...

Coverage Planning Tools Overview Before deploying hardware, use these tools to estimate coverage, find line-of-sight paths, and identify gaps in your network. Most are free and browser-based. MeshCore-Specific Tools ToolURLWhat It Does NoDakMesh Node P...

MeshMapper Wardriving Guide MeshMapper is a platform for mapping actual measured RF coverage of a MeshCore network - not just node locations, but real signal coverage at road level. This is the ground truth that theoretical planners cannot provide. MeshMapper ...

MeshCore uses a hybrid flood-first / direct-route-after approach rather than persistent flooding. For stable repeat-unicast traffic the network quiets down as paths are learned; under mobility, link churn, or heavy group/broadcast traffic it can get louder aga...

Path Hash Modes (MeshCore) Path hash modes control how repeaters identify themselves in routing path headers within MeshCore packets. This feature is available in recent MeshCore firmware versions. Check your firmware release notes for version-specific availab...

Understanding the difference between MeshCore's flood-first, direct-route-after routing and Meshtastic's flood routing explains why the two protocols behave differently in large networks. Flood Routing (Meshtastic) In a managed flood, each relay rebroadcast...

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...

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...

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/...

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...

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 ...

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...

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 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 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...