Skip to main content

Getting Started

SA Mesh uses low-power LoRa mesh networking to keep people connected when normal mobile or internet coverage is unavailable, congested, or simply not the right tool for the job.

The first choice is not which exact device to buy — it is which mesh firmware and network style you want to join.

Recommended first path

For most SA Mesh participants, start with MeshCore and a companion node. It is the simplest way to join the current SA Mesh community network before you experiment with fixed repeaters or more advanced infrastructure.

Choose your path​

RecommendedMeshCoreBest starting point for most SA Mesh users, fixed coverage planning, repeaters and community infrastructure.Alternative / legacyMeshtasticStill useful for small groups, portable experiments and users who specifically want the Meshtastic app ecosystem.

If you are unsure, start with MeshCore and ask in the SA Mesh / SA:MUG community before buying or deploying fixed equipment.

MeshCore or Meshtastic​

MeshCore is the current focus for SA Mesh documentation because it is designed around deliberate routing, fixed repeaters and efficient use of shared airtime.

Meshtastic is still useful for small private groups, temporary events, portable use, GPS/location-sharing workflows and experimentation.

This wiki starts with MeshCore content first. Meshtastic material can be migrated into its own section later if the community wants the new wiki to carry both stacks.

MeshCore is usually the better first path for SA Mesh because:

  • the local documentation and current migration work are MeshCore-first;
  • companion nodes give new users a low-risk way to join;
  • fixed repeaters can be planned deliberately instead of accidentally creating noisy always-on rebroadcasters;
  • local SA, WA and QLD radio settings can remain consistent;
  • troubleshooting can focus on known firmware roles, radio settings and dashboard/map observations.

Start here: Getting started with MeshCore

When Meshtastic still makes sense​

Meshtastic may still be a good fit when you want:

  • a small independent group mesh;
  • portable or event use;
  • GPS/location-heavy workflows;
  • experimentation with the Meshtastic app ecosystem;
  • compatibility with an existing Meshtastic group.

For Meshtastic-specific guidance, start with the migrated Meshtastic getting started and then check current upstream Meshtastic docs for firmware/app changes.

Live SA Mesh tools​

Credits and inspiration​

This top-level onboarding pattern is inspired by the NSW Mesh getting-started page, adapted for SA Mesh wording, links and the current MeshCore-first migration.