Import & Export

Zones can be bulk imported or exported using CSV files. This is useful for initial setup, integration with other systems, or performing bulk edits.

CSV Structure

Each row in the CSV represents a single zone. The following fields are recognized:

Field	Required	Description
name	Required	The display name of the zone (e.g., Zone A).
type	Optional	The zone type (see Zone Types). Defaults to generic.
id	Optional	The system identifier of the zone. If provided, import will attempt to merge with an existing zone. If omitted, a new zone is created.
parent_zone_id	Optional	The id of the parent zone. Zones may nest.

Zones do not have configurable properties - name, type, and parent_zone_id are the complete set of fields.

Example:

name,        type, parent_zone_id
Zone A,      hvac,
Zone A West, hvac, z.1

Nesting Rules

Zones may nest via parent_zone_id, subject to three constraints:

• A zone cannot be its own parent.
• A parent zone must be the same type as its child. An hvac zone cannot be nested under a lighting zone.
• A zone’s type cannot be changed while it has child zones. Re-parent or remove the children first.

Import Behavior

• Merge — If an id is provided and a matching zone exists, the row’s fields are merged into the existing record. Fields not listed remain unchanged.

• Add Zone — If no id is provided, the row is added as a new zone.

• Validation — name is required on every row. If import validation fails, no data will be added or updated. All errors are reported so they can be corrected and the import retried.

Export

Export produces a CSV with the columns name, id, type, and parent_zone_id for every defined zone. This export can be used as a template for re-importing updates - keep the id column to update existing zones, or clear it to create copies.