To conserve batteries, most battery-powered Z-Wave slave devices “sleep” most of the time, and thus can be considered “non-listening” nodes. Whereas, line-powered slave devices are considered “always listening” nodes. Z-Wave driver support for battery-powered devices requires special considerations. See Battery-powered (non-listening) device considerations.

(Frequently Listening Routing Slave) - A special battery-powered Z-Wave device that functions as a routing slave. See Frequently Listening Routing Slave (FLiRS) device considerations.

Multiple Z-Wave devices can be controlled with a single command when placed in a group. Groups are named Group 1, Group 2, and so on.

A Z-Wave device installed on a Z-Wave network. Each node must have a unique “node ID”, an integer value from 1 to 223. Most nodes are slave devices; one or more nodes is a controller device.

The main device used to set up a Z-Wave network. There can be only one primary controller, and it must be used to add or delete devices. A primary controller can be a portable device like a hand-held remote, or a static controller (permanently installed and never removed).

A Z-Wave device that has all slave functionality plus can hold several routes. Routes are assigned by a controller.

A scene is a pre-defined combination of actions that occurs from one command. Scenes are typical to lighting control. However, if other devices support scenes, a scene may include other combinations of Z-Wave device control. For example, a scene may close the blinds, turn on inside lights to a pre-set level, and activate an outdoor motion sensor. Multiple scenes can be defined (Scene 1, Scene 2, etc.).

A Z-Wave network supports multiple controllers, where a secondary controller may be added. A secondary controller cannot be used to add or delete devices; however, it may be able to replicate the configuration of the primary controller.

A Z-Wave device that can transmit information to other Z-Wave nodes only when requested to do so. Slave devices usually have physical inputs and outputs for monitor and control, and typically are the most numerous nodes on a Z-Wave network.

A secondary controller defined as the SUC (Static Update Controller) receives updates from the primary controller when node changes occur on the Z-Wave network. Other controllers on the network can individually request the SUC for network updates. There can be only one SUC on a Z-Wave network.

An SUC (Static Update Controller) can further be configured as a node ID server, allowing all other nodes to include/exclude nodes. The SIS automatically becomes the primary controller when enabled. To maintain consistency, all node ID allocations are maintained by the SIS. There can be only one SIS on a Z-Wave network.