OpenSprinkler integration

Turn OpenSprinkler into a reviewable cannabis irrigation controller.

OpenSprinkler is excellent at executing timed station programs. Core Cannabis adds the crop-day context, table scope, measured-flow runtime, and preflight proof growers need before those programs run.

Keep crop logic outside the controller

Core Cannabis creates the canonical schedule. OpenSprinkler translates approved start times and durations into station programs without recalculating the crop plan.

  • Exact schedule date
  • Exact start time and duration
  • Explicit table-to-zone mapping

Prove the handoff

Preflight compares the visible schedule, applied payload, and controller preview. A connection badge alone is never treated as schedule verification.

  • Displayed schedule proof
  • Grouped program count
  • Mismatch blocks deployment

Support daily automation

When auto-push is enabled, the next schedule can be prepared at lights-off from the approved response or unchanged baseline, then deployed only after validation.

  • Baseline when no response exists
  • Table-scoped adjustment when response exists
  • Deployment records remain history

Preserve operator control

Growers can review the same schedule fields that reach the controller and keep manual testing separate from automated production windows.

  • Manual test allowance
  • Controller emergency stop
  • Read-only deployment history

Questions growers ask

Is Core Cannabis affiliated with OpenSprinkler?

No. Core Cannabis is independent software designed to work with OpenSprinkler controllers and is not affiliated with or endorsed by OpenSprinkler.

Does OpenSprinkler calculate crop steering?

No. Core Cannabis builds the reviewed canonical irrigation events. OpenSprinkler executes the resulting station times and runtimes.

Can each table use a different runtime?

Yes. Station-specific schedules can preserve different volumes and durations by mapped table while using the intended room-level timeline.