Hampden County Mesh

Recommended Settings

Start with the regional radio settings, ordinary client roles, and as few custom options as possible.

Use the regional starting point first

Radios need compatible settings to communicate. Begin with the settings used around Western Massachusetts before changing frequencies, modem presets, node roles, channels, or infrastructure options.

These settings were reviewed in July 2026. Project defaults and application labels can change, so use the current official documentation when an app or firmware release presents different options.

Settings at a glance

These are starting recommendations, not a requirement that every device serve the same purpose. Begin here, confirm the radio works, and make later changes deliberately.

Main local focus

MeshCore

Use the USA/Canada recommended preset wherever the app or web flasher provides it.

Preset
USA/Canada (Recommended)
Frequency
910.525 MHz
Bandwidth
62.5 kHz
Spreading factor
SF7
Coding rate
CR5
Read MeshCore Basics →

Also supported

Meshtastic

Stay close to the ordinary public defaults unless you are intentionally joining another configured network.

Region
United States / US
Modem preset
LongFast / LONG_FAST
Primary channel
Default LongFast public channel
Primary key
AQ== — public default-key shorthand
Device role
CLIENT for ordinary user nodes
MQTT module
Off unless intentionally operating an integration
Read Meshtastic Basics →

MeshCore settings

MeshCore nodes must use matching frequency, bandwidth, spreading factor, and coding rate settings to participate in the same radio network.

Use the named USA/Canada recommended preset when it is available rather than manually entering each parameter. This reduces mistakes and makes it easier to compare your configuration with other local users.

Ordinary companion devices

A normal companion node usually does not need custom repeater commands, automatic infrastructure adverts, or experimental path settings. Apply the radio preset, give the node an appropriate name, and confirm that it can hear normal activity.

Fixed repeater flood adverts

MeshCore repeaters use a configurable flood-advert interval. The firmware default is not the same as the local HCM recommendation.

Hampden County Mesh currently recommends a 47 hour flood-advert interval for intentionally planned, fixed MeshCore infrastructure. This is an HCM regional recommendation, not a general MeshCore default and not a setting for ordinary companion devices.

On a repeater CLI, the corresponding command is:

set flood.advert.interval 47

Repeater advert path hashes

Repeaters running MeshCore firmware 1.14 or newer can use a longer path hash in their own advert broadcasts. This helps mapping and analysis tools distinguish repeaters whose one-byte identifiers might otherwise collide.

HCM’s current starting recommendation for an updated fixed repeater is:

set path.hash.mode 1

Mode 1 selects a two-byte path hash for that repeater’s own adverts. It does not determine which supported path-hash sizes the repeater forwards.

Meshtastic settings

For ordinary local participation, use the United States region, LongFast, the default public LongFast channel, and the CLIENT role.

The public primary key

AQ== represents the default public channel key. It allows devices using the same standard channel configuration to communicate, but it should not be treated as private or secret.

Device roles

Specialized roles such as ROUTER and REPEATER change how a device participates in packet forwarding. HCM recommends leaving handheld, desk, vehicle, and portable nodes on CLIENT unless the device is part of an intentionally planned infrastructure deployment.

MQTT

Normal LoRa messaging does not require MQTT. Leave the MQTT module disabled unless the device has a suitable internet connection and is deliberately being used for an MQTT integration.

The separate permission allowing another connected node to forward data toward MQTT is not the same as running the MQTT module directly on the device.

After the radio is configured

Maps can help show activity observed through participating systems, but they do not prove that your current device can directly reach every point shown.

Try more than one physical location before changing radio settings. Height, surrounding buildings, terrain, antenna orientation, and indoor placement can make a substantial difference.

If you hear nothing

  1. Confirm that the correct region or named preset is selected.
  2. Confirm that all MeshCore radio parameters match the regional preset.
  3. For Meshtastic, confirm US, LONG_FAST, the public LongFast channel, and the expected key.
  4. Make sure the correct antenna is securely attached.
  5. Restart the radio and reconnect the application if necessary.
  6. Try a window, outdoor location, vehicle, or higher ground.
  7. Change one setting at a time while troubleshooting.
A quiet location is not proof that the radio is defective. Ask what activity other users normally observe in your part of Western Massachusetts before repeatedly changing the configuration.

Where to go next

Still not hearing anything?

Share the device model, firmware version, current settings, and a general description of where you tested it.