ZWaveDevice common properties

Common properties (or slots) on any ZWaveDevice appear near the top of its property sheet, as shown in Figure 10.

Figure 10. ZWaveDevice property sheet, showing properties and slots common among all ZWaveDevices

These common Z-Wave device properties or slots are described as follows:

Status, Enabled, Fault Cause, Health, Alarm Source Info

These properties operate the same as for a device object in most drivers. see “Common device components” in the Drivers Guide for general information on these properties.
Max Fail Until Device Down

Specifies how many unanswered device pings must occur before the driver marks this device with a “down” status, where the default value is 2.
Device Profile

Used to define and display the “Device Profile” for this specific type of device. See About Device Profiles.
Node Id

(read-only) The unique Z-Wave node address of the device. It is originally assigned by a Z-Wave primary controller when a Z-Wave device is installed / added to a network.
Read Device On Event Update

This property is visible only if this device is a non-listening (battery-powered) device, and has a default value of false. It controls whether or not the driver attempts to read all Z-Wave device points and components upon receiving an association event message.
If the device is a listening device, it always reads all Z-Wave device points and components on an event message.

Some non-listening battery-powered devices stay awake long enough to read this data, and others do not. If you set this to true and the device does not stay awake long enough to read all the data, it could cause several seconds of communications delay due to communications timeouts.
Node Info

Container slot that lists the Z-Wave device type and supported command classes. See Node Info.
Points

A standard Points device extension (container) for data items in this Z-Wave device that need to be polled for data. See Points.

Node Info

Among ZWaveDevice common properties, Node Info (Node Information) is a container slot for all node information returned from any Z-Wave device. Figure 11 shows an example.

Figure 11. Node Info expanded in ZWaveDevice property sheet

Expand Node Info to see all its read-only properties, including:

Is Listening — Indicates if this node is always listening or not. Typically this is false for any battery-powered node that sleeps.

The driver does not attempt communications to a non-listening device that is asleep. If the device also implements the WakeUp command class, it uses the Wake Up Notification message from the device as an indication that the device is awake, and attempts to read all the device's data at that time.
Optional Functionality — Indicates that this node supports other command classes in addition to mandatory classes for its selected generic and specific device class.
Sensor250ms — If true, indicates that this node is an FLiRS (Frequently Listening Routing Slave) device with a wakeup interval of 250ms.
Sensor1000ms — If true, indicates that this node is an FLiRS (Frequently Listening Routing Slave) device with a wakeup interval of 1000ms.
Basic Device Class — Identifies the Z-Wave library used by this device. Possible values include: Portable Controller, Static Controller, Slave, and Routing Slave.
Generic Device Class — Identifies the main functionality of this device. For Generic Device Class descriptions, refer to document 2 in Z-Wave reference documents.
Specific Device Class — Identifies a specific variant of the Generic Device Class that applies to this device. Again, refer to document 2 in Z-Wave reference documents for descriptions.
Command Classes Raw — A byte array of identifiers for all command classes supported by this device, as received from the device.
Cmd Classes — Container for all Z-Wave command classes supported by the device, where each command class is represented as an expandable node with properties.

Command classes are listed using the format:

xNN CommandClassType,
ver=x, count=y

where NN is the code for that command class, x is version number, and y is number of instances.

For example:

x31 Sensor Multilevel, ver=1, count=3

Expanding any listed command class simply shows (again) its Cmd Class Type, Version, and Instances (count) as separate properties.
Unsupported Cmd Classes — Container for all Z-Wave command classes supported by the device, but not supported by the driver. Unsupported command classes are listed using the format:

xNN CommandClassType

This container should be empty if all the device’s command classes are supported by the driver.

A “Create Command Classes” action is also avaiable on NodeInformation (Node Info). This command automatically occurs upon any device discovery. This creates all the dynamic components under the ZWaveDevice and in its Points container.

Points

Among ZWaveDevice common properties, Points (ZWavePointDevExt) is a container slot for all dynamically added control points (Z-Wave proxy points) for that device. Proxy points correspond to any Z-Wave command classes best modeled as control points, for real-time monitoring and control.

Figure 12. Points of a ZWaveDevice, in the default ZWave Point Manager view of the device extension

Some Z-Wave command classes result in (one or more) dynamically created proxy points, while others result (instead) with dynamically created “child components” directly under the ZWaveDevice parent. See the section ZWaveDevice child components for more information.

A few Z-Wave command classes result in both ZWaveDevice child components and proxy points. For a complete listing of how Z-Wave component modeling occurs for Z-Wave command classes, arranged alphabetically by Z-Wave command class name, see Z-Wave command classes supported.

For more details on Z-Wave proxy points, ZWave proxy points.