Nevada MeshCore Repeater Settings

⚡ Push straight to the repeater experimental

Your browser can talk to a MeshCore companion node directly. Connect one and the repeater fills in the questions below for you — where it is, and what firmware it's running — then the settings can go over the air instead of through copy-paste. Optional: fill the form in by hand and everything still works.

You'll need the repeater's admin password, and your companion has to already know it as a contact. Connecting, reading its position and checking its firmware are all read-only — nothing is written until you press Send settings.

1 Where is your repeater?

Pick the area your repeater covers. If you connected a companion node above, use its suggestion instead.

or browse

2 Paste this into your repeater

Your region scope

Reset to generated

3 Set the scope on your phone

Regions live on repeaters; scopes live on messages. A repeater only forwards a scoped packet when the scope matches one of its regions. In the MeshCore companion app, set the scope on outgoing traffic to the level you want it to travel:

Messages sent with no scope are still forwarded by everyone, so older nodes and unconfigured clients keep working.

How the region tree works

region def walks a chain: each token becomes a child of the one before it. So region def west nv sounev cla lasveg builds this, top to bottom:

*
└─ west          Western US
   └─ nv         Nevada
      └─ sounev  Southern Nevada
         └─ cla   Clark County
            └─ lasveg   Las Vegas

Your repeater now carries all five names. Traffic scoped prb stays in North County. Traffic scoped slo covers the whole county. Traffic scoped west reaches every repeater in the western US that follows this convention.

Region matching is per name, not per level — a repeater that only has slo and not cc will not forward cc-scoped traffic. That is why every node defines the whole chain from west down, even though it only physically sits in one spot.

region def arrived in firmware 1.16. Before that the same tree is built one name at a time with region put <name> [parent]. On 1.15 that is all you need — regions are flood-allowed as they're created. On 1.14 and older each one also needs an explicit region allowf <name>. Switch the firmware version above and you'll get the right form; the resulting tree is identical either way.

Things worth knowing

• Region names never travel. A scoped packet carries two 16-bit transport codes — an HMAC of the region's key over the packet — not the name. So a code costs the same airtime however long it is: slo and san-luis-obispo-county are identical on the air. Short codes are for your own sake at the console, not the mesh's.
• Region names are one flat namespace. Two different places using the same code will merge on any repeater that carries both. The codes on this site are checked for uniqueness across all of Nevada.
• region def does not wipe the existing tree. If a name already exists, its parent gets updated. To start clean, region remove the unwanted names first (children before parents).
• Review before you save. region def replies with the resulting tree. Check it, then run region save — nothing persists across reboot until you do.
• 160 characters per line on repeater serial. Longer trees have to be split across several region def commands; the cursor resets to * between commands. Every chain on this site fits in one line.
• Region filtering needs firmware 1.10+. Newer commands landed later: set owner.info in 1.12, set path.hash.mode in 1.14, set dutycycle in 1.15 (replacing set af), and region def in 1.16. Check yours with ver and pick the matching version above — if a command still comes back unknown, you're on older firmware than you selected.
• These codes are a community convention, not a standard. MeshCore does not ship a national region list. What matters is that your neighbours use the same names — check with your local mesh group before deploying, and open a PR if your area is missing or wrong.