History of Harvestree LoRaWAN firmware releases.
Product line and upgrades. The first industrial firmware line documented here is 26.8.x. Earlier 25.x lines are not detailed on this page; contact MOIZ or your supplier for archive images or legacy support.
If you move a device from 25.x to 26.8.x, plan a full re-commissioning: refresh configuration and calibration with Harvestree Toolbox, and align your LoRaWAN network server payload decoder with the release you deploy. When you connect over USB, if the device firmware is below the 26.8.x line, Harvestree Toolbox prompts you to upgrade the firmware before configuration can continue.
Payload decoder. MOIZ publishes decoder updates in an incremental way: each harvestree_decoder.js release is intended to stay compatible with the firmware versions listed on this page. MOIZ recommends keeping the latest decoder on your LoRaWAN application so decoded uplinks stay aligned with the broadest set of devices and measurement types.
When upgrading firmware, use a MOIZ-qualified image for your hardware — see Firmware update (Toolbox) in the Configuration chapter and Payload decoding in the Communication chapter.
Harvestree firmware
26.8.3 — 2026-06-05
Changed
- LoRaWAN OTAA join: the device waits until storage voltage reaches the configured minimum operating voltage before attempting join (unchanged threshold). The voltage is now re-checked every 300 s (instead of 20 s), and join retries are also paused while storage voltage stays below that limit — lower repeated measurement load while energy is building. USB remains available for configuration during the wait.
- Production tool update for mass production. No functional impact.
26.8.2 — 2026-05-19
Changes
- Maintenance release on the current protocol and measurement model (no new port types or downlink parameters).
- Reference payload decoder and Payload decoding documentation updated for the active firmware line.
26.8.1 — 2026-04-30
First industrial firmware release on the 26.8.x line.
Added
- LoRaWAN downlink for field tuning: GET_PARAM, SET_PARAM, GET_VERSION, and GET_HW_VERSION.
- Application modes: Monitoring, Alarm (unified synchronous and asynchronous paths), Idle, Modbus RTU slave.
- Measurement / ports: expanded port types (magnetic field, current with voltage difference or magnetic sensor, differential voltage with external amplifier, and related AC/RMS paths); dual-band vibration uplink (LF/HF RMS and sub-band ratios).
- Calibration: unified per-port model (offset / LUT per variable) with dedicated vibration and dry-contact handling.
- Regions: AU915 and AS923 support (with data-rate rules in LoRaWAN remote configuration).
Platform and reliability
- Configuration: a single parameter model for Toolbox and LoRaWAN downlink — same read/write behaviour, shared validation, and clearer rejection when a value is not accepted.
- USB session: more robust exchange handling on the configuration link (framing, buffer limits, and error reporting).
- Startup and commissioning: bring-up sequence reworked for field reliability; LoRaWAN join waits until storage voltage reaches the configured limit.
- Measurements: reworked analog DC and AC processing; more stable scalar conversions on common port types.
- Configuration storage: revised layout in flash with range checks; safer persist paths for keys and application settings.
- Fault handling: improved recovery after serious runtime faults; factory reset and low-battery behaviour refined in Alarm mode.
- Hardware interface: measurement front-end pins default to lower-leakage idle states until a function is required.
Changed
- Alarms: HIGH and LOW triggers include the threshold value itself (no hysteresis).
- Application modes: legacy scheduling modes removed; operation is centred on Monitoring, Alarm, Idle, and Modbus RTU slave.
Fixed
- On-board temperature in uplink metadata is correct below 0 °C.
- Vibration calibration offset is expressed in mV, consistent with the measurement chain.
Document version: 1.6
Last updated: 2026-06-05