Recommended Settings

MeshCore settings need to match.

MeshCore nodes need matching radio parameters to hear each other. A mismatch in frequency, bandwidth, spreading factor, coding rate, or preset can make a node appear silent even when nearby activity exists.

Flood advert interval

Use a flood advert interval of 47 hours where that setting is exposed. This helps avoid every node advertising at the same time every day.

Channels

New users can start in Public. For broader Massachusetts discussion, look for #ma-mesh. For general test messages, use #test. For health-check testing, use #ma-hc when a health-check service is available.

Channel details may change as local tools, maps, health checks, and bots are added. Check Discord if you are unsure which channel to use.

Private and public channels

Do not treat public or shared-key channels like private secure messaging. Keep public messages plain and avoid posting private addresses, credentials, screenshots with sensitive details, or anything that could put someone else at risk.

Repeaters and path hashes

Fixed relay-style MeshCore nodes should use the same local radio settings. Nearby Massachusetts MeshCore examples use 2-byte path hashes for repeater deployments.

If you are intentionally configuring a MeshCore repeater and your firmware or app exposes the CLI, the command is:

set path.hash.mode 1

Do not start with repeater behavior just because the option exists. A poorly placed repeater can add noise without improving useful local reach.

Most Meshtastic users should stay on LongFast and CLIENT.

Meshtastic is easiest to start with when you leave the common defaults alone. In this area, normal users should generally use the United States region, the LongFast / Long Range Fast preset, the default LongFast primary channel, and the default key.

Do not start by changing roles

For most users, CLIENT is the correct role. Infrastructure roles such as ROUTER, REPEATER, ROUTER_CLIENT, or ROUTER_LATE should be reserved for fixed sites with good height, power, antenna placement, and a clear reason.

Location settings

Location sharing is useful for maps and testing, but exact home locations do not need to be public. Use approximate location settings when appropriate, especially for a home node.

MQTT

Normal users do not need MQTT to participate. Treat MQTT as map, observer, or integration infrastructure, not as a beginner setup step.

Maps and health checks come later.

Hampden County Mesh is preparing future map, health-check, bot, and observed-activity tools. Those tools are separate from normal beginner setup.

A normal node with the right settings should be enough to begin local testing. Future map and health-check tools should help explain activity, not become a requirement for participation.

• Use Coverage for local terrain notes and MeshMapper links.
• Use MeshCore or Meshtastic basics pages for system-specific role information.
• Do not publish broker credentials, private locations, or sensitive screenshots.
• Do not assume a map point means your device can directly reach that node.

A simple working node is better than a complicated broken one.

• Do not change frequency, bandwidth, spreading factor, coding rate, or region unless you know exactly why.
• Do not use Meshtastic router or repeater roles for a normal handheld, desk, car, or backpack node.
• Do not enable MQTT just because the setting exists.
• Do not publish exact home locations when approximate location is enough.
• Do not assume maximum transmit power is always better.
• Do not judge local reach from one indoor test. Try a window, porch, yard, vehicle, park, hill, or other real location.

If you hear nothing, check the simple things first.

• Confirm you are using the correct region or preset.
• Confirm all MeshCore radio parameters match exactly.
• For Meshtastic, confirm LongFast/default and AQ==.
• Make sure the antenna is attached before transmitting.
• Try a better location, especially near a window or outside.
• Charge the device and restart the app if the device connection is acting strange.
• Ask in Discord and include your device model, firmware, rough town or area, antenna, and what settings you used.