Any Z-Wave device has a Device Type, Role Type, and a list of Command Classes that can be controlled and/or supported. The specification requirements for every layer are well defined in the documentation provided, and they are also referenced in the Certification Portal with a guide to the relevant place in the specifications. The requirement level for a new application development very much depends on the selected Device & Role Type and the number and types of Command Classes that a developer wishes to implement. The Certification Portal will help identify the mandatory requirements during the Initial Selection stage. The Specifications are updated twice per year and marked as version xxxxA and xxxxB signifying the year of the release (e.g. 2022A). The latest released specification version should be used for new development, however it is not certifiable until it is implemented into the Certification Portal and the Compliance Test Tool (CTT). Implementation is normally finalized within the following quarter and then it is referred to as being “in-force”.
Over more than two decades, Z-Wave technology has evolved to what it is today, a ratified multi-source wireless standard for the development of IoT devices. The maturity that comes with these many years focused on the smart home can be seen in the comprehensive command class library that has developed and is one of the key factors in making Z-Wave the leading smart home technology in the world.
These proven command classes drive the Alliance mission to unify devices regardless of brand while progressing the Z-Wave protocol since inception. There are more IoT devices in the home today than any time in history, and that’s nothing compared to what is to come. In order for the promise of industry wide interoperability to happen, the hundreds of millions of existing devices, installations and large ecosystems in the market today must continue to function as well as grow, and Z-Wave is the protocol that can bridge these systems.
Download the current in-force specification package for certification here.
This document specifies the Application layer of the Z-Wave and Z-Wave Long Range protocols.
This specification defines the Network (NWK) layer for ITU-T G.9959 complianttransceivers and Z-Wave long Range transceivers, which enables networkoperations and routing on Z-Wave networks.Implementations claiming compliancewith this specification can be used with an application layer to certify Z-Wave andZ-Wave long range products.
Z-Wave Long Range PHY and MAC layer specification.
Specification of the API between a Z-Wave NCP and a host processor.
Format for representing S2 DSK as well as various product properties in QR codes.
Provisioning Information Types to be specified in QR codes or delivered by provisioning applications.
This document defines commands that must be sent via the Lifeline Association Group when a change occured. Refer to the "Lifeline Reports" tab in this workbook for the requirements.
This document defines Indicator IDs and Property IDs that can be used with the Indicator Command Class. Refer to the "Indicator IDs" and "Property IDs" tabs in this workbook for the requirements.
This document defines types, scales, datasets and other data that can be used with the Meter Table Monitor Command Class. Refer to the individual tabs in this workbook for the assigned values.
This document defines Multilevel Sensor types and scale that can be used with the Multilevel Sensor Command Class. Refer to the "Multilevel Sensor" tab in this workbook for the assigned values.
This document defines Notification Types and Notifications (including State variables, Event/State parameters, etc.) that can be used with the Notification Command Class. Refer to the "Notifications" tab in this workbook for the assigned values.
This document lists the existing Simple AV codes defined in the Simple AV Control Command Class.
This document defines constant identifiers to use for the Icon Type fields defined for the Z-Wave Plus Info Command Class. Individual tabs in this workbook provide access to the change record and to the actual assigned Icon Types. The displayed icons are only suggested graphics. A more simplistic view may be achieved by mapping many different icon type identifiers to the same icon graphics. Likewise, if a GUI does not know the specific icon type, it may use the generic icon type as a fall-back alternative. The generic icon type may be derived by setting the least significant 8 bits of the icon type identifier to zero.