Skip to main content

Meshtastic part 5: find the problem, don't just change settings

Beginner to intermediate · A practical guide to repeatable tests

A Meshtastic node may work well over radio but fail to appear on an MQTT dashboard. Or its public map may show a node you cannot actually contact over radio.

Those are different problems, and changing the antenna won't always help. Start by deciding which part of the system you're testing.

Five parts of the communication path​

  1. Power and hardware: Is the device actually on, running compatible firmware and connected to a suitable antenna?
  2. Radio settings: Do the radios use compatible frequency/slot, region, LoRa preset and channels?
  3. RF propagation: Can a usable signal cross the physical path between stations?
  4. Applications and optional peripherals: Is the phone connected, the message interpreted and any sensor/GPS working?
  5. IP/MQTT service: If used, does the gateway reach the broker, and are topics, keys and directions configured appropriately?

A problem in part 5 doesn't prove a problem in parts 1–4.

Troubleshooting by symptom​

SymptomFirst things to check
Phone cannot connect to the nodePower, Bluetooth permissions/pairing, compatible app, USB/Wi-Fi as applicable
Two nodes can't exchange even one local messageActual RF link, on-air region/frequency slot, preset, channel name and PSK, antenna
Some nearby nodes show, but no messages arriveWhether those nodes are on the same readable channel; what the node list really proves
Messages travel through MQTT but not direct RFVerify gateways, disable MQTT, try a controlled local radio-only experiment
Messages vanish after an Internet outageA previously working path may have been MQTT-dependent; test radio-only peers
Node appears on map but never in local RF testsMap data may be reported over Internet; check reception and reporting source
Device reports power but no temperatureNo supported environmental sensor, sensor disabled, unsupported pins or I²C issue
Temperature displayed but no remote telemetryReporting interval, telemetry module, RF reception, channel conditions
GPS doesn't change after movementFixed position, stale satellite fix, phone permissions, broadcast interval
Traffic slows when every node reports frequentlyChannel use, airtime, too-frequent telemetry/position, over-aggressive repeaters and MQTT downlinks

The RF-only test: the most important baseline​

Have two of your own compatible nodes at safe, accessible locations. Leave both powered by batteries or suitable independent supplies.

  1. Disable MQTT module connectivity and/or all channel uplink/downlink settings for the test. Confirm neither node is using an Internet-assisted route.
  2. If using a phone, connect locally through Bluetooth or another supported non-Internet interface.
  3. Temporarily turn off the phone's cellular and Wi-Fi connections if practical; the client interface should still work on supported Bluetooth-connected devices.
  4. Confirm compatible on-air region, LoRa preset, frequency slot and channel configuration.
  5. Send several short messages and record which ones actually arrive at the receiving radio.
  6. Change one physical condition, such as antenna orientation or a safe ground-level placement, then repeat.
  7. Record failures as well as successes.

This experiment demonstrates performance over the tested local RF path. It doesn't establish state-wide coverage, and success with two radios doesn't prove every part of the wider network will remain powered.

Now test an MQTT gateway separately​

Only use gateways and brokers you're authorized to configure.

  1. Establish the radio-only baseline first.
  2. Enable the chosen MQTT uplink and confirm packets arrive in the intended authorized topic or application.
  3. If you deliberately need downlink, configure it on a suitable channel after reviewing traffic and broker policies.
  4. Keep the radio powered but disconnect the gateway's Internet/Wi-Fi path.
  5. Confirm local RF messages still arrive where a direct or independent radio path exists.
  6. Confirm the remote MQTT-only path has stopped or become unavailable.
  7. Restore Internet and verify the broker reconnection and reporting state.

Don't test an Internet outage by switching off your only repeater: if it was also relaying messages on RF, you will not know whether the radio or Internet side caused the failure.

The offline readiness checklist​

ComponentQuestion to ask
Radio powerCan each essential node run if utility power fails? Battery, solar and run-time matter.
Local antenna pathCan the necessary stations actually hear each other through radio-only hops?
Client interfaceCan you access your messages without cell service, a remote website or an Internet sign-in?
Message/settings compatibilityAre the intended peers on compatible LoRa settings and channel keys?
Location and telemetryDo GPS and sensors work locally, and which readings survive without dashboards?
MQTT gatewayIs any essential route secretly dependent on Wi-Fi, cellular, a router, a broker or a remote VPS?
Written fallback planDo users know which local channels, power supplies and peers work without Internet?

If the application depends on remote map websites, online brokers, or other sites for essential information, it's a hybrid solution. That may be fine—just describe its limitations accurately.

Why MQTT traffic can complicate troubleshooting​

The Meshtastic public MQTT service has rules intended to limit public-broker traffic on RF, including a documented zero-hop policy for broker-origin messages. It also may restrict location precision and which packet types are passed along. Privately operated brokers can have different rules and may cause undesirable duplicate traffic when gateways publish/subscribe too broadly.

It is normal to see different results in a radio node list, a nearby-radio map, a broker monitoring tool, and a website that aggregates reports. These tools are showing different data sources.

Best practice: compare like with like. When testing your antenna, use a known local radio observer and repeatable packet measurements rather than judging success solely from a global map.

More problems that aren't antenna problems​

Wrong channel key​

Two stations may share a frequency and still be unable to read the other's channel messages. A public channel's shared key isn't proof of privacy. Check the channel name/PSK settings on both devices.

Poor GPS reception​

Satellite fixes may fail inside buildings or vehicles depending on device and antenna. This does not necessarily affect text messaging over LoRa. Review fixed-position and phone-location options before assuming the node is defective.

No environmental data​

An environmental module setting cannot create a temperature or pressure sensor that isn't physically present. Verify supported hardware, power, pins, I²C addresses and local sensor detection first.

Airtime congestion​

Repeated position reports, telemetry, too many high-priority routers and MQTT downlinks can compete for limited RF airtime. Before turning up transmit power, consider whether you are sending more packets than the mesh can handle.

Firmware and app version differences​

Menus, supported device roles and defaults change as Meshtastic develops. Read the current official documentation for your version instead of assuming a screenshot or command from years ago still applies.

A simple field log​

You don't need complicated monitoring software. Record the test conditions:

ItemExample
Time and test siteAfternoon, open field / indoor building
Node hardware and firmwareExact model and installed version
Operating settingsRegion, preset, frequency slot, channel identifier (not secret key)
MQTT stateDisabled / uplink-only / uplink and downlink
Antenna and powerActual antenna type, cable and battery level
Results10 packets sent, number received, RSSI/SNR if available
Environmental observationsTerrain, weather, equipment position and interference

Do not post private channel keys, exact private locations or broker passwords to a public forum.

Further learning​

Bring a repeatable observation or failure case: Ask in the community forum. A useful report explains what you tried and what happened, without making anyone feel foolish for not knowing the answer.