Start with climate, data freshness, and faults that an operator must notice immediately.
Small farms and multiple grow boxes
Monitoring, alerts, resource tracking, user access, and maintenance for several growing zones.
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.
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. |
Guides in this section
How to account for water and irrigation in a greenhouse: consumption by zones, automatic watering events, manual actions, leaks and cycle reports.
Where to start automating a greenhouse: microclimate, watering, leaks, notifications, zones and maintenance log.
A short practical playbook of greenhouse monitoring: zones, sensors, alarms, daily inspection and weekly chart analysis.
How to choose between a local controller and a cloud service for irrigation, microclimate and remote control of a greenhouse.
Using the GrowerHub dashboard as an example, let’s look at a mini-farm consisting of two growboxes: climate, light, airflow, watering, sensors, plants and access via the Internet or local server.
How to monitor several grow boxes or greenhouse zones: structure, names, priorities, comparisons and quick troubleshooting.
Which greenhouse and automatic watering scenarios should continue to work without the Internet, and which can be left for the cloud and remote access.
How to relate the result of cultivation to water consumption, light, watering, maintenance and errors so that the next cycle becomes better.
What changes when moving from one box to multiple zones: structure, roles, notifications, maintenance, reporting and reliability.
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.
How to configure GrowerHub alerts so emergencies remain visible without turning routine warnings into noise.
How to divide access in a smart greenhouse so that critical settings are changed by responsible people, and the action log remains clear.
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.