Z-Wave Plus Certification Program
Z-Wave Plus certifications include stringent technical compliance testing as well as a Market Certification The Market Certification, administered by the Z-Wave Alliance, is mandatory and must be completed prior to a Z-Wave Plus device certification being issued.
Access is restricted to licensees. Company and user accounts will be needed to access the portal. Requests for new accounts must be submitted to the certification mailbox and include the company name, company location (country) user’s first & last name and their e-mail address.
An automatic e-mail notification will be sent by the portal when a new account is created. This message will include a link to the portal and a temporary password. The “Getting Started” tab should be the first stop after logging in and completing the registration, This tab is a link to a Wiki which provides a walkthrough of how to create and submit a certification case, a comprehensive user guide and an overview of the certification program.
Certification cases are identified as being in one of the following phases:
- Initial Form Selection – Developer identifies & selects what is being implemented.
- Self-Certification – Developer conducts self certification tests and verifies compliance.
- Initial Review – Case has been submitted by the developer and is pending initial review.
- Wait for Verification Test – Case has passed initial review and developer needs to pay the fees and submit required documentation & test samples to the selected test partner.
- Verification Test – Test Partner has received everything (all required documentation, test samples and fees) and the device is ready to be tested. At the completion of testing, results will be submitted to the Certification Manager for review & processing.
- Wait for Ad Hoc Test – Initial testing resulted in minor issues and the developer needs to submit fixes to the test partner. (Ad Hoc is a 30 day period during which the developer works directly with the test partner to resolve all issues.)
- Ad Hoc Test – The test partner has received everything needed to re-test the device and verify the issues have been resolved. At the completion of testing, results will be submitted to the Certification Manager for review & processing.
- Market Certification – A case may be in this phase for either of the following reasons:
- This is a review-only recertification that has passed the initial review. It will remain in this phase until the Z-Wave Alliance has approved the Market Certification for this device.
- The test results for this case have been received from the test partner; however, the Market Certification for this device has not yet been approved by the Z-Wave Alliance. A device certification cannot be issued until the Market Certification has been approved so this case will remain in this phase until that has been accomplished.
- Certification Finished – The certification case has been closed. Possible outcomes are:
- Passed & certification issued.
- Failed - Device must be resubmitted as a new case.
- Expired – Developer has exceeded the allowed time for ad hoc issue resolution.
Initial Form Selection / Self-Certification: Question Mark icons “?” are located throughout the certification form. Clicking on these icons opens a Wiki page with more information and in many cases the related test specification. The test specifications on these Wiki pages will be updated as needed and replace the separate CTS10999 document (this document will not be updated).
Market Certification: Product & market information can be submitted in the members section of the alliance’s website after a case number has been assigned. Case numbers are assigned during the initial review of the certification form. Please note that full membership in the alliance is required for Z-Wave Plus.
Verification Testing: The testing required depends on the type of device and its functionality. Testing verifies RF functionality, core Z-Wave functionalities and Command Class implementations as identified in the Z-Wave Plus Device Type Specification, Role Type Specification and Command Class Specifications.
Our test partners try to conduct all testing within two to three weeks of a device entering the test queue but the number of devices in the queue changes constantly and our independent test houses get backed-up occasionally. A device doesn’t actually enter the queue until all of the following are completed:
- The submitted form has been reviewed & approved.
- The test house has received payment.
- The test house has received test samples and all necessary documentation (instructions/manual, special instructions if needed, etc.)
A complementary tool, the Z-Wave Compliance Test Tool (CTT) is available to its members. The CTT can be used to help verify that slave devices are performing properly in respect to Z-Wave functionality and that all mandatory device and command class requirements have been implemented properly.
Important Notice: New products MUST be based on the latest specifications and utilize the current certification form but a developer may be finalizing their device and preparing for certification when new versions of the documents are published. Due to this:
- A device may be submitted for certification based on the previous specifications for a period of 60 days from the publication date of the new specifications.
- The form on the certification portal is always the latest approved version so comments MUST be added for any items based on the earlier specifications and not complying with the new specifications.
- Any submission occurring after the 60 day time period MUST be based on the latest specifications.