My Meshtastic Node Isn't Working: A Troubleshooting Guide

Something isn't working. Maybe your node won't show up in the app. Maybe you're seeing zero other nodes even though you know there are people on the mesh nearby. Maybe your node disappeared from the map and you have no idea why. Whatever it is, you're probably closer to fixing it than you think.

This guide covers the most common Meshtastic problems and how to sort them out. We'll go symptom by symptom. Find yours, work through the steps, and you'll either fix it or know exactly what to tell someone in the NEPAMesh Discord when you ask for help.

Check These Things First

Before diving into specific symptoms, run through this list. These four things account for a huge percentage of problems people bring to the Discord.

Is your antenna actually connected? If you have a board with a U.FL connector (the tiny snap-on type), it's easy to think it's seated when it isn't. Press it down until you feel a definite click. A loose antenna means terrible range and can, over time, damage the radio chip. Never power on a LoRa radio without an antenna attached.

Is your USB cable a data cable? Charge-only USB cables won't let the app or the web flasher see your device. If your computer doesn't recognize the node at all, try a different cable before assuming anything is broken. This is the cause of more "my device won't show up" reports than anything else.

Is your region set correctly? In the US, you want US. A freshly flashed node has no region set, and the radio won't transmit until you set one. Go to Radio Configuration in the app, then LoRa, and confirm the region is set.

Is your modem preset LONG_FAST? That's the default for the NEPAMesh network. If someone changed it to something else, your node can't hear or be heard by any other node on the mesh. Check Radio Configuration, then LoRa, and make sure the preset matches.

If all four of those are fine and things still aren't working, keep reading.

The App Won't Connect to My Node

The Meshtastic app connects to your node over Bluetooth. When that connection fails, the app usually just spins or shows "not connected" without much explanation.

Forget the device and pair again. On your phone, go into Bluetooth settings and remove the node from your paired devices list. Then open the Meshtastic app and add it fresh. Stale Bluetooth pairings cause connection failures more often than any actual hardware problem.

Restart both the node and your phone. Bluetooth state can get stuck. A full restart of both devices clears it. Power the node off completely, power it back on, close the app on your phone, reopen it, and try connecting again.

Make sure Bluetooth is enabled on the node. If someone has been into the device configuration, Bluetooth can be disabled. If you have a node with a display, you can often confirm this from the screen. If you have access through another method (serial cable, another phone that was previously paired), check Radio Configuration under Device.

Check the PIN. Some boards require a PIN to pair. The default is usually 123456. If the app asks for a PIN and rejects it, that's a separate issue from the radio itself.

Try the web client. Connect your node via USB cable and open client.meshtastic.org in Chrome or Edge. If the web client can see and connect to your node, the node itself is fine and the problem is specifically with Bluetooth on your phone.

I'm Not Seeing Any Other Nodes

You're connected to your own node but the node list is empty. Nobody else is showing up.

Give it time. Nodes don't announce themselves constantly. The recommended NodeInfo broadcast interval is four hours. If you just powered on and nobody has broadcast recently, your node list will be empty even in an area with active nodes. Wait 15 to 30 minutes before concluding there's a problem. You can also send a message on the primary channel, which will prompt nearby nodes to respond.

Confirm your channel configuration. The primary channel on NEPAMesh uses the default Meshtastic channel key. If your channel has been changed to a custom key, you won't see nodes running the default. In the app, check your channel list. The primary channel should show "Default" or have the standard key. If you're not sure, you can reset it by deleting and re-adding the default channel.

Check your location on the shadow map. propagation.nepamesh.com shows where the NEPAMesh network has coverage and where it doesn't. If you're in a red zone, you may simply be out of range of any active node. That's not a configuration problem, it's a coverage gap. The node placement guide covers how to think about improving reception from a difficult location.

Verify your antenna. A completely disconnected or wrong-band antenna can mean your node transmits but can't receive, or vice versa. Make sure the antenna is meant for 915 MHz (US band). An 868 MHz antenna, which looks identical, is common on boards shipped for European markets and will work poorly on the US mesh.

My Range Is Terrible

You can see one or two nearby nodes but the network feels thin. Messages take forever or don't make it through.

Check the U.FL connector again. Even if it looked seated, check it once more. A partially connected U.FL connector can pass enough signal to see a node 50 feet away while blocking everything beyond that. This is the most common cause of unexpectedly short range.

Move the antenna away from metal. Metal reflects and scatters 915 MHz. A node sitting inside a metal enclosure, mounted under a metal roof overhang, or placed next to a PC case will show dramatically reduced range compared to the same node in the open. Get the antenna above and away from metal surfaces.

Check your node role. If your node is set to CLIENT_MUTE, it receives and transmits its own traffic but doesn't relay for others. That's correct for mobile use. If you have a stationary home node that you want to participate in routing, it should be on CLIENT. The node roles guide covers when each setting applies.

Check hop count. The recommended hop count for NEPAMesh is 5. If yours is set to 1 or 2, messages can only travel one or two relay hops before they stop. In the app, go to Radio Configuration, then LoRa, and check the hop limit.

Try a better antenna. The stock antennas that come with most boards are functional but not impressive. A proper 915 MHz whip antenna, even a cheap one, will out-perform the stubby included antenna. If you want to go further, the homebrew antenna guide walks through building one for under $10.

My Node Isn't Showing Up on the Map

You're connected, you can see other nodes, but your node doesn't appear on map.nepamesh.com.

Check that MQTT is configured. The map pulls from the NEPAMesh MQTT server. Your node needs MQTT enabled and pointed at the right server. If you haven't done this yet, the MQTT setup guide covers the full process. The server credentials are available in the NEPAMesh Discord.

Check "OK to MQTT" in LoRa settings. This one gets missed constantly. Even with MQTT fully configured, your node won't share data to the broker unless "OK to MQTT" is enabled under Radio Configuration, then LoRa. It defaults to off.

Make sure your node has a position. The map needs coordinates to place your node. Options: built-in GPS (needs a sky view to get a fix), position shared from your phone via the app, or a fixed position set manually in Radio Configuration under Position. If none of those are configured, the map has nothing to display.

Wait for the broadcast interval. Even with everything configured correctly, your node reports its position on a schedule. The recommended interval is four hours. After first configuring MQTT, you may need to wait up to an hour for the first report to come through. You can force an immediate broadcast by briefly disabling and re-enabling the position module in the app.

Check map reporting is enabled. In the MQTT module settings, there's a separate toggle for Map Reporting. Make sure it's on and the interval is set (minimum 3600 seconds).

My Node Keeps Restarting or Crashing

The node reboots randomly, crashes under load, or won't stay running.

Suspect the power supply first. This is the most common cause. LoRa radios draw a burst of current when transmitting, and a marginal power source, a cheap cable, a weak USB port, or a nearly dead battery, may not keep up. Try a different cable and a different power source. A powered USB hub or a wall adapter instead of a laptop port often solves it immediately.

Check the battery. If your node has an 18650 or LiPo battery and it's old, it may no longer hold enough charge to power a transmission burst. A battery that reads 3.7V at rest can drop below the minimum threshold the moment the radio fires. Try running the node on USB power only and see if the crashes stop. If they do, the battery needs replacing.

Check for overheating. Some boards, particularly the ESP32-based ones, run warm. In an enclosed space with no airflow, they can get hot enough to cause instability. If the node feels hot to the touch and crashes after running for a while, ventilation or a different enclosure position may fix it.

Update the firmware. Known bugs in older firmware versions can cause crashes on specific hardware. Flash the latest stable release using flasher.meshtastic.org and reconfigure from scratch. Updating firmware resets all settings, so write down your configuration before you flash.

I Updated the Firmware and Now Nothing Works

This is expected behavior, not a bug. Firmware updates erase your node's configuration. After a flash, you have a blank device that needs to be set up again: region, node name, channel keys, MQTT settings, position, all of it.

If the node won't boot at all after a flash, the most likely cause is a failed or incomplete flash. Open the web flasher, select your device, and choose the option to erase the device before flashing. A full erase and reflash resolves most post-update boot failures.

If the web flasher can't see your device after a failed flash, try holding the boot button on the board while plugging in the USB cable. Most boards have a boot mode that forces the device into a state where it accepts a new flash even when the existing firmware is broken. The specific button varies by board; check the documentation for your hardware.

My Messages Aren't Getting Through

You can see other nodes, you can send messages, but nobody receives them, or you're not receiving messages you should be seeing.

Confirm you're on the same channel. The primary channel key has to match on both ends. If you've set a custom key or someone shared a channel QR code that changed your primary channel, you're on a different channel from the default mesh. Check your channel list and make sure the primary channel is using the default key.

Check hop count on both sides. A message needs enough hops to travel from sender to receiver across the relay nodes between them. If the sender has a hop count of 1 and there are two relay nodes between you, the message dies before it arrives. The recommended setting is 5.

Look at the message delivery indicators. In the app, sent messages show delivery status. A single checkmark means transmitted. Two checkmarks mean acknowledged by the destination. If you're only seeing one checkmark consistently, the message is leaving your node but not reaching the destination, which points to a routing or range problem rather than a configuration issue.

Try a broadcast instead of a direct message. Send a message to the primary channel rather than to a specific node. Broadcasts don't require acknowledgment from a specific device and route differently. If your broadcast goes through but direct messages don't, the issue is specific to the direct messaging path to that node.

Still Stuck?

If you've worked through this and things still aren't right, the NEPAMesh Discord is the right next step. When you ask for help, include: what board you're running, what firmware version, what symptom you're seeing, and what you've already tried. That context cuts the back-and-forth in half and gets you to an answer faster.

Discord is at discord.gg/cSpfk6H2hz.

Meshtastic is a registered trademark of Meshtastic LLC. No warranty is provided. Use at your own risk. This post is not endorsed by or affiliated with Meshtastic LLC.