Skip to main content

Terminology

This page defines the core terms used throughout the platform documentation.

Device Model

TermDefinitionExamples
HubCentral gateway that connects to all networks and the cloudZipato Box, Zipabox, cloud instance
NetworkA communication protocol and the devices on itZ-Wave network, Zigbee network, virtual network
DeviceA physical or virtual device connected to a networkLight switch, thermostat, motion sensor
EndpointA logical, addressable part of a device. May map to a native protocol endpoint or be created internally by the platformZ-Wave endpoint #0, Zigbee endpoint #1, KNX group 1/2/3
Device CapabilityA logical function of a device — a set of related attributes and actions describing one aspect of what the device can measure or control. A concept, not a stored layer; its normalized schema is a ClusterOn/off control, brightness control, energy metering
ClusterThe global, normalized schema of a Device Capability — defines which attributes and actions that capability supports. Shared across all devices that have the capabilityOnOff cluster defines PowerState; LevelControl defines BrightnessLevel
Cluster EndpointAssociates a Cluster with a specific Endpoint — represents the concrete capability of that deviceOnOff cluster on Endpoint 0, LevelControl cluster on Endpoint 0
AttributeThe schema definition of a single property on a Cluster (name, data type, read/write/report flags). Shared globally — not a value holderPowerState, BrightnessLevel
AttributeValueDefinitionA concrete, addressable data point for a specific device — holds runtime configuration (TTL, unit, reported flag, hidden flag)BrightnessLevel configuration for one specific device

Capability vs. Cluster, in one line: a Device Capability is the idea of what a device can do; a Cluster is the normalized schema that describes that capability the same way for every device that has it.

For how these pieces are created and fit together, see Device Normalization.