instruction - silicon labs · 2018-08-09 · hcs : item 13.4 . corrected specific device class to...

Instruction Z-Wave Certification Form V8.5

Document No.: INS10637

Version: 35

Description: The document contains the Z Wave Certification Form used in the Z Wave Certification Process.

Written By: DKING;BBR;JFR

Date: 2013-04-24

Reviewed By: BBR;JFR;NTJ

Restrictions: Public

Approved by:

Date CET Initials Name Justification 2013-04-24 12:35:22 NTJ Niels Thybo Johansen

This document is the property of Silicon Labs. The data contained herein, in whole or in part, may not be duplicated, used or disclosed outside the recipient for any purpose. This restriction does not limit the recipient's right to use information contained in the data if it is obtained from another source without restriction.

INS10637-35 Z-Wave Certification Form V8.5 2013-04-24

silabs.com | Building a more connected world. Page ii of iv

REVISION RECORD

Cert. Form Version

Doc. Rev

Date By Page(s) affected

Brief description of changes

8.3 26 20110427 HCS Cc and E-mail Multilevel Sensor Command Class, Version 5 added to cc And new E-mail for certification added

8.3 26 20110504 HCS DCG And DCS Not permitted have been removed and new CC’s add. Multilevel Sensor DC corrected

8.3 26 20110505 HCS Item 13.4 Corrected specific device class to Secure Keypad Door Lock Specific Device Class

8.3 27 20110818 HCS Payment Removed all fees from doc 8.3 28 20111005 DKING Pages 4, 12 &

25 Updated Bulogics address; Made “General Demands for all Protocol Libraries” a separate subsection

8.3 29 20120110 DKING Entire document Minor text changes/updates

8.3 30 20120110 DKING Section 1.6 Section 0 Section 2.2 Section 2.2.2 Section 2.3.3 Section 2.3.4 Section 2.3.4

Section 2.3.5 Section 2.4 Section 2.5 Section 2.6 G.5.2

G.8.2 G.9.3 G.18 D.1 D.8 B.2. B.3.9.1.1 and B.3.9.13.1.1 A.2.6 A.3.6 A.4.5.2.2 A.4.5.3.2 A.4.5.4.2 A.4.6 A.6.11 A.12.4 A.18.4 A.20 A.22 A100+

Section 5 Section 6 Appendix

Deleted 4 week notice Minor rewording of statement Deleted statement regarding direct test house payments Minor rewording Added ZDK acknowledgement & disclaimer Removed section on Built in Peripherals (was 2.3.4) Removed 200 series cert option, simplified descriptions/options & added note regarding QFN testing Revised wording & added requirement for change description Updated Power Sources & added Brazil frequency Revised wording for publication information Added Bulogics’ phone number Added requirement to control unknown devices - Moved to section 2.7.6.3 for Controllers in revision 34 Added option for NWI Added option for FliRS Added option for Explorer Frames Deleted “ for all operations supported by the device” Added documentation for controllers Added option to identify Enhanced Slave Added requirement to control all devices in controlled command classes Moved both to section 2.7.6.3 for Controllers in revision 34 Added Binary Tunable Color Light Specific DC Added Portable Installer Tool Specific DC Added recommended CC (supported) Added recommended CC (supported) Added recommended CC (supported) Added Static Installer Tool Specific DC Added Multilevel Tunable Color Light Specific DC Added Advanced Energy Control Specific DC Added Advanced Energy Control Specific DC Removed Z/IP Generic DC & Z/IP Node Generic DC (was A.20 & A.21) Added Semi Interoperable Generic DC Removed all Z/IP CC’s, Added missing CC’s (Color, CRC16, Manufacturer Specific v2, Multi-Channel v3,Schedule Entry Lock), Command Classes Supported and/or Controlled. Sequenced CC’s in alphabetical order & renumbered them. Added document review results in verification tests Revised wording in descriptions of “Not Passed” section” Removed Appendix C (duplicate of CTT test cases)

https://www.silabs.com/


silabs.com | Building a more connected world. Page iii of iv

8.3 31 20120316 DKING Section 1.6 Section 2.3.2 Section 2.3.4 Section 2.4 G.1.6 G.5.2 G.19 B.4.2 A.4.7 Section 2.7.5.1 A100+

Updated text of 3rd bullet point to describe Ad Hoc Added text field for description of Serial API changes Added check boxes for module used & certification number if custom Added frequency for Russia Updated document requirements Added reference to Controller Functionality section Added section regarding Controller Functionality Clarified requirement for controlled CCs in NIF Added Gateway Specific Device Class Added section regarding Controller Functionality Added Application Capability CC, Association Group Information CC, Device Reset locally CC, Network Management Basic Node CC, Network Management Inclusion CC, Network Management Primary CC, Network Management Proxy CC, Schedule CC, Transport Service CC, Z/IP CC and Z/IP-ND CC (in alphabetical order & renumbered).

8.4 32 20120501 DKING Section 2.3.3 G.1.6 G.2.4 G.17 G.18

D.3

B.3.9.14.1.1 B.3.9.14.1.2 A.113.2 A.159 A.185.2 Section 2.7.6

Re-worded note about Active, Monitored and Obsolete SDKs Updated note to require latest DC & CC, not specific versions Added option for 2nd micro & modified Serial API Added description of fields above table Changed Explorer Frames from Optional to Recommended Moved G.19 to section 2.7.6 Clarified requirement Deleted request to be rediscovered if lost – was B.2.6 Added option for n/a if protocol library does not support this Added option for n/a if protocol library does not support this Added Binary Sensor CC v2 Added Notification CC v3 Added Thermostat Operating State Command Class, v2 Changed format from text to table with verification boxes and changed requirements to match “Minimal Controller Functionality”

8.4 33 20120516 DKING Enabled document protection

8.5 34 DKING Full Document Section 1.3 Section 1.5 Section 1.6 Section 1.7 Section 2.3 Section 2.3 Section 2.3.1 Section 2.3.3 Section 2.3.4 Section 2.4 Section 2.7

G.1.4 G.5.1.1 G.5.2 G.17 G.18 G.19 Section 2.7.3 B.3.9.1.1 B.3.9.13.1.1 A.3.6.5 A.4.6.5 A.100+ Section 2.7.6 2.7.6.3 2.7.7 Appendix A.7 Appendix B

Added Screen Tips for key words Updated text Updated text in #2 & #3 Updated certification process description Updated Singapore billing address Marked fields as required and added comments Added drop-down for product types Added text field for explanation of modification Updated SDK & Library drop-down lists Added comment about using unmodified Z-Wave module Added new Japan frequency Changed legend terminology:” O.a” is now “MS.a” and updated Status fields in form to correspond Re-worded note Re-worded for control instead of support Deleted G.5.2 - Moved to section 2.7.6.3 for Controllers Added note about hex values Changed wording to initiate and/or repeat Deleted G.19 – moved to Controller section Deleted chip specific section – moving to QFN certification form Deleted B.3.9.1.1 Min Controller functionality – moved to 2.7.6.3 Deleted B.3.9.13.1.1 Min Controller functionality – moved to 2.7.6.3 Updated requirement to v3 of Command Class (V2 is discontinued) Updated requirement to v3 of Command Class (V2 is discontinued) Added Central Scene CC & Meter Table Monitor CC v2 Revised entire section on Controllers Added cross references to Device Class Specification in C.2 & C.3 Deleted section on additional software information ( was 2.7.7) Updated text Updated text

8.5 35 20130402 DKING Section 2.2 New address for Pepper-One 8.5 36 20130828 DKING Section 2.2 New address for BuLogics



silabs.com | Building a more connected world. Page iv of iv

Table of Contents1 INTRODUCTION ................................................................................................................................... 2

1.1 Purpose .............................................................................................................................................. 2 1.2 Audience and prerequisites ................................................................................................................ 2 1.3 Validity of this document .................................................................................................................... 2 1.4 Precedence of definitions ................................................................................................................... 2 1.5 Content of this document ................................................................................................................... 3 1.6 Z-Wave Certification Process ............................................................................................................. 3 Certification contact information & further questions .................................................................................... 4 2 Z-WAVE CERTIFICATION FORM ........................................................................................................ 5

2.1 Company information: ........................................................................................................................ 5 2.2 Invoicing of Certification Fees ............................................................................................................ 5

2.2.1 Fees related to certification ...................................................................................................... 6 2.2.2 Payment terms ......................................................................................................................... 6

2.3 Basic Z-Wave Product Certification Information * Required fields ..................................................... 7 2.3.1 Type of Z-Wave Certification.................................................................................................... 7 2.3.2 Product Type ............................................................................................................................ 8 2.3.3 Product Information – Software ............................................................................................... 8 2.3.4 Product Information .................................................................................................................. 9 2.3.5 Resubmission or recertification - Description of changes ........................................................ 9 2.3.6 Use of the Proprietary / Manufacturer Proprietary Command Class .....................................10

2.4 Operating frequencies and voltage ..................................................................................................11 2.5 Publication of Z-Wave Certification ..................................................................................................12 2.6 Selection of the Z-Wave Test Partner ..............................................................................................13 2.7 Z-Wave Product Compliance Statement ..........................................................................................14

2.7.1 General Z-Wave Compliance .................................................................................................16 2.7.2 Product Documentation ..........................................................................................................21 2.7.3 Hardware ................................................................................................................................22 2.7.4 Z-Wave Network Support – Basic Device Classes ................................................................23 2.7.5 Z-Wave Application support ...................................................................................................26 2.7.6 Controllers ..............................................................................................................................53

2.7.6.1 Product Types ................................................................................................................53 2.7.6.2 Control of Preferred VS Non-Preferred Devices (Optional) ...........................................53 2.7.6.3 Controller Compliance ....................................................................................................54

3 SELF-CERTIFICATION ......................................................................................................................56

4 INITIAL CERTIFICATION REVIEW ....................................................................................................57 5 VERIFICATION TEST .........................................................................................................................58

6 CERTIFICATION RESULT .................................................................................................................60

REFERENCES ...........................................................................................................................................64



silabs.com | Building a more connected world. Page 2 of 67

1 INTRODUCTION

1.1 Purpose

This document contains the Z-Wave Certification Form and is used across the entire Z-Wave Certification Process to track and document the results of each step. The Certification Form has to be completed for each product to be Z-Wave certified.

The Z-Wave Certification form is designed to minimize the effort and cost for Z-Wave Certification for all parties involved in the process, i.e. the OEM, the Test Partner, and Silicon Labs. This Microsoft Word file is used to track the entire end-to-end process and to document all of its intermediate and final results.

1.2 Audience and prerequisites

The audience of this document is primarily Z-Wave OEMs and their service providers. Furthermore, this document is used by Silicon Labs and authorized Verification Test Partners during the Z-Wave Certification process.

It is assumed that the reader of this document is familiar with Z-Wave and the Z-Wave Device/Command Class Specifications, with the Z-Wave Certification Overview [6], furthermore with [1], [2], and the Z-Wave Development Kit overall.

1.3 Validity of this document

This updated Certification Form is valid with its release and mandatory to be used for the Z-Wave Certification of all products.

The Z-Wave Certification Overview [6] defines how products currently under development can be certified based on the current version of the Z-Wave Certification Form. It also explains the requirements regarding re-certification when changes to certified devices are made.

Future changes in the Z-Wave Technology, the Z-Wave Device/Command Class Specifications, and/or the Z-Wave Certification Program may cause modifications of this document and/or the Z-Wave Certification Form.

1.4 Precedence of definitions

Regarding Z-Wave Certification, definitions are valid based on the following precedence of documents (“1.” Has highest precedence):

1. Z-Wave Certification Overview [6]

2. Z-Wave Certification Form (this document)

3. Z-Wave Device & Command Class Specifications [2]

4. Z-Wave Device and/or Command Class Specifications not yet incorporated into [2]

5. Z-Wave ZW0301/ZW0401/SD3402 Application Programming Guide [1]




1.5 Content of this document

Section 2 of this document contains the Z-Wave Certification Form. The developer should use the form along with the Device Class Specifications as a guide to the requirements for the type of device being developed. The developer should complete the appropriate sub-sections during the definition stage of development. Prior to submitting the form/device, the developer must conduct their own testing to confirm that they have implemented everything correctly and then complete the Self-Certification column. The Verification column is completed by the test partner during Verification Testing.

Section 3 contains the Self-Certification page which must be filled out and signed by the OEM submitting their product for certification. A separate pdf or image file of this signed page must be submitted along with the entire Word document form. The signature page confirms that the OEM has conducted Self-Certification testing prior to submission of the Certification Form to the Z-Wave Certification Group.

Section 5 is filled in during the Verification Tests by the Z-Wave Test Partner.

Section 4 & 6 records the results of the Initial Certification Review and Final Review by Silicon Labs.

Appendixes containing instructions and guidelines when conducting self-certification of your Z-Wave product prior to submission for verification test at Z-Wave Test Partners.

1.6 Z-Wave Certification Process

The process for Z-Wave certification is straight forward. A detailed description is found in the Z-Wave Certification Overview [6].

Please submit the completed Word document Certification Form and a signed copy of the Self-Certification page (pdf or image file) to the e-mail address below.

If multiple versions of the same device are being developed and the only difference is frequency,the developer should submit the version with the highest priority for the full certification and usethis certification as the basis for re-certifying the additional devices.

Copies of the approved certification form (Initial Review) will be e-mailed to the selected TestPartner and developer. The developer should contact the selected Test Partner to arrangepayment of fees and shipment of test samples as soon as the Z-Wave Certification Form haspassed the initial review. Fees are listed in Section 2.1.3 of the certification overview.

A product does not enter the queue at the test house until they have received everythingincluding payment, samples and product instructions/documentation. The number of products inthis queue varies and there is no way to know how many are ahead of yours until the test househas received everything from you.

The Z-Wave Test Partner will report the test results to the Z-Wave Certification Group and thedeveloper will be notified of the results:

o If the device passes all of the tests, a certification will be issued.o If the device fails due to a few minor issues, the developer will be notified that it is going

into Ad Hoc and they will have 30 days to fix the issues and pass the tests. Failure toresolve the issues within this time frame will result in the case being closed withoutcertification.

o If the device fails due to major issues, we notify the developer that it failed and that theywill have to resubmit new documents and start the process over. This includes newfees.




Certification contact information & further questions

All communication regarding Z-Wave certification including general questions and comments should be directed to the following contacts:

Main Address of Certification group Silicon Labs, Inc. Z-Wave Certification Group Emdrupvej 26 A, 1. DK-2100 Copenhagen O Denmark Tel: +45 70 20 99 40 Fax: +45 70 20 99 50 E-mail: [email protected]

Billing Address:

Silicon Labs Technology Singapore Pte Ltd No. 5 Harper Road #03-01 Singapore 369673


mailto:[email protected]



2 Z-WAVE CERTIFICATION FORM

2.1 Company information:

Company: Street: City, State (Province): ZIP (Postal Code): Country:

Certification Contact:

Name: Title: E-mail address: Telephone: Fax:

2.2 Invoicing of Certification Fees

If a certification fee is due (depends on the Type of Z-Wave Certification as described below) Test House will invoice the OEM/customer upon passing of the Initial Review and an accepted Purchase Order issued to below Billing information.

Please provide a signed purchase order PO in PDF format and other information required by your company to process the invoice for the Certification Fee. Payment details are informed by test house. The case number must be referred to in the PO.

Billing/Vendor address:

Pepper One GmbH Kornmarkt 7 08056 Zwickau Germany

+49 (0) 375 / 39098695

Zertified by BuLogics 4200 Ridge Ave. Philadelphia, PA 19129 USA

+1 (215) 798-1017




2.2.1 Fees related to certification

The transaction fee for money transferee is paid for by the customer. The cost of packaging and shipping products to and from test house is purely paid for by customer. Other expenses which are related to the testing/ retesting of a given product are paid for by the customer e.g. flashing of new software or any other HW or SW changes requested by customer.

2.2.2 Payment terms

Pre-payment will be required before work begins.




2.3 Basic Z-Wave Product Certification Information * Required fields

Product Name*:

Brand Name*: (i.e. product is sold as)

Product Line*:

Model Number/Code*: Only one device can be certified on this form. Please refer to the Certification Overview, INS10638, for details.

Product Version*: Z-Wave software/firmware version or hardware version if hardware device

Product Description*:

Product Type*: Click to select controller Click to select slave (Corresponds to list in section 3.1.1.2 of Device Class Specification, SDS10242-21 or newer)

For all certifications that are “re-certifications” and “review-only certifications”:

Original Certification or Case Number:

Original Product Name:

2.3.1 Type of Z-Wave Certification

Regular Z-Wave Certification

New Product

Product Modification – Description Required

Description:

Issues in previous Z-Wave certification attempt of same product

User updateable products: first certification of product, or more than 12 months since last Regular Product Certification

Update of existing Z-Wave Certification for this product (See comments in Z-Wave Certification Overview for this case)

Re-Certification, all required conditions met

Limited Product Modification - Describe changes in section 2.3.5

Limited issues in previous Z-Wave certification attempt of same product




Review-only Z-Wave Certification (No Certification Fee)

Non-technical modification

Technical change that does not affect the product’s Z-Wave network behavior(provide explanation below)

New software / firmware release of user updateable product (All required conditions are met)

Update from ZW0201 to ZW0301 (No other hardware and/or software changes)

2.3.2 Product Type

General Z-Wave Product Hardware and software of product are being certified

Z-Wave Software Application Product Software is certified; requires Certified Z-Wave Platform product to run on

Z-Wave Hardware Platform Product Hardware together with sample application software is being certified; must use and expose standard Z-Wave Serial API to host application (not a standalone end user product)

Standard Z-Wave Serial API used (Unmodified Serial API firmware from Z-Wave Developer’s Kit)

OEM modified Serial API

Description of changes to Standard Serial API

2.3.3 Product Information – Software

Z-Wave Developer’s Kit version (API version): Click to select ZDK release Other:

Use of anything other than the latest release of the ZDK requires your acknowledgment that there are updates available and that you have elected to use an earlier version which may provide less functionality. An explanation why you are not using the latest version is also required.

Acknowledgement Explanation:

Note: Z-Wave products can only be certified provided they are based on “Active” or “Maintained” or “Monitored” Z-Wave releases (I.e. not on “Beta” z.x0.yy or “Obsolete” Z-Wave releases).

Z-Wave library type used to build the product: Click to select Z-Wave library type Other:




2.3.4 Product Information

Chipset Used

Based on 300 series Single Chip

Based on 400 series Single Chip Silicon Labs Mitsumi

Form of integration

Z-Wave chip directly integrated into product. (Z-Wave module has not been used) Note: This implementation requires QFN testing at an additional cost.

Blueprint used

Z-Wave module is used in product. Cannot be modified and must be implemented in accordance with Sigma Design’s specifications.

Silicon Labs Module Mitsumi Module Custom OEM Module – Must be QFN Certified QFN Certification Number:

Z-Wave Software Application Product

Specify the hardware platform/product that has been used to test the PC GUI program.

Product Name:

Revision:

Vendor:

This hardware platform / product is Z-Wave certified Z-Wave Product Certification Number

Note: If the hardware platform/product is not Z-Wave certified, the product needs to be certified as a General Z-Wave Product.

2.3.5 Resubmission or recertification - Description of changes

Certification is for technical changes that do not affect the product’s Z-Wave network behavior

Note: A clarification why these changes do not affect the product’s Z-Wave network behavior must be included in the change description below,

Certification is for changes that affect the product’s Z-Wave network behavior

Product Change Description:




2.3.6 Use of the Proprietary / Manufacturer Proprietary Command Class

The Proprietary Command Class has been used in this product

Explanation of the use of the Proprietary Command Classes:

Note: The use of the Proprietary and/or Manufacturer Proprietary Command Classes need to be approved by Silicon Labs based on the “Proprietary Command Class Request Form” [5]. Copies of the relevant Proprietary Command Class Request Forms need to be attached to this Certification Form.




2.4 Operating frequencies and voltage

Power Source

The product operates at 110V / 60Hz

The product operates at 230V / 50Hz

The product is battery powered

The product is USB powered

The product operates battery less (energy scavenger, e.g. solar cell)

The product can operate as battery and mains powered

Other -- Description:

Tolerance for alternative mains frequency

The product can also be operated with 50Hz but only in verification testing

The product can also be operated with 60Hz but only in verification testing

Frequency (Select only one)

Country RF Operating frequency 2ch

The product operates at the RF frequency for the US: 908.42 MHz

The product operates at the RF frequency for the EU: 868.42 MHz

The product operates at the RF frequency for Australia and New Zealand: 921.42 MHz

The product operates at the RF frequency for Hong Kong: 919.82 MHz

The product operates at the RF frequency for Malaysia: 868.10 MHz

The product operates at the RF frequency for Singapore: 868.42 MHz

The product operates at the RF frequency for India: 865.22 MHz

The product operates at the RF frequency for Brazil: 921.42 MHz

The product operates at the RF frequency for Russia: 869.0 MHz

Country RF Operating frequency 3ch

The product operates at the RF frequency for Japan: 922-926 MHz

The product operates at the RF frequency for Japan: 951-956 MHz




2.5 Publication of Z-Wave Certification

When a product has successfully passed Z-Wave Certification, Silicon Labs (and/or the Z-Wave Alliance on behalf of Silicon Labs) will publicize this on the Internet and/or other media. The publicized information may include but is not limited to the following:

Company name

Product name

Product description

Generic and specific device classes supported

Supported and controlled Command Classes

Product photo




2.6 Selection of the Z-Wave Test Partner

Conduct Verification Tests at Zertified by BuLogics

Zertified by BuLogics delivers third party compliance testing for the Z-Wave standard. A separate division of BuLogics, Zertified is committed to neutrality, quality assurance and customer satisfaction in its testing process. Zertified draws on BuLogics’ extensive Z-Wave background to offer the most qualified testing engineers experienced specifically in the Z-Wave standard. With each certification test, Zertified ensures complete reliability and interoperability across the most innovative wireless products on the market today.

For more information, please visit www.zertified.com.

Contact Information:

Zertified by BuLogics 4200 Ridge Ave. Philadelphia, PA 19129 USA

Name: Chris Ceperley Email: [email protected] Phone: 215-798-1017

Conduct Verification Test at Pepper-One GmbH

Pepper-One as the first Z-Wave certification house in Europe provides high quality and reliable certification tests for all kinds of Z-Wave products. Engineers at Pepper-One dispose of expert Z-Wave knowledge, long-standing experience in developing Z-Wave hard- and software devices and with extensive and structured testing processes. Pepper-One offers additional support to guarantee a quick and easy certification process for the customer.

Contact Information:

Pepper One GmbH Kornmarkt 7 08056 Zwickau Germany

Name: Mirko Klefker Email: [email protected] Phone: +49 (0) 375 / 39098695

Conduct Verification Tests at Silicon Labs Denmark

Can only be selected by a Feature Expert with prior approval from Certification Manager.


http://www.zertified.com/

mailto:[email protected]



2.7 Z-Wave Product Compliance Statement

The following sections form the Z-Wave Compliance Statement for the product submitted for Certification with this form and must be completed for all types of Z-Wave Certification.

The information for the Z-Wave Compliance Statement is provided in tabular form. The same tables are used by the OEM to state the level of support, to provide a confirmation of the self-certification performed by the OEM, and the result of the Verification Testing (where applicable).

The following notation is used in the form:

Column: Status • The Status column is the requirement status, i.e. defines what need to be implemented for

Z-Wave compliance. • Items and their requirement status are hierarchical in nature. I.e. if an item marked as

optional is implemented by a product, all subordinate items that are marked mandatory are required to be supported. If an item is optional and not implemented, all subordinate items of this first item that are marked mandatory are not required to be supported. All mandatory items that are subordinate to a mandatory item must be supported.

Notation Description

M Mandatory

MS.n Mandatory Selection - Must support at least one of the items marked with status “MS.n”. (e.g. if multiple items are marked with “MS.a.2” one must be supported)

R Recommended

O Optional

n/a Not applicable

X Prohibited

“Item” Conditional, status depends on the support marked for “Item”

Column: Role • The Role column specifies whether the requirement status is regarding controlling other

devices or being controlled.


S Support the related commands, i.e. receive SET / GET commands, send REPORTS

C Controller using this item to control other devices, i.e. send SET / GET commands, receive REPORTS

S + C Supports and Controls the related commands

n/a Not applicable




Column: Support & Self-Certification • The Support column is the fulfillment claimed / targeted by the OEM.• The Self-Certification column is filled out by the OEM to document that a test has been

performed by the OEM.


Y Supported / confirmed in self-certification test (see also additional comments below)

– Not supported

Co

A comment regarding the support of this item is provided by the OEM submitting this Z-Wave Certification Form in an attached document. Note: Use of such comments shall be a rare exception. The Z-Wave Certification Group will make the determination about Z-Wave compliance in this case.

Column: Verification • The Verification column is filled out by the authorized Z Wave Test Partner after test of the

support / non-support of the corresponding item.


Y Compliance verified in test (without Ad-hoc resolution)

YF Test item verified compliance in first attempt but failed in second attempt (Ad-hoc resolution or re-certification)

F Failure in test; Ad-hoc Resolution has not reached compliance; Explanation is provided in section 5 of this document

FY Failure in test in first attempt; compliance verified after Ad-hoc Resolution; Explanation is provided in section 5 of this document

Co A comment regarding the verification of this item is provided by the Z-Wave Test Partner. Refer to details in chapter 5, Verification Test

NT Not tested; Explanation is provided in section 5 of this document




2.7.1 General Z-Wave Compliance

Item Number

Item Description Status Support Certification

Self-Certifi-cation

Verifi-cation

G.1 General Z-Wave Compliance The product does not violate requirements for Z-Wave compliance as defined in [1].

M - - n/a

G.1.1 The device only uses the Generic Device Class, Specific Device Class and Command Classes defined in the “Z-Wave Device Class Specification” document

M - -

G.1.2 All commands (get, set, report etc.) in each Command Class supported by the device are implemented M - -

G.1.3 All mandatory Command Classes for the selected Generic/Specific Device Class are implemented M - -

G.1.4 The device is not based on a beta version of the Z-Wave protocol. Note: Devices based on Beta versions of the SDK cannot be certified. Beta versions end in the Z-Wave version numbering scheme with a “0” in the last digit, e.g. “4.20” or “5.00”

M - -

G.1.5 The optional functionality flag is set in node information frame in case any optional Command Classes are included for the selected device.

M - -

G.1.6 Specify document number and version of the Z-Wave Device Class and Z-Wave Command Class specifications used e.g. enter “19” for SDS10242-19: Note: The latest version of the Device Class and Command Class Specifications must be used. These can be downloaded from the Z-Wave Technical Services website.

Device Class Spec Doc.-Version: Command Class Spec Doc.-Version:

- n/a

Z-Wave Stack

G.2 Certified Z-Wave Stack The product is based on a standard Z-Wave stack

M - - n/a

G.2.1 The entire application runs on the Z-Wave chip (Embedded system) MS.g.2 - - n/a

G.2.2 The application runs at least partially on a second micro-controller (Embedded system) MS.g.2 - - n/a

G.2.3 The application runs on a second micro-controller – The standard Z-Wave Serial API is used. MS.g.2 - - n/a

G.2.4 The application runs on a second micro-controller – A modified Z-Wave Serial API is used. MS.g.2 - - n/a

G.2.5 The application runs on a PC – The application uses the standard Z-Wave Serial API (either directly or hidden through another library layer)

MS.g.2 - - n/a




Item Number


Self-Certifi-cation

Verifi-cation

G.2.6 The application runs on a PC – The application does not use the standard Z-Wave Serial API (either directly or hidden through another library layer)

MS.g.2 - - n/a

Z-Wave Hardware Platform

G.3 Z-Wave Hardware Platform Product is certified as Z-Wave Hardware Platform

O - -

n/a

G.3.1 Product exposes Z-Wave standard Serial API to applications M - - n/a

Meta Data

G.4 Meta Data The product transmits Meta Data as defined in a Command Class and / or other types of information that require multiple Z-Wave messages to transport the entire content between nodes

O - - n/a

G.4.1 All such transmissions are performed by using the Z-Wave API call ZW_SendDataMeta M - - n/a

G.4.2 The product implements traffic shaping / policing having a minimum delay of 35ms after each frame carrying such data as defined in [1].

M - - n/a

G.4.3 The API call ZW-SendDataMeta is used to transmit commands for a Manufacturer Proprietary Command Class. O - - n/a

Basic Command Class

G.5 Basic Command Class The Basic Command Class is implemented in compliance to the generic and specific device class of the product. M - -

G.5.1 The device controls via Basic commands M / O

(Note 5) - -

G.5.1.1 The device controls with OFF (0x00) and ON (0xFF) as minimum. MS.g.5.1 - -

G.5.1.2 It is possible to configure any value to be used in Basic Set commands sent by the device. MS.g.5.1 - -

G.5.1.3 The device learns values to be used in Basic Set commands by enquiring other devices with Basic Get; and is able to learn any value to be used in the Basic Set. MS.g.5.1 - -




Item Number


Self-Certifi-cation

Verifi-cation

Proprietary Command Class and/or Manufacturer Proprietary Command Class

G.6 Proprietary Command Classes This product uses one or multiple Proprietary and/or Manufacturer Proprietary Command Classes. O - - n/a

G.6.1 All use of Proprietary Command Classes approved The product uses the Proprietary Command Class and this has been approved by Silicon Labs based on the “Proprietary Command Class Request Form” [5].

Copies of the relevant Proprietary Command Class Request Forms have been attached to this Certification Form. (see also Note 1)

M - - n/a

Tolerant towards unexpected frame lengths

G.7 The Frame Length field is NOT used to discard an incoming frame in which the frame length longer than expected. The implementation is robust against frames that are longer than expected. (See also Note 3)

M - - n/a

Inclusion Method

G.8 The device shall be able to operate at normal power level when being included into an existing Z-Wave network (For controllers: if instructed to use normal power level by the primary/inclusion controller)

M - -

G.8.1 The device is a slave device and has a user configurable mode to operate at low power level when being included into an existing Z-Wave network. (Notes: 1. It is permitted to make this mode as a default mode2. Mark this item as n/a if the device is not a slave device )

O - -

G.8.1.1 The device’s documentation describes the normal power inclusion versus the low power inclusion, and how to activate either mode.

M - -

G.8.2 This device implements Network Wide Inclusion O - -

Battery operation

G.9 The product is battery operated. O - - n/a G.9.1 When learn mode is initiated the product will operate in normal

transmit mode until an inclusion/exclusion process is completed, before entering power down mode. (Notes: After entering learn mode the device must stay awake until a callback status with the value LEARN_MODE_DONE or LEARN_MODE_FAILED is received from the API.)

M - - n/a




Item Number


Self-Certifi-cation

Verifi-cation

G.9.2 The device can be put into a mode to remain awake and listen to commands through user interaction (e.g. to allow enquiring Version or Manufacturer Specific)

MS.g.9 - -

G.9.2.1 The device’s documentation describes how to activate this mode M - -

G.9.3 This is a FliRS device O - -

Support of Z-Wave Application Security Layer

G.10 The device implements the Z-Wave Application Security Layer in accordance with [7]. O - -

G.10.1 The product documentation (manuals, help files, web page link etc.) clearly describes the product as a Security Enabled Z-Wave Product.

M - -

G.10.2 The functionality and supported / controlled command classes of the device is identical when included as a secure and non-secure device.

MS.g.10 - -

G.10.3 The functionality and / or supported / controlled command classes is different when included as a secure and non-secure device.

MS.g.10 - -

G.10.3.1 The device is categorized with a secure generic or specific device class. M - -

G.10.3.2 The product documentation (manuals, help files, web page link etc.) states a Security Enabled Z-Wave Controller must be used in order to fully utilize the product.

M - -

Additional Aspects of Z-Wave Compliance

G.11 Production test mode A production test mode is implemented in the product

O - - n/a

G.11.1 The production test mode can only be entered by external hardware stimulation M - - n/a

G.12 Factory Reset The device provides a factory reset function

R - -

G.12.1 The factory reset function is described in the documentation R - -

G.13 Power Down The product uses the Power Down functionality in the API.

O - n/a n/a

G.14 Listening Flag of Node Information Frame Listening Flag set to APPLICATION_NODEINFO_LISTENING for continuously powered devices based on a Z-Wave library with repeater functionality. Listening Flag set to APPLICATION_NODEINFO_NOT_LISTENING for not continuously powered devices e.g. battery operated devices.

M - -




Item Number


Self-Certifi-cation

Verifi-cation

G.15 Watchdog Timer The watchdog timer of the Z-Wave chip is enabled

R - - n/a

G.16 Duty cycle The product does not have a transmit duty cycle of more than 1%, relative to a one hour period. (see also Note 2)

M / R - - n/a

The Manufacturer ID referenced in G.17.1 and G.17.2 below is assigned by Silicon Labs. Please send a request to the Z-Wave Certification e-mail address if your company needs one assigned.

The Product Type ID and Prod ID numbers are assigned by the manufacturer and are intended for use in identifying and differentiating various products from the same manufacturer. These numbers should be unique for each device being certified.

G.17 Manufacturer Specific If the Manufacturer Specific command class is supported, provide the values returned in the Manufacturer Specific report in this section (otherwise please insert “n/a”)

Hexadecimal Values Returned (4) n/a n/a

G.17.1 Manufacturer ID 1 -

G.17.2 Manufacturer ID 2 -

G.17.3 Product Type ID 1 -

G.17.4 Product Type ID 2 -

G.17.5 Product ID 1 -

G.17.6 Product ID 2 -

G.18 Explorer Frames The device shall be able to initiate and/or repeat the use of Explorer Frames to obtain a new route to a lost destination node

R - -

Notes:

1. Fill in section 2.3.6 if the product uses Proprietary and/or manufacturer Proprietary command classes2. Regulatory requirement in Europe and suggestion in US.3. Future versions of Z-Wave Device classes may add information to existing commands by extending the length of

such commands. Every Z-Wave implementation must tolerate and support such extended frames. See Section3.1.4, Command Class Versioning, of the Z-Wave Command Class Specification for additional information.

4. Confirm values returned in Self-Certification and in Verification Testing5. Depending on the generic and specific device class of the device, this item is either mandatory or optional.




2.7.2 Product Documentation

Item Number


Self-Certifi-cation

Verifi-cation

D.1 Inclusion / Exclusion / Replication The product documentation (manuals, help files, web page links, etc) describes the ‘inclusion’, ‘exclusion’ and ‘replication’ between Z-Wave node(s)

M - -

D.1.2 Use and explanation non-standard terms If other terms / words are used for ‘inclusion’, ‘exclusion’ and ‘replication’ in the documentation and/or user interface of the product, the product documentation contains at least a list/table explaining the synonyms. (Mark as “n/a” if only standard terms are used)

M - -

D.2 Include device into existing network The product documentation (manuals, help files, web page links, etc) describes how to add the product into an existing Z-Wave network from a 3rd party vendor.

M - -

D.3 Devices from multiple vendors in one network The product documentation (manuals, help files, web page links, etc) has a section which describes how products from different vendors and product categories can be part of the same network and that the different always powered nodes can act as repeaters regardless of vendor. Please note: This can be a generic statement and does not have to address the functions of the DUT.

M - -

D.4 Documentation for Configuration Command Class If the Configuration command class is supported, documentation for showing the use of parameter numbers and values is required. (Mark as “n/a” if Configuration commands are not supported)

M (1) (2)

- -

D.5 Documentation for Associations If the Association command class is supported, documentation is provided about how association groups are used in the device. (Mark as “n/a” if Association commands are not supported)

M (1) (2)

- -

D.6 Documentation related to BASIC commands If the device is based on a device class where the generic and the specific device class do not fully specify which values are implemented in Basic Set commands and/or do not fully specify the denotation of the values in Basic Set commands, such information is provided in the device’s documentation. (Mark as “n/a” if Basic commands are fully specified in the generic and/or specific device class of the device)

M (1)

- -

D.7 Documentation for Verification testing If the testing of any item in certification requires “special” procedures, documentation is provided for this to the test lab. All documentation is provided in English language; or arrangements have been made with the test lab. (Mark “n/a” if both are not applicable)

M - -




D.8 Documentation for Controllers Include description of controlled commands and functions as well as instructions for controlling included devices. (Mark “n/a” if this device is not a controller)

M - -

Notes: 1: Such documentation may be provided on a publicly accessible website, if the product documentation contains

a clear reference to this website and outlines the content that can be found there. 2: Exceptions may be agreed with the Z-Wave Certification Group in certain cases (e.g. risk of damage)

2.7.3 Hardware

Item Number


Self-Certifi-cation

Verifi-cation

H.1 Minimum communication range achieved In order to assure proper communication range, the device must fulfill the following criteria without retransmission:

M - -

Measured in line of sight ; with load (e.g. dimmer: lamp used) CER measured [%]

H.1.1 25m range: CER << 5% (Communication Error Rate)

OEM: % Verification Test Lab: % M

- -




2.7.4 Z-Wave Network Support – Basic Device Classes

Item Number

Item Description Status Support Certification Self-

Certifi-cation

Verifi-cation

Slave

B.1 The product is based on the Slave Library O - - n/a

B.1.1 Inclusion of the product into a Z-Wave network M - -

B.1.2 Exclusion of the product from the Z-Wave network M - -

B.1.3 Send NodeInfo frame based on user interaction M - -

B.1.4 Function as a repeater in the Z-Wave network O - -

B.1.5 Z-Wave Application Security Layer The device supports the Security Command Class

O - -

B.1.5.1 Slave can be included by any controller supporting the Security Command Class as a secure device. M - -

Routing Slave

B.2 The product is based on the Routing Slave Library O - - n/a B.2.1 Device is an Enhanced Slave O - - n/a

B.2.2 Inclusion of the product into a Z-Wave network M - -

B.2.3 Exclusion of the product from the Z-Wave network M - -

B.2.4 Send NodeInfo frame based on user interaction M - -

B.2.5 Function as a repeater in the Z-Wave network O - -

B.2.6 Request topology updates from SUC / SIS O - -

B.2.7 Device will call ZW_RequestNetworkUpdate at least once per day (if SUC / SIS is present) R - - n/a

B.2.8 Z-Wave Application Security Layer The device supports the Security Command Class

O - -

B.2.8.1 Slave can be included by any controller supporting the Security Command Class as a secure device. M - -




Z-Wave Controller Library (Controller, Static Controller, Installer, or Bridge)

B.3 The product is based on a Z-Wave Controller Library O - - n/a

B.3.1

The HomeID is in the range allocated to the OEM or random home ID generation used. Precautions are taken to ensure that NodeID from the allocated range is only used once during production.

M - - n/a

B.3.2 Controller can be included into an existing Z-Wave network M - -

B.3.3 Controller can be excluded from the Z-Wave network M - -

B.3.4 Send NodeInfo frame based on user interaction O - -

B.3.5 Request NodeInfo frame O - -

B.3.6.1 Controller will call ZW_RequestNetworkUpdate at least once per day (if SUC / SIS is present) R - - n/a

B.3.6.2 Controller will call ZW_RequestNetworkUpdate before configuring associations (if SUC / SIS is present) R - -

B.3.7 Controller Replication Commands must always as minimum be acknowledge on application level using the API call “ZW_ReplicationReceiveComplete”

M - -

B.3.8 Controller can only act a secondary controller and can be included into a network started by any controller from any manufacturer

MS.b.3 - -

B.3.8.1

Product documentation clearly describes that the controller can only act as secondary controller; and that another Z-Wave controller is required as primary controller to setup and maintain the network. Product literature and websites include same clarification. (OEM either need to provide samples / drafts; or confirm this will be assured with a comment on the self-certification page)

M - -

B.3.8.2 Z-Wave Application Security Layer The controller implements the Security Command Class

O - -

B.3.8.2.1 The controller can be included by any controller of any type of manufacturer supporting the Security Command Class as a secure device

M - -

B.3.8.2.1.1 The controller will inherit the security scheme from the including controller M - -

B.3.9 Controller can act as primary and/or inclusion controller MS.b.3 - -

B.3.9.1 Ability to include compliant controller and slave nodes of any type from any manufacturer M - -

B.3.9.2 Ability to exclude compliant controller and slave nodes of any type from any manufacturer M - -

B.3.9.3 Receive primary controller role via controller shift M - -

B.3.9.4 Relinquish primary controller role via a controller shift and become secondary controller (in case the controller is in a SIS role or an inclusion controller role this item is exempted)

M - -

B.3.9.5 Support reception of protocol replication data from another controller M - -




B.3.9.6 Ability to replicate protocol data to another controller M - -

B.3.9.7 Ability to replicate group/scene data to another controller O - -

B.3.9.8 Delete a malfunctioning node O - -

B.3.9.9 Support replacement of a malfunctioning node O - -

B.3.9.10 Controller initiates rediscovery of nodes from a SUC / SIS R - -

B.3.9.11 Controller initiates rediscovery from a SUC / SIS when noticing problems in the network R - -

B.3.9.12

Assign SIS capability Controller will always attempt to assign the SIS role to another controller that is being included (in case the controller is in a SIS role or an inclusion controller role this item is exempted)

M - -

B.3.9.13 Z-Wave Application Security Layer The controller implements the Security Command Class

O - -

B.3.9.13.1 The controller can include compliant controller and slave nodes of any type from any manufacturer supporting the Security Command Class as secure devices

M - -

B.3.9.13.2 The controller can be included by any controller of any type from any manufacturer supporting the Security Command Class as a secure device.

M - -

B.3.9.13.2.1 The controller will inherit the security scheme from the including controller. M - -

B.3.9.14 Controller is Static or Bridge Controller O - -

B.3.9.14.1 Controller is not turned off by the consumer (e.g. PCs would typically not fall into this category) O - -

B.3.9.14.1.1 Controller will accept to become SUC upon request (if supported by the protocol library. Mark n/a if not supported )

M - -

B.3.9.14.1.2 Controller will accept to become SIS upon request (if supported by the protocol library. Mark n/a if not supported ))

M - -

B.3.9.15 Controller is portable controller and/or may be turned off by the consumer O - -

B.3.9.15.1 Controller will neither accept to become SUC nor SIS M - -

General Demands for all protocol libraries

B.4.1 All Command Classes supported must be listed in the NIF M - -

B.4.2 Controlled Command Class are listed in the NIF R - -

B.4.2.1 If controlled Command Classes are listed they must be listed correctly with proper use of the control mark. M - -




2.7.5 Z-Wave Application support

Devices can issue commands to control other devices or support – i.e. execute / act upon or “be controlled”- the commands they receive. Correspondingly, “Control” (other devices) and “Support” are the two roles in which a command class can be implemented. Compliance to Z-Wave requires implementing Command Classes in specific roles.

For each Z-Wave Command Class where support is stated in this form, all commands specified in the corresponding Z-Wave Command Class must be implemented.

Items that are stated as “not supported” in the Z-Wave Certification Form must not be implemented in the product.

Item Number

Item Description Status Role Support Certification Self-

Certifi-cation

Verifi-cation

Generic and Specific Device Classes and associated Command Classes

A.1 Alarm Sensor Generic Device Class O n/a - -

A.1.1 No Specific Device Class defined MS.a.1 n/a - -

A.1.1.1 Basic Command Class supported with compliant mapping M S - -

A.1.2 Basic Routing Alarm Sensor Specific Device Class MS.a.1 n/a - -


A.1.2.2 Alarm Sensor Command Class M S+C - -

A.1.2.3 Association Command Class M S - -

A.1.2.4 Manufacture Specific Command Class M S - -

A.1.2.5 Version Command Class M S - -

A.1.3 Routing Alarm Sensor Specific Device Class MS.a.1 n/a - -




A.1.3.4 Battery Command Class M S - -





Item Number


Certifi-cation

Verifi-cation


A.1.3.7 Alarm Silence Command Class R S - -

A.1.4 Basic Zensor Net Alarm Sensor Specific Device Class MS.a.1 n/a - -






A.1.5 Zensor Net Alarm Sensor Specific Device Class MS.a.1 n/a - -







A.1.6 Advanced Zensor Net Alarm Sensor Specific Device Class MS.a.1 n/a - -











Item Number


Certifi-cation

Verifi-cation

A.1.7 Basic Routing Smoke Sensor Specific Device Class MS.a.1 n/a - -






A.1.8 Routing Smoke Sensor Specific Device Class MS.a.1 n/a - -








A.1.9 Basic Zensor Net Smoke Sensor Specific Device Class MS.a.1 n/a - -






A.1.10 Zensor Net Smoke Sensor Specific Device Class MS.a.1 n/a - -






Item Number


Certifi-cation

Verifi-cation





A.1.11 Advanced Zensor Net Smoke Sensor Specific Device Class MS.a.1 n/a - -








A.2 Binary Switch Generic Device Class O n/a - -

A.2.1 Basic Command Class supported with compliant mapping M S - -

A.2.2 Binary Switch Command Class M S - -

A.2.3 Specific Device Class not used MS.a.2 n/a - -

A.2.4 Binary Power Switch Specific Device Class MS.a.2 n/a - -

A.2.4.1 All Switch Command Class M S - -

A.2.4.2 Manufacturer Specific Command Class R S - -

A.2.4.3 Version Command Class R S - -

A.2.4.4 Protection Command Class R S - -

A.2.4.5 Clock Command Class R S - -

A.2.5 Binary Scene Switch Specific Device Class MS.a.2 n/a - -




Item Number


Certifi-cation

Verifi-cation

A.2.5.1 Scene Activation Command Class M S - -

A.2.5.2 Scene Actuator Configuration Command Class M S - -


A.2.5.4 Manufacturer Specific Command Class M S - -


A.2.6 Binary Tunable Color Light Specific Device Class MS.a.2 n/a - -



A.2.6.3 Color Control Command Class – version 1 M S - -

A.2.6.4 Node Naming and Location Command Class R S - -

A.2.6.5 Association Command Class R S - -

A.3 Remote Controller Generic Device Class O n/a - -

A.3.1 Device can control other nodes via Basic Commands M C - -

A.3.2 Device can be controlled via Basic Commands O S - -


A.3.4 Portable Remote Controller Specific Device Class MS.a.3 n/a - -

A.3.4.1 Battery Command Class R S - -




A.3.5 Portable Scene Controller Specific Device Class MS.a.3 n/a - -


A.3.5.2 Scene Activation Command Class M C - -




Item Number


Certifi-cation

Verifi-cation

A.3.5.3 Scene Controller Configuration Command Class M S - -



A.3.5.6 Association Command Class R C - -

A.3.5.7 Scene Actuator Configuration Command Class R C - -

A.3.5.8 All Switch Command Class R C - -

A.3.5.9 Replication Command Class (Controller replication of the application part) R S - -

A.3.6 Portable Installer Tool Specific Device Class MS.a.3 n/a - -

A.3.6.1 Controller Replication Command Class M S+C - -

A.3.6.2 Multi Command Command Class M S - -

A.3.6.3 Version Command Class M S+C - -

A.3.6.4 Manufacturer Specific Command Class M S+C - -

A.3.6.5 Multi Channel Command Class - Version 3 M C - -

A.3.6.6 Association Command Class M C - -

A.3.6.7 Multi Channel Association Command Class - Version 2 M C - -

A.3.6.8 Wake Up Command Class M C - -

A.3.6.9 Configuration Command Class M C - -


A.3.6.11 Battery Command Class R S+C - -

A.3.6.12 Binary Switch Command Class R C - -

A.3.6.13 Multilevel Switch Command Class R C - -

A.3.6.14 Scene Controller Configuration Command Class R C - -





Item Number


Certifi-cation

Verifi-cation


A.3.6.17 Node Naming and Location Command Class R C - -

A.3.6.18 Grouping Name Command Class R C - -

A.3.6.19 Protection Command Class R C - -

A.3.6.20 Powerlevel Command Class R C - -

A.4 Static Controller Generic Device Class O n/a - -


A.4.2 Device can be controlled via Basic Commands O S - -


A.4.4 PC Controller Specific Device Class MS.a.4 n/a - -





A.4.5 Scene Controller Specific Device Class MS.a.4 n/a - -

A.4.5.1 Device can be controlled via Basic Commands M S - -

A.4.5.2.1 Association Command Class M S - -

A.4.5.2.2 Association Command Class R C - -

A.4.5.3.1 Scene Activation Command Class M C - -

A.4.5.3.2 Scene Activation Command Class R S - -

A.4.5.4.1 Scene Controller Configuration Command Class M S - -

A.4.5.4.2 Scene Controller Configuration Command Class R C - -





Item Number


Certifi-cation

Verifi-cation





A.4.6 Static Installer Tool Specific Device Class MS.a.4 n/a - -

A.4.6.1 Controller Replication Command Class M S+C - -


A.4.6.3 Version Command Class M S+C - -

A.4.6.4 Manufacturer Specific Command Class M S+C - -

A.4.6.5 Multi Channel Command Class - Version 3 M C - -

A.4.6.6 Association Command Class M C - -

A.4.6.7 Multi Channel Association Command Class - Version 2 M C - -

A.4.6.8 Wake Up Command Class M C - -

A.4.6.9 Configuration Command Class M C - -


A.4.6.11 Binary Switch Command Class R C - -

A.4.6.12 Multilevel Switch Command Class R C - -

A.4.6.13 Battery Command Class R C - -

A.4.6.14 Scene Controller Configuration Command Class R C - -



A.4.6.17 Node Naming and Location Command Class R C - -

A.4.6.18 Grouping Name Command Class R C - -




Item Number


Certifi-cation

Verifi-cation

A.4.6.19 Protection Command Class R C - -

A.4.6.20 Powerlevel Command Class R C - -

A..4.7 Gateway Specific Device Class MS.a.4 n/a - -

A.4.7.1 Multi-Channel Gateway Specific Device Class M n/a - - n/a

A.4.7.1.1 Clock Command Class R S - -

A.4.7.1.2 Manufacturer Specific Command Class M S - -

A.4.7.1.3 Multi-Channel Command Class version 3 M C - -

A.4.7.1.4 Security Command Class M S+C - -

A.4.7.1.5 Version Command Class M S - -

A.4.7.1.6 Z/IP Gateway Specific Device Class MS.a.4.7.1 n/a - - n/a

All Network Management Command Class MUST be sent securely when used on the Z-Wave PAN, using at least Z-Wave Security Command Class Version 1. When used on the LAN side other means of security SHOULD be used.

Z-Wave Support

A.4.7.1.6.1 Application Capability Command Class M C - -

A.4.7.1.6.2 Multi-Channel Command Class version 3 M S - -

A.4.7.1.6.3 Network Management Basic Node Command Class M S - -

A.4.7.1.6.4 Network Management Inclusion Command Class M S - -

A.4.7.1.6.5 Network Management Primary Command Class M S - -

A.4.7.1.6.6 Network Management Proxy Command Class M S - -

A.4.7.1.6.7 Transport Service Command Class M S+C - -

A.4.7.1.6.8 Z/IP-ND Command Class M S+C - -

IP Support

A.4.7.1.6.9 mDNS Responder M S - -

A.4.7.1.6.10 Ping (ICMP Echo) M S - -

A.4.7.1.6.11 Z/IP Command Class (UDP port 4123) M S+C - -




Item Number


Certifi-cation

Verifi-cation

A.5 Repeater Slave Generic Device Class O n/a - -



A.5.3 Basic Repeater Slave Specific Device Class MS.a.5 n/a - -

A.5.3.1 Powerlevel Test Command Class R S - -




A.6 Multilevel Switch Generic Device Class O n/a - -


A.6.2 Multilevel Switch Command Class M S - -


A.6.5 Multilevel Power Switch Specific Device Class MS.a.6 n/a - -






A.6.6 Multilevel Scene Switch Specific Device Class MS.a.6 n/a - -

A.6.6.1 Scene Activation Command Class M S - -

A.6.6.2 Scene Actuator Configuration Command Class M S - -






Item Number


Certifi-cation

Verifi-cation


A.6.7 Multiposition Motor Specific Device Class (Not recommended for new products)

A.6.8 Motor Control Class A Specific Device Class MS.a.6 n/a - -


A.6.8.2 Binary Switch Command Class M S - -

A.6.8.3 Multilevel Switch Command Class, Version 3 M S - -



A.6.9 Motor Control Class B Specific Device Class MS.a.6 n/a - -






A.6.10 Motor Control Class C Specific Device Class MS.a.6 n/a - -






A.6.11 Multilevel Tunable Color Light Specific Device Class MS.a.6 n/a - -



A.6.11.3 Color Control Command Class – version 1 M S - -




Item Number


Certifi-cation

Verifi-cation

A.6.11.4 Node Naming and Location Command Class R S - -


A.7 Toggle Switch Generic Device Class (Not recommended for new products)

A.8 Remote Switch Generic Device Class O n/a - -



A.8.3 Binary Remote Switch Specific Device Class MS.a.8 n/a - -

A.8.3.1 Binary Switch Command Class M C - -



A.8.4 Multilevel Remote Switch Specific Device Class MS.a.8 n/a - -

A.8.4.1 Multilevel Level Switch Command Class M C - -



A.8.5 Binary Toggle Remote Switch Specific Device Class (Not recommended for new products) A.8.6 Multilevel Toggle Remote Switch Specific Device Class (Not recommended for new products)

A.9 Binary Sensor Generic Device Class O n/a - -


A.9.2 Binary Sensor Command Class M S - -


A.9.4 Routing Binary Sensor Specific Device Class MS.a.9 n/a - -

A.9.4.1 Wakeup Command Class R S - -





Item Number


Certifi-cation

Verifi-cation





A.10 Multilevel Sensor Generic Device Class O n/a - -


A.10.2 Multilevel Sensor Command Class (Implemented version must be selected under optional CC’s) M S - -


A.10.6 Routing Multilevel Sensor Specific Device Class MS.a.10 n/a - -

A.10.6.1 Wakeup Command Class R S - -






A.11 Pulse Meter Generic Device Class O n/a - -


A.11.2 Pulse Meter Command Class M S - -

A.11.3 Specific Device Class not used M n/a - -

A.12 Display Generic Device Class O n/a - -






Item Number


Certifi-cation

Verifi-cation


A.12.3 Simple Display Specific Device Class MS.a.12 n/a - -


A.12.4 Advanced Energy Control Specific Device Class MS.a.12 n/a - -


A.12.4.2 Meter Table Monitor Command Class M S - -

A.12.4.3 Meter Table Configuration Command Class M S - -



A.12.4.6 Rate Table Configuration Command Class R S - -

A.12.4.7 Rate Table Monitor Command Class R S - -

A.12.4.8 Tariff Table Configuration Command Class R S - -

A.12.4.9 Tariff table Monitor Command Class R S - -

A.12.4.10 Demand Control Plan Configuration Command Class R S - -

A.12.4.11 Demand Control Plan Monitor Command Class R S - -

A.13 Entry Control Generic Device Class O n/a - -



A.13.2 Door Lock Specific Device Class MS.a.13 n/a - -


A.13.2.2 Lock Command Class M S - -






Item Number


Certifi-cation

Verifi-cation

A.13.3 Advanced Door Lock Specific Device Class MS.a.13 n/a - -


A.13.3.2 Door Lock Command Class M S - -



A.13.3.5 User Code Command Class R S - -

A.13.3.6 Alarm Command Class R S - -



A.13.4 Secure Keypad Door Lock Specific Device Class MS.a.13 n/a - -


A.13.4.2 Security Command Class M S - -

A.13.4.3 Door Lock Command Class (secured) M S - -

A.13.4.5 User Code Command Class (secured) M S - -

A.13.4.6 Manufacturer Specific Command Class (unsecured) M S - -

A.13.4.7 Version Command Class (unsecured) M S - -



A.15 Window Covering Generic Device Class (Not recommended for new products)

A.16 Thermostat Generic Device Class O n/a - -

A.16.1 The device is permanently listening O - -





Item Number


Certifi-cation

Verifi-cation

A.16.1.2 Device documentation contains explanation of “Energy Saving Mode” and “Comfort Mode” (Mark as n/a if not applicable for the specific device class)

M n/a - -


A.16.5 General Thermostat V2 Specific Device Class MS.a.16 n/a - -

A.16.5.1 Thermostat Mode Command Class M S - -

A.16.5.2 Thermostat Setpoint Command Class M S - -



A.16.5.5 Multilevel Sensor Command Class O S - -

A.16.5.6 Multi Channel Command Class, version 2 (Multi Instance Command Class Not allowed any more) O S - -

A.16.6 Setback Schedule Thermostat Specific Device Class MS.a.16 n/a - -

A.16.6.1 Multi-Command Command Class M S - -

A.16.6.2 Multi-Command Command Class M C - -

A.16.6.3 Climate Control Schedule Command Class M S - -

A.16.6.4 Climate Control Schedule Command Class M C - -

A.16.6.5 Clock Command Class M C - -



A.16.6.8 The device supports the mandatory operation sequence after inclusion as specified in device class specification M n/a - -

A.16.6.9 The device supports the mandatory operation when the schedule is not up to date as specified in device class specification

M n/a - -

A.16.6.10 The device supports all supported and controlled commands when encapsulated by the Multi-Command command class M n/a - -

A.16.6.11 The device is not permanently listening (e.g. battery operated) O n/a - -

A.16.6.11.1 Battery Command Class M S - -

A.16.6.11.2 Wake Up Command Class Version 2 M S - -




Item Number


Certifi-cation

Verifi-cation

A.16.6.11.3 The device supports the mandatory operation upon its wakeup as specified in device class specification M n/a - -

A.16.6.11.4 The device sends as many commands as possible in a single Multi-Command frame R n/a - -

A.16.7 Setpoint Thermostat Specific Device Class MS.a.16 n/a - -


A.16.7.2 Thermostat Setpoint Command Class M S - -




A.16.7.6 Multilevel Sensor Command Class R S - -

A.16.7.7 Multi Command Command Class M C - -

A.16.7.8 Thermostat Setpoint Command Class O C - -

A.16.7.9 The device is not permanently listening (e.g. battery operated) O n/a - -

A.16.7.9.1 Battery Command Class M S - -

A.16.7.9.2 Wake up Command Class M S - -

A.17 AV Control Point Generic Device Class O n/a - -



A.17.3 Satellite Receiver Specific Device Class (Not recommended for new products)

A.17.4 Satellite Receiver V2 Specific Device Class MS.a.17 n/a - -

A.17.4.1 Simple AV Control Class M S - -



A.17.5 Doorbell Specific Device Class MS.a.17 n/a - -




Item Number


Certifi-cation

Verifi-cation

A.17.5.1 Basic Command Class with compliant mapping M S - -

A.17.5.2 Binary Sensor Command Class M S - -







A.18 Meter Generic Device Class O n/a - -

A.18.1 Basic Command Class with compliant mapping M S - -

A.18.2 Specific Device Class Not Used MS.a.18 n/a - -

A.18.3 Simple Meter Specific Device Class MS.a.18 n/a - -

A.18.3.1 Meter Command Class M S - -



A.18.4 Advanced Energy Control Specific Device Class MS.a.12 n/a - -


A.18.4.2 Meter Table Monitor Command Class M S - -

A.18.4.3 Meter Table Configuration Command Class M S - -



A.18.4.6 Rate Table Configuration Command Class R S - -

A.18.4.7 Rate Table Monitor Command Class R S - -




Item Number


Certifi-cation

Verifi-cation

A.18.4.8 Tariff Table Configuration Command Class R S - -

A.18.4.9 Tariff table Monitor Command Class R S - -

A.18.4.10 Demand Control Plan Configuration Command Class R S - -

A.18.4.11 Demand Control Plan Monitor Command Class R S - -

A.19 Ventilation Generic Device Class O n/a - -

A.19.1 Basic Command Class with compliant mapping M S - -

A.19.2 Specific Device Class Not Used MS.a.19 n/a - -


A.19.3 Residential Heat Recovery Ventilation Specific Device Class MS.a.19 n/a - -


A.19.3.2 HRV Status Command Class, Version 1 M S - -

A.19.3.3 HRV Control Command Class, Version 1 M S - -



A.22 Semi Interoperable Generic Device Class (Requires approval for use of Proprietary Command Class) O n/a - -

A.22.1 Manufacturer Specific Command Class M S - -

A.22.2 Proprietary Command Class M S



A.22.4 Energy Production Specific Device Class MS.a.20 n/a - -


A.22.4.2 Energy Production Command Class M S - -




Item Number


Certifi-cation

Verifi-cation

A.99 Insert generic device class not found in this form here O n/a - -

A.99.1 Insert specific device class not found in this form here MS.a.99 n/a - -

A.99.2 Insert specific device class not found in this form here - -




Select only the highest version of the Command Class supported and/or controlled. Example: If Meter CC v3 is supported, do not select v1 and v2.

Item Number


Certifi-cation

Verifi-cation

Add all Command Classes Supported and/or Controlled (Note 1) (Note 2)

A.100.1 Alarm Command Class, version 1 O - - -

A.100.2 Alarm Command Class, version 2 O - - -

A.101 Alarm Sensor Command Class, version 1 O - - -

A.102 Alarm Silence Command Class, version 1 O - - -

A.103 All Switch Command Class, version 1 O - - -

A.104 Application Capability Command Class, version 1 O - - -

A.105 Application Status Command Class, version 1 O - - -

A.106.1 Association Command Class, version 1 O - - -

A.106.2 Association Command Class, version 2 O - - -

A.107 Association Command Configuration Command Class, version 1 O - - -

A.108 Association Group Information Command Class, version 1 O - - -

A.109 Basic Command Class, version 1 M / R (3) - - -

A.110 Basic Tariff Information Command Class, version 1 O - - -

A.111 Basic Window Covering Command Class, version 1 O - - -

A.112 Battery Command Class, version 1 O - - -

A.113.1 Binary Sensor Command Class, version 1 O - - -

A.113.2 Binary Sensor Command Class, version 2 O - - -

A.114 Binary Switch Command Class, version 1 O - - -

A.115 Binary Toggle Switch Command Class, version 1 O - - -

A.116 Central Scene Command Class, version 1 O - - -




Item Number


Certifi-cation

Verifi-cation

A.117 Climate Control Schedule Command Class, version 1 O - - -

A.118 Clock Command Class, version 1 O - - -

A.119 Color Control Command Class, version 1 O - - -

A.120.1 Configuration Command Class, version 1 O - - -

A.120.2 Configuration Command Class, version 2 O - - -

A.121 Controller Replication Command Class, version 1 O - - -

A.122 CRC-16 Encapsulation Command Class, version 1 O - - -

A.123 Demand Control Plan Configuration Command Class, version 1 O - - -

A.124 Demand Control Plan Monitor Command Class, version 1 O - - -

A.125 Device Reset Locally Command Class, version 1 O - - -

A.126 Door Lock Command Class, version 1 O - - -

A.127 Door Lock Logging Command Class, Version 1 O - - -

A.128 Energy Production Command Class, version 1 O - - -

A.129.1 Firmware Update Meta Data Command Class, version 1 O - - -

A.129.2 Firmware Update Meta Data Command Class, version 2 O - - -

A.130 Geographic Location Command Class, version 1 O - - -

A.131 Grouping Name Command Class, version 1 O - - -

A.132 Hail Command Class, version 1 O - - -

A.133 HRV Status Command Class, version 1 O - - -

A.134 HRV Control Command Class, version 1 O - - -

A.135 Indicator Command Class, version 1 O - - -

A.136 IP Configuration Command Class, version 1 O - - -

A.137 Language Command Class, version 1 O - - -




Item Number


Certifi-cation

Verifi-cation

A.138 Lock Command Class, version 1 O - - -

A.139 Manufacturer Proprietary Command Class, version 1 Approved by Silicon Labs based on the “Proprietary Command Class Request Form” [5].

O - - -

A.140.1 Manufacturer Specific Command Class, version 1 R - - -

A.140.2 Manufacturer Specific Command Class, version 2 R - - -

A.141.1 Meter Command Class, version 1 O - - -



A.142 Meter Table Configuration Command Class, version 1 O - - -

A.143.1 Meter Table Monitor Command Class, version 1 O - - -

A.143.2 Meter Table Monitor Command Class, version 2 O - - -

A.144 Meter Table Push Configuration Command Class version 1 O - - -

A.145 Move To Position Window Covering Command Class, version 1 O - - -

A.146 Multi Channel Command Class, version 3 O - - -

A.147 Multi Channel Association Command Class, version 2 O - - -

A.148 Multi Command Command Class, version 1 O - - -

A.149 Multi Instance Association Command Class, version 1 Multi Channel Association Command Class version 2 must be used instead Discontinued

A.150 Multi Instance Command Class, version 1 Multi Channel Command Class version 3 must be used instead Discontinued

A.151.1 Multilevel Sensor Command Class, version 1 O - - -





A.152.1 Multilevel Switch Command Class, version 1 O - - -





Item Number


Certifi-cation

Verifi-cation


A.153 Multilevel Toggle Switch Command Class, version 1 O - - -

A.154 Network Management Basic Node Command Class, version 1 O - - -

A.155 Network Management Inclusion Command Class, version 1 O - - -

A.156 Network Management Primary Command Class, version 1 O - - -

A.157 Network Management Proxy Command Class, version 1 O - - -

A.158 No Operation Command Class, version 1 R - - -

A.159 Node Naming and Location Command Class, version 1 O - - -

A.160 Notification Command Class, version 3 O - - -

A.161 Powerlevel Command Class, version 1 O - - -

A.162 Prepayment Command Class, version 1 O - - -

A.163 Prepayment Encapsulation Command Class, version 1 O - - -

A.164 Proprietary Command Class, version 1 Approved by Silicon Labs based on the “Proprietary Command Class Request Form” [5].

O - - -

A.165.1 Protection Command Class, version 1 O - - -

A.165.2 Protection Command Class, version 2 O - - -

A.166 Pulse Meter Command Class, version 1 O - - -

A.167 Rate Table Configuration Command Class, version 1 O - - -

A.168 Rate Table Monitor Command Class, version 1 O - - -

A.169 Remote Association Activation Command Class, version 1 O - - -

A.170 Remote Association Configuration Command Class, version 1 O - - -

A.171 Scene Activation Command Class, version 1 O - - -

A.172 Scene Actuator Configuration Command Class, version 1 O - - -

A.173 Scene Controller Configuration Command Class, version 1 O - - -




Item Number


Certifi-cation

Verifi-cation

A.174 Schedule Command Class, version 1 O - - -

A.175.1 Schedule Entry Lock Command Class, version 1 O - - -

A.175.2 Schedule Entry Lock Command Class , version 2 O - - -

A.175.3 Schedule Entry Lock Command Class, Version 3 O - - -

A.176.1 Screen Attributes Command Class, version 1 O - - -

A.176.2 Screen Attributes Command Class, version 2 O - - -

A.177.1 Screen Meta Data Command Class, version 1 O - - -

A.177.2 Screen Meta Data Command Class, version 2 O - - -

A.178 Security Command Class, version 1 O - - -

A.179 Sensor Configuration Command Class, version 1 O - - -

A.180.1 Simple AV Control Command Class, version 1 O - - -




A.181 Tariff Table Configuration Command Class, version 1 O - - -

A.182 Tariff Table Monitor Command Class, version 1 O - - -

A.183.1 Thermostat Fan Mode Command Class, version 1 O - - -

A.183.2 Thermostat Fan Mode Command Class version 2 O - - -

A.183.3 Thermostat Fan Mode Command Class version 3 O - - -

A.184 Thermostat Fan State Command Class, version 1 O - - -

A.185.1 Thermostat Mode Command Class, version 1 O - - -

A.185.2 Thermostat Mode Command Class, version 2 O - - -

A.186.1 Thermostat Operating State Command Class, version 1 O - - -




Item Number


Certifi-cation

Verifi-cation

A.186.2 Thermostat Operating State Command Class, version 2 O - - -

A.187 Thermostat Setback Command Class, version 1 O - - -

A.188.1 Thermostat Setpoint Command Class, version 1 O - - -

A.188.2 Thermostat Setpoint Command Class, version 2 O - - -

A.189.1 Time Command Class, version 1 O - - -

A.189.2 Time Command Class, version 2 O - - -

A.190 Time Parameters Command Class, version 1 O - - -

A.191 Transport Service Command Class, version 1 O - - -

A.192 User Code Command Class, version 1 O - - -

A.193 Version Command Class, version 1 R - - -

A.194.1 Wake Up Command Class, version 1 O - - -

A.194.2 Wake Up Command Class, version 2 O - - -

A.195 Z/IP Command Class, version 1 O - - -

A.196 Z/IP-ND Command Class, version 1 O - - -




Item Number


Certifi-cation

Verifi-cation

A.500 Insert command class not found in this form here - - -










Notes:

1 May be superseded by the requirement status for the Command Classes given in the sections on Device Classes 2 OEM need to specify in which roles the Command Classes are supported

(“–“: Not supported; “C”: Control other devices; “S”: Support, i.e. be controlled; “C+S” Both Control and Support role) 3 Mandatory for devices to be supported (i.e. for Role = S)

Recommended for controllers to be able to control with (i.e. for Role = C) 4 It is recommended to use Association Version 2 in devices that support and/or control associations.




2.7.6 Controllers

2.7.6.1 Product Types

The following list extends the Product Type list in section 3.1.1.2 of the Device Class Specification with logical groupings of similar devices called “Home Control Groups”. The selections made here will be used to test minimal controller functionality.

A Controller must be classified as either a Dedicated Controller or a Universal Controller.

• Dedicated Controllers shall only control one Home Control Group and may control via the BasicCC in addition to other controlled command classes. A Dedicated Controller does not have toprovide control of “unknown” devices that have been included into the network.

• Universal Controllers are designed to control multiple Home Control Groups and must becapable of controlling via the Basic CC in addition to other controlled command classes. AUniversal Controller must provide via Basic CC, individual control of “unknown” devices that havebeen included into the network.

This device is designed to control the following Home Control Groups. All Product Types within a specific Home Control Group must be controlled. Any Home Control Group/Product Type not identified here must be recognized as an “unknown” device by the controller. Select all that apply.

HC1 - Door Lock

HC2 - Whole House Energy Meter

HC3 - Meter, Pulse Type

HC4 - Door/Window Sensor PIR/Occupancy Sensor

HC5 - Freeze Alarm Water Leak Sensor/Alarm

HC6 - Light Sensor Temperature Sensor

HC7 - Security Keypad

HC8 - Appliance Module Appliance Module w/Metering On/Off Switch Receptacle Switch, Plug-in

HC9 - Dimmer Dimmer, Plug-in Fan Control

HC10 - Shade/Shutter Control

HC11 - Thermostat

HC12 - Thermostat, Setback

2.7.6.2 Control of Preferred VS Non-Preferred Devices (Optional)

This controller implements a “preferred VS non-preferred” control functionality which provides enhanced control for preferred devices while still providing the required minimum control for all others within the same Home Control Group. Preferred brands/manufacturers must be listed below.

Note: Samples of preferred brands/devices are needed during testing. Please check with the selected test house to determine whether or not they already have samples or if you will need to provide them.




Example 1: Secure Keypad Door Locks. Minimal control includes Lock, Unlock and Check Status. Display of battery level is not required for all brands even if implemented for a preferred brand.

Example 2: Thermostats. Minimal Control includes Adjusting Mode and Setpoint. Reading and/or displaying the current temperature is not required for all brands even if implemented for a preferred brand.

Preferred Manufacturers/Brands:

2.7.6.3 Controller Compliance

Item Number


Certifi-cation

Verifi-cation

C.1 Functionality – All Controllers - This device complies with all mandatory requirements for its Generic and Specific Device Class

M C - -

C.1.1 All certified devices can be included into the DUT’s network. Spot checks will be performed by the test house M C - -

C.1.1.1 After inclusion, non-preferred devices are not forced out of the network (excluded) M C - -

C.1.2 Network Management functionality is included in the application/GUI MS.c.1 C - -

C.1.2.1 Network Management functions (inclusion, exclusion, replication, etc.) are password protected . Any combination is allowed. The password must be provided below for use during certification testing.

O C - -

C.1.2.1.1 Password enter password here n/a

C.1.2.2 Network Management functions are hidden from end user and only accessible to the owner of the device O C - -

C.1.3 This device/software provides a limited control application/GUI that does not include Network Management Functionality. MS.c.1 C - -

C.1.3.1 Network Management functionality is provided through a separate Z-Wave certified application/GUI. Details & certification number must be provided below.

M C - -

C.1.3.1.1 Application Details enter details here n//a C.1.3.1.1.1 Certification Number enter certification number here n/a

C.1.4 Devices from non-preferred manufacturers are placed in a special section of the user interface. (this section should be referred to as “Additional Z-Wave Ecosystem Devices”)

O C - -

C.1.5 The user is informed, upon inclusion of non-preferred devices, that the device being included is not part of the vendors preferred ecosystem, and that control and support of the device by the vendor may be limited.

O C - -

C.1.5.1

Wording similar to the following is used: “You are about to include a Z-Wave compatible device that is not promoted by ‘service provider name’ for use in this application. While the device should work as expected the device may or may not support all of the features of the ‘service provider name’ recommended device.”

M C - -




Item Number


Certifi-cation

Verifi-cation

C.1.5.1.1 A screen capture of the above dialog must be included with the certification submission. (standard image format) M n/a - -

C.1.5.2 The user can select if they wish to continue with inclusion of the non-preferred device or reverse the action (exclude after inclusion is completed). This warning is only permitted to be shown once during each inclusion.

O C - -

C.1.5.2.1 It is not permitted to display additional pop-ups, ask for pin codes or implement any other blocking or discouraging behavior for inclusion or control of non-preferred devices.

M C - -

C.2 This is a Dedicated Controller MS.c.1 C - - n/a

C.2.1 Minimum Controller Functionality as defined in the Device Class Specification[2] is implemented for the specific Home Control Group this device is designed to control. This is the minimum allowed.

M C - -

C.2.2 All Product Types within the designated Home Control Group must be supported with the functionality specified in the Minimum Controller Functionality section of the Device Class Specification [2].

M C - -

C.2.3

If a Preferred VS Non-Preferred control functionality is implemented for devices from various manufacturers, control of non-preferred devices must meet the Minimal Controller Functionality requirements as identified in the Device Class Specification [2].

M C - -

C.2.4 The controller recognizes all devices not included in the designated Home Control Group as “unknown” devices. M C - -

C.2.4.1 Unknown devices can be controlled via the Basic Set commands Off: 0x00 and On: 0xFF O C - -

C.3 This is a Universal Controller MS.c.1 C - - n/a

C.3.1 Minimum Controller Functionality as defined in the Device Class Specification[2] is implemented for all Home Control Groups this device is designed to control. This is the minimum allowed.

M C - -

C.3.2 All Product Types within the designated Home Control Groups must be supported with the functionality specified in the Minimum Controller Functionality section of the Device Class Specification[2].

M C - -

C.3.3

If a Preferred VS Non-Preferred control functionality is implemented for devices from various manufacturers, control of non-preferred devices must meet the Minimal Controller Functionality requirements as identified in the Device Class Specification [2].

M C - -

C.3.4 The controller recognizes all devices not included in the designated Home Control Groups as “unknown” devices. M C - -

C.3.4.1 Unknown devices can be individually controlled via the Basic Set commands Off: 0x00 and On: 0xFF M C - -




3 SELF-CERTIFICATION

The following self-certification must be provided by the party applying for Z-Wave Certification.

Product Name:

Product Number/Code:

Product Version:

Brand Name (Product is sold as)

Company:

Certification by (Name):

Title:

Additional Comments (Optional, e.g. to clarify items that deviate from Z-Wave compliance rules):

Item Number

Comment

Authorization to install and use software provided with the product If the product includes software that needs to be installed, we authorize the test partner and Silicon Labs to install the software and to use the software for Z-Wave certification purposes.

We hereby certify that we have followed the Z-Wave Certification rules; that we conducted the Self-certification tests for the above specified product

and reached the results documented in this form; and that the information provided in this Certification Form is accurate to the best of

our knowledge.

Signature:

Date:

IMPORTANT! This page must be signed and submitted electronically when submitting the entire word document. Submitting a scanned copy of this page via email is sufficient.




4 INITIAL CERTIFICATION REVIEW

Initial Certification Review - General comments & conditions:

Review comments to specific items of the Z-Wave Product Compliance Statement:

Item Number

Comment

Result of Initial Certification Review:

Passed

Passed Conditionally (see above for conditions)

Certification Form is forwarded to Test Partner Date:

Failed

OEM informed and Certification Form returned Date: (No Certification Fee will be invoiced)

Review performed by (Name):

Date:




5 VERIFICATION TEST

DUT (device under test) in verification test identified through:

Photo of DUT (optional)

Documentation of DUT (device under test) reviewed in verification test identified through:

Approval marks / logos: (not part of the Z-Wave certification; may be added after certification)

Device: UL FCC

CE

Z-Wave

Documentation: Z-Wave

Product packaging: Z-Wave

Device provided for testing without product packaging




Verification Test – General comments:

Verification Test results:

Initial Tests After Ad-hoc

Document review passed for all items

Document review failed for items listed

Test date:

Technical Test passed for all items

Technical Test failed for items listed

Test date:

Item Number

Initial Test Test after Ad-hoc Resolution Comment Result Comment Result

Verification Test by (Name):

Z-Wave Test Partner:




6 CERTIFICATION RESULT

Certification Result - Final remarks:

Certification result:

Product has passed Z-Wave Certification

Product has not passed Z-Wave Certification

Failed Document Review; 5 or fewer document issues (cert form or product document) – Ad Hoc review – must submit updated documents within ten days

Failed Document Review; 6 or more document issues (cert form or product document) – Must resubmit as new document review (new document review fee applies)

Technical Issues in up to 2 command classes or protocol items – Ad Hoc review – must resolve within 30 days

Technical Issues in 3-4 command classes or protocol items -- Fail - Current case closed, may resubmit as new case (new document fee and product recertification fee)

Technical Issues in 5 or more command classes or protocol items – Fail - Current case closed, may resubmit as new case (new document fee and new product certification fee)

Award of Z-Wave Logo for the certified product:

Signature page of certification form has been received as fax / original

Payment for Certification Fee has been received

Date:

Certificate of Compliance has been issued

Certification Number assigned:

Final Review

By:

Date:




APPENDIX A Z-WAVE CERTIFICATION PROGRAM All products that use the Z-Wave Technology and carry the Z-Wave logo must be certified. This includes embedded products, Z-Wave gateways or hardware interfaces, and also software products that incorporate the Z-Wave application protocol (i.e. the Z-Wave device & command classes).

The certification process is designed to help OEM customers ensure that products have been correctly and robustly implemented, in accordance with the requirements and criteria described in the Z-Wave device class specification and the Z-Wave certification form. These requirements are designed to ensure that the product will successfully interoperate with other certified Z-Wave products from the same and other vendors, for the same and other applications.

The certification process is in its core a “self-certification” process. The OEM is responsible for ensuring that products are designed and tested for compliance; typically conducted as and recommended to be part of the internal QA process. Furthermore, OEMs must ensure that their product’s certification remains valid over the lifecycle with any changes that may be made on the products.

For more details about the Z-Wave certification process refer to the Z-Wave Certification Overview [6].

Appendix A.1 Certification test areas

As a part of the Z-Wave certification process, the Z-Wave functionality which is declared as implemented in the certification form is to be verified by doing a number of self-certification and verification tests.

Please note that a Z-Wave product that implements a certain Z-Wave functionality in part or full, but where such functionality is not marked as supported in the corresponding section of the product’s Z-Wave certification form, is also in violation to Z-Wave compliance and would thus not pass Z-Wave certification.

The Z-Wave certification form is divided into a number of areas, each reflecting a class of requirements. Each self-certification and verification test case reflects one or several items in such a class. The purpose and contents of each of the classes are described below.

Appendix A.2 General Z-Wave compliance

The general Z-Wave compliance area contains a declaration from the OEM that the device has been designed in accordance with the Z-Wave device class specification. It furthermore outlines the very basic functionality of the device, such as ability to perform factory reset, whether the device is a listening device or not, if it contains ability to enter a production test mode etc. Most items in the general Z-Wave compliance area are review only items.

Appendix A.3 Product documentation

The purpose of the product documentation area is to ensure that the product documentation includes basic information to assure consumers can successfully utilize fundamental Z-Wave functionality of the product.

It further enforces common Z-Wave terminology for basic interactions such as ‘inclusion’ and ‘exclusion’ to be used in all Z-Wave product documentation. In addition to the terminology the documentation must also cover certain subjects in terms of an interoperability statement, and additional documentation for various command classes such as configuration and association.




Appendix A.4 Hardware

The purposes of the hardware area is to ensure that all devices that come to market meet a minimum level of RF performance such that they will operate properly in a mesh network configuration. The hardware area contains only simplistic RF tests which should be possible for most technical personal to perform.

The purpose of the hardware area is not to repeat FCC / CE tests or to perform RF quality testing.

Appendix A.5 Z-Wave network support

The purpose of the Z-Wave network support area is to ensure devices support basic device class functionality. For all devices this includes functionality such as the ability to be included and excluded from a network, and the ability to work as a repeater for other devices. For controllers this area will also include test of advanced controller functionality such as SUC/SIS implementation. Test cases for this area are mostly defined as step-by-step guides including one or many verification steps using the Z-Wave Zniffer network monitor.

Appendix A.6 Z-Wave application support

The Z-Wave application support area tests the application functionality of Z-Wave devices. This area includes tests of all command classes implemented in a device, and tests of special behavior related to the generic and specific device class of the device.

Z-Wave application support tests are mostly defined in the Z-Wave application test case specification language used by the Compliance Test Tool, CTT.

Appendix A.7 Z-Wave controller functionality

The controller functionality section identifies the type of controller being certified as well as the type of devices it is designed to control. It also identifies acceptable optional functionality such as treatment of preferred verses non-preferred devices in a service provider’s network and provides a way to verify compliance.




APPENDIX B TOOLS USED FOR TESTING One of the benefits of the Z-Wave certification process is that the OEM has access to the same tools as the authorized verification test lab. The tools are provided partly via the Z-Wave developer’s kit and by the Z-Wave Alliance.

This section will introduce the tools normally used for testing, and provide references to additional information and instructions about how to use the tools.

Appendix B.1 Tools used for hardware testing

The Enhanced Reliability Test Tool (ERTT) function included in the PC Controller can be used to perform the range testing and determine the CER%. Please refer to the Z-Wave Reliability Test Guideline [3] for information about testing reliability.

Appendix B.2 Tools used for Z-Wave network support testing

Testing supported network management features can be accomplished with modules and sample software from the Z-Wave developer kit. When a reference is made to sample software in the test specification, e.g. a LED dimmer, it means a Z-Wave module loaded with LED dimmer sample software.

An example network for Z-Wave network support testing will typically include a module connected to the PC Controller as the primary controller, a LED dimmer as an example slave device and a Z-Wave “Zniffer” network analyzer to monitor and verify the network traffic.

For more information about how to setup and use the tools mentioned, refer to “PC based Controller User Guide” (INS10240) and “Z-Wave Zniffer User Guide” (INS10249).

Appendix B.3 Tools used for Z-Wave application support testing

The Z-Wave application support is typically verified using the Z-Wave Compliance Test Tool (CTT). The Z-Wave Compliance Test Tool is provided as a membership benefit by the Z-Wave Alliance. The CTT is a Microsoft Windows based application that automates the testing of Z-Wave device and command classes.

Test scripts for new Device and Command Classes created by the Z-Wave community may not be included in the current CTT. These can be tested using an example network typically consisting of a PC Controller as the primary node, an LED dimmer as an example slave device and a Z-Wave “Zniffer” network analyzer to monitor and verify the network traffic.




REFERENCES

The last two digits of the document part number refer to the revision of the document. When the document revision is listed as “xx” please refer to the latest revision of the document.

[1] Silicon Labs, INS10682, Instruction, Z-Wave ZW0401 Appl. Prg. Guide v6.0x Silicon Labs, INS11110, Instruction, Z-Wave AV SD3402 Appl. Prg. Guide Silicon Labs, INS10247, Instruction, Z-Wave ZW0201/ZW0301 Appl. Prg. Guide v5.0x Silicon Labs, INS11095, Instruction, Z-Wave ZW0201/ZW0301 Appl. Prg. Guide v4.5x Silicon Labs, INS10690, Instruction, Z-Wave ZW0201/ZW0301 Appl. Prg. Guide v4.2x

[2] Silicon Labs, SDS10242, Software Design Specification, Z-Wave Device Class Specification Silicon Labs, SDS11060, Software Design Specification, Z-Wave Command Class Specification

[3] Silicon Labs, INS10336, Instruction, Z-Wave Reliability Test Guideline [4] [5] Silicon Labs, INS10479, Instruction, Proprietary Command Class Request Form

[6] Silicon Labs, INS10638, Instruction, Z-Wave Certification Overview

[7] Silicon Labs, SDS10865, Software Design Specification, Z-Wave Application Security Layer


http://www.silabs.com

Silicon Laboratories Inc.400 West Cesar ChavezAustin, TX 78701USA

Smart. Connected. Energy-Friendly.

Productswww.silabs.com/products

Qualitywww.silabs.com/quality

Support and Communitycommunity.silabs.com

DisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.

Trademark InformationSilicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, ISOmodem®, Micrium, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress®, Zentri, Z-Wave and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names mentioned herein are trademarks of their respective holders.

instruction - silicon labs · 2018-08-09 · hcs : item 13.4 . corrected specific device class to...

Documents