In the JACE station running the ZWave driver, a ZWaveNetwork models all slave nodes, where each node is represented by a ZWave device component (either a ZWaveDevice or ZWaveThermostat). No controller node is modeled. For example, no device component models the portable primary controller or the JACE’s Z-Wave interface (apart from some ZWaveNetwork properties). However, the Z-Wave “node ID” value of 1 remains reserved for the Z-Wave portable primary controller.

Each ZWave device component, along with all its child components, is automatically (dynamically) added in the JACE station, once the JACE is installed on the Z-Wave network. Components and proxy points are automatically determined by a device’s supported Z-Wave command classes. This varies from almost any other NiagaraAX driver, where some manual addition (or discovery and selection process), is needed using the network’s “Device Manager” view, as well as in each device’s “Point Manager” view.

Apart from this, the standard NiagaraAX network architecture applies, similar to other serial-based polling drivers. See “About Network architecture” in the Drivers Guide for more details. For example, real-time data is modeled using ZWave proxy points, which reside under ZWave devices, which in turn reside under a ZWaveNetwork container in the station’s DriverContainer (Drivers).

Hierarchically, the component architecture remains: network, device, points extension, points. The points extension is the only obvious “device extension” under a ZWave device—meaning there are no schedule or history device extensions.

Unique to a ZWaveNetwork are Z-Wave “scenes”, which are modeled at the network level using a “Scenes” network extension. A scene defines some collection of actions to one or more Z-Wave devices that can be initiated using a single command. Special views on the network’s “Scenes” extension and child “scenen” components provide easy methods to add new and edit (define) Z-Wave scenes.