Although the term “ZWaveDevice” is used throughout this document when referring to any child device component under the station’s ZWaveNetwork, technically there are two different device components that represent a Z-Wave slave device:
A ZWaveThermostat component is dynamically created for any discovered slave device that implements a “thermostat type” generic or specific device class. Figure 8 shows an example ZWaveThermostat’s property sheet.
A ZWaveDevice component is dynamically created for any discovered slave device using a generic or specific device class that is not a “thermostat type”. For example, a “switch binary”, “switch multilevel” (dimmer), “sensor multilevel”, and so on. Figure 9 shows an example ZWaveDevice’s property sheet.
Both Z-Wave device types (ZWaveThermostat, ZWaveDevice) have the same common collection of slots (properties). Depending on the Z-Wave command classes each device type supports, each type is modeled similarly in the NiagaraAX station by child components and proxy points.