ZigBee Home Automation

Public Application Profile

1
2
3
4
5
6
7
8
9
10
11

ZIGBEE HOME AUTOMATION 12

13
14

PUBLIC APPLICATION PROFILE 15

16
17
18
Home Automation 19
Profile Specification 20
21
ZigBee Profile: 0x0104 22
Revision 25 23
Version 1.0 24
25
26
ZigBee Document 053520r25 27
28
October 25, 2007 12:36 pm
29
Sponsored by: ZigBee Alliance 30
Accepted by This document has been accepted for release by the ZigBee Alliance Board 31
of Directors. 32
33
Abstract This document defines the home automation profile.
34
Keywords ZigBee, Profile, Home Automation, Application Framework. 35
36
37
38
39
40
41
October 27, 2007 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile i

NOTICE OF USE AND DISCLOSURE 1

2
3
4
Copyright © ZigBee Alliance, Inc. (2007). All rights Reserved. The information within this
document is the property of the ZigBee Alliance and its use and disclosure are restricted. 5
6
Elements of ZigBee Alliance specifications may be subject to third party intellectual 7
property rights, including without limitation, patent, copyright or trademark rights (such a
third party may or may not be a member of ZigBee). ZigBee is not responsible and shall not 8
be held responsible in any manner for identifying or failing to identify any or all such third 9
party intellectual property rights. 10
This document and the information contained herein are provided on an “AS IS” basis and 11
ZigBee DISCLAIMS ALL WARRANTIES EXPRESS OR IMPLIED, INCLUDING BUT NOT 12
LIMITED TO (A) ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 13
WILL NOT INFRINGE ANY RIGHTS OF THIRD PARTIES (INCLUDING WITHOUT
LIMITATION ANY INTELLECTUAL PROPERTY RIGHTS INCLUDING PATENT, 14
COPYRIGHT OR TRADEMARK RIGHTS) OR (B) ANY IMPLIED WARRANTIES OF 15
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON- 16
INFRINGEMENT. IN NO EVENT WILL ZIGBEE BE LIABLE FOR ANY LOSS OF
PROFITS, LOSS OF BUSINESS, LOSS OF USE OF DATA, INTERRUPTION OF 17
BUSINESS, OR FOR ANY OTHER DIRECT, INDIRECT, SPECIAL OR EXEMPLARY, 18
INCIDENTIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES OF ANY KIND, IN 19
CONTRACT OR IN TORT, IN CONNECTION WITH THIS DOCUMENT OR THE
INFORMATION CONTAINED HEREIN, EVEN IF ADVISED OF THE POSSIBILITY OF 20
SUCH LOSS OR DAMAGE. All Company, brand and product names may be trademarks 21
that are the sole property of their respective owners. 22
The above notice and this paragraph must be included on all copies of this document that 23
are made. 24
25
ZigBee Alliance, Inc.
2400 Camino Ramon, Suite 375 26
San Ramon, CA 94583, USA 27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
ii Notice of Use and Disclosure

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile v

PARTICIPANTS 1
2
3
4
The following is a list of those who were members of the ZigBee Alliance 5
Application Framework Working Group leadership when this document was 6
released: 7
Phil Jamieson: Chair 8
9
Don Sturek: Editor-in-chief 10
Tim Gillman: Secretary 11
12
13
When the document was released, the Home Automation Profile Task Group 14
leadership was composed of the following members: 15
16
Walter Barnum: Chair of the Home Automation Profile Task Group 17
Mads Westergreen: Vice chair of the Home Automation Profile Task Group 18
19
Solène Quélard: Secretary 20
Contributions were made to this document by the following members: 21
22
Walter Barnum William Keith Phil Rudland 23
Peter Burnett Jens Klostergaard Lyngsø Zachary Smith 24
David Clark Jared Lemke Don Sturek 25
26
Kent Crouse Eetay Natan Mads Westergreen 27
Drew Gislason Isaac Pinhas Urban Wicklander 28
29
Tim Gillman Solène Quélard
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
vi Participants

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile vii

TABLE OF CONTENTS 1
2
3
4
Notice of Use and Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i 5
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii 6
7
Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v 8
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi 9
10
Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv 11
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 12
1.1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 13
14
1.2 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
15
Chapter 2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 16
2.1 ZigBee Alliance Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 17
2.2 European Standards Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 18
19
Chapter 3 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 20
3.1 Conformance Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 21
3.2 ZigBee Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 22
23
Chapter 4 Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . 7 24
Chapter 5 Profile Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 25
5.1 A ZigBee Home Automation Network . . . . . . . . . . . . . . . . . . . . . . 9 26
27
5.2 ZigBee Stack Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
28
5.2.1 ZigBee Routing Table Size Recommendations . . . . . . . . . . . 11 29
5.2.2 ZigBee HA Coordinator Recommendations . . . . . . . . . . . . . 11 30
5.3 Startup Attribute Set (SAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 31
5.3.1 Start Up Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 32
5.3.2 Join Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 33
34
5.3.3 Security Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
35
5.3.4 End Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 36
5.3.5 Link Status Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 37
5.3.6 Concentrator Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 38
5.3.7 APS Transport Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 14 39
5.3.8 Binding Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 40
41
5.4 ZDO Config for HA Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
42
5.5 Other HA Requirements and Best Practices . . . . . . . . . . . . . . . . . . 14 43
5.6 Device Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 1
viii

5.7 ZigBee Cluster Library (ZCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1
5.8 Cluster List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2
5.9 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3
5.9.1 Forming the Network (Start-up Sequence) . . . . . . . . . . . . . . 19 4
5.9.2 Support for Commissioning Modes . . . . . . . . . . . . . . . . . . . . 20 5
5.9.3 Commissioning Documentation . . . . . . . . . . . . . . . . . . . . . . 20 6
5.9.4 Group Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7
8
5.9.5 Group Messaging vs. Unicast Messaging . . . . . . . . . . . . . . . 23
9
Chapter 6 Constants, Error Codes and General Alarms . . . . . . . . 25 10
11
Chapter 7 Device Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12
7.1 Common Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 13
7.1.1 Optional Support for Clusters With Reporting Capability . . 30 14
7.1.2 Manufacturer-Specific Clusters . . . . . . . . . . . . . . . . . . . . . . . 30 15
7.1.3 Cluster Usage Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . 30 16
7.2 Feature and Function Description. . . . . . . . . . . . . . . . . . . . . . . . . . 30 17
18
7.3 Generic Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
19
7.3.1 On/Off Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 20
7.3.2 Level Control Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 21
7.3.3 On/Off Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 22
7.3.4 Level Controllable Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 23
7.3.5 Scene Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 24
25
7.3.6 Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
26
7.3.7 Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 27
7.3.8 Combined Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 28
7.3.9 Range Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 29
7.3.10 Mains Power Outlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 30
7.4 Lighting Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 31
32
7.4.1 On/Off Light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
33
7.4.2 Dimmable Light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 34
7.4.3 Color Dimmable Light. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 35
7.4.4 On/Off Light Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 36
7.4.5 Dimmer Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 37
7.4.6 Color Dimmer Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 38
39
7.4.7 Light Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
40
7.4.8 Occupancy Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 41
7.5 Closure Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 42
7.5.1 Shade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 43
7.5.2 Shade Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile ix

7.6 HVAC Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

1
7.6.1 Heating/Cooling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2
7.6.2 Thermostat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 3
7.6.3 Temperature Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4
7.6.4 Pump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 5
7.6.5 Pump Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 6
7.6.6 Pressure Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 7
8
7.6.7 Flow Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
9
7.7 Intruder Alarm System Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 10
7.7.1 IAS Control and Indicating Equipment (CIE) . . . . . . . . . . . . 77 11
7.7.2 IAS Ancillary Control Equipment (ACE) . . . . . . . . . . . . . . . 79 12
7.7.3 IAS Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 13
7.7.4 IAS Warning Device (WD) . . . . . . . . . . . . . . . . . . . . . . . . . . 82 14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 1
x

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile xi

LIST OF TABLES 1
2
3
4
Table 1.1 Document Revision Change History . . . . . . . . . . . . . . . . . xv 5
Table 5.1 Devices Specified in the HA Profile . . . . . . . . . . . . . . . . . 16 6
Table 5.2 Clusters Used in the HA Profile . . . . . . . . . . . . . . . . . . . . . 18 7
Table 5.3 Example Commissioning Documentation . . . . . . . . . . . . . 21 8
Table 6.1 Constants Specific to the HA Profile . . . . . . . . . . . . . . . . . 25 9
10
Table 7.1 Clusters Common to All Devices . . . . . . . . . . . . . . . . . . . . 29
11
Table 7.2 Example Features and Functions Configuration 12
for an HA Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 13
Table 7.3 Clusters Supported by the On/Off Switch Device . . . . . . . 33 14
Table 7.4 Example Features and Functions Supported by the On/Off 15
Switch Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 16
17
Table 7.5 Clusters Supported by the Level Control Switch Device . 34
18
Table 7.6 Example Features and Functions Supported by the 19
Level Control Switch Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 20
Table 7.7 Clusters Supported by the On/Off Output Device . . . . . . . 36 21
Table 7.8 Example Features and Functions Supported by the 22
On/Off Output Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 23
24
Table 7.9 Clusters Supported by the Level Controllable Output Device 37
25
Table 7.10 Example Features and Functions Supported by the 26
Level Controllable Output Device . . . . . . . . . . . . . . . . . . . . . . . . 38 27
Table 7.11 Clusters Supported by the Scene Selector Device . . . . . . 39 28
Table 7.12 Example Features and Functions Supported by the 29
Scene Selector Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 30
31
Table 7.13 Clusters Supported by the Configuration Tool Device . . 40
32
Table 7.14 Example Features and Functions Supported by the 33
Configuration Tool Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 34
Table 7.15 Clusters Supported by the Remote Control Device . . . . . 42 35
Table 7.16 Example Features and Functions Supported by the 36
Remote Control Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 37
38
Table 7.17 Clusters Supported by the Combined Interface Device . . 44
39
Table 7.18 Example Features and Functions Supported by the 40
Combined Interface Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 41
Table 7.19 Example Features and Functions Supported by the 42
Range Extender Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
xii List of Tables

Table 7.20 Clusters Supported by the Mains Power Outlet Device . . 47

1
Table 7.21 Example Features and Functions Supported by the
2
Mains Power Outlet Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 3
Table 7.22 Clusters Supported by the On/Off Light Device . . . . . . . 49 4
Table 7.23 Example Features and Functions Supported by the 5
On/Off Light Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 6
Table 7.24 Clusters Supported by the Dimmable Light Device . . . . 50 7
8
Table 7.25 Example Features and Functions Supported by the
9
Dimmable Light Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 10
Table 7.26 Clusters Supported by the Color Dimmable Light Device 52 11
Table 7.27 Example Features and Functions Supported by the 12
Color Dimmable Light Device . . . . . . . . . . . . . . . . . . . . . . . . . . 53 13
Table 7.28 Clusters Supported by the On/Off Light Switch . . . . . . . 54 14
15
Table 7.29 Example Features and Functions Supported by the
16
On/Off Light Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 17
Table 7.30 Clusters Supported by the Dimmer Switch Device . . . . . 55 18
Table 7.31 Example Features and Functions Supported by the 19
Dimmer Switch Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 20
Table 7.32 Clusters Supported by the Color Dimmer Switch Device 57 21
22
Table 7.33 Example Features and Functions Supported by the
23
Color Dimmer Switch Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 24
Table 7.34 Clusters Supported by the Light Sensor Device . . . . . . . 58 25
Table 7.35 Example Features and Functions Supported by the 26
Light Sensor Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 27
Table 7.36 Clusters Supported by the Occupancy Sensor Device . . . 60 28
29
Table 7.37 Example Features and Functions Supported by the
30
Occupancy Sensor Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 31
Table 7.38 Clusters Supported by the Shade Device . . . . . . . . . . . . . 61 32
Table 7.39 Example Features and Functions Supported by the 33
Shade Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 34
Table 7.40 Clusters Supported by the Shade Controller Device . . . . 63 35
36
Table 7.41 Example Features and Functions Supported by the
37
Shade Controller Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 38
Table 7.42 Clusters Supported by the Heating/Cooling Unit Device 65 39
Table 7.43 Example Features and Functions Supported by the 40
Heating/Cooling Unit Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 41
Table 7.44 Clusters Supported by the Thermostat Device . . . . . . . . . 66 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile xiii

Table 7.45 Example Features and Functions Supported by the

1
Thermostat Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2
Table 7.46 Clusters Supported by the Temperature Sensor Device . . 69 3
Table 7.47 Example Features and Functions Supported by the 4
Temperature Sensor Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 5
Table 7.48 Clusters Supported by the Pump Device . . . . . . . . . . . . . 70 6
Table 7.49 Pump Actions on Receipt for On/Off Commands . . . . . . 71 7
8
Table 7.50 Relationship Between Level and Setpoint . . . . . . . . . . . . 71
9
Table 7.51 Example Features and Functions Supported by 10
the Pump Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 11
Table 7.52 Clusters Supported by the Pump Controller Device . . . . 73 12
Table 7.53 Example Features and Functions Supported by the 13
Pump Controller Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 14
15
Table 7.54 Clusters Supported by the Pressure Sensor Device . . . . . 75
16
Table 7.55 Example Features and Functions Supported by the 17
Pressure Sensor Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 18
Table 7.56 Clusters Supported by the Flow Sensor Device . . . . . . . . 76 19
Table 7.57 Example Features and Functions Supported by the 20
Flow Sensor Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 21
22
Table 7.58 Clusters Supported by the IAS CIE Device . . . . . . . . . . . 77
23
Table 7.59 Example Features and Functions Supported by 24
the IAS CIE Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 25
Table 7.60 Clusters Supported by the IAS ACE Device . . . . . . . . . . 79 26
Table 7.61 Example Features and Functions Supported by 27
the IAS ACE Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 28
29
Table 7.62 Clusters Supported by the IAS Zone Device . . . . . . . . . . 81
30
Table 7.63 Example Features and Functions Supported by 31
the IAS Zone Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 32
Table 7.64 Clusters Supported by the IAS WD . . . . . . . . . . . . . . . . . 82 33
Table 7.65 Example Features and Functions Supported by 34
the IAS WD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
xiv List of Tables

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile xv

DOCUMENT HISTORY 1
2
3
4
Table 1.1 shows the change history for this specification. 5
Table 1.1 Document Revision Change History 6
7
Revision Version Description
8
0 0.1 Original version. 9
10
1 0.1 Store scene command added to general cluster. 11
2 0.1 Group Identifier and Vendor Identifier fields added 12
into the general frame format to harmonize with 13
CBA. ThermostatControl cluster and Thermostat 14
device description added. Many editorial fixes. 15
16
3 0.3 Added clusters for ThermostatUnit, TempSensor, 17
BinaryInput, BinaryOutput, PumpControl. Many 18
editorial changes. 19
4 0.4 Moved all the cluster specifications to library files. 20
Streamlined the rest of the document accordingly. 21
22
5, 6 0.4 Added space heating / cooling devices. 23
7 0.4 Added remote control and range extender. Many 24
minor editorial changes. 25
26
8 0.4 Added mains power outlet. 27
9 0.4 Added constants, generic device, generic 28
switchable device, generic level controllable 29
device, configuration device and scene selection 30
31
device. Streamlined cluster descriptions. Many
32
editorial improvements.
33
10, 11, 12 0.5 Made changes to resolve comments from LB9. 34
13 0.5 Final changes to resolve comments from LB9. 35
36
Specifically, text was added for polling rates,
37
reporting, commissioning and modifications due to
38
changes in the ZCL. 39
14 0.5 A couple more final adjustments. 40
41
15 0.6 Changes made due to initial comment resolution
42
for LB13.
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
xvi Document History

Table 1.1 Document Revision Change History (Continued)

1
Revision Version Description 2
3
16 0.6 Final changes due to comment resolution. Profile is
4
ready for testing.
5
17 0.7 Added text to specify mandatory start up settings 6
and commissioning behaviors. 7
8
18 0.7 Added text to specify mandatory and optional
9
features and functions per device type.
10
19-24 0.7-0.9 Added text reflecting changes from Paris 2007 11
meeting to ensure interoperability between HA 12
profile devices. 13
14
25 1.0 Editorial changes for release.
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 1

C H A P T E R
1

1
2
3
4
5
6
7
8
9

CHAPTER 1INTRODUCTION 10
11
12
13
1.1 Scope 14
15
This profile defines device descriptions and standard practices for applications 16
needed in a residential or light commercial environment. Installation scenarios 17
range from a single room to an entire home up to 20,000 square feet 18
(approximately 1850m2). The key application domains included in this initial 19
version are lighting, HVAC, window shades and security. Other applications will 20
be added in future versions. 21
22
23
1.2 Purpose 24
25
26
This specification provides standard interfaces and device definitions to allow
27
interoperability among ZigBee devices produced by various manufacturers of
28
home automation products.
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 1
2 Introduction

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 3

C H A P T E R
1

2
2
3
4
5
6
7
8
9

CHAPTER 2REFERENCES 10
11
12
13
The following standards and specifications contain provisions, which through 14
reference in this document constitute provisions of this specification. All the 15
standards and specifications listed are normative references. At the time of 16
publication, the editions indicated were valid. All standards and specifications are 17
subject to revision, and parties to agreements based on this specification are 18
encouraged to investigate the possibility of applying the most recent editions of 19
the standards and specifications indicated below. 20
21
22
2.1 ZigBee Alliance Documents 23
24
[R1] ZigBee document 064321r01, ZigBee Stack Profile 25
26
[R2] ZigBee document 053936r04, ZigBee Cluster Library, Functional
27
Domain: General, ZigBee Application Framework Working Group
28
[R3] ZigBee document 053906r04, ZigBee Cluster Library, Functional 29
Domain: Measurement and Sensing, ZigBee Application Framework Working 30
Group 31
32
[R4] ZigBee document 053990r04, ZigBee Cluster Library, Functional
33
Domain: Lighting, ZigBee Application Framework Working Group
34
[R5] ZigBee document 06023r05, ZigBee Cluster Library, Functional Domain: 35
Closures, ZigBee Application Framework Working Group 36
37
[R6] ZigBee document 06024r05, ZigBee Cluster Library, Functional Domain:
38
Security and Safety, ZigBee Application Framework Working Group
39
[R7] ZigBee document 06014r06, ZigBee Cluster Library, Functional Domain: 40
HVAC, ZigBee Application Framework Working Group 41
42
[R8] ZigBee document 06027r04, ZigBee Cluster Library, Foundation, ZigBee
43
Application Framework Working Group
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 2
4 References

[R9] ZigBee document 064309r02, Commissioning Framework

1
2
2.2 European Standards Documents 3
4
[R10] EN 50131 European Standards Series for Intruder Alarm Systems 5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 5

C H A P T E R
1

3
2
3
4
5
6
7
8
9

CHAPTER 3DEFINITIONS 10
11
12
13
3.1 Conformance Levels 14
15
Expected: A key word used to describe the behavior of the hardware or software 16
in the design models assumed by this Draft. Other hardware and software design 17
models may also be implemented. 18
19
May: A key word indicating a course of action permissible within the limits of the 20
standard (“may” equals “is permitted”). 21
Shall: A key word indicating mandatory requirements to be strictly followed in 22
order to conform to the standard; deviations from shall are prohibited (“shall” 23
equals “is required to”). 24
25
Should: A key word indicating that, among several possibilities, one is 26
recommended as particularly suitable, without mentioning or excluding others; 27
that a certain course of action is preferred but not necessarily required; or, that (in 28
the negative form) a certain course of action is deprecated but not prohibited 29
(“should” equals “is recommended that”). 30
31
32
3.2 ZigBee Definitions 33
34
Attribute: A data entity which represents a physical quantity or state. This data is 35
communicated to other devices using commands. 36
37
Cluster: A container for one or more attributes and/or messages in a command
38
structure.
39
Cluster identifier: A reference to the unique enumeration of clusters within a 40
specific application profile. The cluster identifier is a 16-bit number unique within 41
the scope of the application profile and identifies a specific cluster. Cluster 42
identifiers are designated as inputs or outputs in the simple descriptor for use in 43
creating a binding table. 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 3
6 Definitions

Device: A description of a specific device within an application profile. For

example, the light sensor device description is a member of the home automation 1
application profile. The device description also has a unique identifier that is 2
exchanged as part of the discovery process. 3
4
Node: Same as a unit. 5
Product: A product is a unit that is intended to be marketed. It implements 6
application profiles that may be a combination of private, published, and standard. 7
8
Service discovery: The ability of a device to locate services of interest. 9
Unit: A unit consists of one or more physical objects (e.g., switch, controller, etc.) 10
and their corresponding application profile(s) that share a single 802.15.4 radio. 11
Each unit has a unique 64-bit IEEE address. 12
13
ZigBee coordinator: An IEEE 802.15.4-2003 PAN coordinator. 14
ZigBee end device: an IEEE 802.15.4-2003 RFD or FFD participating in a 15
ZigBee network, which is neither the ZigBee coordinator nor a ZigBee router. 16
17
ZigBee router: an IEEE 802.15.4-2003 FFD participating in a ZigBee network, 18
which is not the ZigBee coordinator but may act as an IEEE 802.15.4-2003 19
coordinator within its personal operating space, that is capable of routing 20
messages between devices and supporting associations. 21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 7

C H A P T E R
1

4
2
3
4
5
6
7
8
9

CHAPTER 4ACRONYMS AND ABBREVIATIONS 10

11
12
13
14
15
ACE Ancillary Control Equipment
16
APS Application Support Sub-layer 17
CIE Control and Indicating Equipment 18
19
HA Home Automation
20
IAS Intruder Alarm Systems 21
WD Warning Device 22
23
ZCL ZigBee Cluster Library 24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 4
8 Acronyms and Abbreviations

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 9

C H A P T E R
1

5
2
3
4
5
6
7
8
9

CHAPTER 5PROFILE DESCRIPTION 10

11
12
13
5.1 A ZigBee Home Automation Network 14
15
Home Automation (HA) networks scale from 2 to 500 nodes. Real world 16
experience suggests that use events and interactions become sluggish as the 500- 17
node limit is approached. HA networks are primarily installed by either home 18
owners, or home automation professionals that may not have any ZigBee 19
expertise. Installation concepts must be easy and uniform across multiple OEM 20
vendors. 21
22
A ZigBee Home Automation system is primarily focused on sporadic real time 23
control of devices, that is, the network is normally quiet, but when a user presses a 24
button on a device, he expects to see the result of that button press across the 25
network quickly. 26
HA Networks could include nodes based on the ZigBee Feature Set or the ZigBee 27
PRO Feature Set. It is recommended that the ratio of the nodes should not be 50/ 28
50, but the majority of the nodes in the network should be based on one Feature 29
Set or the other to get consistent performance. 30
31
Not all products in an OEM home automation system need be “ZigBee HA 32
Certified”, though it is recommended that they all be MSP (Manufacturer Specific 33
Profile) certified. For example, system controllers and remote controls tend to be 34
very OEM system-specific and provide the OEM value. Lighting devices and 35
sensors could be mix and match from multiple vendors. The normal customer 36
experience is that the customer will buy a home automation system based on a 37
single OEM’s ZigBee home automation products and then addend the system with 38
a smaller number of ZigBee home automation products from other vendors. 39
ZigBee HA certified products also must be MSP certified. This provides a 40
reassurance that the underlying golden stack is behaving properly and the 41
application is not abusive to the network. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
10 Profile Description

Though encouraged, ZigBee HA products do not require the support of the

ZigBee commissioning cluster. They all are required to support “E-mode” 1
commissioning. E-mode commissioning would classically involve a button push 2
or two, but could also use an OEM-provided simple tool, such as a remote control. 3
4
No assurances can be made that a ZigBee HA system will interoperate at all with 5
other ZigBee devices, even if they are ZigBee certified under other application 6
profile tests. This is because the other devices may have stack and security 7
settings that are incompatible with the HA application profile, or that their 8
commissioning procedure requires tools that are unavailable to the HA installer. 9
A ZigBee HA makes possible networks such as the following: 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Figure 5.1 Home network enabled by ZigBee HA 30
31
The lights and switches might be controlled wirelessly through ZigBee, as well as 32
blinds, the thermostat and other devices. Using the scene mechanism, what is now 33
a very advanced home theatre system may be implemented with relatively low- 34
cost devices. A single press of a button on the remote control could dim the lights, 35
lower the blinds, turn on the television and begin playing a movie in the DVD 36
player. Another button press, either on the remote or a specific switch within the 37
home could place the home in the “I’m at work” mode, lowering the air- 38
conditioner or heating in all rooms except the atrium, and turning off all lights in 39
the home once motion is no longer detected. The television or PC might provide 40
easy configuration and access to the ZigBee network, and a WiFi router might 41
provide internet access to ZigBee as well. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 11

5.2 ZigBee Stack Profile 1

2
Products that conform to this specification shall use stack profile number 0x01 or 3
profile 0x02, as defined in [R1]. In addition to the requirements specified in [R1], 4
the following requirements are mandatory for this application profile. 5
• Source binding and groups/scenes shall be implemented on a device type basis, 6
see device descriptions for applicability. 7
8
• In their normal operating state, ZigBee end devices shall poll no more 9
frequently than once every 7.5 seconds except where this specification 10
indicates otherwise for a particular device description (e.g., the IAS WD), or 11
under the following conditions. ZigBee end devices may operate with a higher 12
polling rate during commissioning, network maintenance, alarm states, and for 13
short periods after transmitting a message to allow for acknowledgements and 14
or responses to be received quickly, but they must return to the standard rate 15
indicated previously during normal operation. It is recommended that ZigBee 16
end devices poll much less frequently than once per 7.5 seconds, especially 17
when the device normally only communicates due to user interaction (e.g. the 18
On/Off Light Switch). 19
20
5.2.1 ZigBee Routing Table Size Recommendations 21
22
If a HA device is intended to be primarily deployed in a network that does not 23
support many-to-one routing, its routing table size should be increased as much as 24
possible to account for the typically dense topology of a ZigBee HA deployment. 25
Alternatively, it is recommended that devices that will primarily be installed into 26
many-to-one deployments also increase their own routing tables if possible, in 27
case the devices are deployed in networks that use AODV routing for the majority 28
of their messaging, though this may be of secondary concern. 29
30
31
5.2.2 ZigBee HA Coordinator Recommendations 32
33
The coordinator should indicate to the installer when a new device joins the 34
network. This could be via PC client, LCD screen, or other simple LED 35
indication. 36
37
38
5.3 Startup Attribute Set (SAS) 39
40
In order to insure interoperability, all ZigBee HA devices should implement 41
compatible Startup Attribute Sets (SAS). This does not mean that set must be 42
modifiable through a commissioning cluster, but that the device must internally 43
implement these stack settings to insure compatibility and consistent user 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
12 Profile Description

experience. The start up set parameters described by the commissioning cluster

provide a good basis to specify a HA startup set. 1
2
3
5.3.1 Start Up Parameters 4
5
Short Address: 0xFFFF 6
E PANiD: 0x0000000000000000 7
PAN ID: 0xFFFF 8
Channel Mask: All channels in frequency band. If needed, the power transmitted 9
by the device on channel 26 can be lowered to comply with FCC regulations. 10
11
Protocol Version: 0x02 (2006 and later). 12
Stack Profile: 1 (2006) or 2 (2007). 13
14
Startup Control: 15
3 (three) if un-commissioned, so it will join network by association when join 16
command is indicated by button press sequence. 17
0 (Zero) if commissioned. Indicates that the device should consider itself a part of 18
the network indicated by the ExtendedPANId attribute. In this case it will not 19
perform any explicit join or rejoin operation. 20
21
Trust Center Address: 0x0000. 22
Master Key: NULL (This only applies to 2007 stack profile devices). 23
24
Network Key: NULL. 25
Use Insecure Join: 0x01 (True). This flag enables the use of insecure join as a 26
fallback case at startup time. (This only applies to 2007 stack profile devices). 27
28
29
5.3.2 Join Parameters 30
31
ScanAttempts: At boot time or when instructed to join a network, the device 32
should make up to three (3) scan attempts to find a ZigBee Coordinator or Router 33
to associate with. If it has not been commissioned, this means that when the user 34
presses a button or uses another methodology to get it to join a network, it will 35
scan through all of the channels up to three times to find a network that allows 36
joining. If it has already been commissioned, it should scan up to three times to 37
find its old PAN to join. (2007 devices should scan for their old extended PAN ID 38
and 2006 devices can only scan for their old PAN ID). 39
TimeBetweenScans: (1 second) Determines the number of seconds between each 40
unsuccessful scan attempt 41
42
RejoinInterval: (60 seconds or shorter) Is how soon a device will attempt to 43
rejoin the network if it finds itself disconnected. 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 13

MaxRejoinInterval: (15 minutes) Imposes an upper bound on the RejoinInterval

parameter. This interval must be restarted if the device is touched by a human 1
user, i.e. by a button press. This parameter is intended to throttle how often a 2
device will scan to find its network in case the network is no longer present and 3
therefore a scan attempt by the device would always fail, i.e., if a device finds 4
itself disconnected, it will try to rejoin the network, scanning all channels if 5
necessary. If the scan fails to find the network, or fails to successfully rejoin, the 6
device will wait for 15 minutes before attempting to rejoin again. 7
8
9
5.3.3 Security Parameters 10
11
SecurityTimeoutPeriod: Determined by the stack profile. 12
TrustCenterNetworkKey: The Trust Center will pick the network key. ZigBee 13
HA devices shall not depend on pre-configured keys to be commissioned or to 14
interoperate. 15
16
17
5.3.4 End Device Parameters 18
19
IndirectPollRate: Set by stack profile. This is how often a device will poll its 20
parent for new data. It is recommended that an end device designed to receive data 21
should poll its parent every 60 seconds. 22
23
5.3.5 Link Status Parameters 24
25
LinkStatusPeriod: Set by the stack profile. 26
27
RouterAgeLimit: Set by the stack profile. 28
RepairThreshold: Set by the stack profile. 29
30
UpdatedDevice: Set by the stack profile. 31
UpdatedDeviceAlarmMask: Set by the stack profile. 32
33
34
5.3.6 Concentrator Parameters 35
36
ConcentratorFlag: Configures the device to be a concentrator. This would be 37
typically part of an OEM “system controller” and not required to be on a HA 38
certified device or configurable by 3rd party tool. If an OEM does make a device 39
that can be a concentrator, it does not have to be configurable in any standardized 40
way. 41
ConcentratorRadius: 5 (five). OEMs that make a concentrator product will set 42
the max concentrator radius to this value. 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
14 Profile Description

ConcentratorDiscoveryTime: Set by the stack profile. Indicates how soon nodes

should reply to a concentrator after hearing a route request command. 1
2
3
5.3.7 APS Transport Parameters 4
5
MaxFrameRetries: Set by stack profile. This determines the maximum number 6
of retries allowed after a transmission failure. 7
AckWaitDuration: Set by stack profile. This is the maximum number of seconds 8
to wait for acknowledgement of an APS frame. 9
10
11
5.3.8 Binding Parameters 12
13
EndDeviceBindTimeout: 60 seconds. This is the timeout value for end device 14
binding. End device binding is set by coordinator. 15
16
17
5.4 ZDO Config for HA Devices 18
19
ZDO messages relating to binding are either mandatory or optional based on a 20
device-by-device basis. See the device description sections for details on each 21
device and which ZDO messages that each must support. 22
23
24
5.5 Other HA Requirements and Best Practices 25
26
Preferred Channels (11, 14, 15, 19, 20, 24, 25) 27
When forming a new network, or scanning to join a network, HA devices should 28
do channel scans using the above channel mask before scanning the rest of the 29
channels in order to avoid the most commonly used WiFi channels. This is to 30
improve the user experience during installation (quicker joining) and possibly 31
improve bandwidth (on average). 32
Broadcast Policy 33
Broadcasts are to be strongly discouraged for HA devices, except for when 34
invoking scenes. 35
36
Devices are limited to a maximum broadcast frequency of one broadcast per 37
second and strongly encouraged to exercise broadcasts much less frequently. 38
Frequency Agility 39
Frequency Agility would only be officially exercised in a 2007 based network by 40
an OEM system controller, or higher functioning device (system remote etc.). 41
42
• 2007 devices must support frequency agility hooks to be commanded to “go to 43
channel X”. 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 15

• 2006 end devices in a 2007 based network must implement the 2006 orphan
join feature so that they will find a 2007 network that has changed channels. 1
2
Key Updates 3
HA devices are only required to support 2006 “residential mode” security or 2007 4
“standard mode”. 5
Network key updates should be limited due to the possibility of end devices 6
missing two key updates. 7
8
It is strongly encouraged that key updates should only be initiated by the user via 9
interaction with the Trust Center. Auto updates of security keys poses the risk that 10
battery operated devices will miss two key updates and need to be re- 11
commissioned. 12
Return to Factory Defaults 13
In support of a return to factory default capability, HA devices shall implement 14
the ZDO Management Leave server service. When invoked with a unicast address 15
and the DeviceAddress set to NULL=0x00000000, the device shall implement a 16
NWK Leave. When invoked with a broadcast address and the DeviceAddress set 17
to NULL=0x00000000, the device shall wait the broadcast timeout period to 18
allow the message to propagate through network, then the device shall implement 19
a NWK Leave. Prior to execution of the NWK Leave in either case, processing in 20
the device shall ensure all operating parameters are reset to allow a reset to factory 21
defaults. 22
23
24
5.6 Device Descriptions 25
26
Device descriptions specified in this profile are summarized in Table 5.1, 27
“Devices Specified in the HA Profile”. The devices are organized according the 28
end application areas they address. A product that conforms to this specification 29
shall implement at least one of these device descriptions and shall also include the 30
device descriptions corresponding to all applications implemented on the product 31
where a standard device description is specified in this profile. For example, if a 32
product implements both a light dimmer and a light sensor application, then the 33
Dimmable Light and Light Sensor device descriptions must both be supported. 34
35
This list will be added to in future versions of the profile as new clusters are 36
developed to meet the needs of manufacturers. The reserved values shall not be 37
used until the profile defines them. Manufacturer-specific device descriptions 38
shall reside on a separate endpoint and use a private profile ID. 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
16 Profile Description

Table 5.1 Devices Specified in the HA Profile 1

Device Device ID 2
3
On/Off Switch 0x0000 4
Level Control Switch 0x0001 5
6
On/Off Output 0x0002
7
Level Controllable Output 0x0003 8
Scene Selector 0x0004 9
10
Generic

Configuration Tool 0x0005 11

Remote Control 0x0006 12
Combined Interface 0x0007
13
14
Range Extender 0x0008 15
Mains Power Outlet 0x0009 16
17
Reserved 0x000A – 0x00FF
18
On/Off Light 0x0100 19
Dimmable Light 0x0101 20
21
Color Dimmable Light 0x0102
22
On/Off Light Switch 0x0103 23
Lighting

Dimmer Switch 0x0104 24

25
Color Dimmer Switch 0x0105 26
Light Sensor 0x0106 27
Occupancy Sensor 0x0107 28
29
Reserved 0x0108 – 0x1FF 30
Shade 0x0200 31
Closures

32
Shade Controller 0x0201
33
Reserved 0x0202 – 0x2FF 34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 17

Table 5.1 Devices Specified in the HA Profile (Continued)

1
Heating/Cooling Unit 0x0300
2
Thermostat 0x0301 3
Temperature Sensor 0x0302 4
5
Pump 0x0303 6
Pump Controller 0x0304 7
Pressure Sensor 0x0305 8
9
HVAC

Flow Sensor 0x0306 10

Reserved 0x0307 - 0x3FF 11
12
IAS Control and Indicating Equipment 0x0400
13
Intruder Alarm

IAS Ancillary Control Equipment 0x0401 14

IAS Zone 0x0402 15
16
Systems

IAS Warning Device 0x0403

17
Reserved 0x0404-0xFFFF 18
19
20
5.7 ZigBee Cluster Library (ZCL) 21
22
This profile utilizes the clusters specified in the ZigBee Cluster Library. The 23
implementation details for each cluster are given in the ZCL specifications. 24
Further specification and clarification are given in this profile where necessary. 25
26
The ZCL provides a mechanism for clusters to report changes to the value of 27
various attributes. It also provides commands to configure the reporting 28
parameters. The attributes that a particular cluster is capable of reporting are listed 29
in the ZCL specification for each cluster. Products shall support the reporting 30
mechanism for all attributes specified in the ZCL that the product implements 31
within a given cluster. The minimum reporting interval specified in [R8] shall be 32
set to a value greater than or equal to 0x0001. The maximum reporting interval 33
should be set to 0x0000 by default, and if it is set to a non-zero value it shall be set 34
to a value greater than or equal to 0x003C and greater than the value of the 35
minimum reporting interval. These settings will restrict the attributes from being 36
reported more often than once every second if the attribute is changing quickly 37
and at least once every minute if the attribute does not change for a long time. It is 38
recommended that the minimum reporting interval be set to a higher value 39
whenever the application can tolerate it. It is recommended that the maximum 40
reporting interval be set to a much greater value to avoid unnecessary traffic. 41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
18 Profile Description

5.8 Cluster List 1

2
The clusters used in this profile are listed in Table 5.2. The clusters are listed 3
according the functional domain they belong to in the ZCL. The corresponding 4
cluster identifiers can be found in the ZCL Foundation specification [R8]. 5
The functionality made available by all supported clusters shall be that given in 6
their ZCL specifications except where a device description in this profile includes 7
further specification, clarification or restriction as needed for that particular 8
device. 9
10
Most clusters include optional attributes. The application designer must be aware 11
that optional attributes may not be implemented on a particular device. It is the 12
responsibility of a device’s application to discover and deal with unsupported 13
attributes on other devices. 14
It is expected that clusters will continue to be developed in the ZCL that will be 15
useful in this profile. In many cases, new clusters will be organized into new 16
device descriptions that are separate from those currently defined. There may also 17
be situations where it makes sense to add clusters as optional or possibly even 18
mandatory elements of existing device descriptions. Creating new device 19
descriptions is the preferred method of adding new clusters to this specification, 20
because new functionality can be mandated in a new device description without 21
causing compatibility issues with previously-defined devices. 22
23
Manufacturer-specific clusters may be added to any device description in this 24
profile as long as they follow the specifications given in the ZCL Foundation 25
specification [R8]. 26
Table 5.2 Clusters Used in the HA Profile 27
28
Functional Domain Cluster Name 29
General Basic 30
31
General Power Configuration
32
General Device Temperature Configuration 33
General Identify 34
35
General Groups
36
General Scenes 37
General On/Off 38
39
General On/Off Switch Configuration 40
General Level control 41
General Alarms
42
43
Measurement & Sensing I luminance Measurement 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 19

Table 5.2 Clusters Used in the HA Profile (Continued)

1
Measurement & Sensing I luminance Level Sensing
2
Measurement & Sensing Temperature Measurement 3
Measurement & Sensing Pressure Measurement 4
5
Measurement & Sensing Flow Measurement 6
Measurement & Sensing Relative Humidity Measurement 7
Measurement & Sensing Occupancy sensing 8
9
Lighting Color Control 10
HVAC Pump Configuration and Control 11
12
HVAC Thermostat
13
HVAC Fan Control 14
HVAC Thermostat User Interface Configuration 15
16
Closures Shade Configuration
17
Security and Safety IAS ACE 18
Security and Safety IAS Zone 19
20
Security and Safety IAS WD
21
22
23
5.9 Commissioning 24
25
Many, if not all of the devices described in this document will require some form 26
of commissioning, even if the user or installer doesn’t see it. This is because, for 27
example, an actuating device needs to be bound to some sort of target in order to 28
do useful work, and even if the required initializations are done at the factory 29
before the device is sold, the required operations are virtually the same as is the 30
outcome. 31
The ZigBee Alliance has recognized the importance of commissioning and, in 32
particular, the importance of specifications for commissioning in a multi-vendor 33
environment. Thus, commissioning procedures are being designed outside the 34
context of any particular profile, where possible, and grouped under the auspices 35
of the Commissioning Tools Task Group (CTTG). This task group is developing a 36
commissioning framework specification [R9]. 37
38
39
5.9.1 Forming the Network (Start-up Sequence) 40
41
HA devices must form their own network or join an existing network. The 42
commissioning framework [R9] discusses some of the relevant issues in this 43
procedure. 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
20 Profile Description

It is intended that an HA network use simple methods to form a network and to

commission devices into it. The primary means of commissioning a network will 1
use E-mode methods (button presses or similar user actions) to get nodes to join a 2
network. 3
4
This specification has no mandates to the start-up sequence of devices or the 5
network, however, there are some recommended practices: 6
• A device should be able to indicate to the user that it has decided to become the 7
coordinator of a network. 8
9
• A device should be able to indicate to the user, that it has successfully joined a 10
network. 11
• A device should be able to indicate to the user, that it is in the process of 12
searching for or joining a network. 13
14
These indications can be implemented in a number of ways including blinking 15
indicator lights, colored indicator lights, arrays of indicator lights, text displays, 16
graphic displays, audible indicators such as buzzers and speakers, etc. Blinking a 17
green indicator light is the recommended method. 18
19
5.9.2 Support for Commissioning Modes 20
21
Three different commissioning modes are discussed in [R9]. They are denoted A, 22
E and S-mode. All HA devices must support E-mode and may optionally support 23
S-mode. A-mode is not to be supported. E-mode commissioning may be a simple 24
button press or may involve a separate low-cost commissioning tool (like a remote 25
control) that is typically purchased with the vendor’s HA product. 26
27
28
5.9.3 Commissioning Documentation 29
30
To ensure a uniform user experience when commissioning HA devices, all ZigBee 31
HA devices are required to provide documentation with their product that explains 32
how to perform device commissioning in using a common language set, i.e., 33
“form network”, “join network”, etc. The following table is representative of what 34
should be included in the product documentation and also shows the common 35
language to be used. Note that some items are not required to be supported by the 36
device, but if not supported, should be indicated as such in the table. Using a 37
common language set among all HA devices will make it intuitive for a user to 38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 21

install a new device into an existing network, even if the new device is
manufactured by a different OEM than the devices in the existing network. 1
2
Table 5.3 Example Commissioning Documentation
3
ZigBee Action What To Do To Device To Perform Action 4
5
Join Network Press the red button four times. 6
Form Network Press the green button four times. 7
Allow Others To Join Network Hold the red button and press the green button four times. 8
9
Restore Factory Fresh Settings Hold the red and green buttons down simultaneously for 10
15 seconds.
11
Pair Devices Press the red button five times, followed by the green 12
button five times. 13
Enable Identify Mode Press the red button six times, followed by the green 14
button six times. 15
Create Scene Not supported. 16
17
18
Chapter 7, “Device Specifications”, lists which commissioning actions are 19
mandatory or optional on each HA device. The following section describes each 20
action: 21
Join Network: Go find and join the first available HA network. 22
23
Form Network: For devices that can start a network. 24
Allow Others to Join Network: For routers and coordinators only. Allows you 25
can add more nodes to an existing network. This must have a mandatory timeout 26
of 60 seconds. 27
28
Restore to Factory Fresh Settings: Restore the device settings to fresh state (also 29
performs leave). 30
Pair Devices (End Device Bind Request): Bind to any device you can find 31
matching clusters on. This will toggle the bind each time you do it. The ZigBee 32
coordinator does the pairing. 33
34
Example: A user would like to pair two devices (e.g., a switch and a light). 35
A button on each device is pressed and the “pairing” is done using the end device 36
bind request. 37
38
It is required that the Coordinator include the “bind manager”/End device 39
response. The Bind manager uses the ZDP bind/unbind request to create the 40
source binding in the devices. 41
If a device does not contain buttons, a propriety remote control could be used to 42
initiate the same function by sending a telegram to the device (emulating a button 43
press). 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
22 Profile Description

Enable Identify Mode: Sets the device in Identify mode for 60 seconds. This is
used for adding devices to a group or create a scene. 1
2
Group Nodes: Used to add devices to a group. This action sends the “Add group 3
if Identifying” command. This adds all devices that are in “identify mode” to the 4
group. The group ID is picked by the implementer. 5
Create Scene: This action creates a scene using devices present in a group. 6
7
For example, by a button press a “store scene” command is sent. The store scene 8
command should sent to a Group already existing in the network. The Group ID is 9
up to the implementer to pick. 10
If a device does not support an action, the action it must be listed in the device’s 11
documentation as “Not Supported”. 12
13
14
5.9.4 Group Commissioning 15
16
A description of the principals underlying group commissioning, and to some 17
extent commissioning in general, can be found in [R9]. A device that implements 18
the Identify client cluster must implement means for a user interaction to perform 19
E-mode group commissioning initiated from that device. By user interaction on 20
that device, the device shall be possible to: 21
• Set matching devices in identify mode. 22
23
• Perform group binding on selected matching devices. 24
An example of such an implementation could be: 25
26
The user interacts with a device implementing the Identify client cluster to make it 27
enter E-mode group commissioning. When this mode is entered, the device 28
performs the following: 29
• Find devices on the network that match services of a cluster on the device. 30
31
• Put the matched devices in identify mode one at a time. 32
• When a user interaction is performed, the device currently identifying is made 33
subject to a group binding. 34
35
For an On/Off Light Switch the process could be: 36
• The user flips the physical switch 4 times rapidly. The switch (implementing 37
the On/Off client cluster) searches for devices on the network with matching 38
services (implementing the On/Off server cluster). 39
40
• The matched devices are put in identify mode for a short period one at a time. 41
For On/Off Lights, the light bulb could be flashing. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 23

• When a device that the user wants to be a part of this group is identifying, the
user flips the switch once. The switch initiates a group binding to the device 1
currently identifying. 2
3
4
5.9.5 Group Messaging vs. Unicast Messaging 5
6
It is important to consider that groups make use of broadcast transmissions. Group 7
messaging should only be used when a device needs to communicate with a group 8
of greater than 5. For groups of less than 5, standard binding and unicast messages 9
should be employed. Also, there is no acknowledgement service for group 10
messages, because they are broadcast. Unicast messaging shall be used if a device 11
requires APS acknowledgments. 12
The procedures for group commissioning described above and in [R9] can also be 13
used to create one-to-one bindings for unicast messaging with little or no 14
modification. When these procedures are utilized, the decision to create a group or 15
not can be made by the application based on a local device policy. If a device is 16
being bound to only 2 or 3 other devices, a unicast binding entry can be created 17
for each target, and three unicasts will be sent instead of a group broadcast. When 18
the destination is a large number of devices, a group binding entry should be 19
created. This makes group vs. unicast messaging transparent to the user. 20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 5
24 Profile Description

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 25

C H A P T E R
1

6
2
3
4
5
6
7
8
9

CHAPTER 6CONSTANTS, ERROR CODES AND 10

11

GENERAL ALARMS
12
13
14
15
Profile-specific constants are shown in Table 6.1. 16
17
Table 6.1 Constants Specific to the HA Profile
18
Constant Description Value 19
20
minHAGroups Minimum number of groups that shall be supported 16 21
per node, across all endpoints on that node.
22
minHAScenes Minimum number of scenes that shall be supported 16 23
per node, across all groups on all endpoints on that 24
node. This only applies to nodes that implement the
server-side of the Scenes cluster on at least one 25
endpoint. 26
27
Values of the Atrium 0x01
LocationType attribute 28
of the Basic cluster for Bar 0x02 29
use with this profile. Courtyard 0x03 30
31
Bathroom 0x04
32
Bedroom 0x05 33
Billiard Room 0x06 34
35
Utility Room 0x07 36
Cellar 0x08 37
Closet 0x09
38
39
Theater 0x0A 40
Office 0x0B 41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 6
26 Constants, Error Codes and General Alarms

Table 6.1 Constants Specific to the HA Profile (Continued)

1
Values of the Deck 0x0C
LocationType attribute
2
of the Basic cluster for Den 0x0D 3
use with this profile. Dining Room 0x0E 4
5
Electrical Room 0x0F 6
Elevator 0x10 7
Entry 0x11 8
9
Family Room 0x12 10
Main Floor 0x13 11
12
Upstairs 0x14
13
Downstairs 0x15 14
Basement/Lower Level 0x16 15
16
Gallery 0x17
17
Game Room 0x18 18
Garage 0x19 19
20
Gym 0x1A
21
Hallway 0x1B 22
House 0x1C 23
24
Kitchen 0x1D 25
Laundry Room 0x1E 26
Library 0x1F
27
28
Master Bedroom 0x20 29
Mud Room (small room for coats and boots) 0x21 30
31
Nursery 0x22
32
Pantry 0x23 33
Office 0x24 34
35
Outside 0x25
36
Pool 0x26 37
Porch 0x27 38
39
Sewing Room 0x28
40
Sitting Room 0x29 41
Stairway 0x2A 42
43
Yard 0x2B 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 27

Table 6.1 Constants Specific to the HA Profile (Continued)

1
Values of the Attic 0x2C
LocationType attribute
2
of the Basic cluster for Hot Tub 0x2D 3
use with this profile. Living Room 0x2E 4
5
Sauna 0x2F 6
Shop/Workshop 0x30 7
Guest Bedroom 0x31 8
9
Guest Bath 0x32 10
Powder Room (1/2 bath) 0x33 11
12
Back Yard 0x34
13
Front Yard 0x35 14
Patio 0x36 15
16
Driveway 0x37
17
Sun Room 0x38 18
Living Room 0x39 19
20
Spa 0x3A
21
Whirlpool 0x3B 22
Shed 0x3C 23
24
Equipment Storage 0x3D 25
Hobby/Craft Room 0x3E 26
Fountain 0x3F
27
28
Pond 0x40 29
Reception Room 0x41 30
31
Breakfast Room 0x42
32
Nook 0x43 33
Garden 0x44 34
35
Balcony 0x45
36
Panic Room 0x46 37
Terrace 0x47 38
39
Roof 0x48
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 6
28 Constants, Error Codes and General Alarms

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 29

C H A P T E R
1

7
2
3
4
5
6
7
8
9

CHAPTER 7DEVICE SPECIFICATIONS 10

11
12
13
7.1 Common Clusters 14
15
Support for certain clusters is common to all the devices in this profile. The 16
clusters shown in Table 7.1 shall be supported by all devices in this profile as 17
mandatory or optional according the designation given here. Individual device 18
descriptions may place further restrictions on support of the optional clusters shown here. 19
20
Table 7.1 Clusters Common to All Devices 21
Server Side Client Side 22
23
Mandatory 24
25
Basic None
26
Identify 27
Optional 28
29
Clusters with reporting capability Clusters with reporting capability 30
(see sub-clause 7.1.1 for details) (see sub-clause 7.1.1 for details) 31
Power Configuration 32
33
Device Temperature Configuration
34
Alarms 35
Manufacturer-specific Manufacturer-specific 36
(see sub-clause 7.1.2 for details) (see sub-clause 7.1.2 for details) 37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
30 Device Specifications

7.1.1 Optional Support for Clusters With Reporting 1

Capability 2
3
Some clusters support the ability to report changes to the value of particular 4
attributes. These reports are typically received by the client side of the cluster. All 5
devices in this profile may support any cluster that receives attribute reports. 6
7
7.1.2 Manufacturer-Specific Clusters 8
9
The ZCL provides a range of cluster IDs that are reserved for manufacturer- 10
specific clusters. Manufacturer-specific clusters that conform to the requirements 11
given in the ZCL may be added to any device description specified in this profile. 12
13
14
7.1.3 Cluster Usage Restrictions 15
16
Only the clusters specified as mandatory or optional for a device in this 17
specification shall be implemented for any device in this profile. 18
19
20
7.2 Feature and Function Description 21
22
Each device must support a certain set of features and functions. The table below 23
specifies the mandatory and optional features and functions of each device. This 24
chapter contains a description of what must be supported if the feature or function 25
is supported by the device. The mandatory or optional configuration for each 26
device is described in the following sections. 27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 31

Table 7.2 Example Features and Functions Configuration 1

for an HA Device 2
Mandatory/ 3
Device Type/Feature or Function Optional 4
5
Join (end devices and routers only) M
6
7
Form Network (Coordinator only) M
8
9
Allow Others to Join Network (routers and Coordinators only) M
10
Restore to Factory Fresh Settings M
11
12
Pair Devices (End Device Bind Request) O 13
14
Bind Manager (End Device Bind Response - Coordinator only) M 15
16
Enable Identify Mode O 17
18
Group Nodes (send out an Add Group If Identify) O 19
20
Create Scene (Store Scene) O 21
22
Service discovery (Match Descriptor Request) O 23
24
ZDP Bind Response O 25
26
ZDP Unbind Response O 27
28
End Device Annce/Device Annce M 29
30
Service Discovery Response (Match Descriptor Response) M 31
32
33
Join (End Devices and Routers): 34
As described in Section sub-clause 5.9.3. 35
Form Network (Coordinator): 36
As described in Section sub-clause 5.9.3. 37
38
Allow Others to Join Network (Router and Coordinator Only): 39
As described in Section sub-clause 5.9.3. 40
Restore to Factory Fresh Settings: 41
As described in Section sub-clause 5.9.3. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
32 Device Specifications

Pair Devices (End Device Bind Request):

The device must provide a way for the user to issue an End Device Bind request. 1
2
Enable Identify Mode: 3
The device must provide a way for the user to enable Identify for 60 seconds. 4
Group Nodes (Add Group If Identify): 5
If this feature is supported the device must provide a way for the user to send an 6
“Add Group if Identifying Request”. 7
8
Create Scene (Store Scene): 9
The device must provide a way for the user to send a Store Scene request. 10
Service Discovery (Match Descriptor Request): 11
The device must provide a way to send Match Descriptor request, receive Match 12
Descriptor responses and utilize them for commissioning the device. 13
14
ZDP Bind Response: 15
The device must be able to receive a ZDP Bind Request and respond correctly 16
with an ZDP Bind Response. 17
ZDP Unbind Response: 18
The device must be able to receive a ZDP Unbind Request and respond correctly 19
with an ZDP Unbind Response. 20
21
End Device Annce/Device Annce: 22
The device must Send End Device Annce (ZigBee r13 specification)/Send Device 23
Annce (ZigBee r17 specification) upon joining and re-joining a network. 24
Service Discovery Response: 25
The Device must be able to receive a Match Descriptor request, and respond with 26
a Match Descriptor response correctly. 27
28
29
7.3 Generic Devices 30
31
32
7.3.1 On/Off Switch 33
34
The On/Off Switch is capable of sending on, off and toggle commands to devices 35
to switch them on or off. This device should only be used when a more specific 36
device specification (e.g., an On/Off Light Switch) is not available. 37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 33

7.3.1.1 Supported Clusters

1
In addition to those specified in Table 7.1, the On/Off Switch device shall support 2
the clusters listed in Table 7.3. 3
Table 7.3 Clusters Supported by the On/Off Switch Device 4
5
Server Side Client Side 6
7
Mandatory
8
On/Off Switch Configuration On/Off (subject to binding) 9
10
Scenes
11
Groups 12
Identify 13
14
Optional 15
None None 16
17
18
7.3.1.2 Supported Features and Functions 19
The On/Off Switch device shall support the features and functions listed below. 20
21
Table 7.4 Example Features and Functions Supported by the On/Off Switch
22
Device
23
Mandatory/ 24
Device Type/Feature or Function Optional 25
Join (end devices and routers only) M 26
27
Form Network (Coordinator only) M 28
29
Allow Others to Join Network (routers and Coordinators only) M 30
31
Restore to Factory Fresh Settings M 32
33
Pair Devices (End Device Bind Request) O 34
35
Bind Manager (End Device Bind Response - Coordinator only) M 36
37
Enable Identify Mode O 38
39
Group Nodes (send out an Add Group If Identify) O 40
41
Create Scene (Store Scene) O 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
34 Device Specifications

Table 7.4 Example Features and Functions Supported by the On/Off Switch Device
(Continued) 1
Service discovery (Match Descriptor Request) O
2
3
ZDP Bind Response M 4
5
ZDP Unbind Response M 6
7
End Device Annce/Device Annce M 8
9
Service Discovery Response (Match Descriptor Response) M 10
11
12
7.3.2 Level Control Switch 13
14
The Level Control Switch device is capable of sending on, off and toggle 15
commands to a wide range of devices to switch them on or off, and can also 16
control the level of a characteristic of such devices (e.g., brightness of a light or 17
height of a shade). This device should only be used when a more specific device 18
specification (e.g., an On/Off Light Switch) is not available. 19
20
7.3.2.1 Supported Clusters 21
22
In addition to those specified in Table 7.1, the Level Control Switch device shall 23
support the clusters listed in Table 7.5. 24
Table 7.5 Clusters Supported by the Level Control Switch Device 25
26
Server Side Client Side 27
28
Mandatory 29
On/Off Switch Configuration On/Off (subject to binding) 30
31
Level Control (subject to binding) 32
Scenes 33
34
Groups
35
Identify 36
Optional 37
38
None None 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 35

7.3.2.2 Supported Features and Functions

1
The Level Control Switch device shall support the features and functions listed 2
below. 3
Table 7.6 Example Features and Functions Supported by the 4
Level Control Switch Device 5
6
Mandatory/ 7
Device Type/Feature or Function Optional
8
Join (end devices and routers only) M 9
10
Form Network (Coordinator only) M 11
12
Allow Others to Join Network (routers and Coordinators only) M 13
14
Restore to Factory Fresh Settings M 15
16
Pair Devices (End Device Bind Request) O 17
18
Bind Manager (End Device Bind Response - Coordinator only) M 19
20
Enable Identify Mode O 21
22
Group Nodes (send out an Add Group If Identify) O 23
24
Create Scene (Store Scene) O
25
26
Service discovery (Match Descriptor Request) O
27
28
ZDP Bind Response M
29
ZDP Unbind Response M
30
31
End Device Annce/Device Annce M 32
33
Service Discovery Response (Match Descriptor Response) M 34
35
36
37
7.3.3 On/Off Output 38
39
The On/Off Output device is capable of being switched on and off. This device 40
should only be used when a more specific device specification (e.g., a Basic 41
Light) is not available. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
36 Device Specifications

7.3.3.1 Supported Clusters

1
In addition to those specified in Table 7.1, the On/Off Output device shall support 2
the clusters listed in Table 7.7. 3
Table 7.7 Clusters Supported by the On/Off Output Device 4
5
Server Side Client Side 6
7
Mandatory
8
On/Off None 9
10
Scenes
11
Groups 12
Optional 13
14
None None 15
16
7.3.3.2 Supported Features and Functions 17
18
The On/Off Output device shall support the features and functions listed below. 19
Table 7.8 Example Features and Functions Supported by the 20
On/Off Output Device 21
22
Mandatory/ 23
Device Type/Feature or Function Optional
24
Join (end devices and routers only) M 25
26
Form Network (Coordinator only) M 27
28
Allow Others to Join Network (routers and Coordinators only) M 29
30
Restore to Factory Fresh Settings M 31
32
Pair Devices (End Device Bind Request) O 33
34
Bind Manager (End Device Bind Response - Coordinator only) M
35
36
Enable Identify Mode O
37
38
Group Nodes (send out an Add Group If Identify) O
39
40
Create Scene (Store Scene) M (applies to
On/Off cluster 41
only) 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 37

Table 7.8 Example Features and Functions Supported by the

On/Off Output Device (Continued) 1
Service discovery (Match Descriptor Request) O
2
3
ZDP Bind Response O 4
5
ZDP Unbind Response O 6
7
End Device Annce/Device Annce M 8
9
Service Discovery Response (Match Descriptor Response) M 10
11
12
7.3.4 Level Controllable Output 13
14
The Level Controllable Output device can be switched on and off, and its output 15
level adjusted. This device should only be used when a more specific device 16
specification (e.g., a Dimmer Switch) is not available. 17
18
7.3.4.1 Supported Clusters 19
20
In addition to those specified in Table 7.1, the Level Controllable Output device 21
shall support the clusters listed in Table 7.9. 22
Table 7.9 Clusters Supported by the Level Controllable Output Device 23
24
Server Side Client Side 25
26
Mandatory 27
On/Off None 28
29
Level Control
30
Scenes 31
Groups 32
33
Optional 34
None None 35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
38 Device Specifications

7.3.4.2 Supported Features and Functions

1
The Level Controllable Output device shall support the features and functions 2
listed below. 3
Table 7.10 Example Features and Functions Supported by the 4
Level Controllable Output Device 5
6
Mandatory/ 7
Device Type/Feature or Function Optional
8
Join (end devices and routers only) M 9
10
Form Network (Coordinator only) M 11
12
Allow Others to Join Network (routers and Coordinators only) M 13
14
Restore to Factory Fresh Settings M 15
16
Pair Devices (End Device Bind Request) O 17
18
Bind Manager (End Device Bind Response - Coordinator only) M 19
20
Enable Identify Mode O 21
22
Group Nodes (send out an Add Group If Identify) O 23
24
Create Scene (Store Scene) M (applies to
On/Off and
25
Level Control 26
cluster only) 27
28
Service discovery (Match Descriptor Request) O
29
ZDP Bind Response O 30
31
ZDP Unbind Response O 32
33
End Device Annce/Device Annce M 34
35
Service Discovery Response (Match Descriptor Response) M 36
37
38
39
7.3.5 Scene Selector 40
41
The Scene Selector device is capable of setting up and selecting scenes on other
42
devices (including groups of devices).
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 39

7.3.5.1 Supported Clusters

1
In addition to those specified in Table 7.1, the Scene Selector device shall support 2
the clusters listed in Table 7.11. 3
Table 7.11 Clusters Supported by the Scene Selector Device 4
5
Server Side Client Side 6
7
Mandatory
8
None Scenes 9
10
Groups
11
Identify 12
Optional 13
14
None None 15
16
7.3.5.2 Supported Features and Functions 17
18
The Scene Selector device shall support the features and functions listed below. 19
Table 7.12 Example Features and Functions Supported by the 20
Scene Selector Device 21
22
Mandatory/ 23
Device Type/Feature or Function Optional
24
Join (end devices and routers only) M 25
26
Form Network (Coordinator only) M 27
28
Allow Others to Join Network (routers and Coordinators only) M 29
30
Restore to Factory Fresh Settings M 31
32
Pair Devices (End Device Bind Request) O 33
34
Bind Manager (End Device Bind Response - Coordinator only) M
35
36
Enable Identify Mode O
37
38
Group Nodes (send out an Add Group If Identify) M
39
40
Create Scene (Store Scene) M
41
Service discovery (Match Descriptor Request) O 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
40 Device Specifications

Table 7.12 Example Features and Functions Supported by the

Scene Selector Device (Continued) 1
ZDP Bind Response O
2
3
ZDP Unbind Response O 4
5
End Device Annce/Device Annce M 6
7
Service Discovery Response (Match Descriptor Response) M 8
9
10
11
7.3.6 Configuration Tool 12
13
The Configuration Tool device is capable of configuring other devices. This
14
device is intended for configuring newly installed devices and may be used for
15
performance optimization thereafter.
16
The intention of this specification is to define a generic configuration device type. 17
In future versions of the profile, new configuration devices may be specified by 18
explicitly specifying the supported clusters. 19
20
7.3.6.1 Supported Clusters 21
22
In addition to those specified in Table 7.1, the Configuration Tool device shall 23
support all of the mandatory and at least one of the optional clusters listed in 24
Table 7.13. 25
Both client and server forms of the Basic cluster are mandatory, so that the device 26
can interrogate what other devices are present on the network, and so that other 27
devices can also interrogate it if required. The Identify client cluster is mandatory 28
so that the device can ask other devices to identify themselves. 29
Table 7.13 Clusters Supported by the Configuration Tool Device
30
31
Server Side Client Side 32
33
Mandatory 34
None None 35
36
Optional 37
None Basic 38
39
Identify
40
Groups 41
Scenes 42
43
I luminance Level Sensing 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 41

Table 7.13 Clusters Supported by the Configuration Tool Device (Continued)

1
Temperature Measurement 2
Pressure Measurement 3
4
Flow Measurement 5
Occupancy Sensing 6
7
Pump Configuration and Control
8
Shade Configuration 9
Thermostat User Interface Configuration 10
11
12
7.3.6.2 Supported Features and Functions
13
The Configuration Tool device shall support the features and functions listed 14
below. 15
16
Table 7.14 Example Features and Functions Supported by the
Configuration Tool Device 17
18
Mandatory/ 19
Device Type/Feature or Function Optional 20
Join (end devices and routers only) M 21
22
Form Network (Coordinator only) M 23
24
Allow Others to Join Network (routers and Coordinators only) M 25
26
Restore to Factory Fresh Settings M 27
28
Pair Devices (End Device Bind Request) O 29
30
Bind Manager (End Device Bind Response - Coordinator only) M 31
32
Enable Identify Mode O 33
34
Group Nodes (send out an Add Group If Identify) M 35
36
Create Scene (Store Scene) M 37
38
Service discovery (Match Descriptor Request) O 39
40
ZDP Bind Response O
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
42 Device Specifications

Table 7.14 Example Features and Functions Supported by the

Configuration Tool Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.3.7 Remote Control 10
11
The Remote Control device is capable of controlling and monitoring other
12
devices.
13
Typically the Remote Control device is a handheld, battery powered device, that 14
can control devices (e.g., turn a light on/off), monitor devices (e.g., read the status 15
of a temperature sensor) or do some user configuration (e.g., change the setpoint 16
of a thermostat or a light sensor). 17
18
7.3.7.1 Supported Clusters 19
20
In addition to those specified in Table 7.1, the Remote Control device shall 21
support all mandatory and any of the optional clusters listed in Table 7.15. 22
Both client and server ends of the Basic cluster are mandatory, so that the device 23
can interrogate what other devices are present on the network, and so that other 24
devices can also interrogate it if required. The client side of the Identify cluster is 25
mandatory so that the device can instruct other devices to identify themselves. 26
27
The intention of this specification is to define a generic remote control device 28
type. New, explicit remote control devices may be specified in future versions by 29
(more) explicitly specifying the supported clusters. 30
Table 7.15 Clusters Supported by the Remote Control Device 31
32
Server Side Client Side
33
Mandatory 34
35
None Basic 36
Identify 37
38
On/Off
39
Level Control 40
Groups 41
42
Scenes
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 43

Table 7.15 Clusters Supported by the Remote Control Device (Continued)

1
Server Side Client Side 2
Optional 3
4
None Color Control 5
Pump Configuration and Control 6
7
Shade Configuration
8
On/Off Switch Configuration 9
Temperature Measurement 10
11
Illuminance Level Sensing 12
Illuminance Measurement 13
14
7.3.7.2 Supported Features and Functions 15
16
The Remote Control device shall support the features and functions listed below. 17
Table 7.16 Example Features and Functions Supported by the 18
Remote Control Device 19
20
Mandatory/ 21
Device Type/Feature or Function Optional
22
Join (end devices and routers only) M 23
24
Form Network (Coordinator only) M 25
26
Allow Others to Join Network (routers and Coordinators only) M 27
28
Restore to Factory Fresh Settings M 29
30
Pair Devices (End Device Bind Request) O 31
32
Bind Manager (End Device Bind Response - Coordinator only) M 33
34
Enable Identify Mode O 35
36
Group Nodes (send out an Add Group If Identify) O 37
38
Create Scene (Store Scene) O
39
40
Service discovery (Match Descriptor Request) O
41
42
ZDP Bind Response O
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
44 Device Specifications

Table 7.16 Example Features and Functions Supported by the

Remote Control Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
7.3.7.3 Notes on Operation 9
10
To ensure interoperability, a remote controller shall allow the presence of other 11
control devices in the network. In particular, this device should take measures to 12
avoid “fighting” for control. 13
14
7.3.8 Combined Interface 15
16
The Combined Interface device is capable of controlling and monitoring other 17
devices. It is typically a mains-powered device like a personal computer. 18
19
7.3.8.1 Supported Clusters 20
21
In addition to those specified in Table 7.1, the Combined Interface device shall 22
support all mandatory and any of the optional clusters listed in Table 7.17. 23
Both client and server ends of the Basic cluster are mandatory, so that the device 24
can interrogate what other devices are present on the network, and so that other 25
devices can also interrogate it if required. The client side of the Identify cluster is 26
mandatory so that the device can ask other devices to identify themselves. 27
28
Table 7.17 Clusters Supported by the Combined Interface Device 29
Server Side Client Side 30
31
Mandatory 32
33
None Basic
34
Identify 35
On/Off 36
37
Optional 38
None Color Control 39
40
Pump Configuration and Control
41
Shade Configuration 42
On/Off Switch Configuration 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 45

Table 7.17 Clusters Supported by the Combined Interface Device (Continued)

1
Server Side Client Side 2
Temperature Measurement 3
4
I luminance Level Sensing
5
I luminance Measurement 6
Thermostat User Interface Configuration 7
8
Level Control 9
Groups 10
Scenes
11
12
13
7.3.8.2 Supported Features and Functions 14
The Combined Interface device shall support the features and functions listed 15
below. 16
17
Table 7.18 Example Features and Functions Supported by the 18
Combined Interface Device
19
Mandatory/ 20
Device Type/Feature or Function Optional 21
Join (end devices and routers only) M
22
23
Form Network (Coordinator only) M 24
25
Allow Others to Join Network (routers and Coordinators only) M 26
27
Restore to Factory Fresh Settings M 28
29
Pair Devices (End Device Bind Request) O 30
31
Bind Manager (End Device Bind Response - Coordinator only) M 32
33
Enable Identify Mode O 34
35
Group Nodes (send out an Add Group If Identify) O 36
37
Create Scene (Store Scene) O 38
39
Service discovery (Match Descriptor Request) O 40
41
ZDP Bind Response O 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
46 Device Specifications

Table 7.18 Example Features and Functions Supported by the

Combined Interface Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
7.3.8.3 Notes on Operation 9
10
To ensure interoperability, a Combined Interface device shall allow the presence 11
of other control devices in the network. In particular, this device should take 12
measures to avoid “fighting” for control. 13
14
7.3.9 Range Extender 15
16
The Range Extender is a simple device that acts as a router for other devices. The 17
Range Extender device shall not be a ZigBee end device. A product that 18
implements the Range Extender devices shall not implement any other devices 19
defined in this profile. This device shall only be used if the product is not intended 20
to have any other application, or if a private application is implemented that has 21
not been addressed by this profile. 22
23
7.3.9.1 Supported Clusters 24
25
The Range Extender device shall only support the mandatory common clusters 26
listed in Table 7.1. 27
28
7.3.9.2 Supported Features and Functions 29
30
The Range Extender device shall support the features and functions listed below.
31
Table 7.19 Example Features and Functions Supported by the 32
Range Extender Device 33
Mandatory/ 34
Device Type/Feature or Function Optional 35
36
Join (end devices and routers only) M
37
38
Form Network (Coordinator only) M
39
40
Allow Others to Join Network (routers and Coordinators only) M
41
Restore to Factory Fresh Settings M 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 47

Table 7.19 Example Features and Functions Supported by the

Range Extender Device (Continued) 1
Pair Devices (End Device Bind Request) O
2
3
Bind Manager (End Device Bind Response - Coordinator only) M 4
5
Enable Identify Mode O 6
7
Group Nodes (send out an Add Group If Identify) O 8
9
Create Scene (Store Scene) O 10
11
Service discovery (Match Descriptor Request) O 12
13
ZDP Bind Response O 14
15
ZDP Unbind Response O 16
17
End Device Annce/Device Annce M 18
19
Service Discovery Response (Match Descriptor Response) M 20
21
22
7.3.10 Mains Power Outlet 23
24
The Mains Power Outlet device is capable of being switched on and off. This 25
device shall control a mains power outlet. 26
27
7.3.10.1 Supported Clusters 28
29
In addition to those specified in Table 7.1, the Mains Power Outlet device shall 30
support the clusters listed in Table 7.20. 31
Table 7.20 Clusters Supported by the Mains Power Outlet Device 32
33
Server Side Client Side 34
Mandatory 35
36
On/Off None 37
Scenes 38
39
Groups
40
Optional 41
42
None None
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
48 Device Specifications

7.3.10.2 Supported Features and Functions

1
The Mains Power Outlet device shall support the features and functions listed 2
below. 3
Table 7.21 Example Features and Functions Supported by the 4
Mains Power Outlet Device 5
6
Mandatory/ 7
Device Type/Feature or Function Optional
8
Join (end devices and routers only) M 9
10
Form Network (Coordinator only) M 11
12
Allow Others to Join Network (routers and Coordinators only) M 13
14
Restore to Factory Fresh Settings M 15
16
Pair Devices (End Device Bind Request) O 17
18
Bind Manager (End Device Bind Response - Coordinator only) M 19
20
Enable Identify Mode O 21
22
Group Nodes (send out an Add Group If Identify) O 23
24
Create Scene (Store Scene) M
25
26
Service discovery (Match Descriptor Request) O
27
28
ZDP Bind Response O
29
ZDP Unbind Response O
30
31
End Device Annce/Device Annce M 32
33
Service Discovery Response (Match Descriptor Response) M 34
35
36
37
7.4 Lighting Devices 38
39
40
7.4.1 On/Off Light 41
42
The On/Off Light device is a light that can be switched on and off. 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 49

7.4.1.1 Supported Clusters

1
In addition to those specified in Table 7.1, the On/Off Light device shall support 2
the clusters listed in Table 7.22. 3
Table 7.22 Clusters Supported by the On/Off Light Device 4
5
Server Side Client Side 6
7
Mandatory
8
On/Off None 9
10
Scenes
11
Groups 12
Optional 13
14
None Occupancy Sensing 15
16
7.4.1.2 Occupancy Sensing Cluster Support 17
18
If an On/Off Light device supports the Occupancy Sensing cluster, the action 19
taken upon receipt of a report (indicating a change in state of the Occupancy 20
attribute) is left up to the manufacturer. The ability to configure this behavior may 21
be included in a future version of this application profile. 22
23
7.4.1.3 Supported Features and Functions 24
The On/Off Light device shall support the features and functions listed below. 25
26
Table 7.23 Example Features and Functions Supported by the 27
On/Off Light Device 28
Mandatory/ 29
Device Type/Feature or Function Optional 30
31
Join (end devices and routers only) M
32
33
Form Network (Coordinator only) M
34
Allow Others to Join Network (routers and Coordinators only) M
35
36
Restore to Factory Fresh Settings M 37
38
Pair Devices (End Device Bind Request) O 39
40
Bind Manager (End Device Bind Response - Coordinator only) M 41
42
Enable Identify Mode M 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
50 Device Specifications

Table 7.23 Example Features and Functions Supported by the

On/Off Light Device (Continued) 1
Group Nodes (send out an Add Group If Identify) O
2
3
Create Scene (Store Scene) M 4
5
Service discovery (Match Descriptor Request) O 6
7
ZDP Bind Response O 8
9
ZDP Unbind Response O 10
11
End Device Annce/Device Annce M 12
13
Service Discovery Response (Match Descriptor Response) M 14
15
16
7.4.2 Dimmable Light 17
18
The Dimmable Light device is a light that can be switched on and off, and whose 19
luminance level may be controlled. 20
21
7.4.2.1 Supported Clusters 22
23
In addition to those specified in Table 7.1, the Dimmable Light device shall 24
support the clusters listed in Table 7.24. 25
Table 7.24 Clusters Supported by the Dimmable Light Device 26
27
Server Side Client Side 28
29
Mandatory
30
On/Off None 31
Level Control 32
33
Scenes 34
Groups 35
36
Optional
37
None Occupancy Sensing 38
39
40
7.4.2.2 Level Control Cluster (Server) Clarification
41
The Level Control cluster shall allow control over the luminance level of the light. 42
The functionality made available by this cluster shall be that given in specification 43
[R2]. 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 51

When the level is set to 0, the light shall be turned fully off. When the level is set
to 254, the light shall be turned on to the maximum level possible for the device. 1
2
It is recommended that the luminance is interpreted as a logarithmic scale, 3
according to what is given in specification [R4]. 4
5
7.4.2.3 Occupancy Sensing Cluster Support 6
If a Dimmable Light supports the Occupancy Sensing cluster, the action taken 7
upon receipt of a report indicating a change in state of the Occupancy attribute is 8
left up to the manufacturer. The ability to configure this behavior may be included 9
in a future version of this application profile. 10
11
7.4.2.4 Supported Features and Functions 12
13
The Dimmable Light device shall support the features and functions listed below. 14
Table 7.25 Example Features and Functions Supported by the 15
Dimmable Light Device 16
17
Mandatory/ 18
Device Type/Feature or Function Optional
19
Join (end devices and routers only) M 20
21
Form Network (Coordinator only) M 22
23
Allow Others to Join Network (routers and Coordinators only) M 24
25
Restore to Factory Fresh Settings M 26
27
Pair Devices (End Device Bind Request) O 28
29
Bind Manager (End Device Bind Response - Coordinator only) M 30
31
Enable Identify Mode M
32
33
Group Nodes (send out an Add Group If Identify) O
34
35
Create Scene (Store Scene) M
36
37
Service discovery (Match Descriptor Request) O
38
ZDP Bind Response O 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
52 Device Specifications

Table 7.25 Example Features and Functions Supported by the

Dimmable Light Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.4.3 Color Dimmable Light 10
11
The Color Dimmable Light device can be switched on and off, and its luminance,
12
hue, and saturation levels may be controlled.
13
14
7.4.3.1 Supported Clusters 15
In addition to those specified in Table 7.1, the Color Dimmable Light device shall 16
support the clusters listed in Table 7.26. 17
18
Table 7.26 Clusters Supported by the Color Dimmable Light Device
19
Server Side Client Side 20
21
Mandatory 22
On/Off None 23
24
Level Control
25
Color Control 26
Scenes 27
28
Groups 29
Optional 30
31
None Occupancy Sensing 32
33
7.4.3.2 Occupancy Sensing Cluster Support 34
35
If a Color Dimmable Light supports the Occupancy Sensing cluster, the action 36
taken upon receipt of a report indicating a change in state of the Occupancy 37
attribute is left up to the manufacturer. The ability to configure this behavior may 38
be included in a future version of this application profile. 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 53

7.4.3.3 Supported Features and Functions

1
The Color Dimmable Light device shall support the features and functions listed 2
below. 3
Table 7.27 Example Features and Functions Supported by the 4
Color Dimmable Light Device 5
6
Mandatory/ 7
Device Type/Feature or Function Optional
8
Join (end devices and routers only) M 9
10
Form Network (Coordinator only) M 11
12
Allow Others to Join Network (routers and Coordinators only) M 13
14
Restore to Factory Fresh Settings M 15
16
Pair Devices (End Device Bind Request) O 17
18
Bind Manager (End Device Bind Response - Coordinator only) M 19
20
Enable Identify Mode M 21
22
Group Nodes (send out an Add Group If Identify) O 23
24
Create Scene (Store Scene) M
25
26
Service discovery (Match Descriptor Request) O
27
28
ZDP Bind Response O
29
ZDP Unbind Response O
30
31
End Device Annce/Device Annce M 32
33
Service Discovery Response (Match Descriptor Response) M 34
35
36
37
7.4.4 On/Off Light Switch 38
39
The On/Off Light Switch device can send on, off and toggle commands to devices 40
(typically lights) to switch them on or off. 41
The On/Off Light Switch is identical in functionality to the On/Off Switch (see 42
7.3.1), and supports the same clusters. 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
54 Device Specifications

It has a different Device ID (see Table 5.1) to enable more detailed matching if
required, and a more specific icon to be drawn where needed. 1
2
7.4.4.1 Supported Clusters 3
4
In addition to those specified in Table 7.1, the On/Off Light Switch shall support 5
the clusters listed in Table 7.28. 6
Table 7.28 Clusters Supported by the On/Off Light Switch 7
8
Server Side Client Side 9
Mandatory 10
11
On/Off Switch Configuration On/Off 12
Scenes 13
14
Groups
15
Identify 16
17
Optional
18
None None 19
20
7.4.4.2 Supported Features and Functions 21
22
The On/Off Light Switch shall support the features and functions listed below. 23
Table 7.29 Example Features and Functions Supported by the 24
On/Off Light Switch 25
26
Mandatory/ 27
Device Type/Feature or Function Optional 28
Join (end devices and routers only) M 29
30
Form Network (Coordinator only) M 31
32
Allow Others to Join Network (routers and Coordinators only) M 33
34
Restore to Factory Fresh Settings M 35
36
Pair Devices (End Device Bind Request) O 37
38
Bind Manager (End Device Bind Response - Coordinator only) M 39
40
Enable Identify Mode O 41
42
Group Nodes (send out an Add Group If Identify) O 43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 55

Table 7.29 Example Features and Functions Supported by the

On/Off Light Switch (Continued) 1
Create Scene (Store Scene) O
2
3
Service discovery (Match Descriptor Request) O 4
5
ZDP Bind Response M 6
7
ZDP Unbind Response M 8
9
End Device Annce/Device Annce M 10
11
Service Discovery Response (Match Descriptor Response) M 12
13
14
7.4.5 Dimmer Switch 15
16
The Dimmer Switch device can send on, off and toggle commands to devices 17
(typically lights) to switch them on or off, and can also control the level of a 18
characteristic of such devices (typically the brightness of lights). 19
20
The Dimmer Switch is identical in functionality to the Level Control Switch (see 21
sub-clause 7.3.2), and supports the same clusters. 22
It has a different Device ID (see Table 5.1) to enable more detailed matching if 23
required, and a more specific icon to be drawn where needed. 24
25
7.4.5.1 Supported Clusters 26
27
In addition to those specified in Table 7.1, the Dimmer Switch device shall 28
support the clusters listed in Table 7.30. 29
Table 7.30 Clusters Supported by the Dimmer Switch Device 30
31
Server Side Client Side 32
33
Mandatory
34
On/Off Switch Configuration On/Off 35
Level Control
36
37
Scenes 38
Groups 39
40
Optional 41
None None 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
56 Device Specifications

7.4.5.2 Supported Features and Functions

1
The Dimmer Switch device shall support the features and functions listed below. 2
Table 7.31 Example Features and Functions Supported by the 3
Dimmer Switch Device 4
5
Mandatory/ 6
Device Type/Feature or Function Optional
7
Join (end devices and routers only) M 8
9
Form Network (Coordinator only) M 10
11
Allow Others to Join Network (routers and Coordinators only) M 12
13
Restore to Factory Fresh Settings M 14
15
Pair Devices (End Device Bind Request) O 16
17
Bind Manager (End Device Bind Response - Coordinator only) M 18
19
Enable Identify Mode O 20
21
Group Nodes (send out an Add Group If Identify) O 22
23
Create Scene (Store Scene) O
24
25
Service discovery (Match Descriptor Request) O
26
27
ZDP Bind Response M
28
ZDP Unbind Response M
29
30
End Device Annce/Device Annce M 31
32
Service Discovery Response (Match Descriptor Response) M 33
34
35
36
7.4.6 Color Dimmer Switch 37
38
The Color Dimmer Switch device can turn a light on and off, and control the 39
luminance, hue and saturation levels of a multi-color light. 40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 57

7.4.6.1 Supported Clusters

1
In addition to those specified in Table 7.1, the Color Dimmer Switch shall support 2
the clusters listed in Table 7.32. 3
Table 7.32 Clusters Supported by the Color Dimmer Switch Device 4
5
Server Side Client Side 6
7
Mandatory
8
On/Off Switch Configuration On/Off 9
10
Level Control
11
Color Control 12
Scenes 13
14
Groups
15
Identify 16
Optional 17
18
None None 19
20
7.4.6.2 Supported Features and Functions 21
22
The Color Dimmer Switch device shall support the features and functions listed 23
below. 24
Table 7.33 Example Features and Functions Supported by the 25
Color Dimmer Switch Device 26
27
Mandatory/ 28
Device Type/Feature or Function Optional
29
Join (end devices and routers only) M 30
31
Form Network (Coordinator only) M 32
33
Allow Others to Join Network (routers and Coordinators only) M 34
35
Restore to Factory Fresh Settings M 36
37
Pair Devices (End Device Bind Request) O 38
39
Bind Manager (End Device Bind Response - Coordinator only) M 40
41
Enable Identify Mode O
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
58 Device Specifications

Table 7.33 Example Features and Functions Supported by the

Color Dimmer Switch Device (Continued) 1
Group Nodes (send out an Add Group If Identify) O
2
3
Create Scene (Store Scene) O 4
5
Service discovery (Match Descriptor Request) O 6
7
ZDP Bind Response M 8
9
ZDP Unbind Response M 10
11
End Device Annce/Device Annce M 12
13
Service Discovery Response (Match Descriptor Response) M 14
15
16
7.4.7 Light Sensor 17
18
The Light Sensor device reports the illuminance of an area. 19
20
7.4.7.1 Supported Clusters 21
22
In addition to those specified in Table 7.1, the Light Sensor device shall support 23
the clusters listed in Table 7.34. 24
Table 7.34 Clusters Supported by the Light Sensor Device 25
26
Server Side Client Side 27
28
Mandatory
29
Illuminance Measurement None 30
31
Optional
32
None Groups 33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 59

7.4.7.2 Supported Features and Functions

1
The Light Sensor device shall support the features and functions listed below. 2
Table 7.35 Example Features and Functions Supported by the 3
Light Sensor Device 4
5
Mandatory/ 6
Device Type/Feature or Function Optional
7
Join (end devices and routers only) M 8
9
Form Network (Coordinator only) M 10
11
Allow Others to Join Network (routers and Coordinators only) M 12
13
Restore to Factory Fresh Settings M 14
15
Pair Devices (End Device Bind Request) O 16
17
Bind Manager (End Device Bind Response - Coordinator only) M 18
19
Enable Identify Mode O 20
21
Group Nodes (send out an Add Group If Identify) O 22
23
Create Scene (Store Scene) O
24
25
Service discovery (Match Descriptor Request) O
26
27
ZDP Bind Response O
28
ZDP Unbind Response O
29
30
End Device Annce/Device Annce M 31
32
Service Discovery Response (Match Descriptor Response) M 33
34
35
36
7.4.8 Occupancy Sensor 37
38
The Occupancy Sensor device reports the occupancy state of an area. 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
60 Device Specifications

7.4.8.1 Supported Clusters

1
In addition to those specified in Table 7.1, the Occupancy Sensor device shall 2
support the clusters listed in Table 7.36. 3
Table 7.36 Clusters Supported by the Occupancy Sensor Device 4
5
Server Side Client Side 6
7
Mandatory
8
Occupancy sensing None 9
10
Optional 11
None Groups 12
13
14
7.4.8.2 Supported Features and Functions
15
The Occupancy Sensor shall support the features and functions listed below. 16
17
Table 7.37 Example Features and Functions Supported by the
Occupancy Sensor Device 18
19
Mandatory/ 20
Device Type/Feature or Function Optional 21
Join (end devices and routers only) M 22
23
Form Network (Coordinator only) M 24
25
Allow Others to Join Network (routers and Coordinators only) M 26
27
Restore to Factory Fresh Settings M 28
29
Pair Devices (End Device Bind Request) O 30
31
Bind Manager (End Device Bind Response - Coordinator only) M 32
33
Enable Identify Mode O 34
35
Group Nodes (send out an Add Group If Identify) O 36
37
Create Scene (Store Scene) O 38
39
Service discovery (Match Descriptor Request) O 40
41
ZDP Bind Response O
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 61

Table 7.37 Example Features and Functions Supported by the

Occupancy Sensor Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.5 Closure Devices 10
11
12
7.5.1 Shade 13
14
The Shade device provides the ability to open or close window coverings, 15
including setting partially open or partially closed states. This device type 16
includes roller shades, drapes, and tilt-only blinds 17
18
7.5.1.1 Supported Clusters 19
In addition to those specified in Table 7.1, the Shade device shall support the 20
clusters listed in Table 7.38. 21
22
Table 7.38 Clusters Supported by the Shade Device 23
Server Side Client Side 24
25
Mandatory 26
27
Shade Configuration None
28
On/Off 29
Level Control 30
31
Scenes
32
Groups 33
34
Optional
35
None None 36
37
7.5.1.2 On/Off Cluster (Server) Clarification 38
39
The functionality of the supported On/Off cluster follows the specifications in the 40
dependencies section of the Level Control cluster specification [R2]. For this 41
device, “On” shall mean that the shade is open and “Off” shall mean that the shade 42
is closed (i.e. at the level corresponding to the ClosedLimit attribute of the Shade 43
Configuration cluster). 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
62 Device Specifications

7.5.1.3 Level Control Cluster (Server) Clarification

1
The Level Control cluster shall allow control over the position of the shade. The 2
functionality made available shall be that given in its specification [R2]. 3
4
The position of the shade shall correspond to the level by the following
5
relationship:
6
Shade position = ClosedLimit x (255 – Level) /255 7
8
When Level is 0 the shade is at the ClosedLimit and is closed. When Level is 255
9
the shade is at position 0 and is fully open.
10
7.5.1.4 Supported Features and Functions 11
12
The Shade device shall support the features and functions listed below. 13
Table 7.39 Example Features and Functions Supported by the
14
Shade Device 15
16
Mandatory/ 17
Device Type/Feature or Function Optional 18
Join (end devices and routers only) M 19
20
Form Network (Coordinator only) M 21
22
Allow Others to Join Network (routers and Coordinators only) M 23
24
Restore to Factory Fresh Settings M 25
26
Pair Devices (End Device Bind Request) O 27
28
Bind Manager (End Device Bind Response - Coordinator only) M 29
30
Enable Identify Mode M 31
32
Group Nodes (send out an Add Group If Identify) O 33
34
Create Scene (Store Scene) M 35
36
Service discovery (Match Descriptor Request) O
37
38
ZDP Bind Response O
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 63

Table 7.39 Example Features and Functions Supported by the

Shade Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.5.2 Shade Controller 10
11
The Shade Controller device can control the level of a shade, and put it into
12
configuration mode so that the user may adjust its limits.
13
14
7.5.2.1 Supported Clusters 15
In addition to those specified in Table 7.1, the Shade Controller device shall 16
support the clusters listed in Table 7.40. 17
18
Table 7.40 Clusters Supported by the Shade Controller Device
19
Server Side Client Side 20
21
Mandatory 22
None On/Off 23
24
Level Control
25
Shade Configuration 26
Scenes 27
28
Groups 29
Identify 30
31
Optional
32
None None 33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
64 Device Specifications

7.5.2.2 Supported Features and Functions

1
The Shade Controller device shall support the features and functions listed below. 2
Table 7.41 Example Features and Functions Supported by the 3
Shade Controller Device 4
5
Mandatory/ 6
Device Type/Feature or Function Optional
7
Join (end devices and routers only) M 8
9
Form Network (Coordinator only) M 10
11
Allow Others to Join Network (routers and Coordinators only) M 12
13
Restore to Factory Fresh Settings M 14
15
Pair Devices (End Device Bind Request) O 16
17
Bind Manager (End Device Bind Response - Coordinator only) M 18
19
Enable Identify Mode O 20
21
Group Nodes (send out an Add Group If Identify) O 22
23
Create Scene (Store Scene) O
24
25
Service discovery (Match Descriptor Request) O
26
27
ZDP Bind Response M
28
ZDP Unbind Response M
29
30
End Device Annce/Device Annce M 31
32
Service Discovery Response (Match Descriptor Response) M 33
34
35
36
7.6 HVAC Devices 37
38
39
7.6.1 Heating/Cooling Unit 40
41
The Heating/Cooling Unit device can heat or cool a space in a house. It is not 42
mandatory to provide both functionalities (e.g., the device may just heat but not 43
cool). It may be an indoor air handler. 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 65

7.6.1.1 Supported Clusters

1
In addition to those specified in Table 7.1, the Heating/Cooling Unit device shall 2
support the clusters listed in Table 7.42. 3
Table 7.42 Clusters Supported by the Heating/Cooling Unit Device 4
5
Server Side Client Side 6
7
Mandatory
8
On/Off Thermostat 9
10
Scenes
11
Groups 12
Optional 13
14
Fan Control None 15
Level Control 16
17
18
7.6.1.2 Thermostat Cluster (Client) 19
The Thermostat client cluster shall support a subset of the functionality specified 20
in [R7], i.e., the ability to receive notifications of heating and/or cooling demand. 21
22
7.6.1.3 Supported Features and Functions 23
24
The Heating/Cooling Unit device shall support the features and functions listed 25
below. 26
Table 7.43 Example Features and Functions Supported by the 27
Heating/Cooling Unit Device 28
29
Mandatory/
Device Type/Feature or Function Optional 30
31
Join (end devices and routers only) M 32
33
Form Network (Coordinator only) M 34
35
Allow Others to Join Network (routers and Coordinators only) M 36
37
Restore to Factory Fresh Settings M 38
39
Pair Devices (End Device Bind Request) O
40
41
Bind Manager (End Device Bind Response - Coordinator only) M
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
66 Device Specifications

Table 7.43 Example Features and Functions Supported by the

Heating/Cooling Unit Device (Continued) 1
Enable Identify Mode M
2
3
Group Nodes (send out an Add Group If Identify) O 4
5
Create Scene (Store Scene) M 6
7
Service discovery (Match Descriptor Request) O 8
9
ZDP Bind Response O 10
11
ZDP Unbind Response O 12
13
End Device Annce/Device Annce M 14
15
Service Discovery Response (Match Descriptor Response) M 16
17
18
7.6.2 Thermostat 19
20
The Thermostat device can have either built-in or separate sensors for 21
temperature, humidity or occupancy. It allows the desired temperature to be set 22
either remotely or locally. The thermostat may send heating and/or cooling 23
requirement notifications to a heating/cooling unit (e.g., an indoor air handler) or 24
may include a mechanism to control a heating or cooling unit directly. 25
26
7.6.2.1 Supported Clusters 27
28
In addition to those specified in Table 7.1, the Thermostat device shall support the 29
clusters listed in Table 7.44. 30
Table 7.44 Clusters Supported by the Thermostat Device 31
32
Server Side Client Side 33
Mandatory 34
35
Thermostat None 36
Scenes 37
38
Groups
39
Optional 40
41
Thermostat User Interface Fan Control 42
Configuration
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 67

Table 7.44 Clusters Supported by the Thermostat Device (Continued)

1
Server Side Client Side 2
Temperature Measurement 3
4
Occupancy Sensing
5
Relative Humidity Measurement 6
7
7.6.2.2 Temperature Measurement Cluster (Client) 8
9
The functionality made available by the Temperature Measurement client cluster 10
shall be that given in its specification [R3]. It is used to receive temperature 11
measurements when either the local or outdoor temperature for the thermostat 12
cluster is designated to be sensed remotely. 13
14
7.6.2.3 Occupancy Sensing Cluster (Client) 15
16
The functionality made available by the Occupancy Sensing client cluster shall be
17
that given in its specification [R3]. It is used to receive occupancy notifications
18
when occupancy for the thermostat cluster is designated to be sensed remotely.
19
7.6.2.4 Relative Humidity Measurement Cluster (Client) 20
21
The functionality made available by the Relative Humidity Measurement client 22
cluster shall be that given in its specification [R3]. It is used to receive humidity 23
measurements when humidity for the Thermostat cluster is designated to be 24
sensed remotely. 25
26
7.6.2.5 Scene Table Extensions 27
28
The following extension fields shall be added to the Scenes table for the 29
Thermostat cluster: 30
OccupiedCoolingSetpoint 31
32
OccupiedHeatingSetpoint 33
SystemMode 34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
68 Device Specifications

7.6.2.6 Supported Features and Functions

1
The Thermostat device shall support the features and functions listed below. 2
Table 7.45 Example Features and Functions Supported by the 3
Thermostat Device 4
5
Mandatory/ 6
Device Type/Feature or Function Optional
7
Join (end devices and routers only) M 8
9
Form Network (Coordinator only) M 10
11
Allow Others to Join Network (routers and Coordinators only) M 12
13
Restore to Factory Fresh Settings M 14
15
Pair Devices (End Device Bind Request) O 16
17
Bind Manager (End Device Bind Response - Coordinator only) M 18
19
Enable Identify Mode M 20
21
Group Nodes (send out an Add Group If Identify) O 22
23
Create Scene (Store Scene) O
24
25
Service discovery (Match Descriptor Request) O
26
27
ZDP Bind Response O
28
ZDP Unbind Response O
29
30
End Device Annce/Device Annce M 31
32
Service Discovery Response (Match Descriptor Response) M 33
34
35
36
7.6.3 Temperature Sensor 37
38
The Temperature Sensor device reports measurements of temperature. 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 69

7.6.3.1 Supported Clusters

1
In addition to those specified in Table 7.1, the Temperature Sensor device shall 2
support the clusters listed in Table 7.46. 3
Table 7.46 Clusters Supported by the Temperature Sensor Device 4
5
Server Side Client Side 6
7
Mandatory
8
Temperature Measurement None 9
10
Optional 11
None Groups 12
13
14
7.6.3.2 Supported Features and Functions
15
The Temperature Sensor device shall support the features and functions listed 16
below. 17
18
Table 7.47 Example Features and Functions Supported by the
Temperature Sensor Device 19
20
Mandatory/ 21
Device Type/Feature or Function Optional 22
Join (end devices and routers only) M 23
24
Form Network (Coordinator only) M 25
26
Allow Others to Join Network (routers and Coordinators only) M 27
28
Restore to Factory Fresh Settings M 29
30
Pair Devices (End Device Bind Request) O 31
32
Bind Manager (End Device Bind Response - Coordinator only) M 33
34
Enable Identify Mode O 35
36
Group Nodes (send out an Add Group If Identify) O 37
38
Create Scene (Store Scene) O 39
40
Service discovery (Match Descriptor Request) O 41
42
ZDP Bind Response O
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
70 Device Specifications

Table 7.47 Example Features and Functions Supported by the

Temperature Sensor Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.6.4 Pump 10
11
The Pump device is a pump that may have variable speed. It may have optional
12
built-in sensors and a regulation mechanism. It is typically used for pumping
13
water.
14
15
7.6.4.1 Supported Clusters 16
In addition to those specified in Table 7.1, the Pump device shall support the 17
clusters listed in Table 7.48. 18
19
Table 7.48 Clusters Supported by the Pump Device
20
Server Side Client Side 21
22
Mandatory 23
Pump Configuration and Control None 24
25
On/Off
26
Scenes 27
Groups 28
29
Optional 30
Level Control Pressure Measurement 31
32
Alarms Temperature Measurement 33
Pressure Measurement Flow Measurement 34
Temperature Measurement
35
36
Flow Measurement 37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 71

7.6.4.2 On/Off Cluster (Server) Clarifications

1
The actions carried out by the pump on receipt of commands are shown in 2
Table 7.49. 3
Table 7.49 Pump Actions on Receipt for On/Off Commands 4
5
Command Action on Receipt 6
Off If the pump is powered on, store the current
7
level then immediately power it off. 8
9
On If the pump is powered off, power it on and
10
move immediately to the level stored by a
previous Off command. If no such level has 11
been stored, move immediately to the 12
maximum level allowed for the pump. 13
Toggle If the pump is powered on, proceed as for the 14
Off command. If the device is powered off, 15
proceed as for the On command. 16
17
7.6.4.3 Level Control Cluster (Server) Clarifications 18
19
The Level Control cluster shall allow controlling the pump setpoints as specified 20
in [R2], however the transition time is always ignored. 21
22
The Setpoint of the pump is a percentage related to the Level according to
23
Table 7.50.
24
Table 7.50 Relationship Between Level and Setpoint 25
Level Setpoint Meaning 26
27
0 N/A Pump is stopped 28
1 - 200 Level / 2 (0.5 - 100.0%) Pump setpoint in percent 29
30
201 - 255 100.0% Pump setpoint is 100.0%
31
32
7.6.4.4 Pressure Measurement Notification (Server) 33
34
This cluster allows serving of internal pressure measurement if available. This is 35
independent of the Pressure Measurement client cluster, which connects to an 36
external networked pressure sensor. 37
38
7.6.4.5 Temperature Measurement Notification (Server) 39
This cluster allows serving of internal temperature measurement if available. This 40
is independent of the Temperature Measurement client cluster, which connects to 41
an external networked temperature sensor. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
72 Device Specifications

7.6.4.6 Flow Measurement Notification (Server)

1
This cluster allows serving of internal flow measurement if available. This is 2
independent of the Flow Measurement client cluster, which connects to an 3
external networked flow sensor. 4
5
7.6.4.7 Supported Features and Functions 6
7
The Pump device shall support the features and functions listed below. 8
Table 7.51 Example Features and Functions Supported by 9
the Pump Device 10
Mandatory/ 11
Device Type/Feature or Function Optional 12
13
Join (end devices and routers only) M 14
15
Form Network (Coordinator only) M
16
17
Allow Others to Join Network (routers and Coordinators only) M
18
19
Restore to Factory Fresh Settings M
20
Pair Devices (End Device Bind Request) O
21
22
Bind Manager (End Device Bind Response - Coordinator only) M 23
24
Enable Identify Mode M 25
26
Group Nodes (send out an Add Group If Identify) O 27
28
Create Scene (Store Scene) O 29
30
Service discovery (Match Descriptor Request) O 31
32
ZDP Bind Response O 33
34
ZDP Unbind Response O 35
36
End Device Annce/Device Annce M 37
38
Service Discovery Response (Match Descriptor Response) M 39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 73

7.6.5 Pump Controller 1

2
The Pump Controller device can configure and control a Pump device.
3
7.6.5.1 Supported Clusters 4
5
In addition to those specified in Table 7.1, the Pump Controller device shall 6
support the clusters listed in Table 7.52. 7
Table 7.52 Clusters Supported by the Pump Controller Device
8
9
Server Side Client Side 10
11
Mandatory 12
None Pump Configuration and Control 13
14
On/Off
15
Scenes 16
Groups 17
18
Identify
19
Optional 20
21
None Pressure Measurement
22
Temperature Measurement 23
Flow Measurement 24
25
Level Control 26
27
7.6.5.2 Pressure Measurement (Client) 28
29
This cluster allows configuration and monitoring of the Pressure Sensor internal 30
to a Pump device. 31
32
7.6.5.3 Temperature Measurement Notification (Client) 33
This cluster allows configuration and monitoring of the Temperature Sensor 34
internal to a Pump device. 35
36
7.6.5.4 Flow Measurement Notification (Client) 37
38
This cluster allows configuration and monitoring of the Flow Sensor internal to a 39
Pump device. 40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
74 Device Specifications

7.6.5.5 Supported Features and Functions

1
The Pump Controller device shall support the features and functions listed below. 2
Table 7.53 Example Features and Functions Supported by the 3
Pump Controller Device 4
5
Mandatory/ 6
Device Type/Feature or Function Optional
7
Join (end devices and routers only) M 8
9
Form Network (Coordinator only) M 10
11
Allow Others to Join Network (routers and Coordinators only) M 12
13
Restore to Factory Fresh Settings M 14
15
Pair Devices (End Device Bind Request) O 16
17
Bind Manager (End Device Bind Response - Coordinator only) M 18
19
Enable Identify Mode O 20
21
Group Nodes (send out an Add Group If Identify) O 22
23
Create Scene (Store Scene) O
24
25
Service discovery (Match Descriptor Request) O
26
27
ZDP Bind Response M
28
ZDP Unbind Response M
29
30
End Device Annce/Device Annce M 31
32
Service Discovery Response (Match Descriptor Response) M 33
34
35
36
7.6.6 Pressure Sensor 37
38
The Pressure Sensor device measures and periodically reports the pressure of a 39
liquid (typically water). 40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 75

7.6.6.1 Supported Clusters

1
In addition to those specified in Table 7.1, the Pressure Sensor device shall 2
support the clusters listed in Table 7.54. 3
Table 7.54 Clusters Supported by the Pressure Sensor Device 4
5
Server Side Client Side 6
7
Mandatory
8
Pressure Measurement None 9
10
Optional 11
None Groups 12
13
14
7.6.6.2 Supported Features and Functions
15
The Pressure Sensor device shall support the features and functions listed below. 16
17
Table 7.55 Example Features and Functions Supported by the
Pressure Sensor Device 18
19
Mandatory/ 20
Device Type/Feature or Function Optional 21
Join (end devices and routers only) M 22
23
Form Network (Coordinator only) M 24
25
Allow Others to Join Network (routers and Coordinators only) M 26
27
Restore to Factory Fresh Settings M 28
29
Pair Devices (End Device Bind Request) O 30
31
Bind Manager (End Device Bind Response - Coordinator only) M 32
33
Enable Identify Mode O 34
35
Group Nodes (send out an Add Group If Identify) O 36
37
Create Scene (Store Scene) O 38
39
Service discovery (Match Descriptor Request) O 40
41
ZDP Bind Response O
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
76 Device Specifications

Table 7.55 Example Features and Functions Supported by the

Pressure Sensor Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.6.7 Flow Sensor 10
11
The Flow Sensor device measures and periodically reports the flow rate of a liquid
12
(typically water).
13
14
7.6.7.1 Supported Clusters 15
In addition to those specified in Table 7.1, the Flow Sensor device shall support 16
the clusters listed in Table 7.56. 17
18
Table 7.56 Clusters Supported by the Flow Sensor Device
19
Server Side Client Side 20
21
Mandatory 22
Flow Measurement None 23
24
Optional 25
None Groups 26
27
28
7.6.7.2 Supported Features and Functions 29
The Flow Sensor device shall support the features and functions listed below. 30
31
Table 7.57 Example Features and Functions Supported by the
32
Flow Sensor Device
33
Mandatory/ 34
Device Type/Feature or Function Optional 35
Join (end devices and routers only) M 36
37
Form Network (Coordinator only) M 38
39
Allow Others to Join Network (routers and Coordinators only) M 40
41
Restore to Factory Fresh Settings M 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 77

Table 7.57 Example Features and Functions Supported by the

Flow Sensor Device (Continued) 1
Pair Devices (End Device Bind Request) O
2
3
Bind Manager (End Device Bind Response - Coordinator only) M 4
5
Enable Identify Mode O 6
7
Group Nodes (send out an Add Group If Identify) O 8
9
Create Scene (Store Scene) O 10
11
Service discovery (Match Descriptor Request) O 12
13
ZDP Bind Response O 14
15
ZDP Unbind Response O 16
17
End Device Annce/Device Annce M 18
19
Service Discovery Response (Match Descriptor Response) M 20
21
22
7.7 Intruder Alarm System Devices 23
24
25
7.7.1 IAS Control and Indicating Equipment (CIE) 26
27
The IAS CIE device is the central Control and Indicating Equipment for an 28
Intruder Alarm System. It receives inputs from sensors (Zones) and control 29
equipment (ACE), and sends output to a warning device (WD). 30
31
7.7.1.1 Supported Clusters 32
33
In addition to those specified in Table 7.1, the IAS CIE device shall support the 34
clusters listed in Table 7.58. 35
Table 7.58 Clusters Supported by the IAS CIE Device 36
37
Server Side Client Side 38
39
Mandatory
40
IAS ACE IAS WD 41
Identify
42
43
IAS Zone 44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
78 Device Specifications

Table 7.58 Clusters Supported by the IAS CIE Device (Continued)

1
Server Side Client Side 2
Optional 3
4
None Scenes 5
Groups 6
7
8
7.7.1.2 Basic Cluster (Server) Restrictions 9
The ability to disable the device shall not be provided. That is, the DeviceEnable 10
attribute shall be read-only and set to 0. 11
12
7.7.1.3 Supported Features and Functions 13
14
The IAS CIE device shall support the features and functions listed below. 15
Table 7.59 Example Features and Functions Supported by 16
the IAS CIE Device 17
18
Mandatory/
Device Type/Feature or Function Optional 19
20
Join (end devices and routers only) M 21
22
Form Network (Coordinator only) M 23
24
Allow Others to Join Network (routers and Coordinators only) M 25
26
Restore to Factory Fresh Settings M 27
28
Pair Devices (End Device Bind Request) O
29
30
Bind Manager (End Device Bind Response - Coordinator only) M
31
32
Enable Identify Mode O
33
34
Group Nodes (send out an Add Group If Identify) O
35
Create Scene (Store Scene) O 36
37
Service discovery (Match Descriptor Request) O 38
39
ZDP Bind Response O 40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 79

Table 7.59 Example Features and Functions Supported by

the IAS CIE Device (Continued) 1
ZDP Unbind Response O
2
3
End Device Annce/Device Annce M 4
5
Service Discovery Response (Match Descriptor Response) M 6
7
8
9
7.7.2 IAS Ancillary Control Equipment (ACE) 10
11
The IAS ACE device is a remote control for an Intruder Alarm System. A Zigbee
12
enabled ACE device can access an IAS CIE device and manipulate the IAS
13
system, on behalf of a level-2 user (see [R10]). The device can also act as a Zone
14
sensor.
15
16
7.7.2.1 Supported Clusters 17
In addition to those specified in Table 7.1, the IAS ACE device shall support the 18
clusters listed in Table 7.60. 19
20
Table 7.60 Clusters Supported by the IAS ACE Device
21
Server Side Client Side 22
23
Mandatory 24
IAS Zone IAS ACE 25
26
Identify
27
Optional 28
29
None None
30
31
7.7.2.2 Basic Cluster (Server) Restrictions 32
33
The ability to disable the device shall not be provided. That is, the DeviceEnable 34
attribute shall be read-only and set to 0. 35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
80 Device Specifications

7.7.2.3 Supported Features and Functions

1
The IAS ACE device shall support the features and functions listed below. 2
Table 7.61 Example Features and Functions Supported by 3
the IAS ACE Device 4
5
Mandatory/ 6
Device Type/Feature or Function Optional
7
Join (end devices and routers only) M 8
9
Form Network (Coordinator only) M 10
11
Allow Others to Join Network (routers and Coordinators only) M 12
13
Restore to Factory Fresh Settings M 14
15
Pair Devices (End Device Bind Request) O 16
17
Bind Manager (End Device Bind Response - Coordinator only) M 18
19
Enable Identify Mode O 20
21
Group Nodes (send out an Add Group If Identify) O 22
23
Create Scene (Store Scene) O
24
25
Service discovery (Match Descriptor Request) O
26
27
ZDP Bind Response M
28
ZDP Unbind Response M
29
30
End Device Annce/Device Annce M 31
32
Service Discovery Response (Match Descriptor Response) M 33
34
35
36
7.7.3 IAS Zone 37
38
An IAS Zone device detects alarm conditions (e.g. intrusion, fire) and signals 39
them to the Control and Indicating Equipment (CIE) of an IAS system. An IAS 40
Zone device supports up to two alarm types, low battery reports, and supervision 41
of the IAS network. 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 81

7.7.3.1 Supported Clusters

1
In addition to those specified in Table 7.1, the IAS Zone device shall support the 2
clusters listed in Table 7.62. 3
Table 7.62 Clusters Supported by the IAS Zone Device 4
5
Server Side Client Side 6
7
Mandatory
8
IAS Zone None 9
10
Optional 11
None None 12
13
14
7.7.3.2 Basic Cluster (Server) Restrictions
15
The ability to disable the device shall not be provided. That is, the DeviceEnable 16
attribute shall be read-only and set to 0. 17
18
7.7.3.3 Supported Features and Functions 19
20
The IAS Zone device shall support the features and functions listed below. 21
Table 7.63 Example Features and Functions Supported by 22
the IAS Zone Device 23
24
Mandatory/
Device Type/Feature or Function Optional 25
26
Join (end devices and routers only) M 27
28
Form Network (Coordinator only) M 29
30
Allow Others to Join Network (routers and Coordinators only) M 31
32
Restore to Factory Fresh Settings M
33
34
Pair Devices (End Device Bind Request) O
35
36
Bind Manager (End Device Bind Response - Coordinator only) M
37
38
Enable Identify Mode O
39
Group Nodes (send out an Add Group If Identify) O 40
41
Create Scene (Store Scene) O 42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
82 Device Specifications

Table 7.63 Example Features and Functions Supported by

the IAS Zone Device (Continued) 1
Service discovery (Match Descriptor Request) O
2
3
ZDP Bind Response M 4
5
ZDP Unbind Response M 6
7
End Device Annce/Device Annce M 8
9
Service Discovery Response (Match Descriptor Response) M 10
11
12
7.7.4 IAS Warning Device (WD) 13
14
An IAS WD device can produce audible and visible warning indications (siren, 15
strobe lighting, etc.) when instructed to by an IAS Central Indicating Equipment 16
(CIE) on detection of a system alarm condition. The IAS WD can also act as a 17
sensor (Zone). 18
19
7.7.4.1 Supported Clusters 20
21
In addition to those specified in Table 7.1, the IAS WD shall support the clusters 22
listed in Table 7.64. 23
Table 7.64 Clusters Supported by the IAS WD 24
25
Server Side Client Side 26
27
Mandatory 28
IAS WD None 29
30
IAS Zone
31
Optional 32
33
Scenes None
34
Groups 35
36
7.7.4.2 Basic Cluster (Server) Restrictions 37
38
The ability to disable the device shall not be provided, i.e., the DeviceEnable 39
attribute shall be read-only and set to 0. 40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 ZigBee Home Automation
Public Application Profile 83

7.7.4.3 Polling Rate Exception

1
The IAS WD may poll at a maximum rate of once per second when it is 2
implemented as a battery-powered ZigBee end device that sleeps. It is 3
recommended that this exception be used cautiously, and that the number of 4
devices installed in a network that make use of this be kept to a minimum. 5
6
7.7.4.4 Supported Features and Functions 7
8
The IAS WD device shall support the features and functions listed below. 9
Table 7.65 Example Features and Functions Supported by 10
the IAS WD 11
Mandatory/ 12
Device Type/Feature or Function Optional 13
14
Join (end devices and routers only) M 15
16
Form Network (Coordinator only) M
17
18
Allow Others to Join Network (routers and Coordinators only) M
19
20
Restore to Factory Fresh Settings M
21
Pair Devices (End Device Bind Request) O
22
23
Bind Manager (End Device Bind Response - Coordinator only) M 24
25
Enable Identify Mode O 26
27
Group Nodes (send out an Add Group If Identify) O 28
29
Create Scene (Store Scene) O 30
31
Service discovery (Match Descriptor Request) O 32
33
ZDP Bind Response O 34
35
ZDP Unbind Response O 36
37
End Device Annce/Device Annce M 38
39
Service Discovery Response (Match Descriptor Response) M 40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.
 Chapter 7
84 Device Specifications

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This page intentionally blank 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Copyright © 2007 ZigBee Standards Organization. All rights reserved.