# Idaho Mesh > A place for Idaho’s Meshtastic, MeshCore, and LoRa mesh enthusiasts to connect and collaborate Public Ghost content for AI and LLM tooling. This file includes a bounded export of public pages first, then recent public posts. Append `.md` to any post or page URL to get the content in Markdown (for example, `/example-post.md`). ## Pages ### About URL: https://idahomesh.org/about/ Last updated: 2026-01-23T08:17:59.000Z # About Idaho Mesh Idaho Mesh is a community for mesh networking enthusiasts across Idaho. We share technical resources, coordinate on larger projects, and connect people interested in LoRa mesh networking. Whether you're into ham radio, outdoor adventures, or just curious about mesh networking, you'll find your people here. ## All Mesh Welcome We're Mesh technology-agnostic. MeshCore, Meshtastic, Reticulum, or something else entirely—each platform has its strengths and tradeoffs, and we believe in using what works for your situation. Many of us experiment with multiple platforms or use different meshes for different purposes. The community includes people running all kinds of mesh tech, and there's plenty of collective experience to draw from. > We're mesh agnostic; all are welcome. ## IdahoMesh (MeshCore) Distinct from "Idaho Mesh" our online community, "**IdahoMesh"** is also the name of the MeshCore network we started. It launched on January 1, 2026, with the first mountain-top MeshCore repeater in Southwest Idaho. In the weeks since, we've established coverage across nearly all of the Treasure Valley and Boise Metro area, with a growing network of repeaters. We're now working to expand into other regions of Idaho. If you're running MeshCore, check out our [MeshCore page](https://idahomesh.org/meshcore/) for settings and guides to get connected. We also have a MeshCore-specific Discord channel. And if you're already on MeshCore, join our `#idahomesh` channel. ## Meshtastic If you're interested in Meshtastic in Idaho, check out our [Idaho Meshtastic](https://idahomesh.org/meshtastic/) page and join the Meshtastic channel in our Discord server. Want to talk with MeshCore and Meshtastic enthusiasts all over Idaho? Come join us on our Discord [IdahoMesh Discord ](https://discord.gg/8mKr4RCznS?ref=idahomesh.org) ### ### Discord URL: https://idahomesh.org/discord/ Last updated: 2026-01-22T06:21:17.000Z Join our Discord server to connect with other Idaho mesh enthusiasts. We discuss node setups, coverage planning, technical questions, and coordinate installations across the state. Whether you're getting started with your first mesh device or looking to expand the network, come chat with us and help build Idaho's mesh community. Want to talk with Mesh enthusiasts all over Idaho? Come join the IdahoMesh discord! [IdahoMesh Discord ](https://discord.gg/8mKr4RCznS?ref=idahomesh.org) And if you haven't already, sign up for our monthly(ish) newsletter. ## The IdahoMesh Newsletter Signup for our email newsletter to stay in the loop on all things Mesh in Idaho. Subscribe Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. ### Idaho MeshCore URL: https://idahomesh.org/meshcore/ Last updated: 2026-08-04T21:52:05.000Z ## IdahoMesh - MeshCore Resources 📡 See our [getting started guide](https://idahomesh.org/getting-started-with-meshcore/) ## Settings IdahoMesh uses the `USA/Canada (Recommended)` preset. ****Coming from Meshtastic?** MeshCore is fundamentally different. Meshtastic nodes constantly broadcast telemetry and advertisements, while MeshCore reserves the limited bandwidth for actual text messages. Most repeaters only advertise every 24-48 hours, so when you're starting fresh, your node map may look empty even with excellent mesh coverage. Be patient—the best way to test your coverage is to send a message. ## Guides [Getting Started with MeshCore](https://idahomesh.org/getting-started-with-meshcore/) [Adding a MeshCore Repeater to IdahoMesh](https://idahomesh.org/add-a-meshcore-repeater/) Settings, guides, and best practices for adding your repeater to the IdahoMesh. [MeshCore Channels, Rooms, and DMs](https://idahomesh.org/meshcore-channels-rooms-and-dms/) A quick explainer on the differences between Channels, Rooms, and DMs. [MeshCore Regions](https://idahomesh.org/meshcore-regions/) Our plan for rolling out MeshCore region support and how to configure your nodes and repeaters in the Idaho region. [Add an Observer to the Mesh](https://idahomesh.org/add-an-observer/) Follow this guide for the easiest way to set up an Observer and begin pushing data to the LetsMesh map to help us map the IdahoMesh. Want to talk with MeshCore and Meshtastic enthusiasts all over Idaho? Come join us on our Discord [IdahoMesh Discord ](https://discord.gg/8mKr4RCznS?ref=idahomesh.org) ## Coverage Maps There are a few maps showing MeshCore usage in Idaho at the moment; we'd love to make the IdahoMesh.org map encompass all of the smaller meshes across the state into one map. But keep in mind that many nodes won't appear on the maps unless people in the area push to one or more of the map sites. So, don't let the fact that there aren't nodes on the map in your area discourage you from trying the mesh. And of course, you can jump into our Discord to discuss usage in your area to get some pointers. [map.IdahoMesh.org](https://map.idahomesh.org/?ref=idahomesh.org) This map relies on "observer" nodes pushing real-time data to our map server. You can [add an observer node](https://idahomesh.org/add-a-letsmesh-observer/) to put nodes in your area on the map. ![](https://idahomesh.org/content/images/2026/08/mqtt_card-1.png) ## Channels While most of us on the IdahoMesh monitor the public channel, our main channel is the `#idahomesh` you can join via the hashtag join button in your MeshCore app, or by scanning this QR code. ![](https://idahomesh.org/content/images/2026/01/signal-2026-01-23-000101-1.png) #### ## The IdahoMesh Newsletter Signup for our email newsletter to stay in the loop on all things Mesh in Idaho. Subscribe Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. ### Add an Observer to the Idaho Mesh Map URL: https://idahomesh.org/add-an-observer/ Last updated: 2026-08-10T05:04:10.000Z The [Idaho Mesh map](https://map.idahomesh.org/?ref=idahomesh.org) shows our MeshCore network in real time — nodes, coverage, packet paths, and channel activity. It's built from **observers**: nodes that forward traffic they here to our mesh map via MQTT. This is one-way for mapping, troubleshooting, and analytics only. Our MQTT server does not bridge repeaters over the Internet. If you run a repeater, room server, or an always-on companion with reliable power and internet, you can put your corner of the state on the map, which helps us grow the mesh. 📡 If you are using a recent version of the [Observer Firmware](https://observer.gessaman.com/?ref=idahomesh.org), you'll find a preset called `idahomesh` which will auto configure your node to push to our mqtt server `mqqt.idahomesh.org` There are many ways with many tools to run an observer; this page doesn't cover each one; it just gives you the settings. Plug them into whatever tool or firmware you use. If you need help, ping us on [Discord](https://idahomesh.org/connect/) or Signal. ![](https://idahomesh.org/content/images/2026/08/idahomesh-obs-1.png) ## Broker settings Point your observer's MQTT publisher at the Idaho Mesh broker. Your node signs in with its own MeshCore key — no password to set. | Setting | Value | | --------- | ------------------ | | Host | mqtt.idahomesh.org | | Port | 443 | | Transport | WebSockets | | TLS | On | | Auth | Token / JWT | | Audience | mqtt.idahomesh.org | **Alternative — shared login:** if your tool doesn't support token auth, use the community login instead. | Setting | Value | | -------- | ------------ | | Username | idaho | | Password | gemstate2026 | **Format:** if your tool has a list of format options, choose **LetsMesh**. If your tool has no format options, use this topic template: `meshcore/{IATA}/{PUBLIC_KEY}/packets` ## Set your region Tag your data to your area with the IATA code of your nearest airport — in most tools this is a "region" / "IATA" field. For example, if you're anywhere in southwest Idaho, use BOI. ### Add a MeshCore Repeater URL: https://idahomesh.org/add-a-meshcore-repeater/ Last updated: 2026-08-10T05:10:33.000Z ❗ Updated Aug 2026 to match our new suggested settings Adding a repeater is one of the best ways to contribute to the Mesh, as they are the backbone of the MeshCore network. Repeaters receive messages from "companion" nodes and other repeaters, then rebroadcast them across the mesh. 💡 **If you're planning to place a repeater in a high-elevation or otherwise high-profile area, please reach out to us on Discord so we can coordinate to improve the overall mesh.* ## Quick Settings Here are the minimum settings you'll need to ensure your repeater meshes well in Idaho. For best results, we recommend a firmware version of `1.16.0` or newer. 1. Use the `USA/Canada (Recommended)` preset 2. Flood Routed Adverts: `47` hours (default in newer firmware) 3. Zero-hop Adverts: `0` minutes (off) 4. Use 2-Byte path advertisements `set path.hash.mode 1` 5. Set a remote Admin password (make sure to remember this!) 6. (Optionally) Set a Guest password like `idahomesh` to let others see your repeater's stats 7. Set the repeater's location — you can set it to a nearby public landmark for privacy 8. Add the Idaho region tags. On current firmware (1.16.0+), for repeaters in/near the Treasure Valley those settings would be: `region def west pnw id sw-id boi` `region save` 9. Reboot the repeater ### **Repeater Position** We highly recommend you set a location for your repeater. That said, many of us would prefer not to disclose a repeater's exact location, especially if it's at our homes. **We suggest manually setting the repeater's location to a nearby park, major intersection, or landmark**. But please don't set your repeater location too far away, as an accurate *general* location helps us track coverage and plan future repeater needs. ### Next Steps... We suggest all repeater owners join [our Discord](https://idahomesh.org/discord/) to help shape the future of IdahoMesh and to stay informed about mesh operations, needed config changes, etc... In addition to Discord, but especially for repeater owners not on Discord, we suggest repeater owners sign up for [our newsletter](#/portal/signup/free), which will include any updates about important mesh operations. ### Need help? The best way to get help is via [our Discord](https://idahomesh.org/discord/). But if you're already on the mesh, feel free to DM `ASHZ` or ask in the `#idahomesh` channel. ## Sign up for Idaho Mesh A place for Idaho’s Meshtastic, MeshCore, and LoRa mesh enthusiasts to connect and collaborate Join Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. ## Repeater Categories ### Primary Repeaters Primary repeaters are those in locations with lots of "Topographic Prominence." In Idaho, these are almost always going to be located on the tops of mountains. While these repeaters do add significant coverage for companion nodes, more importantly, they extend the mesh backbone over long distances and connect lots of secondary and neighborhood repeaters. 💡 If you're interested in putting up a high coverage "primary" repeater on a mountain with a large coverage area, ****please reach out to us to coordinate efforts**, we'd love to help ensure your primary repeater will be well connected and leveraged within the larger mesh. We can also help with design, logistics, etc. ### Secondary Repeaters Secondary repeaters are those that cover an area between Primary (mountain top) repeaters and Neighborhood (rooftop) repeaters. These may be on hills, tall radio towers, water towers, taller commercial buildings, or other locations where coverage is provided to a larger area, but not at the level of a Primary Repeater. ### Neighborhood / Home Repeaters In general, on MeshCore, it's hard to go wrong adding neighborhood repeaters. Many users will want to add a repeater at their homes. Unlike other meshes, MeshCore generally encourages this in areas where coverage isn't 100%. Please follow the settings and suggestions in this guide, and feel free to reach out if you have any questions. ### ## ### Understanding MeshCore: Channels, Rooms, and DMs URL: https://idahomesh.org/meshcore-channels-rooms-and-dms/ Last updated: 2026-01-29T07:48:54.000Z As I talk to people new to MeshCore, some of the common areas of confusion I hear are around the options for communication. The public channel, hashtag channels, Rooms, and DMs. Let's explore how these differ and when you might want to choose one over another. 💡 Statewide, we use the channel "#idahomesh" If you're able to connect to the SW Idaho Mesh, join us on the "IdahoMesh Room" server. ## Quick Reference | Type | Security | Catch-up | Best For | | ------------------- | -------- | -------- | ------------------------------------ | | Public Channel | None | No | Public conversations, broadcasts | | Room (public) | None | Yes | reliable group messaging | | Hash Channel | None | No | Topic organization | | Private Channel | Good | No | Secure group communications | | Room (private) | Good | Yes | Reliable, secure group communication | | Direct Message (DM) | Best | No | Private 1:1 conversations | ### Channels vs Rooms Before we go through each option noted above, I think it's best to explain the key differences between Channels and Rooms. **Channels**, regardless of type (Public, Hashtag, or Private), are broadcast-only and flood-routed. The message is sent to the entire mesh, and everyone who can hear mesh repeaters and has that channel configured on their companion node will receive it. If a node isn't in a place where it can hear a repeater on the mesh, the node will not (ever) get that message. This can be annoying if you're trying to have a long conversation with someone in a sketchy coverage area. **Rooms** are kind of a cross between a channel and a DM. For those of us old enough to remember BBS systems, Rooms are basically that. Each room requires a room server, a node that hosts the room and stores messages. You must have a path to the room server to use the room. When you log into a room server, you'll get any unread messages sent to your node. This means that if you lose your connection to the mesh, when you get back in range, any recent messages will be synced to your companion. This is extremely handy in many situations. Want to talk with MeshCore and Meshtastic enthusiasts all over Idaho? Come join us on our Discord [IdahoMesh Discord ](https://discord.gg/8mKr4RCznS?ref=idahomesh.org) ## Channels Please keep in mind that all Channels are flood routed. Messages on channels (public, hash, or private) exist in the moment they're transmitted. If you're out of range or your device is off, you miss messages silently. The sender gets no indication that you didn't receive it, and you have no idea you missed anything. ⚠️ **There is no indication that users received a channel message, and users will not know if they are missing messages* ### Public Channel Not much to explain here: messages sent to "Public" are seen by everyone on the mesh, unless they've removed the Public channel. If a user isn't connected to the mesh when the message is sent, they won't receive it. ### Hashtag Channels Hashtag channels are like private channels, but the name is basically the password. Don't consider hashtag channels private; anyone who guesses or learns the channel name can read all messages. Hashtag channels are great for organizing messages by topic. For example, we have an `#idahomesh` channel where we discuss our mesh, hardware, repeater coverage, and growth plans. `#testing` is a channel used in lots of places for test messages, testing repeater coverage, and other related tests. 🔒 If you need security, use Private channels, a Private Room or DMs ## Private Channels Private channels use strong encryption and randomly generated keys. To send or receive messages on private channels, you must have the encryption key. If you create a private channel, you'll need to share the key with everyone you want to join. Like all other channel types, if someone is out of mesh range when a message is posted, they never receive it. If that's a problem, consider a room server. ## Rooms A Room Server stores messages and delivers them when you connect. When you log into a room, you receive the last 16 messages you haven't seen. Rooms can be public or private. Public rooms often have a blank password or one that is widely shared or easily guessable. Private rooms can also be set to read-only, meaning that only admins can post messages; these can be used for announcement boards or other asymmetrical communication needs. ## Direct Messages DMs are end-to-end encrypted messages between two companion nodes. They're the strongest privacy on MeshCore and also the most efficient ### Connect URL: https://idahomesh.org/connect/ Last updated: 2026-08-01T18:55:32.000Z ## Discord The best way to connect with IdahoMesh is through our community Discord server. You can ask questions, talk with Mesh enthusiasts in your region of Idaho, and stay informed about changes to the Mesh landscape. Click the link below to join our community. Want to talk with MeshCore and Meshtastic enthusiasts all over Idaho? Come join us on our Discord [IdahoMesh Discord ](https://discord.gg/8mKr4RCznS?ref=idahomesh.org) ## IdahoMesh Newsletter We also have a newsletter and encourage everyone using any Mesh in Idaho to join our newsletter email list. Once signed up, you can also ask questions and comment on our website posts & newsletter updates. *Barring urgent news, we plan on sending one update every 4-8 weeks. No spam, no ads, and your email address won't be shared with anyone or used for anything other than this newsletter.* ## Sign up for Idaho Mesh A place for Idaho’s Meshtastic, MeshCore, and LoRa mesh enthusiasts to connect and collaborate Join Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. ## MeshCore We'd love to have you connect with us on MeshCore. We hang out in the `#idahomesh` channel; anyone can join by adding the channel via the "join hashtag channel" option in your MeshCore companion app. If your area's mesh can reach Southwest Idaho, you can reach out to the IdahoMesh founder directly. Here's the MeshCore contact card for `ASHZ` ![](https://idahomesh.org/content/images/2026/01/ashz-1.webp) #### ## Signal We have recently started a Signal group. You can join via this invite: [IdahoMesh Signal Group](https://signal.group/?ref=idahomesh.org#CjQKIFQwYSzPXWkeBbyh79bXqyT-x24%5Fqwd3VnN9qZcJH7f4EhBMjgk-Gu8HAsZNLoDKYw7%5F) ## Email us We gotta be honest, IdahoMesh is a labor of love for us, and no one loves email. We highly suggest joining the Discord or Signal linked above. But if you really need to email us, you can reach out via *connect@idahomesh.org* ### Maps & Tools URL: https://idahomesh.org/tools/ Last updated: 2026-08-15T22:50:07.000Z We use a lot of mapping and mesh analysis tools as we work to expand, map and troubleshoot mesh operations. Below you'll find a few we host, as well as a few we like from other sites/group.s ## Idaho Mesh Hosted Tools 📡 All of the tools listed here are fed by our MQTT broker; if you want to help out, [add an Observer](https://idahomesh.org/add-an-observer/). [**IdahoMesh Map**](https://map.idahomesh.org/?ref=idahomesh.org) **\- Our favorite mesh analysis tool, Corescope.** We also have this simplified mesh mapping tool [mm.idahomesh.org](https://mm.idahomesh.org/?ref=idahomesh.org) [IdahoMesh Health Check](https://health.idahomesh.org/?ref=idahomesh.org) \- a tool for testing your node's reach in real time. [IdahoMesh Repeater Audit](https://audit.idahomesh.org/?ref=idahomesh.org) \- This is an in-house tool for tracking which repeaters support multibyte traffic, advertise multibyte, and support the `id` region. **mqtt.idahomesh.org** \- we have our own broker that feeds all of our tools, you can use the `idahomesh` preset in the Observer firmware to feed us data or find the settings on the [add an observer](https://idahomesh.org/add-an-observer/) page. > If you've found a cool new tool, let us know, and we'll consider hosting it. ## Other Maps & Tools [LetsMesh Mesh Map](https://analyzer.letsmesh.net/map?ref=idahomesh.org) \- The best worldwide mesh map [Mesh Mapper](https://meshmapper.net/?ref=idahomesh.org) \- a mesh coverage mapping tool with war driving support. ## Posts ### Important: Updated Repeater Settings URL: https://idahomesh.org/summer-2026-repeater-settings/ Last updated: 2026-08-10T15:02:16.000Z We've been busy the last few weeks rolling out new tools and coordinating changes to repeater settings. We encourage everyone who operates a repeater to adopt these settings as soon as possible. We've also been visiting several of our primary repeater sites in SW Idaho to check on things, upgrade firmware to support multi-byte paths, and we're actively exploring sites for our next primary repeaters. *If you have ideas for new sites, want to share coverage feedback, have a high-profile location and want to host an IdahoMesh repeater, or have questions, please* [*reach out and chat with us*](https://idahomesh.org/connect/)*.* ## New Map & other tools We now have an [Idaho Mesh Map](https://map.idahomesh.org/?ref=idahomesh.org#/live). More than just a map, it includes a lot of tools and analytics you may find useful. We have an MQTT broker `mqtt.idahomesh.org` which feeds the Idaho Mesh Map and other mapping, analytics, and troubleshooting tools in our stack. We already have observers in North, Central, and Southwest Idaho pushing data to our server (thank you!). We'd **love** to have more folks helping out; if you're running a current version of the Observer Firmware, there's an `idahomesh` preset you can use to automatically configure your observer to contribute to our map. For other tools, visit the [IdahoMesh Observers](https://idahomesh.org/add-an-observer/) page for complete settings. Already running an observer and pushing data to LetsMesh or other mapping tools? Great! Most tools, including the observer firmware, allow you to push traffic to multiple MQTT servers. Many of us are pushing to LetsMesh as well as other national and regional MQTT targets. [IdahoMesh Health Check](https://health.idahomesh.org/?ref=idahomesh.org) is another tool we've been playing with recently, fed by the same MQTT data as our map. Let us know if you find it useful. *If there are other tools you'd like to see on IdahoMesh.org, let us know.* ## Repeater Settings Changes ‼️ We are asking everyone to adopt these updates to our IdahoMesh suggested repeater settings. Doing so ensures our mesh operates smoothly and efficiently. Our recommended repeater settings are changing; we've already begun rolling out these changes to primary repeaters in Southwest and Central Idaho and encourage all repeater owners to do the same. If you are setting up a new repeater, or it's been a while, please see our full repeater settings page: [Repeater Settings](https://idahomesh.org/add-a-meshcore-repeater/). Here's a quick reference; see below for more details on each change. ![IdahoMesh Repeater Config Updates — suggested changes for MeshCore firmware 1.16.0 and newer. Terminal commands: set path.hash.mode 1, set advert.interval 0, set flood.advert.interval 47, region remove idaho, region def west pnw id sw-id boi, region save, reboot. Regions differ based on your location — at minimum, add the statewide region: region def id](https://idahomesh.org/content/images/2026/08/idahomesh-repeater-config-1.16.png) ### Path Hash Mode for Adverts We are encouraging all repeater owners to enable 2-byte path advertisements on repeaters. This is a step toward multi-byte paths for all nodes, but at this time **we are only recommending it for repeaters**. This will help us track multi-byte support across the mesh and reduce the frequency of repeater ID collisions, improving our ability to do mesh diagnostics. There are no downsides to moving repeaters to 2-byte paths as they only affect the repeater's own advertisements. You can enable this remotely via the console `set path.hash.mode 1` or via the GUI if directly connected. You must `reboot` the node for this to take effect. ### Advert Interval Our mesh has grown to the point that frequent repeater adverts are not helpful, and we will soon be at the point where they are harmful. New firmwares now default to sending an advert every `47` hours; this is our recommendation. In almost all cases, Zero-Hop adverts should be set to `0` minutes, which is off. MeshCore now includes features that replace the need for more frequent adverts; nodes that advert more often are tying up very limited mesh airtime. **Please do not set flood adverts to less than 24 hours.** `set advert.interval 0 set flood.advert.interval 47` ### Region Change We started [rolling out](https://idahomesh.org/meshcore-regions/) the `idaho` region the day the first region-enabled firmware was released back in January. It has served us well, but as regions have matured in the firmware, most of the meshes across the west have started converging on a common pattern. We think it's worth adopting sooner rather than later, as the migration will be easier now and improves future interconnectivity. As such, the `idaho` region is being retired and replaced with `id`. We are also adopting larger region scopes that are emerging. For Southwest Idaho repeaters on firmware 1.16.0 or newer: `region remove idaho region def west pnw id sw-id boi region save` If you're elsewhere in the state, check with other locals to ensure you're all on the same page and/or hop in our Discord and ask; we're happy to help. 📡 Most importantly, please add `id` as one of your regions for any repeater in or covering part of Idaho. *If you're on an older firmware, you'll need to use the `region put` command. Please verify the region documentation for your firmware version, though we do suggest a more current firmware.* ### Firmware On a personal note, as someone operating well over a dozen MeshCore repeaters, many of them in remote and hard-to-get-to locations, I know updating firmware is a pain. I've got several running ancient firmware (I'll get to most of those in the next week). If your repeater firmware is older than 1.14.0 (March 2026), you're missing out on multi-byte path support as well as months of changes that improve repeater and overall mesh performance. I'd *highly* recommend planning an upgrade to the newly released 1.17.0 in the near future. > Making these changes on your repeaters helps ensure our mesh operates smoothly. We thank everyone who maintains a MeshCore repeater in or near Idaho for their contribution to the IdahoMesh. ## Impact These changes do not negatively impact current mesh traffic; on the contrary, they help ensure our mesh is ready for increased traffic load, especially as all the smaller meshes in the West start to interconnect. Managing performance during this time will be critical. We've had several folks ask if we were planning to lock down repeaters and require the use of regions rather than the current setting, which allows all unscoped traffic. Realistically, there will come a time when we will need to set some key repeaters to require region scopes. We have had to do this already, temporarily, in the early days of IdahoMesh for various reasons, but at this time we have no plans to require region scopes. I'm not sure *when* we'll need to start requiring region scopes on the more high-profile repeaters, but it *will* happen at some point. I'm hoping to give everyone at least a few months to adopt the new regions before that is needed. And if we do need to, we'll certainly communicate it well in advance. But there is no specific timeline for it at this time. ## Thanks! I'm so excited about MeshCore in Idaho! When I put up the first high-profile repeater in Southwest Idaho late last year (December 31, iirc), I had no idea how instantly successful it would be as the few of us with rooftop repeaters could finally link together. As I traveled extensively all over the state this summer (literally...), I was amazed at how far we've collectively come in the last several months. Every major region in the state has a functional mesh, and most are growing at an insane pace. North Idaho is interconnected with Spokane and further west with the Cascadia Mesh. East Idaho is interconnected with Salt Lake City. And meshes are even starting to pop up in very isolated mountain communities like my hometown of Salmon. That's awesome. Keep up the great work, everyone; keep being welcoming to newcomers, and don't be afraid to reach out and ask for help, or to organize and coordinate on new mesh project areas or sites. ### MeshCore Regions URL: https://idahomesh.org/meshcore-regions/ Last updated: 2026-08-01T19:19:13.000Z ## 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](https://idahomesh.org/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](https://idahomesh.org/connect/); we're happy to help! ### Getting Started With MeshCore URL: https://idahomesh.org/getting-started-with-meshcore/ Last updated: 2026-08-03T05:30:19.000Z ## IdahoMesh Quick Start Guide Welcome to MeshCore! If you have any questions or run into problems, we highly suggest you [join our Discord server](https://idahomesh.org/discord/). It's a welcoming community passionate about Mesh technology and off-grid text messaging. ****Coming from Meshtastic?** MeshCore is fundamentally different. Meshtastic nodes constantly broadcast telemetry and advertisements, while MeshCore reserves the limited bandwidth for actual text messages. Most repeaters only advertise every 24-48 hours, so when you're starting fresh, your node map may look empty even with excellent mesh coverage. Be patient—the best way to test your coverage is to send a message. ## 1\. Get a device Any LoRa radio sold as "Meshtastic compatible" works with MeshCore — just make sure it supports **915 MHz** (the US band). Most pair with an app on your phone; some have a built-in screen and keyboard so you don't need one. You'll find options at every price point on Amazon, AliExpress, or Rokland. Not sure what to buy? Ask in [Discord](https://discord.gg/8mKr4RCznS?ref=idahomesh.org) and we'll point you at something for your budget and use case. ## 2\. Flash MeshCore 1. Go to [flasher.meshcore.io](https://flasher.meshcore.io/?ref=idahomesh.org) 2. Connect your device by USB and select it 3. Choose **BLE Companion** firmware 4. Click **Erase**, then **Flash** That's it — your device is now running MeshCore. ## 3\. Connect your phone Install the MeshCore app ([Android](https://play.google.com/store/apps/details?id=com.liamcottle.meshcore.android&ref=idahomesh.org) · [iOS](https://apps.apple.com/us/app/meshcore/id6742354151?ref=idahomesh.org)), open it, and pair with your device over Bluetooth. The default PIN is **123456** — you can change it in the app once you're connected. ## 4\. Configure Give your node a name, then pick the **USA/Canada (Recommended)** region preset. Save, reboot, and you're set. ## 5\. Say hello - Tap the signal icon (top-right) and choose **Advert – Flood Routed**. This announces your node to the mesh, flooding out to every repeater in range (up to 64 hops). - Open the **Public** channel and send a quick "hi" — feel free to mention you're new or testing. If a number appears under your message, that's how many repeaters heard you. One or more means you're on the mesh! ## Next steps Our main chat lives on the **#idahomesh** channel — add it via Add channel → Hashtag channel → #idahomesh, and come say hi. If coverage at home is weak, especially indoors, consider [adding a repeater](https://idahomesh.org/add-a-meshcore-repeater/). More guides are on our [MeshCore resources page](https://idahomesh.org/meshcore/). ## Sign up for Idaho Mesh A place for Idaho’s Meshtastic, MeshCore, and LoRa mesh enthusiasts to connect and collaborate Subscribe Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. ### New Year, New Mesh(core) URL: https://idahomesh.org/meshcore-idaho/ Last updated: 2026-01-29T08:03:13.000Z Yesterday, I deployed the first wide-area Meshcore repeater, providing coverage for the vast majority of Boise, the Treasure Valley, and surrounding areas. _This post is for subscribers only._ ### Welcome URL: https://idahomesh.org/welcome/ Last updated: 2026-01-29T08:08:36.000Z I'm starting "IdahoMesh" - a new community dedicated to bringing together anyone interested in Meshtastic, Meshcore, or other LoRa mesh networks for off-grid communications in Idaho. 💡 Since this was originally posted, we have made significant investments to establish [a reliable MeshCore mesh](https://idahomesh.org/tag/meshcore/). Thus, some of the context in this post is no longer accurate. *If you wound up here and don't know what Meshtastic is, here's the short version: these are low-power radio devices that create their own communication networks without relying on cell towers or the internet. Think group text messaging that works in the backcountry, where your phone has no service. You can learn more at* [*meshtastic.org*](https://meshtastic.org/?ref=idahomesh.org) *and* [*meshcore.org*](https://meshcore.org/?ref=idahomesh.org)*.* ## Why IdahoMesh? Whether you're interested in mesh networks for camping, backcountry exploration, or simply because the technology is fascinating, IdahoMesh is here to connect individuals who recognize the value in reliable, off-grid communication. What matters isn't why you're interested - it's that you're here and want to connect with others. ## Our Goals IdahoMesh exists to help build more reliable mesh networks across Idaho by: - **Building community** \- Connecting existing users and providing a welcoming space for newcomers - **Sharing knowledge** \- Offering technical support and best practices (especially for those just getting started) - **Improving our networks** \- Helping ensure nodes are configured correctly and working efficiently - **Strategic expansion** \- Identifying locations for new repeater nodes where they'll do the most good ## The Current State of Things Idaho already has several Mesh networks up and running, particularly around our major population centers. Many of us use ad hoc mesh networks while camping or exploring the Idaho Mountains. Most of our Meshtastic networks are running on default "LongFast" settings. This is fine in rural areas, but it becomes unreliable once you hit around 50 nodes. With 100 nodes in the Boise area, messaging is already unreliable. Some of us are already testing Meshtastic settings for larger networks, as well as other new mesh platforms, such as Meshcore. I'd love to coordinate experimentation with the goal of a more capable and reliable mesh. ## A Bit About Me I've spent many years working in telecommunications - both for the federal government and in the commercial sector. I've built numerous remote, off-grid mountain-top communication sites and built and maintained 911 centers and critical public safety communication systems. Much of my work involved disaster communications, building emergency communication systems in hurricane- and fire-affected areas where traditional infrastructure had been destroyed. On the fun side, I've also been a ham radio operator for 30 years. After my time in telecommunications, I moved into software development, systems engineering, and site reliability engineering, designing and building globally distributed computer systems focused on reliability and performance at scale. This combination of experience puts technology like Meshtastic firmly within my wheelhouse while still being a fun hobby. ## Mesh Agnostic Approach Many of the Mesh groups around the US are laser-focused on Meshtastic or Meshcore; all too often, I see turf wars between the two sides play out in their online spaces. While most of our current focus is on Meshtastic (since that's what most people are running in Idaho), IdahoMesh welcomes discussion of all off-grid mesh technologies. I'm personally testing Meshcore as well, and while I don't consider it *quite* ready for large public deployments, I've been thrilled with the results I've had as a family mesh for use while camping and hiking. The point isn't to pick winners and losers - it's to build a community where people can learn about and discuss whatever mesh technology they're using or curious about. ## Join Us 1. **Join our Discord server** \- We're working to establish a Discord community (it's brand new) where Idaho mesh users can receive real-time help and connect with others across the state. 2. **Sign up for updates** at IdahoMesh.org to stay informed about new content and community developments. Whether you're running your first node or you've been meshing for years, we'd love to have your voice in IdahoMesh.