End-to-end flow — Harvestree

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.

MOIZ

Device FWPayload formatDecoder JSToolbox

Network

GatewaysLNS / NSOTAA joinOptional Downlink

APPLICATION

ProvisioningIngest MQTT/HTTPDB schemaSCADA / dashboardsAlarm business rules

Who owns what

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; optional codec hosting
Integrator / client IT	Integrator or internal IT	Ingestion pipeline (may run the reference decoder), device registry, database, normalization, security
Business applications	End customer	SCADA, historian, MES, dashboards, alerting rules

Two directions

Uplink — Measurements leave the device on FPort 1, cross the LoRaWAN network, then are decoded with the MOIZ reference codec (on the LNS and/or in your integration service) before storage and business apps.
Downlink (optional) — Remote configuration on FPort 4 with ACK on FPort 2. Not required for uplink-only integration. Reference codec covers FPort 1 only.

%%{init: {
  "flowchart": {
    "curve": "basis",
    "padding": 14,
    "nodeSpacing": 28,
    "rankSpacing": 36,
    "htmlLabels": true,
    "useMaxWidth": true
  },
  "themeVariables": {
    "fontSize": "16px"
  }
}}%%
flowchart TB
  subgraph moiz ["MOIZ"]
    direction LR
    Probes["M8 probes"] --> HVT["Harvestree HVT5"]
    Codec["Reference decoder"]
  end

  subgraph lorawan ["LoRaWAN network"]
    direction LR
    GW["Gateway"] --> LNS["Network server"]
  end

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

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

  HVT -->|"FPort 1 uplink"| GW
  Codec -.->|"optional on LNS"| LNS
  Codec -.->|"or in worker"| Pipe
  LNS -->|"MQTT / HTTP / webhook"| Pipe
  DB --> APP
  APP -.->|"FPort 4 downlink"| LNS

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).
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 data retention on the device — Harvestree does not store historical measurements. Persist and historize uplinks in your application stack.
Payload size — LoRaWAN caps the application payload at 51 bytes (FPort 1). MOIZ restricts allowed port-type combinations at commissioning so supported configurations always fit.