Meshtastic Basics

What Meshtastic is

Meshtastic is open-source firmware and software for compatible LoRa radio devices. Nodes can exchange short messages, position information, telemetry, and other small packets over radio.

A typical personal node connects to a phone, tablet, or computer through a Meshtastic client application. The radio handles the LoRa connection while the application provides the main messaging and configuration interface.

How Meshtastic fits here

Hampden County Mesh supports both Meshtastic and MeshCore. MeshCore remains the main focus for HCM’s shared regional infrastructure, observer systems, live map, and current coverage work.

Meshtastic remains useful for people who already operate Meshtastic nodes, portable communication, position sharing, telemetry, hardware experimentation, and participation in other Meshtastic communities.

Start with one normal node

Use supported hardware, install the current firmware, and get one device working before changing specialized roles, hop limits, frequency slots, or internet integrations.

1. Install the correct firmware. Use the official flasher or the instructions provided for your specific supported device.
2. Connect a client application. Depending on the hardware and platform, this may use Bluetooth, USB, Wi-Fi, or a network connection.
3. Select the United States region. The region controls the legal frequency plan and related radio limits.
4. Use the regional LongFast starting point. Matching modem settings are necessary to hear and relay the same radio traffic.
5. Leave the device role on CLIENT. This is the ordinary starting role for personal and general-purpose nodes.

How the Meshtastic mesh works

Nodes using compatible LoRa modem settings can hear and rebroadcast radio packets even when they do not share the same messaging-channel encryption key. The key determines whether the message contents can be read, while the modem settings determine whether the radio packet can be received.

Region

Selects the frequency plan and limits appropriate for the country where the node is operating.

Modem preset

Controls radio parameters such as bandwidth and spreading factor. Devices need matching settings to participate in the same radio mesh.

Frequency slot

Determines the actual LoRa frequency used within the regional band. A custom primary-channel name can affect the automatically selected slot.

Messaging channel

Defines a message group using a channel name and encryption key. One primary channel and up to seven secondary channels can be configured.

Hop limit

Limits how many rebroadcasts a packet may travel through. Raising it unnecessarily can increase congestion rather than improve delivery.

The default public channel

The default LongFast primary channel uses the publicly known AQ== key. It is useful for public participation and testing, but it should not be treated as private communication.

Hampden County Mesh does not currently maintain a separate regional Meshtastic channel. Use the built-in LongFast public channel unless you are coordinating a different channel with a specific group.

Private channels

A private secondary channel should use a randomly generated key shared only with the intended participants. All participating devices need the matching channel configuration.

Device roles

A role changes forwarding behavior, power use, visibility, and sometimes access to Bluetooth or other interfaces. Do not select a role merely because its name sounds more capable.

CLIENT Normal starting role

Sends and receives messages and can intelligently rebroadcast packets when useful. This is the correct choice for most personal and general-purpose nodes.

CLIENT_MUTE Does not relay

Sends and receives its own traffic but does not rebroadcast packets for other devices. It can be useful for an indoor or handheld node located near a better-positioned node.

CLIENT_BASE Personal base node

Gives forwarding priority to favorited personal nodes. It is intended for a better-positioned home or base node supporting a user’s weaker nearby devices.

TRACKER and SENSOR Specialized devices

Prioritize position or telemetry behavior and may use specialized sleep patterns. Use them for an actual tracking or sensing purpose.

ROUTER and ROUTER_LATE Planned infrastructure

Change rebroadcast timing and infrastructure behavior. Poorly placed or unnecessary routers can increase collisions and reduce network performance.

REPEATER Deprecated

The official documentation marks this role as deprecated in current firmware. Do not use older instructions that recommend it for a new installation.

Location sharing

Meshtastic can obtain position data from an integrated GPS receiver, a paired phone, or a manually configured fixed position. GPS information is not required for ordinary messaging.

Position sharing is configured per messaging channel. The precision setting ranges from 0, which sends no location on that channel, to 32, which sends full precision.

Telemetry

Meshtastic can report ordinary device information such as battery level, voltage, channel utilization, and airtime. Supported external sensors can also provide environmental, air-quality, and other measurements.

Telemetry uses radio airtime like other mesh traffic. Use reasonable update intervals and enable only the measurements that serve an actual purpose.

MQTT

MQTT allows selected Meshtastic packets to pass between a radio mesh and an MQTT broker when an internet connection is available.

Enabling the MQTT module alone is not enough. Individual messaging channels also need uplink or downlink enabled before their packets cross the gateway.

Uplink

Allows messages from the local radio mesh to be forwarded toward the configured MQTT broker.

Downlink

Allows packets arriving through MQTT to be transmitted onto the local radio mesh.

Client proxy

Allows a connected client, such as a phone, to provide the internet path when the radio itself does not have Wi-Fi or Ethernet.

Map reporting

Can publish an unencrypted report containing node identity, hardware, firmware, role, and location with configurable precision.

If a Meshtastic node seems quiet

1. Confirm that the United States region is selected.
2. Confirm that the expected modem preset and frequency slot match.
3. Confirm that the messaging-channel name and key match.
4. Leave the device role on CLIENT while troubleshooting.
5. Make sure the correct antenna is attached securely.
6. Check that the phone or computer remains connected to the node.
7. Leave the radio powered long enough to hear normal activity.
8. Try a window, outdoor location, vehicle, or higher ground.
9. Change one setting at a time.

Where to go next