Meshtastic part 1: making your first radio connection
Beginner level · No MQTT or Internet service needed for the basic radio test
A first Meshtastic experiment should answer a simple question: Can two radios communicate over LoRa without the Internet? Do that before configuring brokers, dashboards, public maps or a permanent repeater.
The pieces involved
| Piece | What it actually does |
|---|---|
| Meshtastic radio | Runs the firmware and uses a LoRa transceiver to transmit and receive short packets |
| Antenna | Couples the radio's signal to the surroundings; must suit the radio's operating band |
| Phone or computer | Provides a convenient app, keyboard, screen or management connection |
| Other Meshtastic nodes | Receive compatible packets and may relay them when configured and able |
| MQTT broker | Optional Internet infrastructure, not required for a local radio link |
A phone linked to a Meshtastic node by Bluetooth can be offline from the cell network while the node continues to use LoRa. Hardware without onboard Bluetooth may use other supported interfaces.
Before you power up or transmit
- Identify your exact hardware model and frequency variant. LoRa modules built for different bands are not interchangeable simply because their connectors look alike.
- Attach an appropriate antenna as the device maker directs before enabling transmission.
- Install a supported firmware version using official getting-started and flashing instructions. Don't select an image based only on a similar-looking board.
- Use the correct regulatory region, usually US for the United States, subject to equipment and applicable rules. Do not choose another region to bypass limitations.
- Charge the battery or provide a suitable supply; unreliable power can look like an RF problem.
- Learn whether your device has GPS, supported sensor pins, Wi-Fi, Bluetooth or a display. Not all models support every feature.
A careful first-contact experiment
What you need: two compatible Meshtastic nodes and a way to access at least one client interface. Do this on frequencies and with hardware authorized for your location.
- Connect each device to its supported app or computer interface.
- Confirm the correct region, frequency slot and LoRa modem preset. Both nodes must be radio-compatible.
- Make sure they share a suitable communication channel with compatible channel name and pre-shared key.
- Keep the radios reasonably close but not touching, and avoid enclosing the antennas in metal.
- Send a short test message from one node and check the other node's interface.
- Note what actually happened: did the second node show the message, did it arrive after a delay, and did an acknowledgment or receive report appear?
For the clearest first experiment, disable MQTT uplink and downlink and leave Internet connectivity off. That way a successful message is not silently being carried by an online gateway. Later, you can turn MQTT on deliberately and compare.
What needs to match?
Two stations in range generally need compatible operating band, region-specific channel/frequency slot and LoRa modulation parameters. Channels also need compatible names/keys for the intended message group.
A LoRa preset controls the tradeoff between on-air time, data rate and sensitivity. Two radios using different presets can fail to hear each other even while operating in the same region.
A channel is a configured group for messages. The primary channel's name can also influence the automatic frequency-slot selection, so changing it may unexpectedly move you away from other nearby users when the slot is set automatically.
Learn more from Meshtastic's official radio-settings guide and channel configuration.
The channels and encryption distinction
A Meshtastic node can have a primary channel and additional configured channels. Channel names, keys and options help control which messages the app can read; they do not create unlimited separate RF bandwidth. Devices with compatible on-air settings still share airtime.
A is used by channel members to decrypt that channel's message payloads. A default, publicly known channel key is not private simply because encryption is enabled. Never publish a private key or a QR code containing it.
An important nuance: radios may rebroadcast packets they cannot personally decrypt, depending on their rebroadcast settings. That's one reason receiving a packet, relaying it and being able to read it are different concepts.
Which device role should I choose?
For a first handheld or home experiment, CLIENT is the normal starting point. It can send, receive and intelligently help rebroadcast some packets.
| Role | Plain-language purpose | Tradeoff |
|---|---|---|
| CLIENT | Normal personal node, often connected to an app | Good default for beginners |
| CLIENT_MUTE | Personal node that doesn't forward others' traffic | Useful near better placed infrastructure or in a congested mesh |
| CLIENT_BASE | Personal base designed to prioritize your favored nodes | Helpful for a stronger home node serving weaker personal nodes |
| TRACKER | Prioritizes position broadcasts | Specialized behavior and power tradeoffs |
| SENSOR | Prioritizes telemetry broadcasts | Specialized behavior and sleep/receive tradeoffs |
| ROUTER / ROUTER_LATE | Infrastructure-oriented retransmission behavior | Requires good site placement and understanding of airtime; avoid choosing one just because it sounds powerful |
Role details change between firmware versions. Some older roles have been deprecated, so consult the current device configuration rather than following an old screenshot or forum command.
Why not set every node to router? More broadcasting can create congestion; the network's sharing rules and timing matter just as much as raw radio coverage. A badly positioned high-priority node can be less helpful than a properly placed ordinary client.
What limits a mesh?
Every and rebroadcast uses constrained radio airtime. Relays can help around terrain and buildings only if each hop has a workable RF path. More nodes do not automatically improve message delivery, and a public online map does not prove that a direct over-the-air path exists.
In addition to protocol settings, verify antenna placement, feedline loss, power stability and RF interference. See our antenna learning path.
Troubleshooting the first test
| Symptom | Start by checking |
|---|---|
| Devices pair with phones but cannot exchange messages | Region, LoRa preset, frequency slot, channel setup, keys and actual RF range |
| Node appears on an Internet map but not over RF | Map/MQTT reporting path; try a controlled radio-only exchange |
| Device only receives a few nearby nodes | Antenna band, mounting, interference, terrain and radio compatibility |
| Messages are delayed | Congestion, rebroadcast timing, poor signal or route conditions |
| Battery drains unexpectedly | GPS, screen, radio activity, Wi-Fi, sleep settings and firmware/device characteristics |
Try it next
Once you've proven direct radio communication, choose one additional feature at a time:
- Add MQTT and compare on-air and online paths.
- Add an environmental sensor and share a measurement.
- Test GPS and position sharing with privacy controls.
- Follow the offline resilience checklist.
Official starting points: Getting Started, Radio Settings, Device Roles.
Questions welcome: Northern Michigan Mesh forum.