Meshtastic Nodes Cannot See Each Other: Checklist

[Pavel]

Short answer: Nodes must share a compatible region, frequency slot, modem preset and channel configuration, and they need RF link margin. Diagnose configuration before range: place nodes metres apart, verify firmware compatibility and compare channel settings without publishing keys.

Before you start​

• Set the correct regional radio profile before testing; frequency plan, permitted power and duty-cycle constraints depend on location.
• Use the same modem preset, channel settings and channel key on nodes that are expected to communicate.

Step-by-step method​

1. Step 1: Set both nodes to the correct same region and modem preset, then reboot. Confirm each reports its own radio as healthy rather than disabled by an unsupported region.
2. Step 2: Compare primary channel name and pre-shared key privately, along with frequency slot and role. Do not post the key in screenshots or logs.
3. Step 3: Test outdoors a few metres apart with known correct antennas attached before power-up. Check packet logs for transmit, receive, decode or duty-cycle errors.
4. Step 4: Reset one controlled configuration only if differences remain, then test a default channel. Once direct communication works, restore private settings carefully.

Concrete example​

If both nodes show transmissions but neither decodes the other at two metres, a channel key, preset, region or frequency-slot mismatch is more likely than range. If one logs no RF activity, inspect antenna and radio hardware.

How to judge the result​

The fault is fixed when direct messages pass both ways repeatedly at close range, then continue over the intended route with acceptable RSSI/SNR and delivery rate.

What to record​

• Record RSSI, SNR, hop count, delivery success and antenna height for a fixed route instead of quoting one maximum-distance message.
• Line of sight, Fresnel clearance and antenna placement usually improve range more effectively than additional transmit power.
• For solar nodes, calculate daily energy use and worst-month solar input, then include battery reserve for poor weather.

Common mistakes​

• Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
• Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
• Increasing transmit power cannot repair mismatched encryption keys or modem presets and may create unnecessary interference.

Final check​

Power-cycle both nodes and repeat the same bidirectional route test. Save region, preset, antenna, RSSI, SNR and delivery rate while keeping channel keys and precise locations private.