RF and telemetry gateway roles — field network¶

Purpose¶

Separate field “gateway” ( RF → IP / MQTT aggregation, buffering) from WAN customer-premises equipment—both are “gateways” in English but have different failure modes, power tiers, and backup implications.

Scope¶

• In scope: Logical roles (fixed tower vs mobile, bridge to broker, local buffer when cloud absent).
• Out of scope: Specific vendor stacks unless cited as examples on comparison pages.

Knowns¶

• The two-site stack treats broker path and SoR authority as first-class—see field telemetry entity and SoR analysis.
• Comparisons exist for fixed vs mobile and LoRaWAN vs Meshtastic for fixed telemetry.

Assumptions¶

• At least one G-class spine exists where the doctrine applies—see Field node classes (G/R/S/H/W).

Related analyses¶

• Farm sensor architecture — Demory farm site · Gateway and controller patterns — Demory (~120 acres)
• Field telemetry reference architecture — homestead + 120-acre farm
• Telemetry system of record — boundaries and authority
• Fixed gateway tower vs mobile or vehicle gateway
• LoRaWAN vs Meshtastic for fixed farm telemetry

Related topics¶

• LoRa, MQTT, and gateway bridges (ingest router; not a source note)

Related source notes¶

• None required at entity level; see ingests linked from the topic above when a claim needs raw/ grounding.

Outstanding unknowns¶

• Which RF families are in play per paddock after pilot (mesh vs LoRaWAN vs HaLow segment)—deployment decision, not wiki-invented.