Skip to content

Search guides, devices and posts

Back to MeshCore

MeshCore Repeater Setup

Build network infrastructure for your community. A well-placed repeater can cover an entire town or bridge the gap between rural homesteads across the North Dakota plains.

This guide covers everything from choosing hardware and flashing firmware to solar power systems and cold-weather deployment strategies for North Dakota's climate.

Checked October 2026 against MeshCore 1.18.0.

What is a MeshCore Repeater?

In MeshCore, repeaters are the backbone of the network. In Meshtastic, most nodes can rebroadcast (managed flooding). MeshCore instead designates specific devices as repeaters, and only those devices relay traffic. Companions and room servers don't.

A repeater listens for messages from companion devices and other repeaters, then rebroadcasts them to extend coverage. It doesn't need a phone connection or user interaction, just power, an antenna and a good location. It doesn't keep routing tables either: flood messages carry their own hop list, and direct messages carry the path the sender learned.

Think of repeaters like cell towers for your mesh network. The more repeaters in good locations, the better the coverage for everyone.

Repeater vs Companion vs Room Server

Companion: your personal device, sends/receives your messages
Repeater: relays messages, extends coverage, no personal messaging
Room Server: stores messages for offline users, like a bulletin board

When to Deploy a Repeater

  • You want to extend coverage to an area that can't reach existing nodes
  • You have access to a high location (rooftop, grain elevator, hilltop)
  • You want to bridge two groups of users who can't reach each other directly
  • You want to contribute infrastructure to the NodakMesh network

When NOT to Deploy a Repeater

  • You're the only MeshCore user in your area (get a companion first)
  • You don't have a good elevated location (a repeater at ground level helps little)
  • The area already has strong repeater coverage

Hardware Selection

Recommended Devices for Repeaters

Budget

Heltec V3

Affordable and easy to find. Good for indoor repeaters or sites with wall power, since its ESP32 uses more power than nRF52 boards. The built-in screen shows the repeater's name and radio settings.

~$20-30
Best for Solar

RAK WisBlock

Low-power nRF52840 core: RAK's RAK4631 datasheet lists 17 mA in LoRa receive. The RAK19007 base board has a 5 V solar panel connector and a battery charger built in. A popular choice for off-grid solar repeaters.

~$30-50
Premium

Station G2

High-power amplifier (rated up to 36.5 dBm by UnitEng) and a low-noise receive amplifier, built as a stack of circuit boards. It isn't weatherproof, so put it in an enclosure outdoors. Best for fixed sites with power. Set its transmit power from the MeshCore FAQ's table, not the 22 dBm used on plain boards.

~$109

Antenna Recommendations

Omni-Directional Antennas

Best for general coverage. Radiates signal in all directions (360°). Use when you want to cover a wide area around the repeater.

  • 5.8 dBi fiberglass omni: good all-around choice
  • 8 dBi omni: more range but narrower vertical pattern
  • Stock antenna: fine for indoor or temporary setups

Directional Antennas (Yagi)

Best for point-to-point links. Focuses signal in one direction for maximum range to a specific target.

  • Use when bridging two locations (e.g., farm-to-town)
  • 10-14 dBi gain possible with a Yagi
  • Must be aimed precisely at the target

Power Options

Wall Power

Simplest option. Use a good 5 V USB adapter: Heltec asks for at least 600 mA for the V3, or it may reboot under load, and 1 A gives headroom. Best for indoor repeaters, attic installations, or locations near an outlet. High-power boards like the Station G2 need more; check the maker's spec.

Battery

Runtime is battery capacity divided by average draw, and draw depends on the board and on traffic. For example, a board averaging 50 mA empties a 3000 mAh battery in about 60 hours. Good for temporary deployments, events, or testing locations.

Solar

The usual choice for permanent off-grid installations. Pair a low-power nRF52 board with a panel and battery sized for your worst winter week, not an average day (see the solar section below).

Step-by-Step Repeater Setup

1

Flash Repeater Firmware

  1. a Visit the MeshCore Flasher in Chrome or Edge
  2. b Connect your device via USB
  3. c Select your device (e.g., "Heltec v3", "RAK WisBlock / WisMesh (RAK 4631)")
  4. d Choose the Repeater role (not Companion)
  5. e Pick the version, press Flash! and wait for it to finish. Our firmware guide covers each step.
2

Configure Radio Settings

Repeater firmware doesn't accept Bluetooth connections. Set these over USB with the repeater setup option in the web flasher, or log in to the repeater from the MeshCore app on your companion node (our app guide shows how). The app can only reach it once the radio settings match, so do the first setup over USB.

Radio Settings 910.525 MHz, 62.5 kHz, SF7, CR5 (US)

A freshly flashed repeater starts on the European default (869.618 MHz, 62.5 kHz, SF8), so a US repeater hears nothing until you change it. Run set radio 910.525,62.5,7,5, then reboot. Frequency, bandwidth and spreading factor must match every other node on your mesh; if yours uses another preset, copy it from your companion

Admin Password Default: password

Anyone who knows the default can log in and change your repeater, so set your own with password <new-password> (up to 15 characters). The guest password (set guest.password) is blank by default

Name and Location e.g., "NoDak-Fargo-RPT"

set name <name> picks a descriptive name that helps users identify your repeater. set lat and set lon put it on maps; both default to 0

ID Prefix Avoid duplicates nearby

By default, message paths name each repeater by the first byte of its public key (two hex characters), so two nearby repeaters with the same prefix can confuse direct routing. The key is random; if yours matches a nearby repeater, the MeshCore app (1.39 and newer) can give it a new key with a prefix you choose, under remote management. That makes it a new identity, so contacts will see it as a new node

Adverts Defaults are fine

A new install sends a zero-hop advert every 2 minutes, but that stops as soon as you save any setting; set advert.interval (60 to 240 minutes) if you want them. It floods an advert across the mesh every 47 hours (flood.advert.interval). After setup, send advert once so the whole mesh learns about it right away

MeshCore also has regions (since 1.10), which are flood scopes, not frequency bands. Leave them alone unless your mesh uses them.

3

Configure Advanced Settings

TX Power Depends on the board

set tx <dbm> (1 to 22) sets the LoRa chip's output, and the default varies by board. Higher power = more range but more battery drain. On a plain SX1262 board, 22 dBm is the chip's maximum. Boards with an extra amplifier (Station G2, Heltec V4, E22 30 or 33 dBm modules) put out more than the number you set, so check the MeshCore FAQ's table first: it gives 16 dBm on a US Station G2 for 35 dBm out, and 9 dBm as the most for a 2 W E22-900M33S. It warns that wrong values can damage the radio. Stay within your country's limits

TX Delay Defaults: 0.5 and 0.3

txdelay (flood) and direct.txdelay (direct) scale the random wait before a repeater retransmits, so nearby repeaters don't talk over each other. Leave them at the defaults unless you're fine-tuning a busy mesh

Power Saving Off by default

For battery and solar sites, powersaving on lets the repeater sleep between radio activity. It works on nRF52 boards (right away) and ESP32 boards (after 2 minutes), but not on other boards or bridge builds

GPS Optional

You don't need GPS for the map: adverts use the set lat / set lon location by default. On a board with GPS, gps on then gps setloc saves its position, or gps advert share sends the live GPS position. GPS is off by default and costs power, so a fixed repeater rarely needs it

4

Mount and Deploy

The single most important factor for repeater performance is height. A repeater mounted 30 feet up will dramatically outperform one at ground level, regardless of other settings.

Mounting Options

  • Rooftop: J-mount or chimney mount. Best option for most homes. Even a single-story roof makes a huge difference.
  • Attic: Good compromise if you can't mount externally. Some signal loss through the roof, but still much better than ground level. Avoid metal roofs.
  • Tripod/Mast: Portable option for temporary deployments or testing new locations before permanent install.
  • Grain elevator/Silo: If you have access, these are the holy grail in ND. Height + flat surrounding terrain = incredible range.
  • Tower: If you have an existing antenna tower, adding a LoRa repeater is trivial and gives unmatched coverage.

Line of Sight

LoRa performs best with clear line of sight. North Dakota's flat terrain is a massive advantage here: you can often see the horizon in every direction. Even modest elevation (20-30 feet) gives you line of sight to nodes miles away across the plains. Trees, buildings, and hills between your repeater and the target will reduce range significantly.

5

Verify Operation

Once your repeater is powered on and deployed, verify it's working:

  1. 1 Check the map: Once your companion hears its advert, the repeater shows up in Contacts and, if you set its location, on the app's Map tab. The online MeshCore map only shows it after someone uploads its advert (see Troubleshooting below).
  2. 2 Test with a companion: Walk or drive away from the repeater with a companion device. Send messages and verify they're being relayed. The app can show each channel message's hop count (a message setting), and its path viewer shows which repeaters a message went through.
  3. 3 Check signal strength: Log in to the repeater and open Status, which shows the last RSSI and SNR it heard, or, within direct range, use Ping (Zero Hop) from your contacts list. SNR tells you more than RSSI: at SF7, LoRa can decode down to about -7.5 dB SNR (Semtech's SX1262 datasheet), so a link well above that has margin.
  4. 4 Ask the community: Post on Discord and ask if anyone can see your repeater.

Solar-Powered Repeater Setup

Solar is the go-to power source for remote repeater deployments. Low-power LoRa boards draw little enough that a small panel can run them, even at North Dakota's latitude, as long as the panel and battery are sized for winter.

Solar Panel

Size the panel from your repeater's daily use, not from a rule of thumb. For example, a board averaging 20 mA at 3.7 V uses about 1.8 Wh a day; with only a few peak sun hours on a December day, you'd want several times that from the panel to recharge after cloudy days. Face it south, tilted at about your latitude (46° to 49° across North Dakota) or steeper to favour winter sun.

NREL's free PVWatts calculator gives month-by-month solar figures for your exact location.

Battery

Use a LiPo or 18650 pack big enough to carry the repeater through several days without sun. Bigger batteries bridge longer cloudy periods. For northern winters, oversized batteries are worth the extra cost: December days in North Dakota are only about 8 to 9 hours long, and cold cuts the capacity a battery can deliver.

Most lithium cells, LiFePO4 included, must not be charged below freezing (0°C / 32°F). Check the charging temperature range on your battery's datasheet.

Charge Controller

Some LoRa boards have a solar input and charger built in, such as the RAK19007 WisBlock base board (5 V panel connector). For custom builds with a separate controller, an MPPT controller gets more from the panel than a PWM one, especially when the panel's voltage is well above the battery's.

Enclosure

Use an IP65+ rated weatherproof enclosure. Size it to fit device, battery, and any charge controller. Add silica gel packets to prevent moisture condensation. Insulation (foam or fiberglass) helps protect the battery in extreme cold.

North Dakota Deployment Tips

Great Plains Line-of-Sight Advantage

North Dakota's flat terrain is a big advantage for LoRa, because range on open ground is mostly set by the radio horizon. A quick estimate in miles is 1.41 × (√h1 + √h2), with both antenna heights in feet. A repeater 100 feet up a grain elevator and a handheld at 6 feet come to about 18 miles; two repeaters each 100 feet up, about 28 miles. Real links can fall short of that with weak signals, trees or buildings in the way.

Cold Weather Considerations

North Dakota winters are brutal on batteries. At -40°F (which happens), lithium batteries deliver far less of their capacity, and below freezing most of them must not be charged at all.

  • Use an insulated enclosure with foam or fiberglass lining
  • Oversize your battery, and check its cold-temperature ratings on the datasheet
  • Pick a battery or charger with low-temperature charge protection, so it won't charge when it's too cold
  • If wall power is available, use it, since batteries are the weak link in winter
  • Test your setup during a cold snap before relying on it

Rural Coverage Strategy

For maximum rural coverage, think about repeater chains along major highways (I-94, I-29, US-2, US-83). Space them by what each pair of sites can actually reach (use the horizon estimate above, then test), and a chain can create a corridor of coverage connecting towns. Grain elevators along rail lines are ideal mounting points because they're tall, have power nearby, and they're spaced regularly across the state.

Practical ND Use Cases

Repeaters enable real-world applications across North Dakota: farm-to-farm communication during harvest, hunting group coordination in the Missouri River breaks, volunteer fire department dispatch in rural areas without reliable cell service, storm chasing coordination during severe weather season, and oil field communications in the Bakken.

Troubleshooting

Repeater not appearing on the map

There are two maps. The Map tab in the MeshCore app shows repeaters your companion has heard over the radio; the online map at map.meshcore.io only shows a repeater after someone uploads its advert (open the contact, Share, then Upload to Internet Map, or run an auto-uploader). Both plot the location inside the advert, which is 0,0 until you run set lat and set lon. Set both and send advert. More fixes in MeshCore repeater not showing up or not repeating.

Poor range despite good location

Check your antenna connection: a loose or damaged SMA connector can cut range badly. Verify you're using a 915 MHz antenna (not 868 MHz or a random 2.4 GHz WiFi antenna). Make sure the antenna has clear line of sight and isn't blocked by metal roofing or siding. If it transmits but hears little, check that radio.rxgain is on and look at the noise floor with stats-radio over USB.

Battery draining too fast

Check TX power settings: higher power uses more energy. Turn on powersaving if your board supports it. Ensure your solar panel is sized correctly and getting full sun. Verify the charge controller is working by watching the battery voltage in the app's Status screen. In winter, faster drain is normal and expected; see the cold weather section above.

Key prefix collisions

If two nearby repeaters share the same 1-byte ID prefix, direct routing through them can get confused. Check the MeshCore map and your Contacts for repeaters near you (the app's search finds a prefix if you type it after <, like <a3). If you find a collision, give your repeater a new key with a different prefix from the app's remote management. Meshes that switch to 2- or 3-byte path hashes (firmware 1.14 and newer) make collisions much rarer.

Repeater keeps rebooting

Usually a power issue. Check your USB cable, power supply voltage, and battery connections. A failing battery or undersized solar panel can cause brownouts and reboots under transmit load. Try a fresh firmware flash if the problem persists.

Messages not relaying

Verify the repeater firmware is actually flashed (not Companion), and that get repeat says on. Check that the radio settings (frequency, bandwidth, spreading factor) match the companion devices trying to reach it. A repeater relays flood traffic without anyone having to discover it first, so if floods still don't get through, check the hop limits (flood.max, default 64) and any region rules. Repeaters older than 1.14 drop packets that use 2- or 3-byte path hashes, so update old repeaters.

Repeater FAQ

How many repeaters does a network need?

It depends on terrain, antenna height and the area you want to cover. On flat ground, the radio-horizon estimate in the deployment tips above gives a first idea of how far each site reaches. For town coverage, one repeater at a high point often suffices. For highway corridors, space repeaters by what each pair of sites can reach, and test before you commit.

Can one device be both a repeater and room server?

Not with a single firmware flash: you need to choose one role, and room server firmware doesn't relay. However, some community members run both a repeater and a room server on separate devices at the same location to provide both coverage and message storage. See our Room Server Guide for details.

Do I need permission to install a repeater?

No FCC license or government permission is needed. MeshCore operates on the license-free ISM band. However, you do need permission from the property owner if you're mounting on someone else's building, tower, or grain elevator. Always get written permission for shared or commercial structures.

Can I manage my repeater remotely?

Yes, over the mesh. Repeaters don't take Bluetooth connections, so you log in to the repeater as admin from the MeshCore app on your companion, wherever the mesh can reach it, and use Status, Command Line and Settings. The phone apps add a short wait before each remote session unless you buy Remote Management; the desktop apps are fully unlocked. The MeshCore CLI can log in through a companion too. Ethernet builds (RAK4631 with a RAK13800) also take commands over TCP port 23, and a repeater plugged into a Raspberry Pi over USB can be managed with a serial terminal such as picocom.

How long will a solar repeater last?

With a properly sized solar system, it keeps running unattended. The LoRa hardware has no moving parts. The weakest link is usually the battery, which wears out with charge cycles and heat; LiFePO4 cells are generally rated for more cycles than LiPo. Check on your installation periodically, especially after severe weather, and watch its battery voltage in the app's Status screen.

Related Guides

Using Meshtastic instead? See our Meshtastic router & repeater guide for Meshtastic device roles, router configuration, and deployment strategy.