If you’re setting up a node in Las Vegas, the first thing you want to do is see how far that signal actually travels. Whether you’re aiming for a node across town or just seeing if you can hit a friend a few miles away, range testing is the best way to dial in your setup.

However, the "right" way to test isn't just turning on the Range Test module and letting it rip. In a valley as active as ours, sending automated pings to the LongFast public chat is a quick way to clutter everyone’s handhelds (and a fast way to get your node blocked by others).

Here is the best practice for obtaining accurate data while maintaining a clean local mesh.

The Strategy: The "Private Channel Swap"

To achieve a real-world result, you need to test at the exact same frequency that the rest of us are using. We do this by temporarily swapping our channel slots so your test pings stay private but stay on the "active" airwaves.

1. Move "LongFast" to Slot 1

Keep the public mesh active, but move it to a secondary channel slot to ensure your testing doesn't broadcast to the entire valley.

  • In the Meshtastic App, go to Channels.
  • Add LongFast to Slot 1 with the default key (AQ==).
  • You’ll still see the local chat, but your automated tests won't post there.

2. Make a Private Channel Slot 0 (Primary)

The Range Test module is hard-coded to broadcast on Channel 0.

  • Select Slot 0 and give it a private name (e.g., Range_Test_A).
  • Generate a private key. Both your testing nodes must have this exact same Slot 0 configured.
  • Now, when you start the test, the "Seq #" (or similar) messages stay between your devices only.

3. Lock Frequency Slot 20

This is the most critical step. Usually, Meshtastic changes your frequency based on your channel name. If you use a private name for Channel 0, your radio might jump to a "quiet" frequency where you aren't fighting the local noise.

  • Go to Radio Configuration > LoRa.
  • Manually set the Frequency Slot to 20.
  • This keeps you on 906.875 MHz, the standard for our region, so your test results are actually representative of how the node performs in the real world.

Best Practices for Your Test Run

  • Set Hops to 0: In the Range Test module settings, set Max Hops to 0. You want to know if your two nodes can hear each other. You don't need a node on the other side of town repeating your test pings.
  • 30 or 60 Second Interval: Even on a private channel, don't ping more than once or twice a minute. It keeps the noise floor lower for everyone else and saves your battery.
  • Disable MQTT (preferably leave it off permanently so your are not broadcasting over the internet)
  • Use Local High Points: We have great natural elevation. Spots like Exploration Peak, Lone Mountain, or the edges of Anthem and Summerlin are perfect for testing line-of-sight across the valley without needing to head toward the congestion of the Strip.
  • Reset the Module: Once you're done, remember to toggle the Range Test module OFF so you aren't sending unnecessary pings while you're off the air.


More details: https://meshtastic.org/docs/configuration/module/range-test/