Mesh Radio in Your CERT EMCOMM Kit

You already have a comms plan. It covers your VHF voice net, your ARES/RACES frequencies, your ICS 205 form, and the EOC contact number. The question isn’t whether to add a MeshCore mesh — it’s where a data mesh fits in what you’re already doing, and what it can do that voice can’t.

Two layers, two jobs

The stack most CERT and ARES/RACES teams already run has voice as its backbone. VHF and UHF voice — ARES nets, simplex tactical channels, the EOC contact frequency — is interoperable, familiar, and required for coordination with first responders and served agencies. It doesn’t go away.

A MeshCore data mesh adds a parallel layer. It runs on 915 MHz in the US, does not require an amateur license to operate, and carries structured data: digital messages between field teams and the EOC, periodic node status reports, and GPS position packets from nodes that carry location data. What it does not do is replace voice. A field team can’t call for help on a mesh; they can report their status on one.

Running both layers simultaneously is straightforward. Voice traffic happens on its own frequencies; mesh traffic happens on the LoRa channel. Neither blocks the other. Operators who hold amateur licenses can work both. CERT volunteers without licenses can operate the mesh hardware (ISM band, no license required to transmit in the US on 915 MHz under Part 15 rules) and contribute field data without touching the licensed voice net.

What the mesh adds

Digital messaging. Text messages between nodes don’t need to compete for airtime on the voice net, don’t require a relay operator to transcribe them accurately, and don’t get lost in radio noise. For status reports, resource requests, or damage assessments moving between field teams and a logistics function at the operations center, a digital channel is more reliable for structured data than voice.

Node status and position. A MeshCore node that transmits periodically sends signal quality and hop-count data that an observer can publish to the broker. From there, Waev shows which nodes are active, whether any have gone silent, and whether hop counts have changed — meaning paths have changed. During an activation, this is a live picture of your data infrastructure’s health.

A record. Voice communications are ephemeral unless someone is logging. Digital messages and Waev’s packet history are timestamped and searchable after the event. That’s the after-action review: which nodes were active at which times, where path changes occurred, and what the link quality looked like at the moment a team reported trouble.

The ARES/RACES fit

ARES (the ARRL’s Amateur Radio Emergency Service) and RACES (Radio Amateur Civil Emergency Service) are both structures for licensed amateurs serving emergency management. They operate on amateur frequencies under Part 97 rules and are activated by different authorities — ARES by the ARRL Emergency Coordinator, RACES by a government official.

A MeshCore mesh sits outside both structures in one sense: it’s not a licensed amateur operation. It’s an ISM-band data network operating under Part 15. A licensed ARES or RACES operator can run the mesh alongside their licensed operations without any conflict — two separate systems, two separate frequency allocations, each doing a distinct job.

What the mesh adds to an ARES/RACES deployment is the data layer that typical voice-only EmComm infrastructure lacks. An ARES net can pass formal traffic and coordinate field operations. A mesh can carry position data and node health telemetry that the voice net isn’t designed to handle efficiently.

The verification gap

Served agencies — EOCs, Red Cross chapters, local emergency management — increasingly ask about network health. “Is your mesh up?” deserves a better answer than “we think so.” That gap is what Waev fills.

A baseline built over 30 days before an activation gives you:

The baseline answers the served agency’s question with data: these nodes were active as of yesterday, these links are healthy at +11 dB, this relay’s packet rate is 45/hour and has been stable for three weeks. That’s a health report you can hand to a served agency, not an estimate. For more on building and reading a 30-day baseline, see what to watch when the grid goes down.

What to add to your go-kit

For a CERT or ARES EMCOMM go-kit with Waev integration, the minimum additions to existing voice equipment:

One or more MeshCore field nodes. These are the mesh radios that field teams carry or deploy. Each node can relay packets, send messages, and broadcast status. No internet connection required at the field level.

One observer node. This is a MeshCore-compatible device running gateway firmware that connects to your MQTT broker over TCP/IP. Positioned at your operations center, where internet access is available. This is the bridge between the radio mesh and the Live Map. Without it, the mesh operates but is not visible.

A broker. Self-hosted (Mosquitto on a Raspberry Pi or a VPS) or third-party. The observer publishes to the broker; Waev subscribes and reads. The data stays with you — bring-your-own-broker means you hold the keys. A served agency asking about data custody gets a simple answer: the data is on your broker.

A Waev account connected to the broker. This is the analytics layer. Connect it before any exercise and start the baseline. By activation day, you’ll have weeks of context.

The readiness drill

Integrate the mesh into your regular exercises the same way voice is integrated: as a parallel capability that gets tested under realistic conditions.

Before any exercise, run the readiness check: baseline in Network Stats, topology review in Live Map for SPOFs, packet rate from sentinels in Outpost. During the exercise, have the operations center monitor the Live Map while field teams operate. After the exercise, use Packet Search to review the timeline and write up findings.

If the exercise reveals a marginal link or a relay that needs repositioning, that’s the finding. It’s better as a finding during a drill than as a surprise during an activation.

---

Questions about integrating mesh data into your CERT or ARES EMCOMM kit, or preparing for an upcoming exercise? Write to us. We’re glad to help with pre-exercise reviews.