Who is this for?
This guide is for IT departments, data engineers, and software integrators who must connect Harvestree sensors to a LoRaWAN network server (LNS), decode application payloads, persist time-series data, and feed SCADA, historians, dashboards, or cloud analytics.
Field installation, probe selection, and USB commissioning are covered in the user documentation. This guide focuses on the digital integration path.
Quick start (5 steps)
- Provision on LNS — Register each device with OTAA (DevEUI, JoinEUI, AppKey). See LoRaWAN onboarding.
- Install payload codec — Deploy
harvestree_decoder.json the LNS (FPort 1). See Data contract. - Receive uplinks — Confirm FPort 1 frames are decoded to JSON.
- Persist data — Store raw + normalized metrics. See Data model.
- Connect applications — SCADA, historian, Grafana, Python, etc. See Target systems.
What MOIZ provides vs what you build
| MOIZ provides | Your team builds |
|---|---|
| Application payload format, reference JavaScript decoder, USB Toolbox for initial commissioning | LNS provisioning, MQTT/HTTP integrations, database schema, business logic, dashboards |
| Protocol documentation (payload layout; optional remote configuration) | Alarm rules, asset registry, multi-site tagging, OT/IT security boundaries |
| Release notes and reference decoder | Decoder version alignment, data retention, replay pipelines |
Guide chapters
ArchitectureEnd-to-end data flow and responsibilities.
LoRaWAN onboardingOTAA, regional alignment, codec, LNS checklist.
Data contractJSON output, frame types, decoder install.
Data modelPersist raw + normalized telemetry; registry and unit mapping.
Ingestion pipelinesMQTT, webhooks, Python and Node.js examples.
Target systemsSCADA, historians, Grafana, cloud.
Validation checklistPass/fail criteria for go-live.