MeshCore Off-Grid Repeat: Turn Any Companion Device into a Temporary Repeater
MeshCore Off-Grid Repeat lets companion devices forward mesh packets for other nodes — turning your phone and LoRa board into a temporary repeater. Learn how to enable it, when to use it, and where the trade-offs are.
MeshCore has a feature that quietly changes the math on temporary mesh deployments. It’s called Off-Grid Repeat, and it lets any companion device — the LoRa board connected to your phone or computer — forward mesh packets for other nodes on the network.
In normal MeshCore operation, companions don’t repeat. That’s by design — it keeps routing clean and prevents loops. But in off-grid scenarios where you don’t have dedicated repeater nodes deployed, that design choice means gaps in coverage. Off-Grid Repeat fills those gaps by letting companion devices temporarily act as repeaters.
How MeshCore Routing Normally Works
Understanding Off-Grid Repeat requires understanding why companions don’t repeat by default.
MeshCore separates nodes into roles:
- Repeaters — always-on, stationary nodes that forward packets through the mesh. They’re the backbone.
- Room servers — similar to repeaters but also host channels and store-and-forward messages.
- Companions — the LoRa board connected to your phone or computer via BLE, USB, or TCP. They send and receive your messages but do not rebroadcast other devices’ packets.
This role separation is intentional. If every companion rebroadcast every packet, you’d get the same scaling problems that plague flood-based protocols — exponential traffic growth, collisions, and wasted airtime. MeshCore avoids this by keeping rebroadcasting limited to dedicated infrastructure nodes.
But there’s a problem: what if you don’t have any dedicated infrastructure deployed?
What Off-Grid Repeat Does
When you enable Off-Grid Repeat on a companion device, that device starts forwarding mesh packets for other nodes. Your phone and LoRa board become a temporary repeater.
This means a group of people with companion devices can form a mesh network without any pre-deployed repeater hardware. Each device with Off-Grid Repeat enabled will relay packets for the others, extending range beyond single-hop distances.
The feature is available in MeshCore Open and requires firmware version 9 or later on your companion device.
How to Enable Off-Grid Repeat
- Open MeshCore Open and connect to your companion device
- Go to Settings → Node Settings → Radio Settings
- Select one of the three Off-Grid presets:
- Off-Grid 433 MHz (433.000 MHz)
- Off-Grid 869 MHz (869.000 MHz)
- Off-Grid 918 MHz (918.000 MHz)
- Toggle Off-Grid Repeat to on
- Save
The toggle only appears on firmware v9 and later. If you don’t see it, your firmware needs updating.
The Frequency Requirement
Off-Grid Repeat only works on the three Off-Grid preset frequencies. If you try to enable it on any other frequency, the app blocks the save and shows a warning: “Off-grid repeat requires 433, 869, or 918 MHz frequency.”
This restriction exists because Off-Grid Repeat is designed for scenarios where all participating devices agree on a common frequency ahead of time. The three Off-Grid presets serve as well-known meeting points — everyone in the group switches to the same Off-Grid preset, enables repeat, and the mesh forms itself.
- 433 MHz — available in most regions globally, lower data rate, longer range
- 869 MHz — EU ISM band
- 918 MHz — US/Canada ISM band
Pick the preset that’s legal in your region. Everyone in the group needs to be on the same one.
When Off-Grid Repeat Makes Sense
Emergency and Disaster Response
Your group is deployed to an area with no cell service and no pre-existing mesh infrastructure. Each person has a phone and a companion LoRa board. Everyone switches to the same Off-Grid preset, enables repeat, and suddenly the group has a multi-hop mesh network with no hardware pre-deployment.
Temporary Events
Field day operations, outdoor events, search and rescue coordination, group hikes in remote areas. Any scenario where you need mesh coverage for hours or days, not permanently.
Testing and Planning
Before investing in dedicated repeater hardware for a permanent deployment, you can use Off-Grid Repeat to test coverage patterns. Walk the area with companions in repeat mode, see where packets get through and where they don’t, then decide where to place dedicated repeaters.
Bootstrapping a New Mesh
Starting a MeshCore network from scratch and don’t have repeaters yet? Off-Grid Repeat lets you get messaging working between companion users immediately while you build out dedicated infrastructure.
Strengths
No extra hardware — every companion device you already own can become a repeater. No additional purchase needed.
Zero cost — built into MeshCore Open, which is free and open-source. No subscription, no premium tier.
Simple activation — one toggle in radio settings. No firmware changes, no reflashing. Just switch preset and enable.
Mutual coverage — in a group of 5 people spread across a valley, each person’s device extends coverage for everyone else. The mesh gets denser with every participant.
Cross-platform — works on Android, iOS, Linux, Windows, macOS, and web. Whatever device runs MeshCore Open can participate.
Limitations and Trade-offs
Be clear-eyed about what Off-Grid Repeat is and isn’t.
Battery Drain
Companion devices are not optimized for continuous packet forwarding. A dedicated repeater running EasySkyMesh firmware can idle at 5mA. A companion device running Off-Grid Repeat will drain your phone’s battery noticeably faster because:
- The LoRa radio stays in receive mode continuously
- Every received packet triggers processing and potential retransmission
- Your phone must stay on and maintain the BLE/USB/TCP connection
For a dedicated repeater, power efficiency is the whole game. For Off-Grid Repeat, you’re trading battery life for temporary coverage. Plan accordingly — bring a battery pack.
Frequency Lock
You can only use the three Off-Grid preset frequencies. If your region normally operates on a different frequency (say, a specific EU sub-band), you’ll need to switch everyone to the Off-Grid preset. This means you can’t participate in an existing mesh that runs on a different frequency while Off-Grid Repeat is active.
No Power Saving Mode
Dedicated repeater firmware supports powersaving on for aggressive current reduction. Off-Grid Repeat on a companion doesn’t have this — the companion firmware isn’t designed for it. Your idle current will be significantly higher than a tuned repeater.
Device Must Stay Connected
Your phone or computer needs to maintain its connection to the companion LoRa board. If BLE disconnects, or your phone goes to sleep and kills the app, the repeat function stops. On Android this means keeping the app in the foreground or configured to avoid battery optimization. On iOS, background BLE behavior may limit reliability.
Still Evolving
The MeshCore project roadmap lists “off-grid client repeat mode” as an upcoming feature area, suggesting the current implementation may continue to develop. The protocol support is in firmware v9+, and the app toggle is functional, but expect refinements over time.
Off-Grid Repeat vs. Dedicated Repeaters
| Off-Grid Repeat | Dedicated Repeater | |
|---|---|---|
| Cost | Free (existing hardware) | Requires separate LoRa board |
| Setup time | 30 seconds (toggle) | Requires flashing, mounting, powering |
| Battery life | Hours (drains phone) | Days to weeks (optimized firmware) |
| Idle current | High (companion firmware) | 5–13mA (EasySkyMesh) |
| Reliability | Depends on phone staying connected | Always-on, independent |
| Coverage | Mobile, moves with the person | Fixed, consistent coverage area |
| Use case | Temporary, emergency, testing | Permanent infrastructure |
Off-Grid Repeat is not a replacement for dedicated repeaters. It’s a complement — useful when dedicated repeaters aren’t available or practical.
Practical Tips
Agree on the frequency before you need it. If your group might need Off-Grid Repeat, decide which preset everyone will use before you’re in the field without internet to coordinate.
Position matters. Even in repeat mode, your companion device is limited by its antenna and placement. Hold it high, keep it near a window, clip it to the outside of your pack. Every meter of elevation helps.
Keep your phone charged. Off-Grid Repeat uses more power than normal companion operation. An external battery pack is not optional for extended use.
Test before you rely on it. Switch to Off-Grid Repeat in your backyard first. Walk around, check range, understand the behavior before you’re depending on it in the field.
Disable when you don’t need it. Switch back to your normal regional preset and disable repeat when the temporary deployment is over. No reason to stay on Off-Grid frequencies when your regular mesh infrastructure is available.
Getting Started
You need two things:
MeshCore Open — free download on GitHub, available via Obtainium on Android, or TestFlight on iOS
Firmware v9 or later on your companion LoRa board — flash via the MeshCore Flasher
For more on the app, see our MeshCore Open guide. For the latest firmware changes, check our MeshCore v1.14.1 release post.
If you need permanent coverage instead of temporary off-grid repeat, see our repeater setup guide and firmware guide for deploying dedicated infrastructure nodes.
Comments
Related Posts

Meshtastic Range Test: How to Map Your Mesh Coverage
Learn how to measure and map your Meshtastic mesh coverage using the built-in range test module, trace route, signal metrics, and MeshMapper. Includes tips for maximizing range in North Dakota terrain.

Meshtastic MQTT Setup: Bridge Your Mesh to the Internet
Complete guide to setting up MQTT on Meshtastic. Connect your LoRa mesh to the internet for remote monitoring, mesh bridging, Home Assistant integration, and Grafana dashboards.

MeshCore for Emergency Preparedness: Off-Grid Communication When It Matters
A field guide to building MeshCore emergency communication networks — repeater placement, hardware kits, real-world scenarios, and integration with ARES, RACES, and volunteer fire departments.