One bad night in flower undoes months

A bad night in flower kills the run

Late flower is unforgiving — an RH spike at lights-out puts water on the buds, and week-8 bud rot ends months of work over a weekend. LoopString catches the spike the night it happens.

Tuned by hand, and you forget to undo it

Clone, veg, flower, dry, and cure each want their own targets, and the dehu you crank at lights-out is easy to forget to turn back up. LoopString holds your night RH target on its own schedule, so the room is not riding on you remembering.

No one sees the slow drift

A grow with several flower rooms plus veg, dry, and cure has no single view, so a room drifts for hours before anyone notices — usually once the quality has already slipped.

The state wants environmental records

METRC and BioTrack track the plants; inspectors increasingly want the environment too, and a paper log is an audit risk. LoopString keeps timestamped records you can export per room.

VPD held per room, on the Pi

The Pi drives AC, dehumidifier, humidifier, exhaust, and CO₂ for each room, computing VPD on-site so the target follows the canopy — not just the wall thermostat.

Every room on one screen

Veg, every flower room, dry, and cure on one dashboard with sparkline trends. Recipes drive the stage transitions from veg through late flower to dry and cure.

A text before the buds are at risk

Narrow alert windows per room per stage, plus drift detection that catches a failing AC compressor, a stuck dehumidifier, or a CO₂ regulator wandering off — before it reaches the canopy.

Records built for inspection

Every reading logged with a timestamp, and per-room daily, weekly, and full-run PDF reports for inspection, QA, and lot-level traceability.