Integrate PKYDrip with ThingsBoard & Your Systems | PKYDrip
An Open Platform, Not a Closed Box
PKYDrip is built for integrators. Our controllers and fertigation machines are designed to plug into your stack — whether that is the PKYDrip cloud, a self-hosted instance, or a third-party platform like ThingsBoard. Field protocols and platform integration paths are documented and publicly available.
Integration Paths
| Path | What It Gives You | Status |
|---|---|---|
| PKYDrip Cloud Platform | Ready-made dashboards, scheduling, alarms, multi-tenant roles | Shipping |
| ThingsBoard connection | Bridge device telemetry and control into your own ThingsBoard instance — device data flows in as standard telemetry attributes | Documented example |
| Field bus (Modbus RTU) | Direct integration with PLCs and third-party controllers on site | Documented |
| Platform message bridge | Device-to-cloud transport for custom back ends and OEM builds | Documented |
Example: Connecting PKYDrip to ThingsBoard
A common integration for smart-agriculture companies: keep PKYDrip controllers running irrigation and fertigation locally, while ThingsBoard consumes device telemetry for fleet-wide dashboards and rule chains.
Device layer: controllers publish telemetry (zone status, flow, EC/pH, sensor values) over the platform message bridge.
Bridge layer: a lightweight connector maps PKYDrip device topics/registers to ThingsBoard device profiles.
ThingsBoard layer: standard dashboards, rule chains and alarms — your existing team manages it like any other ThingsBoard device.
The step-by-step guide (device profile JSON, bridge configuration, topic map) lives in our public documentation site.
Public Documentation
Installation & wiring guides for irrigation controllers, 3/5-channel fertigation machines, EC/pH controllers and wireless valve controllers
Platform integration guide — including the ThingsBoard connection example
Real deployment case notes (watermelon, 1 ha strawberry, and other projects)
Full documentation site: docs.pky-dripirrigation.com (launching). Until then, request the current documentation package directly.