Automation
One garden, many zones
Zones are how PlantHub scales from one houseplant to a multi-zone greenhouse. Each zone has a location, an environment type, and inherits AI settings from your tenant defaults — so adding a new bed is a few clicks, not a config rewrite.
What a zone gives you
- Shared location. All devices in the zone use the same lat/lon for weather lookups — no need to set it per device.
- Environment type.
indoor,outdoor, orgreenhouse. The AI uses this to decide whether weather matters. - Zone-scoped AI settings. Override Conservative/Balanced/etc. for a whole zone without touching individual devices.
- Cross-device pattern learning. The nightly rollup aggregates per-device learning to the zone level, finding patterns like "morning watering + ventilation outperforms evening" across multiple plants.
- Dashboard grouping. The summary endpoint supports
?groupBy=zonefor at-a-glance overviews.
Typical setups
Single houseplant
You don't need zones at all. One device, no zone, default settings — done.
Apartment with plants in multiple rooms
Create one zone per room ("Kitchen", "Living room", "Bedroom"), tag them all indoor, and let the AI tune lighting and ventilation per room based on the specific microclimate.
Outdoor garden with beds
One zone per raised bed, all tagged outdoor. The forecast applies, and beds with different crops (lettuce vs tomatoes) get different plant-profile defaults at the device level.
Greenhouse
One zone tagged greenhouse with all devices inside. The AI learns at the zone level — vent + mist patterns generalize across plants, and a single Conservative override applies to the whole structure when you're away.
API
Zones are CRUD-managed under /api/v1/zones. See the API reference for the full request/response shapes.