Troubleshooting Common Problems

After you have confirmed that a repeater is online and checked it with path traces, the next step is to interpret what those checks are telling you. Most repeater problems fall into a few common patterns. Identifying the pattern first usually points to a practical next action.

Repeater Is Online but Rarely Used

A repeater that appears in Discover and responds to remote commands, yet almost never shows up in real message paths, is not filling a useful coverage gap.

Common causes include:

The site does not actually improve any routes that people need.
Nearby higher-elevation or better-placed repeaters already provide reliable paths, so MeshCore prefers them.
The repeater’s region settings are too restrictive (or too open) for the traffic that exists in the area.
Antenna height or location is marginal, so the repeater is only usable under ideal conditions.

What to try:

Run several path traces from different nearby companions. If the repeater only appears when you force it, it is probably not needed for normal traffic.
Temporarily adjust region settings so the repeater can forward a broader set of local traffic, then watch whether it begins to appear in ordinary paths.
If the site still sees almost no use after a few days, consider relocating the antenna or the entire station rather than leaving an idle repeater on the air.

Weak or Inconsistent Signal Levels

Path traces that include the repeater but show poor SNR (near 0 dB or negative) or weak RSSI indicate a marginal link.

Common causes include:

Antenna is too low, obstructed by trees or buildings, or pointed poorly.
Long or lossy coaxial cable between the radio and the antenna.
Local interference raising the noise floor.
The path is simply too far or blocked by terrain for reliable communication.

What to try:

Repeat the path trace several times at different hours. Consistent weak readings point to a site or antenna issue; occasional weak readings may be temporary interference or weather.
If you can reach the site, raise the antenna a few meters or move it a short distance to a clearer spot and retest. Small changes in height or clearance often produce larger improvements than changing radio power.
Check cable connections and consider a shorter or lower-loss feed line if the run is long.

Paths That Used to Work Now Fail

A route that previously included the repeater and now fails (or the repeater no longer appears in traces) usually means something has changed.

Common causes include:

The repeater has gone offline or is rebooting frequently (power, overheating, or firmware issue).
A better path has become available, so MeshCore is no longer choosing this one.
Antenna damage, loose connection, or vegetation growth has degraded the link.
Region or other configuration changes on this or a neighboring repeater have altered forwarding behavior.

What to try:

Confirm the repeater is still online and reachable with a direct path trace or remote login.
Compare recent path traces with older ones. If the repeater has simply been replaced by a different route, the site may no longer be necessary for that particular path.
If the repeater is online but links have become weak, revisit antenna height, cable, and local obstructions.

Signs of Congestion or Excessive Airtime

A repeater that is frequently chosen but seems to make the local network slower or less reliable may be contributing to congestion.

Common indicators include:

Many short-range, low-value repeats of the same flood packets.
Path traces that succeed only intermittently even though signal levels look adequate.
Local users reporting that messages take longer or fail more often after the repeater was added.

What to try:

Review the repeater’s region configuration. Limiting it to the regions that actually need to be forwarded through that site reduces unnecessary airtime.
Check whether several low-profile repeaters are clustered in the same area. Removing or relocating the least useful ones often improves overall reliability more than adding another station.
The next lesson covers specific tuning options (including TX delay and region adjustments) that can reduce congestion without removing the repeater.

A Practical Troubleshooting Sequence

When something seems wrong, work through these steps in order:

Confirm the repeater is online and responding.
Run path traces both to and through the repeater. Note whether it appears and what the SNR/RSSI values look like.
Compare current behavior with earlier observations. Has usage dropped, have signals weakened, or has congestion increased?
Make one change at a time (antenna position, region settings, or temporary removal) and retest.
If the site still does not improve useful coverage or reliability, it is reasonable to relocate or remove it.

Repeater Troubleshooting Checklist

Use this short checklist when a repeater is not performing as expected. Check the items in order and stop when you find the cause.

☐ Online? Does the repeater appear in Discover or respond to a remote command / path trace?
☐ Power stable? Has it been rebooting or dropping offline? Check power source, connections, and any low-voltage cutoff.
☐ Appears in real paths? Run traces from more than one nearby station. Does it show up in ordinary (not forced) routes?
☐ Signal levels acceptable? In the trace results, are SNR values generally positive and stable? Are RSSI readings reasonable for the distance?
☐ Antenna and cable OK? Is the antenna clear of obstructions, mounted vertically, and connected with a short, low-loss cable?
☐ Region settings appropriate? Is the repeater forwarding the regions that local users actually need, without carrying unnecessary wide-area traffic?
☐ Congestion signs? Are local users seeing slower or less reliable delivery since this repeater was added? Are many low-value repeats occurring nearby?
☐ One change at a time? After each adjustment (antenna, regions, temporary removal), retest with path traces before making another change.
☐ Still not useful? If the site does not improve coverage or reliability after reasonable checks, relocate or remove it.

Most problems become clearer once you separate “is it reachable?” from “is it useful?” The monitoring checks from the previous lesson give you the data; the steps and checklist above help you decide what to do with it.

Next: Tuning Repeater Settings

← Previous: Monitoring Repeater Performance

Continue to: Tuning Repeater Settings →

Was this material helpful? Leave feedback or suggest a correction.