3 min read

MeshCore Regions

Planning the rollout MeshCore regions on the IdahoMesh...
MeshCore Regions
Photo by Vidar Nordli-Mathisen / Unsplash

Regions on IdahoMesh

Regions are changing! We're starting to transition to a new region naming scheme, this page has been updated to match the new setup.

Region filtering is a MeshCore feature that allows messages to be scoped to specific geographic areas. This reduces unnecessary network traffic by keeping local conversations local, while still allowing mesh-wide communication when needed. Please see the FAQ at the bottom

How It Works

When you send a message on a group channel, you can choose to either:

  • Send globally (default) — Your message is repeated by all repeaters on the mesh
  • Send to a region — Your message is only repeated by repeaters configured for that region

Update (August 2026): IdahoMesh is adopting the new emerging standard Pacific Northwest region hierarchy used by our neighboring mesh communities. Our repeaters now carry west, pnw, id, sw-id, and (in the Treasure Valley) boi — replacing the single #idaho region we set up when regions were first introduced to MeshCore. #idaho remains configured on existing repeaters during the transition, so nothing breaks.

For Regular Users

You don't need to do anything. By default, your messages are sent globally and will continue to work exactly as before.

If you want to scope your messages (recommended only after most repeaters are configured):

Mobile App

  1. Open a group channel chat (like #idahomesh)
  2. Tap Set Region Scope
  3. Select id region

The channel title bar will show which region your messages are scoped to. Your scope preference is saved per channel, so you only need to set it once. You can see which region tags are live near you with Tools → Discover Regions in the app.

For Repeater Operators

You'll need to configure your repeater with the new region tags. If you don't, messages scoped to those regions will not be repeated by your repeater. Configuration is easy — on current firmware (1.16.0+) it's one line:

region def west pnw id sw-id boi
region save

Outside the Treasure Valley but in SW Idaho, drop boi. If you configured #idaho back in January, Full steps are on our Add A MeshCore Repeater page.

Rollout Plan

Phase 1 (Now): Repeater operators add the new tags. No user action required — global messaging continues to work.

Phase 2 (Fall 2026): Once most repeaters are configured, we'll encourage users to set channel scope to boi, sw-id, or id for local channels

Phase 3 (Future): We may eventually need to limit unscoped flooding on IdahoMesh repeaters to reduce unintentional cross-region traffic. We'll communicate that change well in advance.

FAQ

Will my messages stop working if I don't set a region?

No. Global/legacy messages (the default) are still forwarded by all repeaters. You only need to set a region if you want to limit where your messages go.

What if I set my scope, but some repeaters aren't configured yet?

Your message will be forwarded by any repeater that carries that tag. Repeaters that don't carry it will not forward your scoped message — which is why we roll out repeater config before encouraging users to scope.

Can I send to multiple regions?

You can only scope a message to one region at a time. If you need mesh-wide reach, use the global/wildcard scope (the default).

What happened to #idaho?

It was our starting point before the regional hierarchy matured. It still works on repeaters that carry it, but as regions have evolved, a new standard has emerged.

What about other regions / sub-regions?

Other regions around the state are starting to align on this new emerging standard, in general all repeaters in the state should have west, pnw and most importantly id. It appears meshes across Idaho are going with the sw-id, e-id, s-id, c-id and n-id scheme.

Questions?

Join our Discord community; we're happy to help!