Sub-GHz field networking — synthesis¶
Purpose: One file that maps everything this wiki treats as sub-GHz field networking—LoRa PHY stacks, LoRaWAN, Meshtastic mesh, IEEE 802.11ah / Wi‑Fi HaLow—and routes readers to canonical analyses, comparisons, entities, and source clusters. It does not replace detailed pages; it indexes them.
Integration: New RF captures should activate per AGENTS.md: cluster source-notes get Evidence summaries; doctrine pages absorb claims that change architecture or stop rules. Start from Off-grid power and field networking hub or the source index below—not this page alone.
Scope — what “sub-GHz” means here¶
| In scope | Notes |
|---|---|
| LoRa physical layer | Chirp spread spectrum; shared by LoRaWAN and Meshtastic. |
| LoRaWAN | Star / gateway → network server → application; sparse telemetry, LPWAN. |
| Meshtastic | LoRa mesh (multi-hop), local survivability, bridges to IP/MQTT at gateways. |
| Wi‑Fi HaLow (802.11ah) | Sub-GHz IP-class links; different ops model than LPWAN. |
| MQTT / app bridges | How sensor traffic reaches brokers and consumers—not a radio layer, but wired throughout. |
| Adjacent / contrasted | Notes |
|---|---|
| WAN (Starlink, LTE, fiber) | Not a field sensor radio; see WAN vs field RF below. |
| Conventional 2.4 / 5 / 6 GHz Wi‑Fi | Compared in four-way analyses; not “sub-GHz” but part of the same field networking decisions. |
| NB‑IoT / cellular LPWAN | Mentioned in Field network IoT comparisons (HaLow, LoRa, NB-IoT); not a primary East Tennessee stack in this vault. |
Executive summary¶
- Field sub-GHz in this repo is organized around sparse telemetry (LoRaWAN or Meshtastic) vs IP throughput where needed (HaLow segments), always on an off-grid-aware power and local-first survivability story—especially for
SITE_FARM(Demory). - LoRaWAN fits star coverage to one or more gateways; terrain and gateway placement dominate range claims—treat vendor numbers as hypotheses.
- Meshtastic adds mesh relay and community/off-grid voice; density and partitions matter as much as “range.”
- Wi‑Fi HaLow trades 802.11-style ops (segmentation, patching, AP/CPE power) for longer-range IP than indoor Wi‑Fi—not automatic farm-wide mesh.
- Starlink / LTE / fiber are WAN backhaul roles; they must not be confused with field sensor links (canonical rule across sensor architecture pages).
WAN vs field RF (non-negotiable)¶
Starlink, cellular, and terrestrial broadband answer “how does the farm reach the internet or site-to-site VPN?” Sub-GHz field stacks answer “how do sensors and field nodes reach a gateway / broker when Wi‑Fi or Ethernet is impractical?”
Authoritative articulation: Farm sensor architecture — Demory farm site (Starlink = WAN only). WAN strategy: Connectivity strategy — Claxton home base and Demory farm site. WAN roles as entities: WAN edge and backhaul roles vs RF telemetry gateway roles.
Three stacks — mental model¶
| Stack | Shape | Best mental picture |
|---|---|---|
| LoRaWAN | Star to GW + NS | Sparse uplinks, excellent sleep; gateway concentration risk. |
| Meshtastic | Mesh | Multi-hop fill-in; map ≠ RF; bridge at G to IP/MQTT. |
| Wi‑Fi HaLow | 802.11ah segment | IP-native where deployed; plan AP/CPE power and security like Wi‑Fi. |
Deeper criteria (coverage, power, survivability, IP vs sparse): LoRaWAN vs Wi‑Fi HaLow vs Meshtastic — Demory farm sensor layer.
Start here — by reader goal¶
Comparisons (wiki)¶
LoRaWAN vs Wi‑Fi HaLow vs Meshtastic — Demory farm sensor layer— Primary three-way forSITE_FARMsensing.Wi‑Fi HaLow vs LoRaWAN vs Meshtastic vs conventional Wi‑Fi — farm field networking— Four-way matrix (adds conventional Wi‑Fi).LoRaWAN vs Meshtastic for fixed farm telemetry— Star/gateway vs mesh; SPOF and ops.Meshtastic vs Wi‑Fi HaLow vs conventional Wi‑Fi — off-grid farm operations— Off-grid-first operations framing.Anderson County vs Campbell County — operating implications— Not RF physics—two-site context for where telemetry and WAN assumptions differ.
Concepts¶
LoRa (radio)— PHY vs stacks.LoRaWAN— LPWAN star model.Meshtastic— LoRa mesh firmware ecosystem.Wi-Fi HaLow— 802.11ah sub-GHz Wi‑Fi.
Analyses — architecture, gateway patterns, degraded modes¶
Entities — roles and link layers¶
Field node classes (G/R/S/H/W) — off-grid farm rolesRF telemetry gateway roles — field networkField radio link classes — LPWAN, mesh, and IP bridgesWAN edge and backhaul roles
Standards (naming and boundaries)¶
Field node identity and naming standardGateway naming and role assignment standardSite-to-site network role boundaries standard
Source clusters and notable batches¶
| Kind | Page |
|---|---|
| Demory planning index | Off-grid power, field RF, and optional WAN — source index |
| Sensor layer cluster | Demory farm sensor layer — official and operator-grade source cluster |
| Tennessee batch (LoRaWAN, ChirpStack, Meshtastic, Decentlab, HaLow) | Inbox batch — 2026-04-18 |
| Electrical / Starlink batch | Electrical, networking, and Starlink — inbox batch (2026-04-23) |
Illustrative Meshtastic / solar node sources (operator-grade mixed authority): Building solar-powered Meshtastic community network, How to build a solar Meshtastic node the easy way, Meshtastic nodes basics and deployment (Seeed), Solar Meshtastic GPS ESP32 outdoor.
Related topics (narrative and precision ag)¶
Smart agriculture, Meshtastic, and LoRaWANPrecision agriculture— concept; see source-notes fromField network IoT comparisonsfor LPWAN article links.
Runbooks touching field / backhaul¶
Runbook — broker or backhaul downRunbook — power loss at remote siteRunbook — sensor false positive and alert triage
Meta¶
- Catalog:
index.md— full wiki index (this page is a focused slice). - Package artifact backlog (matrices, Evidence queues):
Package artifact backlog — canonical East Tennessee packages.