Overview#
A search-and-rescue team drops into a valley with no cellular coverage, switches on a dozen Meshtastic radios, and within minutes every handset, vehicle node, and relay appears on the command post map with its GPS position, battery health, and signal quality, all without a single manual entry.
The Meshtastic LoRa Mesh Node Integration connects a Meshtastic LoRa gateway to the Argus platform and pulls every visible mesh node into the common operating picture. Off-grid teams that already run low-power, long-range radio meshes, whether in disaster zones, remote search areas, or forward operating bases, register their gateway once and let the platform keep node positions and telemetry up to date. Operators see where each radio is, how much battery it has left, and how strong its link is, all scoped to their own organisation.
Because every node is bridged into the platform's operational entity graph as a land unit with a live latitude and longitude, Meshtastic radios sit on the same map as drones, sensors, and ground teams. Each pull writes an auditable ingest record, so commanders have a defensible trail of exactly what was synced, when, and from which gateway.
Key Features#
- Automatic Node Discovery: Pull every node visible to a Meshtastic gateway in a single operation, capturing node identifier, long and short names, and hardware model so the full mesh appears without manual data entry.
- Live Position and Telemetry: Each node carries its GPS latitude and longitude, battery level, and signal-to-noise ratio, giving operators position, power health, and link quality for every radio in the field.
- Common Operating Picture Bridge: Every synced node is promoted into the operational entity graph as a land-domain unit with a real-time position, so Meshtastic radios appear on the same map as all other tracked assets.
- Aggregate Mesh Statistics: A single read returns total node count, average battery level, and average signal-to-noise ratio across the organisation's mesh, giving a fast read on overall network health.
- Clearance-Level Row Filtering: Reads apply per-user clearance filtering, so each operator sees only the nodes their classification level permits, with a secrecy level set per sync.
- Strict Organisation Scoping: Every read, write, and statistic is scoped to the calling organisation, so one tenant can never see or alter another tenant's mesh nodes.
- Auditable Ingest Records: Each pull emits an immutable interoperability ingest record capturing the gateway address, node count, and secrecy level, giving a defensible trail of every ingest event.
- Optional Gateway Authentication: A gateway pull accepts an optional bearer token, so meshes fronted by an authenticated gateway are reached using the same standard credential scheme.
Use Cases#
Emergency Response and Disaster Relief#
When fixed infrastructure is down or absent, response teams run Meshtastic radio meshes to stay in contact and share position. Registering the gateway brings every responder's radio onto the command map automatically, so coordinators can see team dispersal, dead spots, and failing batteries at a glance.
Search and Rescue#
Search parties spread across remote terrain carry LoRa radios that relay position back through the mesh. The platform turns those positions into live units on the map, letting the incident commander track coverage, identify gaps, and redirect teams without radio calls for every status check.
Forward Operating Bases#
A base running a Meshtastic mesh for short-range coordination gains a consolidated picture of every node, its battery state, and its link quality. Operators spot degraded relays before they drop out and keep the mesh topology healthy.
Off-Grid Field Operations#
Survey crews, environmental monitors, and remote work parties operating beyond cellular range use LoRa meshes for low-power connectivity. The integration removes manual position reporting, scoping each crew's nodes to their own organisation with a full audit trail.
Integration#
A customer plugs in by registering a Meshtastic gateway address and then pulling nodes on demand from their own applications or the Argus console, all through an authenticated, organisation-scoped programmable interface.
- Gateway Connectivity: Argus reaches the Meshtastic gateway over its own REST interface at the standard node resource path, retrieving node records and mesh status as structured JSON, so no bespoke agent has to run on the gateway.
- Optional Bearer Credential: A pull accepts an optional bearer token that is presented to the gateway using the standard authorisation header, so meshes behind an authenticated gateway are reached without custom wiring.
- Normalised Node Model: Raw mesh records are mapped into a consistent node model, the same shape every reader sees, giving customers one predictable structure across every connected mesh.
- Operational Bridge: Each persisted node is emitted as a live land-domain unit with a position, so it immediately joins the wider operating picture alongside all other operational entities.
- Identity and Access: Caller access is governed by OAuth2-issued tokens carried as JSON Web Tokens, with every operation scoped to the calling organisation and recorded for compliance.
- Downstream Workflows: Once nodes land as operational entities, existing mapping, alerting, and dispatch workflows pick them up, so the benefit reaches field teams without extra plumbing.
The typed schema publishes three operations: meshtasticNodes lists the organisation's nodes, meshtasticStats returns aggregate battery and signal-to-noise statistics, and syncMeshtasticNode pulls fresh node data from a gateway address with an optional bearer token and a secrecy level.
Open Standards#
- LoRa: the long-range, low-power radio modulation that carries the underlying mesh traffic, giving the capability reach across off-grid distances where cellular and Wi-Fi cannot operate.
- Meshtastic Mesh Protocol: the open mesh networking protocol that defines node identity, position, and telemetry, which the connector consumes natively through the gateway interface.
- REST: all gateway interaction follows a resource-oriented style over plain HTTP verbs and resource paths such as
/api/v1/nodes, the interface a Meshtastic gateway publishes. - RFC 8259 JSON: node records and mesh status are exchanged as standard structured JSON, and stored records keep the same consistent shape.
- RFC 6750 OAuth 2.0 Bearer Token: an optional gateway credential is presented as a standard bearer token in the authorisation header, the common scheme for authenticated gateways.
- RFC 8446 TLS / HTTPS: every connection to a gateway runs over transport-layer security with certificate verification, protecting node data and credentials in transit.
- OAuth 2.0 (RFC 6749): caller access to the platform is authorised through standard token issuance before any operation runs.
- JSON Web Token (RFC 7519): organisation-scoped access is carried in signed JWT bearer tokens.
- WGS 84 / EPSG:4326: node latitude and longitude use the common geographic reference model shared across the platform's mapping workflows, so Meshtastic positions align with every other map layer.
- ISO 8601: node last-heard and ingest timestamps use the standard date-time representation for unambiguous time handling across systems.
- GraphQL: the public surface is published as a typed, schema-described interface for predictable, organisation-scoped requests.
Security & Compliance#
- Strict Tenant Isolation: Every read, write, and statistic is scoped to the calling organisation, so one customer can never read or act on another customer's mesh nodes.
- Clearance-Level Filtering: Reads apply per-user clearance filtering against the secrecy level recorded on each node, so operators see only the data their classification permits.
- Authenticated Surface: All operations require an authenticated, authorised caller, and anonymous access is rejected.
- Verified Transport: Gateway connections enforce transport-layer security with certificate verification, protecting telemetry and any bearer credential in transit.
- Immutable Audit Logging: Every sync writes an append-only interoperability ingest record capturing the gateway address, node count, and secrecy level, giving a defensible trail for review and compliance reporting.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26