7.3. Z-Wave Plus v2 Device Type Definition

7.3.1. Optional Command Classes

\requirement{DT:00.11.000F.1}{4}

Device Types MAY support optional Command Classes on top of the minimum mandatory set of supported Command Classes. However, the following Command Classes MUST NOT be supported optionally in a Device Type:

  • Barrier Operator

  • Color Switch

  • Window Covering

  • Multilevel Switch

  • Thermostat Mode

  • Thermostat Setpoint

  • Thermostat Setback

  • Sound Switch

  • Simple AV Control

  • Door Lock

  • Binary Switch

\requirement{DT:00.11.0010.1}{0}

It means that if supported, these command classes MUST fit the exact actuator Command Class list of a Device Type. If several actuator Command Classes not belonging to the Device Type need to be supported, they MUST be partitioned in End Points which match the actuator Command Class list of a Device Type.

Multi Channel Root Devices MAY still aggregate some of the above mentioned Command Classes from their end points for backwards compatibility. The optional Command Class rule applies:

  • For the node (Root Device) if the node does not support Multi Channel Command Class

  • For each and every end point if the node supports the Multi Channel Command Class

7.3.2. Supporting Device Type Overview

The Z-Wave Plus v2 certification program defines a new set of Device Type based on which Command Classes are supported. They are classified into 3 categories:

  • Actuator supporting device types.

  • Data reporting devices types

  • Other devices types.

The list of Supporting Device Types is shown in Table 7.6, Table 7.7 and Table 7.8.

Table 7.6 Z-Wave Plus v2 Supporting Actuator Device Types Overview

Device Type

Mandatory

Recommended Options

Role Types

Lock

Door Lock, v4

Security 0 (S0)

User Code

Entry Control

All except WOEEN

Motorized barrier

Barrier Operator

Notification, v8

Security 0 (S0)

All except WOEEN

Color Switch

Color Switch, v3

Multilevel Switch v4 or Binary Switch v2

Multi Command

All except WOEEN

Window Covering

Window covering

Multilevel Switch v4

All except WOEEN

Thermostat

Thermostat Mode, v3

Thermostat Setpoint

Time, v3

Multilevel Sensor

Schedule, v4

Thermostat Setback

All except WOEEN

Sound Switch

Sound Switch

All except WOEEN

AV Control Point

Simple AV Control

All except WOEEN

Multilevel Switch

Multilevel Switch, v4

All except WOEEN

Binary Switch

Binary Switch, v2

All except WOEEN
Table 7.7 Z-Wave Plus v2 Supporting Data Reporting Device Types Overview

Device Type

Mandatory

Recommended Options

Role Types

Entry Control Keypad

Entry Control

Security 0 (S0)

All

Multilevel Sensor

Multilevel Sensor, v11

Multi Command (control)

All

Notification Sensor

Notification, v8

Multi Command (control)

All

Meter Sensor

Meter, v5

Multi Command (control)

All

Central Scene

Central Scene, v3

Basic (control)

All
Table 7.8 Z-Wave Plus v2 Supporting Other Device Types Overview

Device Type

Mandatory

Recommended Options

Role Types

Repeater

No other Command Class than Section 7.2.2.1

AOEN

IR Repeater

IR Repeater Command Class

AOEN

7.3.3. Controlling Device Type Overview

The Z-Wave Plus v2 certification program defines a new set of Device Type for controllers based on which Command Classes are supported and controlled.

All static controllers (i.e. CSC or SSC Role Type)

\requirement{DT:00.11.0010.2}{0} \requirement{DT:00.11.0010.3}{0} \requirement{DT:00.12.0010.4}{0} \requirement{DT:00.12.0010.5}{0}

  • MUST support the Time Command Class, version 1 or higher, i.e. they MUST reply to a Time Get with a Time Report (support); and

  • SHOULD support the Time Command Class, version 3 or higher; and

  • SHOULD control the Time Command Class by sending Time Get to nodes that advertise support of the Time Command Class; and

  • SHOULD support the Clock Command Class and Time Parameters Command Class as many legacy devices use (control) those.

The controlling Device Type overview is shown in Table 7.9.

Table 7.9 Z-Wave Plus v2 Controlling Device Types overview

Device Type

Mandatory (Support)

Mandatory (Control)

Role Types

Gateway

CRC-16 Encapsulation

Multi Command

Node Provisioning

Security 0 (S0)

Time

Association, version 2

Association Group Information, version 3

Basic, version 2

Central Scene, version 3

CRC-16 Encapsulation

Firmware Update Meta Data, version 5 Indicator, version 3

Meter, version 5

Multi Channel, version 4

Multi Channel Association, version 3

Multilevel Sensor, version 11

Notification, version 8

Security 0 (S0)

Security 2 (S2)

Version, version 2

Wake up, version 2

CSC

Generic Controller

Multi Command

Time (CSC & SSC Role Types)

Basic

Indicator, version 3

The actuator Command Classes of at least 1 actuator Device Type

Version, version 2

Wake up, version 2

CSC, SSC, RPC, PC, NAEN

7.3.4. From Z-Wave Plus to Z-Wave Plus v2 Certification

Table 7.10 indicates the recommended transitions from a Z-Wave Plus Device Type to a Z-Wave Plus v2 Device Type.

Table 7.10 Equivalent Z-Wave Plus and Z-Wave Plus v2 Device Types

Z-Wave Plus DT(s)

Suggested Z-Wave Plus v2 DT(s)

On/Off Power Switch

Power Strip

Valve – Open/close

Irrigation control

Binary Switch

Siren

Binary Switch

Sound Switch

Door Lock – Keypad

Lockbox

Lock

Light Dimmer Switch

Fan Switch

Multilevel Switch

Set Top box

TV

Sub system

Controller

Gateway

Generic Controller

Remote Control – Multi purpose

Remote control – Simple

Wall controller

Generic Controller

Central Scene

Sub Energy Meter

Whole Home Meter

Meter Sensor

Gateway

Central Controller

Gateway

Thermostat – HVAC

Thermostat – Setback

Thermostat

Remote control -AV

Generic Controller

Window Covering

Window Covering

The following Device Types are unchanged and have the same equivalent Device Type in the Z-Wave Plus v2 certification program:

  • Sensor - Notification

  • Sensor - Multilevel

  • AV Control Point

  • Sound Switch

  • Barrier Operator

  • Entry Control keypad

  • Repeater

The following Device Type is discontinued:

  • Display - Simple

7.3.5. Actuator Supporting Device Types

7.3.5.1. Lock DT

The Lock Device Type is intended for nodes implementing a lock mechanism with optional handles. It can be a door lock, a lockbox as well as a safe.

7.3.5.1.1. Generic and Specific Device Class

\requirement{DT:01.11.0001.1}{0}

The Lock Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_ENTRY_CONTROL (0x40)

  • SPECIFIC_TYPE_DOOR_LOCK (0x01)

7.3.5.1.2. S2 Security Classes

\requirement{DT:01.11.0002.1}{0}

The Root Device MUST request Access Control Security Class if it (or any End Point) uses this Device Type.

7.3.5.1.3. Mandatory Command Classes

\requirement{DT:01.11.0003.1}{0}

The Lock MUST support the following Command Classes:

  • Door Lock, version 4

  • Basic, version 2

  • Security 0 (S0)

Recommended optional command classes for advanced applications:

  • User Code

  • Entry Control

  • Generic Schedule

  • Authentication

  • Authentication Media Write

7.3.5.1.4. Basic Command Class Requirements

\requirement{DT:01.11.0004.1}{0}

The Basic Command Class MUST be mapped according to Table 7.11.

Table 7.11 Lock Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value)

Door Lock Operation Set (Door Lock Mode)

Basic Report (Current Value = 0x00)

Door Lock Operation Report (Door Lock Mode = 0x00)

Basic Report (Current Value = 0xFF)

Door Lock Operation Report (Door Lock Mode != 0x00)

7.3.5.2. Motorized Barrier DT

The Motorized Barrier Device Type is intended for barriers, gates or garage doors devices.

7.3.5.2.1. Generic and Specific Device Class

\requirement{DT:02.11.0001.1}{0}

The Motorized Barrier Device Type MUST use the following Generic Device Class:

  • GENERIC_TYPE_ENTRY_CONTROL (0x40)

\requirement{DT:02.11.0002.1}{0}

The Motorized Barrier Device Type MUST use one of the following Specific Device Classes based on its capabilities within the Barrier Operator Command Class:

  • SPECIFIC_TYPE_SECURE_GATE (0x06) if it can both open and close

  • SPECIFIC_TYPE_SECURE_BARRIER_OPEN_ONLY (0x08) if it can open only

  • SPECIFIC_TYPE_SECURE_BARRIER_CLOSE_ONLY (0x09) if it can close only

7.3.5.2.2. S2 Security Classes

\requirement{DT:02.11.0003.1}{0}

The Root Device MUST request Access Control Security Class if it (or any End Point) uses this Device Type.

7.3.5.2.3. Mandatory Command Classes

\requirement{DT:02.11.0004.1}{0}

The Motorized Barrier Devices MUST support the following Command Classes:

  • Barrier Operator

  • Notification, version 8

  • Basic, version 2

  • Security 0 (S0)

7.3.5.2.4. Basic Command Class Requirements

\requirement{DT:02.11.0005.1}{0}

The Basic Command Class MUST be mapped according to Table 7.12.

Table 7.12 Motorized Barrier Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value)

Barrier Operator Set (Target Value)

Basic Report (Current Value = 0x00)

Barrier Operator Report (State = 0x00)

Basic Report (Current Value = 0xFF)

Barrier Operator Report (State > 0x00)

7.3.5.3. Color Switch DT

The Color Switch Device Type is intended for a lighting product having the ability to change its color.

7.3.5.3.1. Generic and Specific Device Class

\requirement{DT:03.11.0001.1}{0}

The Color Switch Device Type MUST use the following Generic Device Classes:

  • GENERIC_TYPE_SWITCH_BINARY (0x10) if supporting Binary Switch

  • GENERIC_TYPE_SWITCH_MULTILEVEL (0x11) if supporting Multilevel Switch

\requirement{DT:03.11.0002.1}{0}

The Color Switch Device Type MUST use the following Specific Device Classes:

  • SPECIFIC_TYPE_COLOR_TUNABLE_BINARY (0x02) if supporting Binary Switch

  • SPECIFIC_TYPE_COLOR_TUNABLE_MULTILEVEL (0x02) if supporting Multilevel Switch

7.3.5.3.2. Mandatory Command Classes

\requirement{DT:02.11.0003.1}{0}

The Color Switch MUST support the following Command Classes:

  • Color Switch, version 3

  • Multilevel switch, version 4 or Binary Switch, version 2

  • Basic, version 2

7.3.5.3.3. Basic Command Class Requirements

\requirement{DT:02.11.0005.1}{0}

The Basic Command Class MUST be mapped according to Table 7.13 if supporting the Binary Switch Command Class or Table 7.14 if supporting the Multilevel Switch Command Class.

Table 7.13 Color Switch Device Type Basic mapping for Binary Switch

Basic Command

Mapped Command

Basic Set (Value)

Binary Switch Set (Target Value)

Basic Report (Current Value, Target Value, Duration)

Binary Switch Report (Current Value, Target Value, Duration)
Table 7.14 Color Switch Device Type Basic mapping for Multilevel Switch

Basic Command

Mapped Command

Basic Set (Value)

Multilevel Switch Set (Value)

Basic Report (Current Value, Target Value, Duration)

Multilevel Switch Report (Current Value, Target Value, Duration)

7.3.5.4. Window Covering DT

The Window Covering Device Type is intended for curtains or blinds allowing the end user to control the amount of light going through windows.

7.3.5.4.1. Generic and Specific Device Class

\requirement{DT:04.11.0001.1}{0}

The Window Covering Device Type MUST use the following Generic Device Classes:

  • GENERIC_TYPE_SWITCH_MULTILEVEL (0x11)

\requirement{DT:04.11.0002.1}{0}

The Window Covering Device Type MUST use one of the following Specific Device Classes based on its capabilities within the Window Covering Command Class:

  • SPECIFIC_TYPE_CLASS_A_MOTOR_CONTROL (0x05) if no position/endpoint awareness

  • SPECIFIC_TYPE_CLASS_B_MOTOR_CONTROL (0x06) if endpoint aware

  • SPECIFIC_TYPE_CLASS_C_MOTOR_CONTROL (0x07) if position and endpoint aware

7.3.5.4.2. Mandatory Command Classes

\requirement{DT:04.11.0003.1}{0}

The Window Covering MUST support the following Command Classes:

  • Window Covering, version 1

  • Multilevel Switch, version 4 (MUST be redundant to Window Covering, i.e. actuating the same hardware)

  • Basic, version 2

7.3.5.4.3. Basic Command Class Requirements

\requirement{DT:04.11.0004.1}{0}

The Basic Command Class MUST be mapped according to Table 7.15.

Table 7.15 Window Covering Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value=0xFF)

Multilevel Switch Set (0xFF) if endpoint aware

Start level change(Up/down) if not endpoint aware

Basic Set (Value=0x00)

Multilevel Switch Set (0x00) if endpoint aware

Stop level change if not endpoint aware

Basic Set (Value=0x01..0x63)

Multilevel Switch Set (0x01..0x63) if position aware

Start level change(Up/down) if not position aware

Basic Report (Current Value, Target Value, Duration)

Multilevel Switch Report (Current Value, Target Value, Duration)

Current Value and Target Value MUST be set to 0xFE if not position aware

7.3.5.5. Thermostat DT

The Thermostat Device Type is intended by thermostats that support set points and modes. It is typically used for all mainstream thermostats that can support e.g. Heating, Cooling and Fans.

7.3.5.5.1. Generic and Specific Device Class

\requirement{DT:05.11.0001.1}{0}

The Thermostat Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_THERMOSTAT (0x08)

  • SPECIFIC_TYPE_THERMOSTAT_GENERAL_V2 (0x06)

7.3.5.5.2. Mandatory Command Classes

\requirement{DT:05.11.0002.1}{0}

The Thermostat MUST support the following Command Classes:

  • Thermostat Mode, version 3

  • Thermostat Set Point

  • Basic, version 2

Recommended optional command classes:

  • Multilevel Sensor, supporting Sensor Type 0x01 (temperature)

  • Time, version 3

  • Schedule, version 4

  • Thermostat Setback

7.3.5.5.3. Basic Command Class Requirements

\requirement{DT:05.11.0003.1}{0}

The Basic Command Class MUST be mapped according to Table 7.16.

Table 7.16 Thermostat Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value=0xFF)

Thermostat Mode Set (Mode = 0x01, 0x02 or 0x03)

Basic Set (Value=0x00)

Thermostat Mode Set (Mode = 0x00, 0x0B, 0x0C or 0x0D)

Basic Report (Current Value = 0xFF)

Thermostat Mode Report (Mode = 0x01, 0x02 or 0x03)

Basic Report (Current Value = 0x00)

Thermostat Mode Report (Mode = 0x00, 0x0B, 0x0C or 0x0D)

\requirement{DT:05.11.0004.1}{0}

Other modes than 0x01, 0x02 or 0x03 MAY be mapped to Basic (Value=0xFF). In this case, it MUST be documented in the user manual.

\requirement{DT:05.11.0005.1}{0}

Other modes than 0x00, 0x0B, 0x0C or 0x0D MAY be mapped to Basic (Value=0x00). In this case, it MUST be documented in the user manual.

7.3.5.6. Sound Switch DT

The Sound Switch Device Type is intended for products with the ability to issue sound notifications with a pre-programmed sound inventory. It can be used for a doorbell, chime, siren, alarm clock or any device issuing sounds.

7.3.5.6.1. Generic and Specific Device Class

\requirement{DT:06.11.0001.1}{0}

The Sound Switch Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_AV_CONTROL_POINT (0x03)

  • SPECIFIC_TYPE_SOUND_SWITCH (0x01)

7.3.5.6.2. Mandatory Command Classes

\requirement{DT:06.11.0002.1}{0}

The Sound Switch MUST support the following Command Classes:

  • Sound Switch

  • Basic, version 2

7.3.5.6.3. Basic Command Class Requirements

\requirement{DT:06.11.0003.1}{0}

The Basic Command Class MUST be mapped according to Table 7.17.

Table 7.17 Sound Switch Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value)

Sound Switch Tone Play Set (Tone Identifier)

Basic Report (Current Value = 0x00)

Sound Switch Tone Play Report (Tone Identifier = 0x00)

Basic Report (Current Value = 0xFF)

Sound Switch Tone Play Report (Tone Identifier > 0x00)

7.3.5.7. AV Control Point DT

The AV Control Point Device Type is intended for products with the ability to receive IR codes. It can be a TV, DVD player or any multimedia device that can now be also controller via Z-Wave.

7.3.5.7.1. Generic and Specific Device Class

\requirement{DT:07.11.0001.1}{0}

The AV Control Point Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_AV_CONTROL_POINT (0x03)

  • SPECIFIC_TYPE_NOT_USED (0x00)

7.3.5.7.2. Mandatory Command Classes

\requirement{DT:07.11.0002.1}{0}

The AV Control Point Device Type MUST support the following Command Classes:

  • Simple AV Control

  • Basic, version 2

7.3.5.7.3. Basic Command Class Requirements

\requirement{DT:07.11.0003.1}{0}

The Basic Command Class MUST be mapped according to Table 7.18.

Table 7.18 AV Control Point Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value)

Simple AV Set (Command).

The associated AV Codes Commands to the values 0x00 and 0xFF chosen be the manufacturer MUST switch the node’s main functionality On and Off. (such as play/pause or volume up/volume down)

Basic Report (Current Value)

None

The reported value MAY indicate if the node’s main functionality is On or Off. (such as play/paused) else current value SHOULD be set to 0x00.

7.3.5.8. Multilevel Switch DT

The Multilevel Switch Device Type is intended for products that can be switched between more than 2 discrete levels or states, such a light dimmer, water valve or a fan.

7.3.5.8.1. Generic and Specific Device Class

\requirement{DT:08.11.0001.1}{0}

The Multilevel Switch Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_SWITCH_MULTILEVEL (0x11)

  • SPECIFIC_TYPE_NOT_USED (0x00)

7.3.5.8.2. Mandatory Command Classes

\requirement{DT:08.11.0002.1}{0}

The Multilevel Switch Device Type MUST support the following Command Classes:

  • Multilevel Switch, version 4

  • Basic, version 2

7.3.5.8.3. Basic Command Class Requirements

\requirement{DT:08.11.0003.1}{0}

The Basic Command Class MUST be mapped according to Table 7.19.

Table 7.19 Multilevel Switch Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value)

Multilevel Switch Set (Value)

Basic Report (Current Value, Duration)

Multilevel Switch Report (Value, Duration)

7.3.5.9. Binary Switch DT

The Binary Switch Device Type is intended for any actuator functionality that can only be switched between 2 states (On and Off). It can be a valve, a light switch, a plug-in module.

7.3.5.9.1. Generic and Specific Device Class

\requirement{DT:09.11.0001.1}{0}

The Binary Switch Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_SWITCH_BINARY (0x10)

  • SPECIFIC_TYPE_NOT_USED (0x00)

7.3.5.9.2. Mandatory Command Classes

\requirement{DT:09.11.0002.1}{0}

The Binary Switch MUST support the following Command Classes:

  • Binary Switch, version 2

  • Basic, version 2

\requirement{DT:09.12.0001.1}{0}

If the node can measure energy, water or gas consumption, it is RECOMMENDED to support:

  • Meter, version 5

7.3.5.9.3. Basic Command Class Requirements

\requirement{DT:09.11.0003.1}{0}

The Basic Command Class MUST be mapped according to Table 7.20.

Table 7.20 Binary Switch Device Type Basic mapping

Basic Command

Mapped Command

Basic Set (Value)

Binary Switch Set (Value)

Basic Report (Current Value, Duration)

Binary Switch Report (Value, Duration)

7.3.6. Reporting Supporting Device Types

7.3.6.1. Entry Control Keypad DT

The Keypad Device Type is intended for keypads or authentication devices reporting user input to a controlling application.

7.3.6.1.1. Generic and Specific Device Class

\requirement{DT:11.11.0001.1}{0}

The Entry Control Keypad Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_ENTRY_CONTROL (0x40)

  • SPECIFIC_TYPE_SECURE_KEYPAD (0x0B)

7.3.6.1.2. S2 Security Classes

\requirement{DT:11.11.0002.1}{0}

The Root Device MUST request Access Control Security Class if it (or any End Point) uses this Device Type.

7.3.6.1.3. Mandatory Command Classes

\requirement{DT:11.11.0003.1}{0}

The Entry Control Keypad MUST support the following Command Classes:

  • Entry Control

  • Security 0 (S0)

Recommended optional command classes:

  • Indicator, version 3 (with other Indicator IDs than Identify)

7.3.6.1.4. Basic Command Class Requirements

\requirement{DT:11.11.0004.1}{0}

Basic Command Class MUST NOT be supported

7.3.6.2. Multilevel Sensor DT

The Multilevel Sensor Device Type is intended for sensor reporting instantaneous numerical readings or measurements.

7.3.6.2.1. Generic and Specific Device Class

\requirement{DT:12.11.0001.1}{0}

The Multilevel Sensor Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_SENSOR_MULTILEVEL (0x21)

  • SPECIFIC_TYPE_ROUTING_MULTILEVEL_SENSOR (0x01)

7.3.6.2.2. Mandatory Command Classes

\requirement{DT:12.11.0002.1}{0}

The Multilevel Sensor MUST support the following Command Classes:

  • Sensor Multilevel, version 11

\requirement{DT:12.12.0001.1}{0}

If the node issues more than one command regularly, it is RECOMMENDED to control:

  • Multi Command

7.3.6.2.3. Basic Command Class Requirements

\requirement{DT:12.11.0003.1}{0}

Basic Command Class MUST NOT be supported

7.3.6.3. Notification Sensor DT

The Notification Sensor Device Type is intended for sensors reporting events or local state changes.

7.3.6.3.1. Generic and Specific Device Class

\requirement{DT:13.11.0001.1}{0}

The Notification Sensor Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_SENSOR_NOTIFICATION (0x07)

  • SPECIFIC_TYPE_NOTIFICATION_SENSOR (0x01)

7.3.6.3.2. Mandatory Command Classes

\requirement{DT:13.11.0002.1}{0}

The Notification Sensor MUST support the following Command Classes:

  • Notification, version 8

\requirement{DT:13.12.0001.1}{0}

If the node issues more than one command regularly, it is RECOMMENDED to control:

  • Multi Command

7.3.6.3.3. Basic Command Class Requirements

\requirement{DT:13.11.0003.1}{0}

Basic Command Class MUST NOT be supported

7.3.6.4. Meter Sensor DT

The Meter Sensor Device Type is intended for sensors measuring cumulated values. The most typical application is an electricity meter, but it can also be used for sensor measuring gas or water consumption.

7.3.6.4.1. Generic and Specific Device Class

\requirement{DT:14.11.0001.1}{0}

The Meter Sensor Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_METER (0x31)

  • SPECIFIC_TYPE_NOT_USED (0x00)

7.3.6.4.2. Mandatory Command Classes

\requirement{DT:14.11.0002.1}{0}

The Meter Sensor MUST support the following Command Classes:

  • Meter, version 5

\requirement{DT:14.12.0001.1}{0}

If the node issues more than one command regularly, it is RECOMMENDED to control:

  • Multi Command

\requirement{DT:14.12.0002.1}{0}

For advanced metering applications, it is RECOMMENDED to support the following command classes:

  • Meter Table Monitor, version 2

  • Meter Table Push Configuration

  • Rate Table Monitor

7.3.6.4.3. Basic Command Class Requirements

\requirement{DT:14.11.0003.1}{0}

Basic Command Class MUST NOT be supported

7.3.6.5. Central Scene DT

The Central Scene Device Type is intended for nodes with buttons or GUI allowing to report user input/button press to a central application, which in turn will actuate or control other nodes.

This Device Type can be used for nodes such as wall switches or panels with a set of buttons. Such devices will send Scene Notifications to the Lifeline destination in order to trigger scenes.

7.3.6.5.1. Generic and Specific Device Class

\requirement{DT:15.11.0001.1}{0}

The Central Scene Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_WALL_CONTROLLER (0x18)

  • SPECIFIC_TYPE_NOT_USED (0x00)

7.3.6.5.2. Mandatory Command Classes

\requirement{DT:15.11.0002.1}{0}

The Central Scene MUST support the following Command Classes:

  • Central Scene, version 3

7.3.6.5.3. Basic Command Class Requirements

\requirement{DT:15.11.0003.1}{0}

Basic Command Class MUST NOT be supported

7.3.7. Other Device Types

7.3.7.1. Repeater DT

The Repeater Device Type is intended for nodes being part of the network with no application functionalities. Such nodes help as Z-Wave repeaters and strengthen the network reliability.

7.3.7.1.1. Role Type

\requirement{DT:21.11.0001.1}{0}

The Repeater Device Type MUST use the AOEN Role Type.

7.3.7.1.2. Generic and Specific Device Class

\requirement{DT:21.11.0002.1}{0}

The Repeater Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_REPEATER_END_NODE (0x0F)

  • SPECIFIC_TYPE_REPEATER_END_NODE (0x01)

7.3.7.1.3. Mandatory Command Classes

\requirement{DT:21.11.0003.2}{0}

The Repeater Device Type MUST NOT support any other Application Command Class than the list defined in Section 7.2.2.1 Root Device level. Additional Management Command Classes MAY be supported.

\requirement{DT:21.11.0004.1}{0}

The Repeater Device Type MUST NOT control any Command Class.

7.3.7.1.4. Basic Command Class Requirements

\requirement{DT:21.11.0005.1}{0}

Basic Command Class MUST NOT be supported

7.3.7.2. IR Repeater DT

The IR Repeater Device Type is intended for nodes having the ability to read or repeat IR signals. They do not have any other application functionality. Such repeater nodes also help as Z-Wave repeaters and strengthen the network reliability.

7.3.7.2.1. Role Type

\requirement{DT:22.11.0001.1}{0}

The IR Repeater Device Type MUST use the AOEN Role Type.

7.3.7.2.2. Generic and Specific Device Class

\requirement{DT:22.11.0002.1}{0}

The Repeater Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_REPEATER_END_NODE (0x0F)

  • SPECIFIC_TYPE_IR_REPEATER (0x03)

7.3.7.2.3. Mandatory Command Classes

\requirement{DT:22.11.0003.1}{0}

The IR Repeater MUST support the following Command Classes:

  • IR Repeater, version 1

\requirement{DT:22.11.0004.1}{0}

The IR Repeater Device Type MUST NOT support any additional Command Class (other than the mandatory list above and the list defined in Section 7.2.2.1 Root Device level.

\requirement{DT:22.11.0005.1}{0}

The IR Repeater Device Type MUST NOT control any Command Class.

7.3.7.2.4. Basic Command Class Requirements

\requirement{DT:22.11.0006.1}{0}

Basic Command Class MUST NOT be supported

7.3.8. Controlling Device Types

7.3.8.1. Gateway DT

\requirement{DT:31.13.0002.1}{4}

The Gateway Device Type is intended for all gateway controllers that provide access in and potentially out of the Z-Wave network as well as extensive controlling capabilities over Z-Wave. This DT MAY provide transparent access for all types of IP Packets between several network technologies.

7.3.8.1.1. Role Type

\requirement{DT:31.11.0001.1}{0}

The Gateway Device Type MUST use the CSC Role Type.

7.3.8.1.2. Generic and Specific Device Class

\requirement{DT:31.11.0002.1}{0}

The Gateway Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_STATIC_CONTROLLER (0x02)

  • SPECIFIC_TYPE_GATEWAY (0x07)

7.3.8.1.3. S2 Security Classes

\requirement{DT:31.11.0003.1}{0}

If bootstrapped in another network, it MUST request all S2 Security Classes. (S2 Access Control, S2 Authenticated and S2 Unauthenticated)

7.3.8.1.4. Mandatory Command Classes

\requirement{DT:31.11.0004.1}{0}

The Gateway MUST support the following Command Classes in a Z-Wave network:

  • CRC-16 Encapsulation

  • Inclusion Controller

  • Multi Command

  • Security 0 (S0)

  • Time

\requirement{DT:31.11.0005.2}{0}

The Gateway SHOULD support Node Provisioning Command Class in a Z-Wave network.

\requirement{DT:31.12.0005.3}{0}

If the Gateway relies on a Z/IP library, it SHOULD support the following Command Classes in an IP network:

  • Z/IP, version 4

\requirement{DT:31.12.0001.1}{0}

If the Gateway relies on a Z/IP client to provide application functionalities, it SHOULD support the following Command Classes in an IP network:

  • Z/IP Gateway

  • Z/IP ND

  • Z/IP Portal

  • Mailbox

  • Network Management Proxy, version 2

  • Network Management Inclusion, version 3

  • Network Management Basic, version 2

\requirement{DT:31.11.0006.3}{0}

The Gateway MUST provide full control of the following Command Classes:

  • Association, version 2

  • Association Group Information, version 3

  • Basic, version 2

  • Central Scene, version 3

  • CRC-16 Encapsulation

  • Firmware Update Meta Data, version 5

  • Indicator, version 3

  • Meter, version 5

  • Multi Channel, version 4

  • Multi Channel Association, version 3

  • Multilevel Sensor, version 11

  • Notification, version 8

  • Security 0 (S0)

  • Security 2 (S2)

  • Version, version 2

  • Wake up, version 2

\requirement{DT:31.13.0001.1}{0}

A Gateway Device Type MAY provide a subset of its capabilities (supported and controlled command classes) if it has the Secondary Controller Role in a network.

\requirement{DT:31.11.0008.1}{0}

A Gateway Device Type MUST provide full control of any Command Class that it controls. It MUST NOT provide partial control for any Command Class.

7.3.8.1.6. Basic Command Considerations

\requirement{DT:31.11.0007.1}{0}

Basic Command Class MUST NOT be supported.

7.3.8.2. Generic Controller DT

The Generic Controller Device Type is intended for all more constrained or simple controllers allowing users to make basic use of the Z-Wave network and controlling a pre-defined set of actuator nodes as well as unknown actuator nodes.

7.3.8.2.1. Generic and Specific Device Class

\requirement{DT:32.11.0001.1}{0}

The Generic Controller Device Type MUST use the following Device Classes:

  • GENERIC_TYPE_GENERIC_CONTROLLER (0x01)

  • SPECIFIC_TYPE_NOT_USED (0x00)

7.3.8.2.2. Mandatory Command Classes

\requirement{DT:32.11.0002.1}{0}

The Generic Controller MUST support the following Command Classes:

  • Multi Command

  • Time (CSC & SSC Role Types)

\requirement{DT:32.11.0003.3}{0}

The Generic Controller MUST provide full control of the following Command Classes:

  • Basic

  • Indicator, version 3

  • The mandatory actuator Command Classes of at least one actuator Device Type

  • Version, version 2

  • Wake up, version 2

\requirement{DT:32.13.0001.1}{0}

A Generic Controller Device Type MAY provide full control or partial control of any other Command Class not listed above.

7.3.8.2.4. Basic Command Considerations

\requirement{DT:32.11.0004.1}{0}

Basic Command Class MUST NOT be supported.