Field telemetry network — two-site¶

What this entity is: The logical system connecting field devices at SITE_FARM (and sometimes SITE_HOME) to gateways, backhaul, MQTT broker, consumers (Home Assistant, DB, alerts), and records—as one cross-cutting stack, regardless of whether radios are LoRaWAN, mesh, or Wi‑Fi.

Why it matters: Splitting discussion only by radio without broker / SoR / security context produces sideways analyses; this entity is the anchor for “the whole path.”

Canonical analyses

• Package map: Reference architecture — 5-acre home base + 120-acre farm
• Stack detail: Field telemetry reference architecture — homestead + 120-acre farm
• SITE_FARM (Demory) sensor architecture: Farm sensor architecture — Demory farm site · Sensor checklist matrix — Demory farm · LoRaWAN vs Wi‑Fi HaLow vs Meshtastic — Demory farm sensor layer
• Authority: Telemetry system of record — boundaries and authority

Gateway classes (tradeoffs, not one vendor): Fixed gateway tower vs mobile or vehicle gateway, LoRaWAN vs Meshtastic for fixed farm telemetry.

Does not claim: Your broker hostname, VLAN layout, or chosen radio—placeholders stay in architecture pages until deployed.

Operating-object entities (roles, not vendors): RF and telemetry gateway roles, WAN edge and backhaul roles, Field node classes (G/R/S/H/W), Field radio link classes.

Related

• farmOS — agronomic records side of the same data story
• Glossary: System of record (farm data)