3.2.53. Z-Wave Plus Info Command Class, version 2

The Z-Wave Plus Info Command Class is used to differentiate between Z-Wave Plus, Z-Wave for IP and Z-Wave devices. Furthermore this command class provides additional information about the Z-Wave Plus device in question.

\requirement{CC:005E.02.00.11.001}{8}

The Z-Wave Plus Info Command Class defines two icon types. Icon types allow for a meaningful, homogeneous representation in user and installer Graphical User Interfaces (GUI), respectively. A Z-Wave Plus product MUST specify valid icon types. Icon types do not affect the operation of a product or how it is certified. The actual graphical appearance of icons is out of scope of this specification. Any app may define its own icon library mapping to the Icon Type identifiers.

3.2.53.1. Compatibility Considerations

3.2.53.1.1. Node Information Frame (NIF)

\requirement{CC:005E.02.00.21.001}{0}

A supporting node MUST always advertise the Z-Wave Plus Info Command Class in its NIF, regardless of the inclusion status and security bootstrapping outcome.

\requirement{CC:005E.02.00.21.002}{0}

The Z-Wave Plus Info Command Class MUST be advertised as the first supported command class in Node Information Frame (NIF).

3.2.53.2. Multi Channel considerations

A Multi Channel device implements a Root Device and a number of Multi Channel End Points.

\requirement{CC:005E.02.00.11.002}{0}

The Z-Wave Plus Info Command Class MUST be supported for each End Point in order to advertise individual icons for each End Point.

\requirement{CC:005E.02.00.11.003}{8}

This means that the Z-Wave Plus Version, Role Type and Node Type information is advertised in a redundant fashion. The advertised Z-Wave Plus Version, Role Type and Node Type information values MUST be identical for the Root Device and all Multi Channel End Points.

3.2.53.3. Z-Wave Plus Info Get Command

The Z-Wave Plus Info Get Command is used to get additional information of the Z-Wave Plus device in question.

\requirement{CC:005E.02.01.11.001}{0}

The Z-Wave Plus Info Report Command MUST be returned in response to this command.

\requirement{CC:005E.02.01.11.002}{0}

This command MUST NOT be issued via multicast addressing.

\requirement{CC:005E.02.01.11.003}{0}

A receiving node MUST NOT return a response if this command is received via multicast addressing. The Z-Wave Multicast frame, the broadcast NodeID and the Multi Channel multi-End Point destination are all considered multicast addressing methods.

Table 3.199 Z-Wave Plus Info Get Command

7

6

5

4

3

2

1

0

Command Class = COMMAND_CLASS_ZWAVEPLUS_INFO (0x5E)

Command = ZWAVEPLUS_INFO_GET (0x01)

3.2.53.4. Z-Wave Plus Info Report Command

The Z-Wave Plus Info Report Command is used to report version of Z-Wave Plus framework used and additional information of the Z-Wave Plus device in question.

Table 3.200 Z-Wave Plus Info Report Command

7

6

5

4

3

2

1

0

Command Class = COMMAND_CLASS_ZWAVEPLUS_INFO (0x5E)

Command = ZWAVEPLUS_INFO_GET (0x01)

Z-Wave Plus Version

Role Type

Node Type

Installer Icon Type MSB

Installer Icon Type LSB

User Icon Type MSB

User Icon Type LSB

Z-Wave Plus Version (8 bits)

The Z-Wave Plus Version field enables a future revision of the Z-Wave Plus framework where it is necessary to distinguish it from the previous frameworks.

\requirement{CC:005E.02.02.11.006}{0}

This field MUST be set to 1 if the sending node is compliant with Z-Wave Plus [35].

This field MUST be set to 2 if the sending node is compliant with Device Type v2 Specification.

Role Type (8 bits)

The Role Type field indicates the role the Z-Wave Plus device in question possess in the network and functionalities supported. The full functionality is determined in conjunction with the Device Type.

Node Type (8 bits)

The Node Type field indicates the type of node the Z-Wave Plus device in question possess in the network.

The table below shows the current list of Node Types:

Table 3.201 Node Type Identifiers

Value

Identifier

Node Types

0x00

NODE_TYPE_ZWAVEPLUS_NODE

Z-Wave Plus node

0x02

NODE_TYPE_ZWAVEPLUS_FOR_IP_GATEWAY

Z-Wave Plus for IP gateway

\requirement{CC:005E.02.02.11.002}{0}

All other values are reserved and MUST NOT be used by a sending node. Reserved values MUST be ignored by a receiving node.

Z-Wave Plus for IP gateway

The device provides access to and from IP networks and allows IP hosts to discover resources in the Z-Wave network via Z/IP Discovery.

\requirement{CC:005E.02.02.11.003}{0}

Two IP services MUST be available to represent Z-Wave resources in the IP domain: ICMP Echo (Ping) and UDP port 4123 (Z-Wave control protocol).

The device is typically a stand-alone device based on a residential IPv6 router. The Z-Wave interface is presented as an IP network interface to external clients but all IP communication to classic Z-Wave nodes is terminated by the gateway and forwarded in classic Z-Wave frames.

Installer Icon Type (16 bits)

The Installer Icon Type field indicates the icon to use in Graphical User Interfaces for network management, e.g. in a floor plan. Installer Icons provide a finer granularity than user icons, e.g. a light on/off resource may be a built-in wall outlet, a plug-in module or an entire power strip. A sensor may be a single sensor icon or multiple sensors in one casing.

For further details, refer to the User Icon Type section below.

User Icon Type (16 bits)

The User Icon Type field indicates the icon to use in Graphical User Interfaces for end users. User Icons provide a basic granularity, e.g. a light resource is always shown as a light bulb whether the physical device is a built-in wall outlet, a plug-in module or the output of a power strip.

\requirement{CC:005E.02.02.11.004}{0} \requirement{CC:005E.02.02.13.001}{4}

In case of multi-endpoint devices, e.g. power strips or multi-sensors, the info command class MUST be supported and Icon Types MUST be specified for each endpoint.

The User Icon Type MAY differ for individual endpoints.

\requirement{CC:005E.02.02.12.001}{12}

Icon types are defined by the Z-Wave Alliance [34]. The 16 bit identifier values defined by [34] allows the GUI designer to know how a given product would like to be represented using resources from the GUI designer’s own favorite icon library. The icon graphics found in [34] are only suggested graphics. Output device icons SHOULD be tailored to the actual geographical region.

\requirement{CC:005E.02.02.12.002}{0} \requirement{CC:005E.02.02.11.005}{4}

If a GUI does not know the specific icon type, it SHOULD use the generic icon type as a fallback alternative. The generic icon type MUST be derived by setting the least significant 8 bits of the icon type identifier to zero.