Sigrow sensors ship data over a private LoRa network to the Sigrow cloud platform. The platform exposes an API that climate computers and third-party systems can consume. This post covers what data is available, which climate computers integrate, and how it fits into an existing greenhouse installation without replacing anything.
Full API documentation: api.sigrow.com
Available measurements
Sensor Measurements Update interval Stomata Camera Leaf temperature, fruit temperature, stomatal conductance, leaf-level VPD, PAR, Real Transpiration Rate Pixel Air temperature, RH, dew point, VPD 5 min Soil Pro+ Substrate water content, EC, substrate temperature, RH, PAR 5 min Soil Mini Substrate water content, EC, temperature 5 min DrainSense Drain EC, pH, temperature, drain volume, gutter weight 5 minAll readings in SI/metric units. Timestamps in GMT.
Supported climate computers
- Priva Horticulture
- Hoogendoorn Growth Management
- Ridder
- HortOS
- Argus Controls
Integration is available via API, Modbus, or BACnet. No hardware changes to the climate computer installation.
How it fits
Sensors ──LoRa──▶ Gateway ──▶ Sigrow Cloud ──▶ API / Modbus / BACnet ──▶ Climate Computer
Enter fullscreen mode Exit fullscreen mode
The sensor network is independent from the climate computer’s own sensor bus. Both run in parallel. The climate computer reads Sigrow data and uses it as additional input for its existing control logic.
Example: Soil Pro+ reports substrate EC every 5 minutes. The climate computer reads the value, compares it to the fertigation recipe target, and adjusts feed EC or volume on the next cycle. Same pattern for drain steering with DrainSense, or VPD-based screen and vent control with Pixel.
What the API does not do
The API provides measurement data. It does not replace the climate computer’s control logic, recipe management, or alarm handling. The climate computer stays in charge.
답글 남기기