Specification documents form a constellation in which each document defines the requirements for a given building block of a Z-Wave application. The diagram shows how the specification documents are set together, down from the physical layers up to the most applicative layers. The dark blue color indicates Z-Wave Plus specific documents.
Each product must follow this specification to be able to pass the certification program and ensure interoperability in the ecosystem of existing products. As a Z-Wave developer you need to use the latest version of specification when starting a new application development. All specification development is done in a gate process to ensure quality, consistency and continuing interoperability. Each Z-Wave node implements several Z-Wave specification documents depending on the intended application. You do not need to go through all the specifications to develop your application. You application may need only a subset of the Z-Wave specification.
Z-Wave Specification Update Calendar
The Specifications are typically updated 4 times a year. Each release is denoted by the year and a letter, like: 2016A, 2016B, 2016C, 2016D. Suggestions or clarification questions are gathered and used in documents called contributions. Documents denoted “Contributions 2016A” are contributions to the 2016A release aiming at being integrated in the 2016B release. Specifications contributions are submitted to Open Review every 1st March, 1st June, 1st September and 1st December. During the Open Review, partners and members are encouraged to review the changes and provide feedback and comments. Open Review lasts 30-days, unless important changes are introduced during the Open Review, in which case the Open Review period is extended. New documents and contributions are approved and official at the end of Open Review. The main and released specification documents are typically updated during the 2 weeks following the end of the Open Review periods.
Send your Z-Wave specification inquiries to: email@example.com