Family Emergency Preparedness

Practical guides for households — no license or technical background required. Plan, configure, and use mesh to keep your family connected when cell service fails.

Setting Up a Family Mesh Network Before Disaster Strikes

Most emergency communications guides are written for trained responders or amateur radio operators. This guide is for families — no amateur license required, no technical background assumed.

⚠️ Read this first — mesh is a supplement, not a lifeline. LoRa mesh (Meshtastic and MeshCore) is best-effort: messages may not get through. There is no guaranteed delivery, coverage depends on nodes being in range and powered, and a delivered/ACK indicator is only a best-effort radio acknowledgment — not proof a person received or will act on your message. It is NOT a replacement for 911, NWS/official alerts, or licensed voice radio. For any life-threatening emergency, use 911 or voice first; use your family mesh as a fallback when those are unavailable, and always have a non-radio backup plan (a meeting place and an out-of-area contact).

No amateur license is required because these devices operate on the 915 MHz ISM band under FCC Part 15 — but use only FCC-certified hardware on the default US/Canada preset, and do not modify the frequency or power beyond the certified configuration.

What You Need

You need at least two nodes to communicate at all — one for you and one for each person you need to reach. Each node is a self-contained device that communicates directly with other nodes without any cellular or internet infrastructure — but only when the two nodes are within radio range of each other or of a relaying node.

Minimum kit per family member

For a family of four, four nodes. You don't need one for every household member — prioritize whoever is most likely to be separated from the group (commuters, college students, elderly relatives in another home).

Realistic Range Expectations

LoRa range varies significantly with terrain and environment. The figures below are approximate, observed values and vary widely — always test your own coverage. Plan conservatively:

If your family lives within direct radio range, node-to-node messaging usually works well — but LoRa mesh is best-effort with no guaranteed delivery, and obstacles can cut range to under a mile in cities, so "a few miles" may not connect in a dense area. Larger separations require intermediate nodes to relay messages. Always have a non-radio backup plan, and test your actual coverage before you need it.

Setting Up a Private Family Channel

MeshCore supports encrypted private channels. Set up a dedicated family channel before a disaster — do not rely on the default public channel for family communications. (Encryption is permitted here because the network operates under Part 15 on the ISM band; encryption would be prohibited if these messages were sent on amateur radio frequencies.)

  1. In the MeshCore app, create a new channel with a name your family will recognize (your last name, "HOME", or a short codeword).
  2. Set a channel key/password and share the channel to each family member's app in person ahead of time — use the channel QR code or share link, and do not send the link by text message or email.
  3. All family nodes must use the same channel name and key to communicate privately. Verify every device shows the same channel name before you finish, then send a test message on it.
  4. Keep the default public channel enabled as a secondary — it lets you communicate with neighbors and community responders.

Test Before You Need It

Equipment you have never tested will fail you in an emergency. Run a family mesh drill at least once:

  1. Configure all devices together. Verify each node appears on every other node's list.
  2. Send a test message from each node to each other node. Confirm receipt both ways.
  3. Test at realistic distances — walk or drive to where family members would actually be (workplace, school, a neighbor's house) and verify the link holds.
  4. Test on battery — disconnect from USB and confirm each node runs for its expected battery life.
  5. Update firmware if you are comfortable doing so before storing nodes — but only with the device plugged in and following the official flashing guide, because an interrupted update can disable (brick) the node. Outdated firmware is a common silent failure point, but a working older version is far better than a bricked node; if you are not comfortable, have someone experienced help.

Storage and Readiness

Your Family Communication Plan

Having mesh hardware is only half the plan. The other half is knowing what to communicate, when, and how. A simple, agreed-upon procedure keeps messages short, actionable, and interpretable under stress.

Designate a Mesh Coordinator

Choose one person — usually whoever is most comfortable with the technology — as the family's mesh coordinator. Their role during an event:

Name a backup coordinator in case the primary is the one who is unreachable.

Important: the coordinator cannot confirm a message was delivered unless the recipient explicitly replies. Mesh delivery is best-effort with no guarantee. Treat no reply as a failed contact and fall back to the contingency plan immediately — do not assume the message got through, and do not treat the coordinator or the mesh as a reliable dispatch layer for life-safety decisions.

Check-In Schedule

Agree on a check-in schedule before any emergency — not during one. A predictable schedule reduces unnecessary worry and keeps the channel clear:

The Status Message Format

LoRa packets are small. Keep messages short. Agree on a standard format everyone can remember under stress:

NAME / STATUS / LOCATION / NEEDS

Examples:

Agreed status codes

Remember mesh delivery is best-effort — sending an EMERGENCY message does not guarantee anyone received it. Always attempt 911/voice for a life-threatening situation and treat the mesh message as a supplement, confirmed only when someone replies.

Write these codes on a small card and tape it to the back of each node so anyone can use it without training.

Rally Points

Agree on two physical meeting locations before any emergency — do not rely on mesh to communicate them during one:

Both locations must be known to every family member from memory. Walk or drive to them at least once so everyone knows the route.

If a Device Fails

Plan for at least one node failing. Options to build in advance:

Off-Grid Repeat: Turning Your Companion into an Emergency Relay

MeshCore companions don't repeat packets by default — that's intentional, and unlike a Meshtastic client a MeshCore companion will not relay traffic on its own. Repeating is left to dedicated infrastructure nodes to keep routing clean. But in a small ad-hoc situation where no repeater infrastructure exists — a campsite, a festival, or a neighborhood cut off in a disaster — Off-Grid Repeat lets you stand up a temporary local mesh from gear you already own: a single toggle in the MeshCore app turns a companion device into a temporary relay. The MeshCore developers describe this feature as being for ad-hoc, temporary meshes (camping, festivals), not as a way to extend an existing mesh or as standing emergency infrastructure — MeshCore "does not work well with dynamic repeaters." Treat it as a gap-filler you reach for when you have nothing better, and move to a dedicated always-on repeater as soon as you can.

This is a fragile, temporary stopgap. A phone-tethered relay depends on the phone staying powered, foregrounded, and BLE-connected within about 10 meters of the board, and mesh delivery is best-effort with no guarantee that any message arrives. Do not rely on a phone-based relay as life-safety infrastructure. It is not a replacement for 911, NWS alerts, or licensed voice nets — use those first for anything life-threatening, and use mesh only as a fallback when they are unavailable.

No extra hardware. No laptop. One setting change on your phone — provided your board already runs feature-capable firmware. If it doesn't, a one-time firmware update is needed first (see Requirements).

Requirements

The Frequency Requirement — Read This First

Off-Grid Repeat only works on one of three dedicated Off-Grid preset frequencies. It cannot be enabled on the standard USA/Canada preset (910.525 MHz) or any other regional frequency. The app will block the save and show a warning if you try. These preset center frequencies are firmware-defined values (as documented in the MeshCore project as of mid-2026) and could change in a future firmware release — confirm the actual values in your app rather than memorizing a number, so your whole group stays on a matching frequency.

The three Off-Grid presets are:

For families and neighborhoods in the US and Canada: agree on Off-Grid 918 MHz before a disaster happens. Every person who wants to participate in the off-grid mesh needs to switch to the same preset. Everyone who wants to communicate but doesn't need to relay can also switch to 918 MHz without enabling repeat.

⚠ Warning — switching to an Off-Grid preset cuts you off from the regional mesh. Moving to an Off-Grid preset (918 MHz) takes you off the normal USA/Canada mesh (910.525 MHz). While you are on an Off-Grid preset you cannot reach anyone on the standard regional mesh — including community repeaters, Mesh America infrastructure, and responders. A family that switches to 918 MHz "before a disaster" and forgets can be silently cut off from the wider mesh during the actual event without understanding why. Only switch when you specifically need the off-grid self-relay, make sure your whole group switches together, and switch back together when the emergency is over. This is a real trade-off: you gain a self-forming local mesh, you lose contact with anyone who hasn't switched.

How to Enable Off-Grid Repeat

  1. Open MeshCore Open and connect to your companion device.
  2. Go to Settings → Node Settings → Radio Settings. (The exact menu path is app-version dependent — these labels reflect MeshCore Open as of mid-2026; if your version differs, look for the Radio Settings section.)
  3. Tap Choose Preset and select Off-Grid 918 MHz (US/Canada).
  4. Scroll down to Enable Repeat Mode and toggle it on. (The toggle is named "Enable Repeat Mode"; its exact placement may vary by app version.)
  5. Tap the checkmark to save. The settings are written to the LoRa board.

The toggle only appears once the board is running feature-capable firmware (see Requirements). If it's not visible, update the firmware first.

Disaster Deployment Setup

Once repeat mode is enabled, the device becomes a relay for all nearby nodes on the same Off-Grid frequency. To get the most out of it during an emergency:

Practical Family Setup

A straightforward temporary disaster deployment for a household:

  1. Designate one device in the household as the off-grid relay — a spare companion that isn't someone's primary phone. A dedicated spare is better than a phone someone needs to use.
  2. Before any emergency: switch that device to Off-Grid 918 MHz, enable repeat, test that it relays messages from your other family nodes.
  3. During an emergency: plug it in near a high window and leave it running. It relays for your family and for any neighbor who has also switched to Off-Grid 918 MHz. Remember this is a temporary gap-filler, not a substitute for a dedicated repeater — and that delivery is best-effort, so confirm anything important rather than assuming it got through.
  4. Your family's other devices switch to Off-Grid 918 MHz to communicate — they don't need to enable repeat, just use the same frequency.

Off-Grid Repeat vs. a Dedicated Repeater Node

Off-Grid RepeatDedicated Repeater
Free — uses hardware you already ownRequires a separate LoRa board (typically ~$30–60 as of 2026; price varies by board and vendor)
Ready in 30 secondsRequires flashing and setup
Drains phone battery, needs power sourceLow draw — can run for an extended period on a small battery or solar when correctly sized (estimate; depends on battery/solar sizing and traffic)
Phone must stay on and BLE-connectedAlways-on, fully independent
Mobile — moves with the personFixed, consistent coverage
Emergency and temporary usePermanent infrastructure

Off-Grid Repeat is a gap-filler, not a replacement. This is the most important thing to understand about the feature. If you're building out a home or neighborhood mesh for long-term use, dedicated repeater nodes are the right answer. Off-Grid Repeat is what you use when you don't have that infrastructure yet — or when you're somewhere that infrastructure can't follow you. It is intended for small, temporary, ad-hoc groups, not as backbone or emergency-relay infrastructure, and delivery over it remains best-effort.

Turning It Off

When the emergency is over, switch back to the standard regional preset (USA/Canada Recommended) and disable repeat. There's no reason to stay on Off-Grid frequencies when your normal mesh infrastructure is available — it would isolate you from the broader regional mesh.

When Cell Service Fails — Common Scenarios

Cell networks fail in predictable ways during disasters. Understanding when and how they fail helps you plan for when mesh becomes your primary communication path.

Mesh is a supplement, not a lifeline. LoRa mesh is best-effort with no guaranteed delivery: messages may silently fail to arrive, the shared radio channel can saturate under heavy load, and coverage depends on powered relay nodes being in range. It is NOT a replacement for 911, NWS alerts, or licensed amateur/voice nets. For any life-threatening emergency, use 911/voice first; use mesh as a fallback when those are unavailable.

Power Outage

What happens to cell service: Cell sites are required to have at least 8 hours of battery backup (24 hours at switching sites), and many add generators. In an extended blackout without refueling, battery-only sites can go silent within hours, and broader coverage degrades over the following day or two.

What mesh does: Nodes run entirely on their own batteries — no grid required. A fully charged T-Echo or similar device runs roughly 12–48 hours depending on message volume and screen-on time (treat this as an estimate; actual runtime depends on the device and how it is used). Depending on the device and screen use, a 10,000 mAh bank can extend a node's runtime to several days.

Practical steps:

Wildfire Evacuation

What happens to cell service: Towers in or near fire zones are destroyed or de-energized. A mass evacuation can spike demand and congest remaining towers, making calls and data slow or unreliable, sometimes within minutes of an evacuation order.

What mesh does: LoRa mesh has no central tower to overload, so it is more resilient than cellular under mass demand. But the radio channel is shared and half-duplex; heavy local traffic still causes collisions and delays, so keep messages short and infrequent.

Practical steps:

Earthquake

What happens to cell service: Physical tower damage, severed fiber backhaul, and simultaneous call attempts make cell networks unreliable in the hours following a major earthquake. Call failure rates can be very high near the epicenter of a major quake.

What mesh does: No central infrastructure to fail. If your node is intact and powered, it communicates with any nearby node — even if every cell tower in the region is down.

Practical steps:

Hurricane and Severe Weather

What happens to cell service: Tower damage, flooding, and grid failure cumulatively degrade coverage. Service is often worst in the 12–48 hours after a direct hit.

What mesh does: Nodes deployed before the storm can operate through and after it.

Practical steps:

What Mesh Cannot Do

Honest limitations — important to understand before you depend on mesh in an emergency:

Extending Your Network to the Neighborhood

A two-node family setup is a solid start. Adding even one or two neighbors with nodes transforms a household link into a neighborhood communications network — more range, more redundancy, more shared situational awareness.

Why the Neighborhood Unit Matters

In a significant disaster, the household is rarely the right unit for coordination. Knowing that the road south is blocked, that a neighbor needs help, or that the water is safe to drink is the kind of local intelligence that neither cell broadcasts nor emergency radio provides for hours or days after an event. Mesh fills that gap at the neighborhood level. Keep in mind that mesh is best-effort and supplemental — it is not a replacement for 911 or official alerts.

The Impact of One Elevated Node

A single node at elevation — a rooftop, a tall fence post, a second-story window — dramatically expands coverage:

If you can get one household in your immediate area to permanently host an elevated repeater node, everyone with a device in range benefits.

Starting a Neighborhood Mesh Group

This doesn't require a formal organization — just a few neighbors with nodes and a shared channel. A practical starting approach:

  1. Find two or three interested neighbors. A neighborhood Nextdoor post, HOA meeting, or block party conversation is enough. Frame it as "emergency preparedness" — most people respond positively.
  2. Set up a shared neighborhood channel with a simple name (your street name, neighborhood name) and distribute the key in person. This channel is separate from your private family channel.
  3. Agree on basic channel norms: What goes on the neighborhood channel? Keep it focused — infrastructure status, road conditions, resource sharing (generator fuel, water), wellness checks. Not general chat.
  4. Map your coverage. Have each household send a test message and note who receives it directly. Gaps in coverage reveal where an elevated or repeater node would help most.

Connecting to Broader Networks

Your neighborhood mesh doesn't operate in isolation during a major event:

Next Steps