Coming from Meshtastic

Why Tri-Cities Mesh moved to MeshCore, and what changes for you.

Tri-Cities Mesh started on Meshtastic. In 2026 the community moved to MeshCore. This page covers what’s different and how to switch.

Why we switched

Meshtastic is a great project and got a lot of us into LoRa mesh. As the local network grew, we wanted a design that scales better over our hills and valleys:

  • Repeaters do the relaying. In Meshtastic, nearly every radio rebroadcasts what it hears, which crowds the airwaves as the mesh grows. In MeshCore, only dedicated repeaters relay. Phones and handheld companions don’t.
  • Direct messages find a route. The first message to someone is flooded, and after that MeshCore sends DMs along a known path, so they don’t hit the whole mesh each time.
  • Room servers. Built-in bulletin boards keep messages for people who were offline.
  • Easy remote management. You can check on and configure repeaters from the app over the air.

What changes for you

The two networks can’t talk to each other, so a Meshtastic radio won’t see MeshCore traffic and MeshCore radios won’t see Meshtastic traffic.

MeshtasticMeshCore
Your phone’s radioUsually relays trafficA companion that doesn’t relay
Fixed relaysRouter / Client rolesRepeater firmware
Radio settingsLongFast, etc.USA/Canada preset: 910.525 MHz, BW 62.5, SF7, CR5
IdentityNode number (!abcd1234)A public key (contacts show a short prefix)
AppMeshtastic appMeshCore app

Reflashing your radio

Most common Meshtastic hardware, including Heltec V3, RAK4631, T-Beam, T-Echo, and Seeed trackers, runs MeshCore too.

  1. Write down anything you want to keep from your Meshtastic settings, such as the name and channel keys.
  2. Open the MeshCore flasher, pick your device, and choose Companion, or Repeater if it’s a fixed site.
  3. Follow Getting Started from step 3.