The closed loop: levers, signal and plant state

What this is (and why a grow room is a loop)

A grow room is a loop, not a panel of independent dials you set and forget. You change a control, the room and plants respond, sensors measure that response, you work out what it means, and that tells you what to change next. Around and around, every minute of every day.

A closed loop means the output feeds back to the input: what the plant tells you decides your next move, and then you watch what that move actually did. This guide teaches the whole circle as one thing, with three jobs sitting on it: getting the action right (cause), getting the measurement honest (perception), and getting the meaning out (cognition).

You never move just one thing. Every control pushes on four linked balances at once: heat, water vapour, CO2 and the salt in the root zone. The finished version of this loop is a room that senses its own state, knows what its actions will do, and corrects its own drift before that drift becomes damage.

Key terms, defined once

This field is loaded with jargon, so here is every term you need before the real content. Most are everyday ideas with intimidating names. Don't memorise them. Each one comes back in context.

The levers: every control moves four things at once

The room is one coupled system, not a set of independent knobs. Turn up the light and you have not just added light: you have added heat, made the plants drink and sweat faster (raising humidity), increased CO2 demand, and sped up how fast the root zone dries and concentrates salt^[4]. Light is at once a heat source, a transpiration driver, a CO2-demand creator and an HVAC load^[5].

Everything you can do sorts into four balances you are always disturbing: energy (heat), moisture (water vapour), carbon (CO2) and salt (root-zone EC), with around eleven primary lever families acting across them^[5]. The right question before any change is not ‘what does this lever do?’ but ‘which balance am I disturbing, and can the rest of the room absorb it?’

Reading the signal, then reading the plant

You have to see the room's response without being fooled, then turn it into meaning. Every measurement is signal plus noise, and in practice around 70% of raw alerts are noise that must be rejected before they ever reach a decision^[2].

Reading plant state is the leap from ‘VWC fell 12% overnight’ (a number) to ‘the plant is steering generative as intended, no action needed’ or ‘reduce dryback 3% tonight or expect tip burn in about 48 hours’ (a decision). The goal is to infer the plant, not just display the room.

Three signal habits, in order, get you there:

• Sample at the right speed for the biology: fast enough to catch a 30-minute irrigation response, slow enough not to log useless jitter.
• Filter out scatter with rolling or median averages before you look.
• Judge with control limits, lines drawn from the process's own history, conventionally the mean and roughly ±3 standard deviations (sigma)^[1].

Then aggregate, don't trust one reading: believe n-of-12, not n-of-1. A clean, classified signal is the only acceptable input to inference. Inference then fuses several cleaned signals into named conditions, each with a confidence level and an evidence chain, judged against a learned envelope rather than a fixed line. 1.4 kPa VPD is fine in late flower but punishing in early veg.

Closing the loop: one problem, traced all the way round

The three jobs become one machine here. Watch a single ordinary problem, slow salt creep in the root zone, travel the whole loop.

1. 1
   Cause sets the conditions

   A long dryback plus a flat feed concentrates salt a little more each cycle. The slowest balance is loading.
2. 2
   Perception refuses to overreact

   It ignores any single EC spike, but flags a sustained four-day rising run past the control limit as a true signal.
3. 3
   Cognition gives it meaning

   It fuses that run with feed and dryback data into a named precursor, 'salt accumulation, tip-burn precursor', with confidence and evidence.
4. 4
   Prescribe and act

   It pulls the dryback lever back, closing the loop about four days before tip burn would appear, and the salt balance starts recovering.

Bridge metrics let the three jobs talk to each other. Dryback %, VPD and VPD-hours, pore-water EC and recovery slope are each computed once on a consistent definition and read by every part. Always prescribe with a number and show your work: name the action, the setpoint, the deadline and the expected outcome, expandable to the full evidence on demand. Never be a black box.

How to build the loop, step by step

You build the loop one rung at a time, and you do not earn the next rung until the previous one is genuinely running. Almost none of this needs new capital. Most of it is discipline.

1. 1
   Arc I: get your actions coupling-aware

   Before any change, name which of the four balances it moves and in which direction. Treat every failure as a capacity or coordination problem, not one bad lever.
2. 2
   Arc II: get your signals honest

   Stop watching live numbers (they invite over-reaction). Set a sampling cadence per channel, put a rolling average on every decision chart, and compute control limits from your own history.
3. 3
   Arc III: get your decisions inferred

   Judge against an envelope per cultivar/stage/photoperiod. Fuse before you flag, because no signal stands alone. Make every advisory prescribe a number and show its evidence, and go quiet by default.
4. 4
   Close the loop last, and gently

   Gate the first automated write-back to a low-risk, reversible move, for example a 3-point dryback nudge behind a confirm. Keep expensive or irreversible actions human-approved.

Pitfalls: oscillation and chasing noise

Two failure modes ruin a loop: chasing noise and oscillation. Feed a controller noise, meaning single spikes, jitter and ghost trends, and it acts on events that never happened, actively destabilising the room. A loop fed noise doesn't help, it amplifies. Oscillation comes from reacting too fast, too hard, or to readings still inside normal variation, so the room swings back and forth instead of settling^[1].

• Aliasing: sampling too slowly invents phantom trends, and over-sampling logs jitter you can't act on and tempts you to tamper. Match cadence to the biology^[7].
• The Stage-2 trap: reacting to live numbers is more stressful than flying blind. It's a wall of noise to panic at.
• Walk the loop, not the wiggle: smooth enough to act calmly, but never so smooth you go blind to a real fast event. Keep raw data one click away.

Realistic expectations

• You don't have to automate to win. Intelligence reaches the screen long before autonomous actuation, and stopping there is a fine, stable outcome.
• Numbers are starting points, not gospel. Reference setpoints are commercial-cultivation starting points to calibrate against your own facility's history. The method is universal; the setpoints are yours.
• Prove it small. Pick one room and one failure pattern, run it in shadow-mode for one cycle, and prove the lead time on a single advisory before you scale.

Get your actions coupling-aware, your signals honest, and your decisions inferred. Then, and only then, consider closing the loop. To go deeper on the perception half, read the signal and noise paper. For the cognition half and how it reaches you, read the plant-state dashboard guide.