Mini-farm of two grow boxes: how to organize control and automation
Divide a small farm into zones, set light schedules and test watering before buying sensors. A practical walkthrough of the GrowerHub demo farm.
Small farms and multiple grow boxes
Monitoring, alerts, resource tracking, user access, and maintenance for several growing zones.
Guides in this topic (12)
Greenhouse automation: what to control first
Where to start automating a greenhouse: microclimate, watering, leaks, notifications, zones and maintenance log.
Local controller or cloud service: what to choose for a greenhouse
How to choose between a local controller and a cloud service for irrigation, microclimate and remote control of a greenhouse.
Scaling from box to mini-farm: what changes
What changes when moving from one box to multiple zones: structure, roles, notifications, maintenance, reporting and reliability.
Monitoring multiple grow boxes: zones, sensors and one dashboard
How to monitor several grow boxes or greenhouse zones: structure, names, priorities, comparisons and quick troubleshooting.
Reliability of automation without the Internet: what should work locally
Which greenhouse and automatic watering scenarios should continue to work without the Internet, and which can be left for the cloud and remote access.
Show more articles (6)
Reports on harvest and resources: water, light, labor and results
How to relate the result of cultivation to water consumption, light, watering, maintenance and errors so that the next cycle becomes better.
User roles in a smart greenhouse: owner, operator and observer
How to divide access in a smart greenhouse so that critical settings are changed by responsible people, and the action log remains clear.
Service mode: how to replace a sensor without chaos in automation
Why do you need a service mode when replacing a sensor, cleaning droppers or servicing a zone, and how to prevent the automation from mistaking the service for an emergency.
Accounting for water and irrigation in a greenhouse: why do you need a log?
How to account for water and irrigation in a greenhouse: consumption by zones, automatic watering events, manual actions, leaks and cycle reports.
Mini-farm alerts: emergencies, risks and maintenance
Which greenhouse alerts are useful, how to choose thresholds, and what you can already check in GrowerHub: readings, history and automation.
Greenhouse monitoring: quick playbook
Start monitoring with GrowerHub: one greenhouse, fresh readings, sensor history, daily checks and one verified automation scenario.
Help me choose where to start
Where to start
Multiple zones do not require a large automation project on day one. Build a shared overview, use consistent equipment names, and surface faults first; add control scenarios one at a time.
Start with climate, data freshness, and faults that an operator must notice immediately.
Show each zone with the same core measurements and keep site-wide problems separate.
Track update times, missing data, and equipment that needs attention.
Choose your first step
| Situation | Where to start | Why |
|---|---|---|
| Data is spread across several applications | One zone overview and consistent names | The operator must first be able to understand the farm at a glance. |
| Zones use different operating modes | Separate resources and scenarios per zone | One shared rule for different equipment makes faults harder to diagnose. |
| You need remote monitoring | Data freshness and failure notifications | A polished chart is misleading when its latest reading is stale. |
Organize the farm into clear zones
Connect a coordinator, assign discovered devices to rooms or greenhouses, and get a shared overview without describing crops first.