Troubleshooting

New to the mesh and something isn’t working? Start here. These are the most common issues people run into when setting up a node in the Amarillo area.

Meshtastic

I don't see my node on PotatoMesh or MeshMonitor

PotatoMesh and MeshMonitor both show nodes that our ingest node (TC-CMD) has heard over RF. If your node isn’t showing up on either dashboard, it means TC-CMD hasn’t received a packet from you yet. Here’s what to check:

1. Verify your channel settings

Your node must be on the LongFast channel (the default Meshtastic preset) to be heard by the mesh. If you’ve changed the modem preset, added encryption keys, or switched to a private channel, your packets will be invisible to other nodes.

Setting	Expected Value
Region	United States
Modem Preset	Long Range Fast
Channel	LongFast (default)

2. Make sure position broadcasting is on

Both dashboards place nodes on the map using their broadcast position. If position sharing is disabled, your node won’t appear on either map even if TC-CMD can hear your messages.

In the Meshtastic app: Settings > Position > Position Broadcast — make sure it’s enabled with a reasonable interval (1 hour is a good default).

You can also set a fixed position instead of using GPS. This is useful for stationary indoor nodes that don’t have a GPS lock.

3. Check whether you can see TC-CMD

Open your Meshtastic app and look at the node list. If you can see TC-CMD, it can almost certainly hear you too — RF is roughly symmetric. If TC-CMD doesn’t appear in your list at all, your packets likely aren’t reaching it.

4. Increase your hop count

The default hop count is 3, which works for most situations. But if you’re on the edge of the mesh or there aren’t many relay nodes between you and TC-CMD, your packets may run out of hops before they arrive.

Try bumping your hop count to 5. Don’t go higher than you need — every extra hop adds airtime for the entire network.

5. Improve your antenna or placement

This is the single biggest factor in range. A radio sitting on a desk with a stock rubber duck antenna will have a fraction of the range of one mounted near a window or elevated with a tuned antenna.

• Get up high — a second-story window, attic, or rooftop makes a massive difference
• Upgrade the antenna — even a cheap 915 MHz fiberglass antenna ($10–15) dramatically outperforms the stubby antennas that ship with most radios
• Avoid obstructions — LoRa loves line of sight; interior walls, metal roofing, and dense trees all reduce range

6. Be patient

PotatoMesh doesn’t poll — it populates nodes as it hears them broadcast. Depending on your node’s broadcast interval, it may take up to an hour for your position to appear and several hours before your node shows up consistently.

My messages aren't showing on PotatoMesh or MeshMonitor

Both dashboards only display messages that TC-CMD can decode. A few things can prevent this:

• Direct messages (DMs) are encrypted to a specific node. Unless your DM is addressed to TC-CMD, it won’t appear on the dashboard. Try sending a message on the LongFast primary channel instead.
• Private channels with encryption keys that TC-CMD doesn’t share won’t be decoded. Only messages on the default LongFast channel appear.
• Range — same as above. If your packets aren’t reaching TC-CMD, your messages won’t show up either.

My node shows up but with the wrong position

If your node appears on the dashboard but in the wrong location, check your position settings:

• GPS lock — if your node has a GPS module, make sure it has a clear sky view. GPS needs time to acquire satellites, especially on first power-up.
• Fixed position — if you’re using a fixed position, double-check the coordinates. A typo in latitude or longitude can place you in a completely different area.
• Stale position — if your node was previously at a different location, the old position may persist until a new one is broadcast.

I can hear others but nobody hears me

If your node list is populated but nobody seems to receive your messages:

• Check your transmit power — some devices default to low power. In the Meshtastic app, check Settings > LoRa > TX Power and make sure it’s set to an appropriate level (typically the maximum your device supports).
• DIY hardware — Raspberry Pi Pico builds with SX1262 LoRa hats can work, but they sometimes have lower effective transmit power or antenna matching issues compared to purpose-built LoRa radios. Consider testing with a known-good radio to rule out hardware issues.
• Role — make sure your role is set to Client (not Client Mute, which suppresses rebroadcasts).

I'm not sure I have the right hardware

Most LoRa radios that support Meshtastic work in the Amarillo area. The key requirements are:

• 915 MHz band (US ISM band) — make sure your radio isn’t a 433 MHz or 868 MHz variant
• SX1262 or SX1276 LoRa chip — both are well-supported by Meshtastic
• Meshtastic firmware support — check the Meshtastic supported hardware list for your specific board

DIY builds (Raspberry Pi Pico, ESP32, etc.) work but require more setup and may have lower performance compared to purpose-built devices like the Heltec V3 or RAK WisMesh Pocket.

---

Still stuck?

If your messages are reaching the mesh, try asking for help there first — someone nearby may be able to troubleshoot with you in real time over RF.

Otherwise, reach out online: