System architecture — Harvestree Integration Guide

End-to-end data flow

The diagram below shows how measurement data travels from the physical probes to your business applications, and how optional remote commands travel back to the device.

Who owns what (read left to right)

Zone	Owner	Typical content
MOIZ	Manufacturer	Harvestree device, application protocol, reference decoder, Toolbox (USB commissioning)
LoRaWAN network	Operator or client IT	Gateway, network server (LNS), join routing, codec hosting
Integrator / client IT	Integrator or internal IT	Ingestion pipeline, device registry, database, normalization, security
Business applications	End customer	SCADA, historian, MES, dashboards, alerting rules

Two directions

Uplink (solid, left → right) — Measurements leave the device on FPort 1, cross the LoRaWAN network, are decoded (codec on LNS using MOIZ reference), then ingested and stored by the integrator stack before reaching business apps.
Downlink (dashed, right → center) — Optional: remote configuration on FPort 4 with ACK on FPort 2. Not required for uplink-only integration. See LoRaWAN remote configuration.

Diagram

flowchart LR
  subgraph moiz ["MOIZ"]
    Probes["M8 probes"]
    HVT["Harvestree HVT5"]
    Codec["Reference decoder"]
  end

  subgraph lorawan ["LoRaWAN network"]
    GW["Gateway"]
    LNS["Network server"]
  end

  subgraph integrator ["Integrator / client IT"]
    Pipe["Ingestion pipeline"]
    DB[("Database")]
  end

  subgraph apps ["Business applications"]
    APP["SCADA · historian · dashboards"]
  end

  Probes --> HVT
  HVT -->|"FPort 1 uplink"| GW
  GW --> LNS
  Codec -.->|"codec on LNS"| LNS
  LNS -->|"MQTT / HTTP / webhook"| Pipe
  Pipe --> DB
  DB --> APP
  APP -.->|"FPort 4 downlink"| LNS

Roles and responsibilities

Party	Typical responsibility
MOIZ	Device firmware, application protocol, reference decoder, Toolbox USB commissioning, protocol documentation
LoRaWAN operator / LNS admin	Radio coverage, gateway, join server, routing uplinks and downlinks
Client IT / integrator	Device registry, codec deployment, ingestion, database, dashboards, SCADA connectors, security
Field team	Mounting, probe wiring, initial USB setup (see user docs)

Integration constraints to design for

Energy gating — OTAA join and measurement uplinks occur only when storageVoltage is at or above the configured minimum (voltage_limit, factory default 3500 mV). Below threshold, the device may send keepalive frames only (status: 0). See Operation.
Irregular cadence — Measurement period is configurable (20 s to 7 days). Plan time-series storage for sparse/variable intervals.
Dynamic port layout — Bytes 1–4 of each uplink encode configured port types; decoded JSON keys change when port configuration changes.
No alarm hysteresis in firmware — Alarm decisions use the current sample. Add filtering in your application if needed.
Payload size — LoRaWAN caps the application payload at 51 bytes (FPort 1). MOIZ currently restricts allowed port-type combinations at commissioning (Harvestree Toolbox) so that supported configurations always fit within this limit. Integrators do not need to size port mixes themselves for factory-supported setups; follow the commissioned port layout in each uplink.