🛰️ Off-Grid Meshtastic Kit for 6

• Every device is a LoRa radio node (~915 MHz in the US) that text-relays for the others — a true mesh. No internet, no cell tower, no monthly fee.
• Phones connect to a node over Bluetooth with the Meshtastic app (iOS/Android) — that's the texting UI. GPS positions get reported to the mesh automatically.
• Practical range: ~1–5 km in town (buildings/trees), 10–15+ km line-of-sight from a hill. Each extra node extends coverage — 6 moving devices + a few fixed routers = a working family mesh.
• Messages hop up to 7 default relay hops; direct line-of-sight between two kids on the same channel works without any infrastructure.
• US: running these certified 903–928 MHz devices at ≤1W is legal under FCC Part 15 without an amateur license (a Technician ticket only lets you run more power).

Extras

• 5V USB power banks or wall chargers + good antennas for the fixed routers (~$30 total)
• Lanyards / MOLLE clips / small carabiners for the card trackers (~$15)
• Nothing else — no gateways, no servers, no subscriptions required

1. Flash firmware — all devices ship flashable to current Meshtastic firmware (2.x); the web flasher at flasher.meshtastic.org handles it over USB/BL. Keep every node on the same firmware version and region (US 915 MHz).
2. One shared family channel with a random PSK (private by default — set the same on all 6). Name it e.g. FAMILY. Keep the default LongFast modem preset for range/battery balance.
3. Roles: kids' trackers = Client (or Client Hidden if you don't want them relaying); home/parents' fixed nodes = Router (or Router Late) — every router you add is range the kids get for free.
4. GPS settings on trackers: position broadcast every 15–30 min normally, "smart" mode on; fixed routers: GPS off, USB power, ignore other routers off.
5. Phones: install Meshtastic app, Bluetooth-pair each kid's device to their phone (or yours, if you want to watch everyone on one map). Enable the built-in map + position messages.
6. Test protocol for kids: "if I can't see your dot on the map and texts bounce, climb to high ground — every extra node in range relays for you."

• Texting: a few seconds of latency per hop; short messages only (~227 chars max, split into fragments). It's walkie-talkie text, not iMessage.
• Battery reality: T1000-E class trackers = several days to a week+ with 15–30 min GPS intervals; ESP32 routers on power banks = days; on wall power = forever.
• Dead zones happen: dense forest/valleys can break direct links — the mesh heals the moment one more family member (or any passing Meshtastic node) is in range.
• Privacy: your private channel is encrypted with a shared key; strangers' public-channel nodes can still relay your traffic but can't read it.
• Bonus: the same mesh handles texts, GPS shared locations, and simple sensor packets (temperature, door sensors, etc.) — and it works when the cell network is congested or down.

Yes — but it's experimental, and the T1000-E can't do it. Per the official Meshtastic audio-module docs: continuous voice (Codec2) needs a 2.4 GHz SX128x radio — the sub-GHz (915 MHz) mesh isn't wide enough for audio packets, even in Short Fast mode.

• Supported boards: LILYGO TLora 2.1-1.8 and TLora T3S3 (T3 S3 Meshtastic from ~$18, verified on lilygo.cc). You add an I2S MEMS mic + MAX98357 3W I2S amp + speaker (~$10–15 in parts per node).
• How it behaves: half-duplex, push-to-talk style, Codec2 at ≤700 bps–2400 bps — think submarine/garbled radio voice, not phone quality. Channel must be ≥2 kbit/s.
• The catch: a voice node's radio is 2.4 GHz, so it lives on its own mesh — it can't relay for the 915 MHz text fleet. Voice only works device-to-device on the 2.4 GHz layer, and 2.4 GHz has shorter range than 915 MHz.

Practical options, best → worst:

1. Keep text as the primary system (it's what Meshtastic is good at) and let the phone app's notification + map do the work. This is what 95% of families use.
2. Hybrid: swap 2 of the 6 trackers for a pair of TLora T3S3 + mic/amp builds as a dedicated voice pair (e.g. the two oldest kids), keeping the other 4 on T1000-E text/GPS. Cost: ~$35–45 per voice node built.
3. Reality check: if voice is a hard requirement for all 6, Meshtastic is the wrong tool — FRS/GMRS walkie-talkies (or Zello over LTE where available) do off-grid voice better and cheaper. Meshtastic's superpower is GPS tracking + texting with zero infrastructure.

A Baofeng can never join the Meshtastic mesh directly — it's FM/digital voice on 2m/70cm, while Meshtastic is LoRa spread-spectrum on 915 MHz. Different physics, no firmware path. Integration always happens through a bridge box, and the bridge point is MQTT: any Meshtastic node with Wi-Fi (or one flashed as a router with MQTT enabled) publishes positions + messages to an MQTT broker, and bridge software on a Raspberry Pi subscribes and republishes into the radio world.

What actually works today (verified projects, Oct 2026):

• APRS bridge (the clean path): Meshtastic GPS positions → MQTT → APRS-IS. Working bridges: jaredquinn/meshtastic-bridge, robertodurrer/aprs-meshtastic_bridge, theresiasnow/meshtop, and meshsat/meshsat (Meshtastic ↔ Iridium/SMS/APRS/TAK over Reticulum, very active). Once positions are on APRS-IS, any APRS radio/TNC setup can see the kids' dots — and it shows on aprs.fi for free.
• Voice bridge (Meshtastic ↔ DMR/YSF/P25): MMDVM-based bridges (e.g. Pi-Star/BlueDV hotspots with bridge plugins) can link a DMR talkgroup to Meshtastic's experimental Codec2 audio. A Baofeng DM-32/DM-52 DMR handheld (GPS + Bluetooth built in) is the only Baofeng class that realistically takes part — analog UV-5R-style radios can only do the APRS-packet side via a TNC, not the mesh.
• Home Assistant / MQTT: official Meshtastic MQTT integration means positions/messages can pop up in HA, Node-RED, etc. — the easiest "integration into something" if the something is software.

Reality check for the family build: the Baofeng path adds a Pi, an MQTT broker, a licensed operator (ham ticket for the 2m/70cm side), and a TNC or DMR handheld per person. For 6 people off-grid, it's a fun parent's hobby layer on top of the T1000-E mesh — not a replacement. If the goal is just "walkie-talkie feel," FRS/GMRS radios remain simpler.

• meshtastic.org — Getting Started / device catalog (T1000-E specs: nRF52840, LR1110, 700 mAh, GPS)
• Seeed Studio store — SenseCAP T1000-E for Meshtastic, $39.90 (live page, Oct 2026)
• RAK Store — WisMesh Tag, $39.00 (live page, Oct 2026)
• Elecrow store — ThinkNode M9 keyboard terminal, as low as $74.90 (live page, Oct 2026)
• LILYGO store — T-Echo (alternative with screen), $44.61 (live page, Oct 2026)
• meshtastic.org/docs/configuration/module/audio — Audio (Codec2) module: 2.4 GHz SX128x only; supported boards TLora 2.1-1.8 / TLora T3S3 (live page, Oct 2026)
• GitHub repo search (Oct 2026): meshsat/meshsat, jaredquinn/meshtastic-bridge, robertodurrer/aprs-meshtastic_bridge, theresiasnow/meshtop — live Meshtastic↔APRS bridges