Meshtastic FAQs - Part I

Meshtastic FAQs - Part I

Making that first contact

What am i doing wrong

Being part of the Meshtastic community for a while, I’ve seen the same questions come up again and again. This is the start of a short FAQ-style blog series where I’ll gather those common headaches, expand on the usual short forum replies, and add the extra context that actually helps. These posts will also be added to the website’s Docs/FAQ section.

Let’s get you connected.

1. Why don’t I “hear/see” any other nodes?

Not seeing any other nodes in your list (or on the screen/app) is the most common frustration for newcomers. Meshtastic only communicates when settings match exactly, and everything depends on real LoRa reception, direct or via hops.

Here are the usual suspects and how to fix them:

Antenna issues

This is almost always the first thing to check. No antenna, loose connection, or the wrong antenna means you’re probably not hearing anyone (and you may have stressed the transmitter).

A 433 MHz antenna looks identical to an 868 MHz one, but they are completely incompatible.

Fix:

Make sure you have a proper 868 MHz antenna securely connected (for EU868 devices, especially here in Sweden).

No one transmitting nearby

You’ve seen the impressive YouTube videos with 100+ km links and busy city meshes… then you switch on your node and hear nothing but silence. That’s a very common experience.

Fix:

Check the public maps (meshtastic.liamcottle.net is a good start) for active or recently active nodes in your area. Look for local Meshtastic groups on Facebook, Discord or Reddit and say hello. Sometimes the whole mesh really does start with just you and one friend.

Physical / range issues

LoRa works best with line-of-sight. Walls, hills, trees, being indoors or low elevation can block signals completely. Nodes only show up once they successfully receive a packet.

Fix:

Take the node outside with a clear view of the sky. Raise the antenna a little if you can. Check the SNR/RSSI values in the app. For testing, try increasing the hop limit to 5 - 7 (default is 3).

Mismatched channel settings or encryption keys

This is one of the biggest reasons people can’t see each other. Everything has to match: primary channel, region (EU868), frequency slot, and PSK.

Fix:

Share your channel settings with a QR code or link. For easy testing, reset to defaults or create a secondary channel with PSK set to AQ== (public, no encryption).

Wrong LoRa modem preset or region

A node on LongSlow simply can’t talk to one on ShortFast.

Fix:

Go to Radio Configuration => LoRa and make sure both nodes use the same preset (LongFast is the most popular choice) and the correct regulatory region.

Node role misconfiguration

Having too many nodes set as ROUTER or REPEATER can create congestion and collisions.

Fix:

Set handheld and mobile nodes to CLIENT or CLIENT_MUTE. Reserve ROUTER for fixed, well-placed relay stations.

Firmware / MQTT confusion

Older firmware can cause compatibility problems, and public maps mostly show MQTT-relayed nodes (your local LoRa mesh can be completely separate).

Fix:

Update to the latest firmware. If you’re using the app, try clearing the cache or reconnecting.

Electromagnetic interference

Less common, but things like noisy power supplies or LED lights can raise the noise floor so high that signals get drowned out.

Fix:

An SDR dongle can help you see what’s really happening on the frequency.

My favourite starting point

Try this first, it solves the problem for most people:

1. Match region + channel + set PSK to AQ==
2. Test with two nodes right next to each other
3. Once that works, gradually move them apart

2. I’m seeing nodes but my messages show the cloud-with-line-through-it icon

That icon means the message didn’t get through or never received an acknowledgment.

Meshtastic uses managed flooding: your node sends the message, others rebroadcast it, and if you hear the rebroadcast you stop retrying (that’s your quiet “OK, it arrived”). No rebroadcast = eventual failure.

Common reasons: no route, channel/PSK mismatch, too many routers causing collisions, low hop limit, or just temporary congestion.

Quick test: Send a message to a node (or your second device) that is physically very close. If that works, the issue is further out in the mesh, not with your own transmitter.

3. I see nodes on the map but I can’t DM them

Public maps mainly show MQTT-relayed nodes. Seeing someone on the map does not mean you have a working LoRa path to them.

DMs need an actual multi-hop LoRa route. If you don’t see any hops or SNR values locally, there’s no real connection.

Closing

This isn’t everything, of course. Meshtastic is still very much a frontier. We’re not passive consumers; we’re pioneers. A bit of confusion, some debugging, and happy experimenting are all part of the fun.

Don’t give up. Try a different angle and you’ll probably crack it.

You’ve got this! Now go make that first contact, and come back and tell us how it went. We’d love to hear the story.

Written by JohanV
2026-03-01