Difference between revisions of "ZWave API"
(→HSM100 (battery, temperature, motion, light)) |
|||
(48 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | [[Category: | + | [[Category: Automation| ]] |
[[Category: RF Control]] | [[Category: RF Control]] | ||
[[Category: ZWave]] | [[Category: ZWave]] | ||
[[Category: Programmer's Guide]] | [[Category: Programmer's Guide]] | ||
− | + | [[Category: Documentation]] | |
+ | {{versioninfo}} | ||
= Introduction = | = Introduction = | ||
The ZWave API is not available for free. You have to get the Zensys SDK for command specifications and device class definitions. This page tries to collect all the freely available information about ZWave. The final goal is to provide a header file with all necessary definitions for basic operation with open source software. | The ZWave API is not available for free. You have to get the Zensys SDK for command specifications and device class definitions. This page tries to collect all the freely available information about ZWave. The final goal is to provide a header file with all necessary definitions for basic operation with open source software. | ||
Line 11: | Line 12: | ||
= API = | = API = | ||
== Frame specification == | == Frame specification == | ||
− | Karl | + | Karl Denninger implemented basic ZWave support in his software "HomeDaemon". He advised that basic frame specification can be derived from his source code (http://www.denninger.net/homedaemon.htm). |
== Basic Classes == | == Basic Classes == | ||
Line 49: | Line 50: | ||
additional information from http://zwaveworld.com/forum/index.php?showtopic=237: | additional information from http://zwaveworld.com/forum/index.php?showtopic=237: | ||
>?FI003,017,000 //basic class 3 (slave), generic class 0x11 (multlevel switch), specific class 0 | >?FI003,017,000 //basic class 3 (slave), generic class 0x11 (multlevel switch), specific class 0 | ||
+ | |||
+ | ==== All the known classes ==== | ||
+ | COMMAND_CLASS_BASIC 0x20 <BR> | ||
+ | COMMAND_CLASS_BATTERY 0x80 <BR> | ||
+ | COMMAND_CLASS_WAKE_UP 0x84 <BR> | ||
+ | COMMAND_CLASS_CONTROLLER_REPLICATION 0x21 <BR> | ||
+ | COMMAND_CLASS_SWITCH_MULTILEVEL 0x26 <BR> | ||
+ | COMMAND_CLASS_SWITCH_ALL 0x27 <BR> | ||
+ | COMMAND_CLASS_SENSOR_BINARY 0x30 <BR> | ||
+ | COMMAND_CLASS_ALARM 0x71 <BR> | ||
+ | COMMAND_CLASS_MULTI_CMD 0x8F <BR> | ||
+ | COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE 0x46 <BR> | ||
+ | COMMAND_CLASS_CLOCK 0x81 <BR> | ||
+ | COMMAND_CLASS_ASSOCIATION 0x85 <BR> | ||
+ | COMMAND_CLASS_CONFIGURATION 0x70 <BR> | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC 0x72 <BR> | ||
+ | -<BR> | ||
+ | COMMAND_CLASS_SCENE_ACTIVATION 0x2B <BR> | ||
+ | COMMAND_CLASS_SCENE_ACTUATOR_CONF 0x2C <BR> | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC 0x72 <BR> | ||
+ | COMMAND_CLASS_VERSION 0x86 <BR> | ||
+ | COMMAND_CLASS_MANUFACTURER_PROPRIETARY 0x91 <BR> | ||
+ | COMMAND_CLASS_NODE_NAMING 0x77 <BR> | ||
+ | COMMAND_CLASS_POWERLEVEL 0x73 <BR> | ||
+ | COMMAND_CLASS_MARK 0xEF <BR> | ||
+ | COMMAND_CLASS_HAIL 0x82 <BR> | ||
+ | COMMAND_CLASS_MULTI_INSTANCE 0x60 <BR> | ||
+ | COMMAND_CLASS_SENSOR_MULTILEVEL 0x31 <BR> | ||
+ | COMMAND_CLASS_SWITCH_BINARY 0x25 <BR> | ||
==== Basic ==== | ==== Basic ==== | ||
Line 54: | Line 84: | ||
BASIC_GET | BASIC_GET | ||
BASIC_SET | BASIC_SET | ||
+ | |||
==== Mandatory ==== | ==== Mandatory ==== | ||
==== Multilevel Sensor ==== | ==== Multilevel Sensor ==== | ||
Line 86: | Line 117: | ||
The HSM100 is a motion sensor (probably the best as for now) (2008) | The HSM100 is a motion sensor (probably the best as for now) (2008) | ||
− | Device supports classes: | + | Device supports classes: 60, 31, 70, 84, 85, 80, 72, 77, 86 |
− | Manufacturer ID: | + | Manufacturer ID: 1E (HomeSeer) Type: 02 ID: 01 |
− | Lib: 2.31 App: 1.4 Also know with Lib: 2.40 App: 1.6 | + | Lib: 2.31 App: 1.4 Also know with Lib: 2.40 App: 1.6 or App: 1.7 |
+ | COMMAND_CLASS_MULTI_INSTANCE, 60 | ||
+ | COMMAND_CLASS_SENSOR_MULTILEVEL, 31 | ||
+ | COMMAND_CLASS_CONFIGURATION, 70 | ||
+ | COMMAND_CLASS_WAKE_UP, 84 | ||
+ | COMMAND_CLASS_ASSOCIATION, 85 | ||
+ | COMMAND_CLASS_BATTERY, 80 | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 | ||
+ | COMMAND_CLASS_NODE_NAMING, 77 | ||
+ | COMMAND_CLASS_VERSION 86 | ||
+ | |||
+ | |||
The following frame from personal observations is described below<BR> | The following frame from personal observations is described below<BR> | ||
Line 166: | Line 208: | ||
Motion detection for module with address 7 <BR> | Motion detection for module with address 7 <BR> | ||
<BR> | <BR> | ||
− | 01 09 00 04 00 07 03 20 01 00 no move <BR> | + | 01 09 00 04 00 07 03 20 01 <U>00</U> no move <BR> |
− | 01 09 00 04 00 07 03 20 01 FF move <BR> | + | 01 09 00 04 00 07 03 20 01 <U>FF</U> move <BR> |
<BR> | <BR> | ||
<BR> | <BR> | ||
− | C O N F I G U R A T I O N <BR> | + | C O N F I G U R A T I O N HSM100<BR> |
− | SET Unit | + | SET Unit 0Ch to report no move delay after 1 minute |
− | 01 0C 00 13 0C 05 70 04 02 01 01 05 03 99 | + | 01 0C 00 13 0C 05 70 04 02 01 <U>01</U> 05 03 99 |
− | + | set unit 0Ch to wake up every 6 minutes | |
− | + | 01 0D 00 13 0C 06 84 04 00 <U>01</U> 68 01 05 03 05 | |
− | + | set unit 0Ch to wake up every 12 minutes | |
− | + | 01 0D 00 13 0C 06 84 04 00 <U>02</U> D0 01 05 03 BE | |
− | + | set unit 12 to wake up every 18 minutes | |
− | + | 01 0D 00 13 0C 06 84 04 00 <U>04</U> 38 01 05 03 50 | |
− | + | Set unit 0Ch led off | |
− | + | 01 0C 00 13 0C 05 70 04 03 01 <U>00</U> 05 03 99 | |
− | + | Set unit 0Ch led ON | |
− | + | 01 0C 00 13 0C 05 70 04 03 01 <U>FF</U> 05 03 66 | |
− | set unit | + | |
− | 01 0D 00 13 0C 06 84 04 00 01 68 01 05 03 05 | + | Get sofware association for unit 0Ch |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | 01 0D 00 13 0C 06 84 04 00 02 D0 01 05 03 BE | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | set unit 12 to 18 minutes | + | |
− | 01 0D 00 13 0C 06 84 04 00 04 38 01 05 03 50 | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | Set unit | + | |
− | 01 0C 00 13 0C 05 70 04 03 01 00 05 03 99 | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | Set unit | + | |
− | 01 0C 00 13 0C 05 70 04 03 01 FF 05 03 66 | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | Get sofware association unit | + | |
Write 01 0A 00 13 0C 03 85 02 01 05 03 69 | Write 01 0A 00 13 0C 03 85 02 01 05 03 69 | ||
Read 01 0C 00 04 00 0C 06 85 03 01 04 00 01 7F // YES associated | Read 01 0C 00 04 00 0C 06 85 03 01 04 00 01 7F // YES associated | ||
OR | OR | ||
Read 01 0B 00 04 00 0C 05 85 03 01 04 00 7A // NOT associated | Read 01 0B 00 04 00 0C 05 85 03 01 04 00 7A // NOT associated | ||
− | Remove software association Unit | + | Remove software association Unit 0Ch |
01 0B 00 13 0C 04 85 04 01 01 05 03 68 | 01 0B 00 13 0C 04 85 04 01 01 05 03 68 | ||
− | Set software association Unit | + | Set software association Unit 0ch |
01 0B 00 13 0C 04 85 01 01 01 05 03 6D | 01 0B 00 13 0C 04 85 01 01 01 05 03 6D | ||
+ | Force to optimize Unit 0Ch | ||
+ | 01 05 00 48 0C 03 BD | ||
+ | 01 04 00 4A 05 B4 | ||
− | ==== RZP15 Vizia Leviton Appliance Module switch ==== | + | ==== RZP15 Vizia Leviton Appliance Module switch 908.42Mhz ==== |
− | supports classes: 25,27,2B,2C | + | supports classes: 25, 27, 2B, 2C, 85, 72, 86, 91, 77, 73, EF, 82 |
− | manufacturer ID: | + | manufacturer ID: 00 1D (Leviton) |
− | Type: | + | Type: 101 ID: 206 |
version: Lib: 2.6 App: 0.3 | version: Lib: 2.6 App: 0.3 | ||
+ | COMMAND_CLASS_SWITCH_BINARY, 25 | ||
+ | COMMAND_CLASS_SWITCH_ALL, 27 | ||
+ | COMMAND_CLASS_SCENE_ACTIVATION, 2B | ||
+ | COMMAND_CLASS_SCENE_ACTUATOR_CONF, 2C | ||
+ | COMMAND_CLASS_ASSOCIATION, 85 | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 | ||
+ | COMMAND_CLASS_VERSION, 86 | ||
+ | COMMAND_CLASS_MANUFACTURER_PROPRIETARY, 91 | ||
+ | COMMAND_CLASS_NODE_NAMING, 77 | ||
+ | COMMAND_CLASS_POWERLEVEL, 73 | ||
+ | COMMAND_CLASS_MARK, EF | ||
+ | COMMAND_CLASS_HAIL, 82 | ||
Frame to send ON | Frame to send ON | ||
− | 01 0A 00 13 UU 03 20 01 | + | 01 0A 00 13 UU 03 20 01 63 05 03 CR |
Frame to send OFF | Frame to send OFF | ||
− | 01 0A 00 13 UU 03 20 01 | + | 01 0A 00 13 UU 03 20 01 00 05 03 CR |
Request supported classes | Request supported classes | ||
Line 240: | Line 268: | ||
Supported classes response | Supported classes response | ||
− | 01 09 01 41 C9 0C 00 04 10 UU CR | + | 01 09 01 41 C9 0C 00 04 10 03 CR |
+ | |||
+ | Request: 01 04 00 41 UU CR | ||
+ | Answer: | ||
+ | <B>C2 C3 C4 C5 C6 C7 C8 C9 C10 C11 C12</B> | ||
+ | 01 09 01 41 C9 0C 00 04 11 04 62 | ||
+ | |||
+ | C2= Start | ||
+ | C3= length | ||
+ | C4= | ||
+ | C5= | ||
+ | C6= | ||
+ | C7= | ||
+ | C8= | ||
+ | C9= Basic class (1=controller, 2= static controller, 3=slave, 4=routing slave) | ||
+ | C10= Device type (1=controller, 10=switch, 11=Dimmer, 12=transmitter, 8=Thermostat, 9=shutter,21=?) | ||
+ | C11= | ||
+ | C12= CRC | ||
+ | |||
+ | |||
Where UU is the unit number to switch ON - OFF and CR is the XORING AND checksum for the frame | Where UU is the unit number to switch ON - OFF and CR is the XORING AND checksum for the frame | ||
− | ==== RZS15 Vizia Leviton Wall switch ==== | + | ==== RZS15 Vizia Leviton Wall switch 908.42Mhz ==== |
− | Supports classes: 25,27,2B,2C | + | Supports classes: 25, 27, 2B, 2C, 85, 72, 86, 91, 77, 73, EF, 82 |
Manufacturer ID: 0 1D (Leviton) | Manufacturer ID: 0 1D (Leviton) | ||
− | Type: | + | Type: 301 ID: 206 |
Version: Lib: 2.6 App: 0.3 | Version: Lib: 2.6 App: 0.3 | ||
+ | COMMAND_CLASS_SWITCH_BINARY, 25 | ||
+ | COMMAND_CLASS_SWITCH_ALL, 27 | ||
+ | COMMAND_CLASS_SCENE_ACTIVATION, 2B | ||
+ | COMMAND_CLASS_SCENE_ACTUATOR_CONF, 2C | ||
+ | COMMAND_CLASS_ASSOCIATION, 85 | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 | ||
+ | COMMAND_CLASS_VERSION, 86 | ||
+ | COMMAND_CLASS_MANUFACTURER_PROPRIETARY, 91 | ||
+ | COMMAND_CLASS_NODE_NAMING, 77 | ||
+ | COMMAND_CLASS_POWERLEVEL, 73 | ||
+ | COMMAND_CLASS_MARK, EF | ||
+ | COMMAND_CLASS_HAIL, 82 | ||
− | ==== RZP03 Vizia Leviton Appliance Module dimmer ==== | + | ==== RZP03 Vizia Leviton Appliance Module dimmer 908.42Mhz ==== |
− | Device supports classes: 26,27,2B,2C | + | Device supports classes: 26, 27, 2B, 2C, 85, 72, 86, 91, 77, 73, EF, 82 |
− | Manufacturer ID: | + | Manufacturer ID: 00 1D(Leviton) Type: 201 ID: 206 |
+ | Lib: 2.6 App: 0.3 | ||
The difference between a switch and a dimmer is the class <B>26</B> for dimmer and 25 for switch | The difference between a switch and a dimmer is the class <B>26</B> for dimmer and 25 for switch | ||
+ | COMMAND_CLASS_SWITCH_MULTILEVEL, 26 | ||
+ | COMMAND_CLASS_SWITCH_ALL, 27 | ||
+ | COMMAND_CLASS_SCENE_ACTIVATION, 2B | ||
+ | COMMAND_CLASS_SCENE_ACTUATOR_CONF, 2C | ||
+ | COMMAND_CLASS_ASSOCIATION, 85 | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 | ||
+ | COMMAND_CLASS_VERSION, 86 | ||
+ | COMMAND_CLASS_MANUFACTURER_PROPRIETARY, 91 | ||
+ | COMMAND_CLASS_NODE_NAMING, 77 | ||
+ | COMMAND_CLASS_POWERLEVEL, 73 | ||
+ | COMMAND_CLASS_MARK, EF | ||
+ | COMMAND_CLASS_HAIL 82 | ||
<B> Frame to send: to light ON with 9% </B> | <B> Frame to send: to light ON with 9% </B> | ||
Line 271: | Line 343: | ||
<B>With UU is equal to the unit ID and CR is the checksum (XORING)</B> | <B>With UU is equal to the unit ID and CR is the checksum (XORING)</B> | ||
+ | |||
+ | ==== VRE06 Vizia Leviton Wallplate VRE06 908.40Mhz ==== | ||
+ | |||
+ | ==== Intermatic HA04C Outdoor Lighting Module switch 908.42Mhz ==== | ||
+ | Device supports classes: 20, 25, 27, 86, 72 | ||
+ | Brand 00 05 type 00 04 ID 00 03 | ||
+ | version: Lib: 1.28 App: 2.0 | ||
+ | COMMAND_CLASS_BASIC, 20 | ||
+ | COMMAND_CLASS_SWITCH_BINARY, 25 | ||
+ | COMMAND_CLASS_SWITCH_ALL, 27 | ||
+ | COMMAND_CLASS_VERSION, 86 | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 | ||
+ | |||
+ | ==== Electronic Solutions Inc DBMZ DC motor controler ==== | ||
+ | Device supports classes: 26, 72, 86, 27, 70, 73 | ||
+ | Manufacturer ID: 00 33(Electronic Solutions Inc) Type: 5250 ID: 3032 | ||
+ | Lib: 2.24 App: 1.1 | ||
+ | The difference between a switch and a dimmer is the class 26 for dimmer and 25 for switch | ||
+ | COMMAND_CLASS_SWITCH_MULTILEVEL, 26 | ||
+ | COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 | ||
+ | COMMAND_CLASS_VERSION, 86 | ||
+ | COMMAND_CLASS_SWITCH_ALL, 27 | ||
+ | COMMAND_CLASS_CONFIGURATION, 70 | ||
+ | COMMAND_CLASS_POWERLEVEL, 73 | ||
==== Removing device 05h from the Z-TROLLER ==== | ==== Removing device 05h from the Z-TROLLER ==== | ||
Line 407: | Line 503: | ||
105210: 14.07.2008 18:07:55.707 +0.0 W 06 . | 105210: 14.07.2008 18:07:55.707 +0.0 W 06 . | ||
+ | Simple steps to add a device | ||
+ | S 01 04 00 4A 01 B0 Request the z-trolle to START adding a device | ||
+ | R 06 01 07 00 4A 02 01 00 00 B1 | ||
+ | S 06 | ||
+ | R 01 07 00 4A 02 02 00 00 B2 | ||
+ | S 06 | ||
+ | R 01 16 00 4A 02 03 12 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 24 The button was pushed | ||
+ | S 06 | ||
+ | R 01 07 00 4A 02 06 12 00 A4 The device 12h was added | ||
+ | S 06 | ||
+ | S 01 04 00 4A 05 B4 Send the z-troller a adding device completion | ||
+ | ------------------- | ||
+ | Simple steps to remove device 10h | ||
+ | S 01 04 00 4B 01 B1 Send to the z-troller a START to remove a device | ||
+ | R 06 01 07 00 4B 03 01 00 00 B1 | ||
+ | S 06 | ||
+ | R 01 07 00 4B 03 02 00 00 B2 | ||
+ | S 06 | ||
+ | R 01 16 00 4B 03 03 10 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 26 The button on the device was pushed | ||
+ | S 06 | ||
+ | R 01 07 00 4B 03 06 00 00 B6 | ||
+ | S 06 | ||
+ | S 01 04 00 4A 05 B4 Send the z-troller a END remove device | ||
+ | R 06 | ||
− | ==== Getting | + | ==== Getting neighborhood info for a unit (z-troller) ==== |
01 07 00 80 UU 00 01 03 CR | 01 07 00 80 UU 00 01 03 CR | ||
+ | |||
+ | ==== Restart the z-troller ==== | ||
+ | 01 03 00 08 F4 | ||
==== Manufacturer Specific ==== | ==== Manufacturer Specific ==== | ||
Line 480: | Line 603: | ||
LMCE will look for the next 4 bytes to get the list of devices. It seems to be a bit map. In this case, the first byte is 0x3 or in binary 00000011 so devices ID 1 and 2 are present. It is unclear to me why we only look at 4 bytes (32 zwave devices) while the protocol supports 232 | LMCE will look for the next 4 bytes to get the list of devices. It seems to be a bit map. In this case, the first byte is 0x3 or in binary 00000011 so devices ID 1 and 2 are present. It is unclear to me why we only look at 4 bytes (32 zwave devices) while the protocol supports 232 | ||
− | NOTE: this is a (already fixed) bug in the old version of the closed pluto Z-Wave driver. The actual closed driver and the new open source driver (http://svn.linuxmce.org/ | + | NOTE: this is a (already fixed) bug in the old version of the closed pluto Z-Wave driver. The actual closed driver and the new open source driver (http://svn.linuxmce.org/svn/trunk/src/ZWave) of course honor all 232 devices (29*8) |
Line 490: | Line 613: | ||
</pre> | </pre> | ||
− | Pressing "all units on" on the ZTH200: | + | Pressing "all units on" on the [[ZTH200]]: |
<pre> | <pre> | ||
41 03/28/08 15:50:58.553 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x4 0x39 (#######'#9) <0xb70f4b90> | 41 03/28/08 15:50:58.553 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x4 0x39 (#######'#9) <0xb70f4b90> | ||
Line 496: | Line 619: | ||
</pre> | </pre> | ||
− | Pressing "all units off" on the ZTH200: | + | Pressing "all units off" on the [[ZTH200]]: |
<pre> | <pre> | ||
41 03/28/08 15:51:43.713 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x5 0x38 (#######'#8) <0xb70f4b90> | 41 03/28/08 15:51:43.713 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x5 0x38 (#######'#8) <0xb70f4b90> | ||
Line 520: | Line 643: | ||
</pre> | </pre> | ||
=== Simple configuration download === | === Simple configuration download === | ||
− | A ZTH200 with a ZDP Lamp plug (id 2) in group 2 (named "Wohnzimmer" also gives us some group information: | + | A [[ZTH200]] with a ZDP Lamp plug (id 2) in group 2 (named "Wohnzimmer" also gives us some group information: |
this seems to be the group membership: | this seems to be the group membership: | ||
Line 804: | Line 927: | ||
= References = | = References = | ||
− | http://www.basshome.com/leviton_z-wave_documentation_1970_ctg.htm | + | http://www.basshome.com/leviton_z-wave_documentation_1970_ctg.htm (dead link, redirects to home page) |
http://zwaveworld.com/forum/index.php?showtopic=237 | http://zwaveworld.com/forum/index.php?showtopic=237 |
Latest revision as of 21:11, 2 January 2011
Version | Status | Date Updated | Updated By |
---|---|---|---|
710 | Unknown | N/A | N/A |
810 | Unknown | N/A | N/A |
1004 | Unknown | N/A | N/A |
1204 | Unknown | N/A | N/A |
1404 | Unknown | N/A | N/A |
Usage Information |
Contents
- 1 Introduction
- 2 API
- 2.1 Frame specification
- 2.2 Basic Classes
- 2.3 Device Types
- 2.4 Command and Device classes
- 2.4.1 Command/Device Classes
- 2.4.1.1 Basic Slave Device
- 2.4.1.2 All
- 2.4.1.3 Multilevel Switch
- 2.4.1.4 All the known classes
- 2.4.1.5 Basic
- 2.4.1.6 Mandatory
- 2.4.1.7 Multilevel Sensor
- 2.4.1.8 Setback schedule thermostat
- 2.4.1.9 HSM100 (battery, temperature, motion, light)
- 2.4.1.10 RZP15 Vizia Leviton Appliance Module switch 908.42Mhz
- 2.4.1.11 RZS15 Vizia Leviton Wall switch 908.42Mhz
- 2.4.1.12 RZP03 Vizia Leviton Appliance Module dimmer 908.42Mhz
- 2.4.1.13 VRE06 Vizia Leviton Wallplate VRE06 908.40Mhz
- 2.4.1.14 Intermatic HA04C Outdoor Lighting Module switch 908.42Mhz
- 2.4.1.15 Electronic Solutions Inc DBMZ DC motor controler
- 2.4.1.16 Removing device 05h from the Z-TROLLER
- 2.4.1.17 Adding device 12h to the Z-TROLLER (vizia switch)
- 2.4.1.18 Getting neighborhood info for a unit (z-troller)
- 2.4.1.19 Restart the z-troller
- 2.4.1.20 Manufacturer Specific
- 2.4.1.21 Version
- 2.4.1.22 All Switch
- 2.4.1.23 Configuration
- 2.4.1.24 Power Level
- 2.4.1 Command/Device Classes
- 2.5 Device configuration data
- 3 Traces
- 4 Pluto Source Code
- 5 Framing
- 6 Capturing your own sample transactions
- 7 References
- 8 Tools used
- 9 Links
Introduction
The ZWave API is not available for free. You have to get the Zensys SDK for command specifications and device class definitions. This page tries to collect all the freely available information about ZWave. The final goal is to provide a header file with all necessary definitions for basic operation with open source software.
IMPORTANT: all information added to this page _must_ have a reference to the source where it came from.
API
Frame specification
Karl Denninger implemented basic ZWave support in his software "HomeDaemon". He advised that basic frame specification can be derived from his source code (http://www.denninger.net/homedaemon.htm).
Basic Classes
From the Leviton Z-Wave RS232 ASCII Interface Programming Guide (RZC0P-1LW, 10/9/2007):
Controller 1 Static controller 2 Slave 3 Routing Slave 4
that leads us to some definitions:
#define OZA_BASIC_CLASS_CONTROLLER 0x01 #define OZA_BASIC_CLASS_STATIC_CONTROLLER 0x02 #define OZA_BASIC_CLASS_SLAVE 0x03 #define OZA_BASIC_CLASS_ROUTING_SLAVE 0x04
Device Types
From the Z-Wave Configuration Information-1.pdf:
CONTROLLER 0x01 (like the ZTH200, Classes: ) SWITCH/APPLIANCE 0x10 (ZRP200, Classes: 25, 27, 75) DIMMER 0x11 (ZDP200, ZDW230, .., Classes: 26, 27, 75, ...) TRANSMITTER 0x12 THERMOSTAT 0x08 SHUTTER 0x09
Command and Device classes
From the Electronic Solutions, Inc. DBMZ Advanced User manual:
Command/Device Classes
Basic Slave Device
All
Multilevel Switch
- COMMAND_CLASS_SWITCH_MULTILEVEL
MULTILEVEL_SWITCH_GET MULTILEVEL_SWITCH_SET MULTILEVEL_SWITCH_START_LEVEL_CHANGE MULTILEVEL_SWITCH_STOP_LEVEL_CHANGE
additional information from http://zwaveworld.com/forum/index.php?showtopic=237:
>?FI003,017,000 //basic class 3 (slave), generic class 0x11 (multlevel switch), specific class 0
All the known classes
COMMAND_CLASS_BASIC 0x20
COMMAND_CLASS_BATTERY 0x80
COMMAND_CLASS_WAKE_UP 0x84
COMMAND_CLASS_CONTROLLER_REPLICATION 0x21
COMMAND_CLASS_SWITCH_MULTILEVEL 0x26
COMMAND_CLASS_SWITCH_ALL 0x27
COMMAND_CLASS_SENSOR_BINARY 0x30
COMMAND_CLASS_ALARM 0x71
COMMAND_CLASS_MULTI_CMD 0x8F
COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE 0x46
COMMAND_CLASS_CLOCK 0x81
COMMAND_CLASS_ASSOCIATION 0x85
COMMAND_CLASS_CONFIGURATION 0x70
COMMAND_CLASS_MANUFACTURER_SPECIFIC 0x72
-
COMMAND_CLASS_SCENE_ACTIVATION 0x2B
COMMAND_CLASS_SCENE_ACTUATOR_CONF 0x2C
COMMAND_CLASS_MANUFACTURER_SPECIFIC 0x72
COMMAND_CLASS_VERSION 0x86
COMMAND_CLASS_MANUFACTURER_PROPRIETARY 0x91
COMMAND_CLASS_NODE_NAMING 0x77
COMMAND_CLASS_POWERLEVEL 0x73
COMMAND_CLASS_MARK 0xEF
COMMAND_CLASS_HAIL 0x82
COMMAND_CLASS_MULTI_INSTANCE 0x60
COMMAND_CLASS_SENSOR_MULTILEVEL 0x31
COMMAND_CLASS_SWITCH_BINARY 0x25
Basic
- COMMAND_CLASS_BASIC
BASIC_GET BASIC_SET
Mandatory
Multilevel Sensor
(from the Vizia RF Application Note)
- COMMAND_CLASS_SENSOR_MULTILEVEL
example get:
>N4SE49,4 (RZC0P Syntax)
sensor report:
<N004:049,005,001,009,075 049: device class 005: command report 001: value send is a temperature value 009: value represented with 1 byte in degrees fahrenheit 075: 75° F
Setback schedule thermostat
from http://www.innovus.dk/fileadmin/user_upload/manual/VD2_standard_01_RA-PLUS.pdf
Supported: COMMAND_CLASS_ASSOCIATION COMMAND_CLASS_BATTERY COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE COMMAND_CLASS_MANUFACTURER_SPECIFIC COMMAND_CLASS_MULTI_CMD COMMAND_CLASS_VERSION COMMAND_CLASS_WAKE_UP Controlled: COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE COMMAND_CLASS_CLOCK COMMAND_CLASS_MULTI_CMD
HSM100 (battery, temperature, motion, light)
The HSM100 is a motion sensor (probably the best as for now) (2008)
Device supports classes: 60, 31, 70, 84, 85, 80, 72, 77, 86 Manufacturer ID: 1E (HomeSeer) Type: 02 ID: 01 Lib: 2.31 App: 1.4 Also know with Lib: 2.40 App: 1.6 or App: 1.7 COMMAND_CLASS_MULTI_INSTANCE, 60 COMMAND_CLASS_SENSOR_MULTILEVEL, 31 COMMAND_CLASS_CONFIGURATION, 70 COMMAND_CLASS_WAKE_UP, 84 COMMAND_CLASS_ASSOCIATION, 85 COMMAND_CLASS_BATTERY, 80 COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 COMMAND_CLASS_NODE_NAMING, 77 COMMAND_CLASS_VERSION 86
The following frame from personal observations is described below
0030.354<01 05 00 13 03 00 EA
0030.344<06 01 04 01 13 01 E8
0030.244<01 09 00 04 00 0A 03 80 03 64 1C BATTERY 100%
0030.233<01 05 00 13 03 00 EA
0030.223<01 04 01 13 01 E8
0030.223<06
0030.193<06 02 31 05 03 01 00 A5 LIGHT 1%
0030.193<01 0E 00 04 00 0A 08 60
0030.183<01 05 00 13 03 00 EA
0030.173<01 04 01 13 01 E8
0030.163<06
0030.063<06 03 31 05 01 2A 02 D5 5A TEMPERATURE 72.5F
0030.063<01 0F 00 04 00 0A 09 60
0029.743<01 05 00 13 03 00 EA
0029.733<01 04 01 13 01 E8
0029.733<06
0029.593<01 08 00 04 00 0A 02 84 07 78
The HSM100 when awake send a frame and stay awake for about 2.5 seconds to answer to request. 01 08 00 UU 00 03 02 84 07 CR when this frame is received if we need to get the temperature we have to send 01 0C 00 13 UU 05 60 06 03 31 04 05 03 ...and to get the light % 01 0C 00 13 UU 05 60 06 02 31 04 05 03 if there is a change in light level or temperature a frame will be answered by the HSM100 to indicate the temperature or / and the light level
Light % level Let's take the frame
06 02 31 05 03 01 02 A7
'VB express 2008 sample code to get the light level in % If InStr(temp, "06 02 31 05 03") Then j = InStr(temp, "06 02 31 05 03") carac = Mid(temp, j + 18, 5) resultat = carac & "-" & HexToDec(Mid(temp, j + 18, 2)) & "%" End If
Temperature measure
06 03 31 05 01 2A 02 E2 6D
j = InStr(temp, "06 03 31 05 01") carac = Mid(temp, j + 18, 5) If carac <> "" Then temperature1 = HexToDec(Mid(temp, j + 21, 2)) If HexToDec(Mid(temp, j + 18, 2)) = 3 Then temperature1 = ((temperature1 - 25) / 10) + 79.3 End If
If HexToDec(Mid(temp, j + 18, 2)) = 2 Then temperature1 = ((temperature1 - 170) / 10) + 68.2 End If
If HexToDec(Mid(temp, j + 18, 2)) = 1 Then temperature1 = ((temperature1 - 170) / 10) + 41.1 End If ' in case °celsius are requested instead of °F tc = Format((5 / 9) * (temperature1 - 32), "##.#") temp = temperature1 calculate_temperature = temp End If
Motion detection for module with address 7
01 09 00 04 00 07 03 20 01 00 no move
01 09 00 04 00 07 03 20 01 FF move
C O N F I G U R A T I O N HSM100
SET Unit 0Ch to report no move delay after 1 minute
01 0C 00 13 0C 05 70 04 02 01 01 05 03 99
set unit 0Ch to wake up every 6 minutes
01 0D 00 13 0C 06 84 04 00 01 68 01 05 03 05
set unit 0Ch to wake up every 12 minutes
01 0D 00 13 0C 06 84 04 00 02 D0 01 05 03 BE
set unit 12 to wake up every 18 minutes
01 0D 00 13 0C 06 84 04 00 04 38 01 05 03 50
Set unit 0Ch led off
01 0C 00 13 0C 05 70 04 03 01 00 05 03 99
Set unit 0Ch led ON
01 0C 00 13 0C 05 70 04 03 01 FF 05 03 66
Get sofware association for unit 0Ch Write 01 0A 00 13 0C 03 85 02 01 05 03 69 Read 01 0C 00 04 00 0C 06 85 03 01 04 00 01 7F // YES associated OR Read 01 0B 00 04 00 0C 05 85 03 01 04 00 7A // NOT associated
Remove software association Unit 0Ch
01 0B 00 13 0C 04 85 04 01 01 05 03 68
Set software association Unit 0ch
01 0B 00 13 0C 04 85 01 01 01 05 03 6D
Force to optimize Unit 0Ch
01 05 00 48 0C 03 BD 01 04 00 4A 05 B4
RZP15 Vizia Leviton Appliance Module switch 908.42Mhz
supports classes: 25, 27, 2B, 2C, 85, 72, 86, 91, 77, 73, EF, 82 manufacturer ID: 00 1D (Leviton) Type: 101 ID: 206 version: Lib: 2.6 App: 0.3 COMMAND_CLASS_SWITCH_BINARY, 25 COMMAND_CLASS_SWITCH_ALL, 27 COMMAND_CLASS_SCENE_ACTIVATION, 2B COMMAND_CLASS_SCENE_ACTUATOR_CONF, 2C COMMAND_CLASS_ASSOCIATION, 85 COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 COMMAND_CLASS_VERSION, 86 COMMAND_CLASS_MANUFACTURER_PROPRIETARY, 91 COMMAND_CLASS_NODE_NAMING, 77 COMMAND_CLASS_POWERLEVEL, 73 COMMAND_CLASS_MARK, EF COMMAND_CLASS_HAIL, 82
Frame to send ON 01 0A 00 13 UU 03 20 01 63 05 03 CR
Frame to send OFF 01 0A 00 13 UU 03 20 01 00 05 03 CR
Request supported classes 01 04 00 41 UU CR
Supported classes response 01 09 01 41 C9 0C 00 04 10 03 CR Request: 01 04 00 41 UU CR Answer: C2 C3 C4 C5 C6 C7 C8 C9 C10 C11 C12 01 09 01 41 C9 0C 00 04 11 04 62 C2= Start C3= length C4= C5= C6= C7= C8= C9= Basic class (1=controller, 2= static controller, 3=slave, 4=routing slave) C10= Device type (1=controller, 10=switch, 11=Dimmer, 12=transmitter, 8=Thermostat, 9=shutter,21=?) C11= C12= CRC
Where UU is the unit number to switch ON - OFF and CR is the XORING AND checksum for the frame
RZS15 Vizia Leviton Wall switch 908.42Mhz
Supports classes: 25, 27, 2B, 2C, 85, 72, 86, 91, 77, 73, EF, 82 Manufacturer ID: 0 1D (Leviton) Type: 301 ID: 206 Version: Lib: 2.6 App: 0.3 COMMAND_CLASS_SWITCH_BINARY, 25 COMMAND_CLASS_SWITCH_ALL, 27 COMMAND_CLASS_SCENE_ACTIVATION, 2B COMMAND_CLASS_SCENE_ACTUATOR_CONF, 2C COMMAND_CLASS_ASSOCIATION, 85 COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 COMMAND_CLASS_VERSION, 86 COMMAND_CLASS_MANUFACTURER_PROPRIETARY, 91 COMMAND_CLASS_NODE_NAMING, 77 COMMAND_CLASS_POWERLEVEL, 73 COMMAND_CLASS_MARK, EF COMMAND_CLASS_HAIL, 82
RZP03 Vizia Leviton Appliance Module dimmer 908.42Mhz
Device supports classes: 26, 27, 2B, 2C, 85, 72, 86, 91, 77, 73, EF, 82 Manufacturer ID: 00 1D(Leviton) Type: 201 ID: 206 Lib: 2.6 App: 0.3 The difference between a switch and a dimmer is the class 26 for dimmer and 25 for switch COMMAND_CLASS_SWITCH_MULTILEVEL, 26 COMMAND_CLASS_SWITCH_ALL, 27 COMMAND_CLASS_SCENE_ACTIVATION, 2B COMMAND_CLASS_SCENE_ACTUATOR_CONF, 2C COMMAND_CLASS_ASSOCIATION, 85 COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 COMMAND_CLASS_VERSION, 86 COMMAND_CLASS_MANUFACTURER_PROPRIETARY, 91 COMMAND_CLASS_NODE_NAMING, 77 COMMAND_CLASS_POWERLEVEL, 73 COMMAND_CLASS_MARK, EF COMMAND_CLASS_HAIL 82
Frame to send: to light ON with 9% 01 0A 00 13 UU 03 20 01 09 05 03 CR
Frame to send: to light ON with 95% 01 0A 00 13 UU 03 20 01 5F 05 03 CR
Frame to switch off 01 0A 00 13 UU 03 20 01 00 05 03 CR
Request supported classes unit 02 01 04 00 41 02 B8 Supported classes response 06 01 09 01 41 C9 0C 00 04 11 04 62
With UU is equal to the unit ID and CR is the checksum (XORING)
VRE06 Vizia Leviton Wallplate VRE06 908.40Mhz
Intermatic HA04C Outdoor Lighting Module switch 908.42Mhz
Device supports classes: 20, 25, 27, 86, 72 Brand 00 05 type 00 04 ID 00 03 version: Lib: 1.28 App: 2.0 COMMAND_CLASS_BASIC, 20 COMMAND_CLASS_SWITCH_BINARY, 25 COMMAND_CLASS_SWITCH_ALL, 27 COMMAND_CLASS_VERSION, 86 COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72
Electronic Solutions Inc DBMZ DC motor controler
Device supports classes: 26, 72, 86, 27, 70, 73 Manufacturer ID: 00 33(Electronic Solutions Inc) Type: 5250 ID: 3032 Lib: 2.24 App: 1.1 The difference between a switch and a dimmer is the class 26 for dimmer and 25 for switch COMMAND_CLASS_SWITCH_MULTILEVEL, 26 COMMAND_CLASS_MANUFACTURER_SPECIFIC, 72 COMMAND_CLASS_VERSION, 86 COMMAND_CLASS_SWITCH_ALL, 27 COMMAND_CLASS_CONFIGURATION, 70 COMMAND_CLASS_POWERLEVEL, 73
Removing device 05h from the Z-TROLLER
029178: 14.07.2008 17:48:28.899 +0.0 W 01 04 00 4B 01 B1 Waiting a unit button get pressed 029181: 14.07.2008 17:48:28.914 +0.0 R 06 01 07 00 4B 02 01 00 00 B0 029182: 14.07.2008 17:48:28.914 +0.0 W 06 029461: 14.07.2008 17:48:33.242 +0.0 R 01 07 00 4B 02 02 00 00 B3 029464: 14.07.2008 17:48:33.257 +0.0 W 06 029491: 14.07.2008 17:48:33.648 +0.0 R 01 16 00 4B 02 03 05 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 32 029494: 14.07.2008 17:48:33.663 +0.0 W 06 029501: 14.07.2008 17:48:33.741 +0.0 R 01 07 00 4B 02 06 00 00 B7 029504: 14.07.2008 17:48:33.757 +0.0 W 06 029590: 14.07.2008 17:48:35.069 +0.0 W 01 04 00 4A 05 B4 Confirm unit 5 has been removed
Adding device 12h to the Z-TROLLER (vizia switch)
104436: 14.07.2008 18:07:46.521 +0.0 W 01 04 00 4A 01 B0 ...J.° 104439: 14.07.2008 18:07:46.536 +0.0 R 06 01 07 00 4A 02 01 00 00 B1 ....J....± 104440: 14.07.2008 18:07:46.536 +0.0 W 06 104589: 14.07.2008 18:07:48.833 +0.0 R 01 . 104591: 14.07.2008 18:07:48.848 +0.0 R 07 00 4A 02 02 00 00 B2 ..J....² 104592: 14.07.2008 18:07:48.848 +0.0 W 06 104601: 14.07.2008 18:07:48.958 +0.0 R 01 . 104603: 14.07.2008 18:07:48.973 +0.0 R 16 00 4A 02 03 12 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 24 wsï$ 104604: 14.07.2008 18:07:48.973 +0.0 W 06 104647: 14.07.2008 18:07:49.614 +0.0 R 01 07 00 4A 02 06 12 00 A4 ...J....¤ 104648: 14.07.2008 18:07:49.614 +0.0 W 06 104714: 14.07.2008 18:07:50.614 +0.0 W 01 04 00 4A 05 B4 ...J.´ 104717: 14.07.2008 18:07:50.629 +0.0 R 06 104914: 14.07.2008 18:07:53.691 +0.0 W 01 03 00 02 FE 104917: 14.07.2008 18:07:53.707 +0.0 R 06 . 104919: 14.07.2008 18:07:53.722 +0.0 R 01 . 104921: 14.07.2008 18:07:53.738 +0.0 R 25 01 02 04 00 1D 6F BB 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 104923: 14.07.2008 18:07:53.754 +0.0 R 00 00 00 00 00 00 00 00 00 00 02 01 15 104924: 14.07.2008 18:07:53.754 +0.0 W 06 . 104928: 14.07.2008 18:07:53.785 +0.0 W 01 04 00 41 01 BB ...A.» 104931: 14.07.2008 18:07:53.801 +0.0 R 06 01 09 01 41 92 06 00 02 02 00 22 104932: 14.07.2008 18:07:53.801 +0.0 W 06 . 104936: 14.07.2008 18:07:53.832 +0.0 W 01 04 00 41 02 B8 ...A.¸ 104939: 14.07.2008 18:07:53.847 +0.0 R 06 01 09 01 41 C9 0C 00 04 11 04 62 104940: 14.07.2008 18:07:53.847 +0.0 W 06 . 104944: 14.07.2008 18:07:53.879 +0.0 W 01 04 00 41 03 B9 ...A.¹ 104947: 14.07.2008 18:07:53.894 +0.0 R 06 01 09 01 41 C9 0C 00 04 10 03 64 104948: 14.07.2008 18:07:53.894 +0.0 W 06 . 104952: 14.07.2008 18:07:53.926 +0.0 W 01 04 00 41 04 BE ...A.¾ 104955: 14.07.2008 18:07:53.941 +0.0 R 06 01 09 01 41 C9 0C 00 04 10 03 64 104956: 14.07.2008 18:07:53.941 +0.0 W 06 . 104960: 14.07.2008 18:07:53.972 +0.0 W 01 04 00 41 06 BC ...A.¼ 104963: 14.07.2008 18:07:53.988 +0.0 R 06 01 09 01 41 C9 0C 00 04 10 03 64 ....AÉ.....d 104964: 14.07.2008 18:07:53.988 +0.0 W 06 . 104968: 14.07.2008 18:07:54.019 +0.0 W 01 04 00 41 07 BD ...A.½ 104971: 14.07.2008 18:07:54.035 +0.0 R 06 01 09 01 41 49 0C 00 04 21 01 D7 ....AI...!.× 104972: 14.07.2008 18:07:54.035 +0.0 W 06 . 104976: 14.07.2008 18:07:54.066 +0.0 W 01 04 00 41 09 B3 ...A.³ 104979: 14.07.2008 18:07:54.082 +0.0 R 06 01 09 01 41 51 0C 00 04 21 01 CF ....AQ...!.Ï 104980: 14.07.2008 18:07:54.082 +0.0 W 06 . 104984: 14.07.2008 18:07:54.113 +0.0 W 01 04 00 41 0A B0 ...A.° 104987: 14.07.2008 18:07:54.129 +0.0 R 06 01 09 01 41 51 0C 00 04 21 01 CF ....AQ...!.Ï 104988: 14.07.2008 18:07:54.129 +0.0 w 06 . 104992: 14.07.2008 18:07:54.160 +0.0 W 01 04 00 41 0C B6 ...A.¶ 104995: 14.07.2008 18:07:54.176 +0.0 R 06 01 09 01 41 51 0C 00 04 21 01 CF ....AQ...!.Ï 104996: 14.07.2008 18:07:54.176 +0.0 W 06 . 105000: 14.07.2008 18:07:54.207 +0.0 W 01 04 00 41 0D B7 ...A.· 105003: 14.07.2008 18:07:54.222 +0.0 R 06 01 09 01 41 51 0C 00 04 21 01 CF ....AQ...!.Ï 105004: 14.07.2008 18:07:54.222 +0.0 W 06 . 105008: 14.07.2008 18:07:54.254 +0.0 W 01 04 00 41 0E B4 ...A.´ 105011: 14.07.2008 18:07:54.269 +0.0 R 06 01 09 01 41 C9 0C 00 04 10 03 64 ....AÉ.....d 105012: 14.07.2008 18:07:54.269 +0.0 W 06 . 105016: 14.07.2008 18:07:54.301 +0.0 W 01 04 00 41 10 AA ...A.ª 105019: 14.07.2008 18:07:54.316 +0.0 R 06 01 09 01 41 49 0C 00 04 21 01 D7 ....AI...!.× 105020: 14.07.2008 18:07:54.316 +0.0 W 06 . 105024: 14.07.2008 18:07:54.347 +0.0 W 01 04 00 41 12 A8 ...A.¨ 105027: 14.07.2008 18:07:54.363 +0.0 R 06 01 09 01 41 C9 0C 00 04 10 03 64 ....AÉ.....d 105028: 14.07.2008 18:07:54.363 +0.0 W 06 . 105032: 14.07.2008 18:07:54.394 +0.0 W 01 07 00 03 01 02 00 00 F8 ........ø 105035: 14.07.2008 18:07:54.410 +0.0 R 06 . 105038: 14.07.2008 18:07:54.441 +0.0 W 01 03 00 20 DC ... Ü 105041: 14.07.2008 18:07:54.457 +0.0 R 06 01 08 01 20 00 3D 0C 9E 01 78 .... .=..x 105042: 14.07.2008 18:07:54.457 +0.0 W 06 . 105046: 14.07.2008 18:07:54.488 +0.0 W 01 04 00 60 12 89 ...`. 105049: 14.07.2008 18:07:54.504 +0.0 R 06 01 04 01 60 01 9B ....`. 105050: 14.07.2008 18:07:54.504 +0.0 W 06 . 105057: 14.07.2008 18:07:54.582 +0.0 R 01 15 00 49 84 12 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 A1 wsï¡ 105058: 14.07.2008 18:07:54.582 +0.0 W 06 . 105062: 14.07.2008 18:07:54.613 +0.0 W 01 09 00 13 12 02 72 04 05 03 85 ......r... 105065: 14.07.2008 18:07:54.629 +0.0 R 06 01 04 01 13 01 E8 ......è 105066: 14.07.2008 18:07:54.629 +0.0 W 06 . 105071: 14.07.2008 18:07:54.675 +0.0 R 01 05 00 13 03 00 EA ......ê 105072: 14.07.2008 18:07:54.675 +0.0 W 06 . 105075: 14.07.2008 18:07:54.691 +0.0 R 01 0E 00 04 00 12 08 72 05 00 1D 01 01 02 06 81 .......r....... 105076: 14.07.2008 18:07:54.691 +0.0 W 06 . 105080: 14.07.2008 18:07:54.722 +0.0 W 01 09 00 13 12 02 86 11 05 03 64 .........d 105083: 14.07.2008 18:07:54.738 +0.0 R 06 01 04 01 13 01 E8 ......è 105084: 14.07.2008 18:07:54.738 +0.0 W 06 . 105089: 14.07.2008 18:07:54.785 +0.0 R 01 05 00 13 03 00 EA ......ê 105090: 14.07.2008 18:07:54.785 +0.0 W 06 . 105093: 14.07.2008 18:07:54.800 +0.0 R 01 0D 00 04 00 12 07 86 12 03 02 06 00 03 73 .............s 105094: 14.07.2008 18:07:54.800 +0.0 W 06 . 105098: 14.07.2008 18:07:54.832 +0.0 W 01 09 00 13 12 02 85 05 05 03 73 ...... ...s 105101: 14.07.2008 18:07:54.847 +0.0 R 06 01 04 01 13 01 E8 ......è 105102: 14.07.2008 18:07:54.847 +0.0 W 06 . 105107: 14.07.2008 18:07:54.894 +0.0 R 01 05 00 13 03 00 EA ......ê 105108: 14.07.2008 18:07:54.894 +0.0 W 06 . 105111: 14.07.2008 18:07:54.910 +0.0 R 01 09 00 04 00 12 03 85 06 01 61 ....... ..a 105112: 14.07.2008 18:07:54.910 +0.0 W 06 . 105116: 14.07.2008 18:07:54.941 +0.0 W 01 0B 00 13 12 04 85 01 01 01 05 03 73 ...... .....s 105119: 14.07.2008 18:07:54.957 +0.0 R 06 01 04 01 13 01 E8 ......è 105120: 14.07.2008 18:07:54.957 +0.0 W 06 . 105125: 14.07.2008 18:07:55.004 +0.0 R 01 05 00 13 03 00 EA ......ê 105126: 14.07.2008 18:07:55.004 +0.0 W 06 . 105130: 14.07.2008 18:07:55.035 +0.0 W 01 04 00 47 12 AE ...G.® 105133: 14.07.2008 18:07:55.050 +0.0 R 06 01 04 01 47 01 BC ....G.¼ 105134: 14.07.2008 18:07:55.050 +0.0 W 06 . 105147: 14.07.2008 18:07:55.222 +0.0 R 01 . 105149: 14.07.2008 18:07:55.238 +0.0 R 05 00 47 04 00 B9 ..G..¹ 105150: 14.07.2008 18:07:55.238 +0.0 W 06 . 105154: 14.07.2008 18:07:55.269 +0.0 W 01 05 00 46 12 01 AF ...F..¯ 105157: 14.07.2008 18:07:55.285 +0.0 R 06 01 04 01 46 01 BD ....F.½ 105158: 14.07.2008 18:07:55.285 +0.0 W 06 . 105173: 14.07.2008 18:07:55.488 +0.0 R 01 05 00 46 85 00 39 ...F .9 105174: 14.07.2008 18:07:55.488 +0.0 W 06 . 105178: 14.07.2008 18:07:55.519 +0.0 W 01 09 00 13 12 02 77 05 05 03 81 ......w... 105181: 14.07.2008 18:07:55.535 +0.0 R 06 01 04 01 13 01 E8 ......è 105182: 14.07.2008 18:07:55.535 +0.0 W 06 . 105187: 14.07.2008 18:07:55.582 +0.0 R 01 05 00 13 03 00 EA ......ê 105188: 14.07.2008 18:07:55.582 +0.0 W 06 . 105191: 14.07.2008 18:07:55.597 +0.0 R 01 08 00 04 00 12 02 77 06 92 .......w. 105192: 14.07.2008 18:07:55.597 +0.0 W 06 . 105196: 14.07.2008 18:07:55.628 +0.0 W 01 09 00 13 12 02 77 02 05 03 86 ......w... 105199: 14.07.2008 18:07:55.644 +0.0 R 06 01 04 01 13 01 E8 ......è 105200: 14.07.2008 18:07:55.644 +0.0 W 06 . 105205: 14.07.2008 18:07:55.691 +0.0 R 01 05 00 13 03 00 EA ......ê 105206: 14.07.2008 18:07:55.691 +0.0 W 06 . 105209: 14.07.2008 18:07:55.707 +0.0 R 01 08 00 04 00 12 02 77 03 97 .......w. 105210: 14.07.2008 18:07:55.707 +0.0 W 06 .
Simple steps to add a device S 01 04 00 4A 01 B0 Request the z-trolle to START adding a device R 06 01 07 00 4A 02 01 00 00 B1 S 06 R 01 07 00 4A 02 02 00 00 B2 S 06 R 01 16 00 4A 02 03 12 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 24 The button was pushed S 06 R 01 07 00 4A 02 06 12 00 A4 The device 12h was added S 06 S 01 04 00 4A 05 B4 Send the z-troller a adding device completion ------------------- Simple steps to remove device 10h S 01 04 00 4B 01 B1 Send to the z-troller a START to remove a device R 06 01 07 00 4B 03 01 00 00 B1 S 06 R 01 07 00 4B 03 02 00 00 B2 S 06 R 01 16 00 4B 03 03 10 0F 04 10 03 25 27 2B 2C 85 72 86 91 77 73 EF 82 26 The button on the device was pushed S 06 R 01 07 00 4B 03 06 00 00 B6 S 06 S 01 04 00 4A 05 B4 Send the z-troller a END remove device R 06
Getting neighborhood info for a unit (z-troller)
01 07 00 80 UU 00 01 03 CR
Restart the z-troller
01 03 00 08 F4
Manufacturer Specific
- COMMAND_CLASS_MANUFACTURER_SPECIFIC
Show the ESI product data:
MANUFACTURER_SPECIFIC_GET
Example return message:
0x00 0x33 0x52 0x50 0x30 0x32 0x00: maunfacturer id high byte 0x33: manufacturer id low byte, ID: 0x0033 Product type ID "RP" Product ID "02"
Version
- COMMAND_CLASS_VERSION
VERSION_GET
Example return message:
0x04 0x02 0x06 0x01 0x01 0x5a 0x04: Library type 4 for basic slave device 0x02: Protocol version 2 0x06: Protocol sub version 6 0x01: Application version 1 0x01: Application sub version 1 0x5a: ?
All Switch
- COMMAND_CLASS_SWITCH_ALL
SWITCH_ALL_GET SWITCH_ALL_ON SWITCH_ALL_OFF
Configuration
- COMMAND_CLASS_CONFIGURATION
Each parameter is a single byte ("0" or "1")
CONFIGURATION_GET CONFIGURATION_SET
Power Level
- COMMAND_CLASS_POWERLEVEL
POWERLEVEL_TEST_NODE_SET POWERLEVEL_TEST_NODE_GET POWERLEVEL_TEST_NODE_REPORT
Example: POWERLEVEL_SET, 5, 60 set the ZWave node's power level to 5 for the length of 60 seconds
Device configuration data
Traces
Starting the ZWave device:
40 03/28/08 15:53:34.590 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb698bb90> 41 03/28/08 15:53:34.741 0x6 0x1 0x10 0x1 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x32 0x2e 0x33 0x31 0x0 0x1 0x96 (#####Z-Wave 2.31###) <0xb718cb90> 40 03/28/08 15:53:34.792 0x1 0x3 0x0 0x20 0xdc (### #) <0xb698bb90> 41 03/28/08 15:53:35.042 0x6 0x1 0x8 0x1 0x20 0x0 0x0 0x55 0x28 0x2 0xa9 (#### ##U(##) <0xb718cb90> 40 03/28/08 15:53:35.092 0x1 0x3 0x0 0x2 0xfe (#####) <0xb698bb90> 41 03/28/08 15:53:35.342 0x6 0x1 0x25 0x1 0x2 0x4 0x4 0x1d 0x3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2 0x1 0xc4 (##%#) <0xb718cb90> 40 03/28/08 15:53:35.393 0x1 0x4 0x0 0x52 0x1 0xa8 (###R##) <0xb698bb90> 41 03/28/08 15:53:35.643 0x6 0x1 0x4 0x1 0x52 0x1 0xa9 (####R##) <0xb718cb90> 40 03/28/08 15:53:35.694 0x1 0x3 0x0 0x56 0xaa (###V#) <0xb698bb90> 41 03/28/08 15:53:35.944 0x6 0x1 0x4 0x1 0x56 0x0 0xac (####V##) <0xb718cb90> 40 03/28/08 15:53:35.995 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb698bb90> 41 03/28/08 15:53:36.245 0x6 0x1 0x9 0x1 0x41 0xc9 0x0 0x0 0x3 0x11 0x0 0x6d (####A######m) <0xb718cb90> 40 03/28/08 15:53:36.296 0x1 0x4 0x0 0x41 0x2 0xb8 (###A##) <0xb698bb90> 41 03/28/08 15:53:36.545 0x6 0x1 0x9 0x1 0x41 0xd2 0x6 0x0 0x2 0x2 0x0 0x62 (####A######b) <0xb718cb90>
Interesting string:
0x1 0x2 0x4 0x4 0x1d 0x3 0x0 0x0 0x0 ... 0x1 means it is a response 0x2 means it is initialization data 0x4 is the version 0x4 is the capabilities
LMCE will look for the next 4 bytes to get the list of devices. It seems to be a bit map. In this case, the first byte is 0x3 or in binary 00000011 so devices ID 1 and 2 are present. It is unclear to me why we only look at 4 bytes (32 zwave devices) while the protocol supports 232
NOTE: this is a (already fixed) bug in the old version of the closed pluto Z-Wave driver. The actual closed driver and the new open source driver (http://svn.linuxmce.org/svn/trunk/src/ZWave) of course honor all 232 devices (29*8)
Switching on a ZDP200 lamp plug from the Orbiter:
40 03/28/08 15:49:20.707 0x1 0xa 0x0 0x13 0x1 0x3 0x26 0x1 0x63 0x5 0x6 0xa3 (#\n####&#c###) <0xb68f3b90> 41 03/28/08 15:49:21.007 0x6 0x1 0x4 0x1 0x13 0x1 0xe8 (#######) <0xb70f4b90> 41 03/28/08 15:49:21.307 0x1 0x5 0x0 0x13 0x6 0x0 0xef (#######) <0xb70f4b90>
Pressing "all units on" on the ZTH200:
41 03/28/08 15:50:58.553 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x4 0x39 (#######'#9) <0xb70f4b90> 41 03/28/08 15:50:58.854 0x1 0x8 0x0 0x4 0x0 0xef 0x2 0x27 0x4 0x3d (#######'#=) <0xb70f4b90>
Pressing "all units off" on the ZTH200:
41 03/28/08 15:51:43.713 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x5 0x38 (#######'#8) <0xb70f4b90> 41 03/28/08 15:51:44.014 0x1 0x8 0x0 0x4 0x0 0xef 0x2 0x27 0x5 0x3c (#######'#<) <0xb70f4b90>
Pressing the local switch on the ZDP200 (toggling from off to on):
41 03/28/08 15:52:37.284 0x1 0xc 0x0 0x49 0x84 0x1 0x6 0x3 0x11 0x0 0x26 0x27 0x75 0x5f (###I######&'u_) <0xb70f4b90>
Learn Mode
Start
We send:
40 04/11/08 18:25:26.852 0x1 0x4 0x0 0x50 0x1 0xaa (###P##) <0xb68d9b90>
response:
41 04/11/08 18:25:27.052 0x6 (#) <0xb70dab90> 41 04/11/08 18:25:29.763 0x1 0x7 0x0 0x50 0x2 0x1 0xef 0x0 0x44 (###P####D) <0xb70dab90> 35 04/11/08 18:25:29.763 ZWJobSetLearnMode: len = 6 buf = 0x00 0x50 0x02 0x01 0xef 0x00 <0xb68d9b90> 36 04/11/08 18:25:29.763 ZWJobSetLearnMode: start learning <0xb68d9b90>
Simple configuration download
A ZTH200 with a ZDP Lamp plug (id 2) in group 2 (named "Wohnzimmer" also gives us some group information:
this seems to be the group membership:
0x1 0xb 0x0 0x4 0x2 0xef 0x5 0x21 0x31 0x8 0x2 0x2 0x0 (#######!1####)
this is the scene information:
0x1 0x16 0x0 0x4 0x2 0xef 0x10 0x21 0x32 0x9 0x2 0x57 0x4f 0x48 0x4e 0x5a 0x49 0x4d 0x4d 0x45 0x52 0x20 0x20 0x12 (#######!2##WOHNZIMMER #)
Battery Powered devices
unsolicited wake up frame:
0x1 0x8 0x0 0x4 0x4 0x2 0x2 0x84 0x7 0x74 (#########t)
Pluto Source Code
The pluto project at one point in time included zwave control classes. The source code for these classes was published for some time at svn.plutohome.com. These classes are no longer published. However, substantial details of framing formats were derivable from that source code.
Some snippets that explain how to construct some interesting PDUs are the following (all snippets from code that was labelled GPLed at the top. Full interpretation of this code requires access to the z-wave SDK headers, which are labelled proprietary and thus are not included here):
- JobSwitchChangeLevel
setState(ZWaveJob::RUNNING); size_t len = 9; char data[9]; data[0] = REQUEST; data[1] = FUNC_ID_ZW_SEND_DATA; data[2] = (char)d->nodeID; data[3] = DATA_LEN; // 3 data[4] = COMMAND_CLASS_SWITCH_MULTILEVEL; data[5] = SWITCH_MULTILEVEL_SET; data[6] = d->level; data[7] = TRANSMIT_OPTION_ACK | TRANSMIT_OPTION_AUTO_ROUTE; data[8] = 1;
- JobSwitchBinaryGet
setState(ZWaveJob::RUNNING); size_t len = 8; char data[8]; data[0] = REQUEST; data[1] = FUNC_ID_ZW_SEND_DATA; data[2] = (char)d->nodeID; data[3] = DATA_LEN; data[4] = COMMAND_CLASS_SWITCH_MULTILEVEL; data[5] = SWITCH_BINARY_GET; data[6] = TRANSMIT_OPTION_ACK | TRANSMIT_OPTION_AUTO_ROUTE; data[7] = 2; return handler()->sendData(data, len);
- JobSetLearnNodeState
char buffer[10];
buffer[0] = REQUEST; buffer[1] = FUNC_ID_ZW_SET_LEARN_NODE_STATE; buffer[2] = mode(); buffer[3] = 1; // Callback FunctionID buffer[4] = 0;
setState(ZWaveJob::RUNNING);
d->failed = false;
return handler()->sendData(buffer, 3);
Z-Wave protocol Reset:
First command: /** */
01 08 00 03 01 02 01 01 21 D6
00 = request 03 = FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION 01 = listening /** not moving */ 02 = node generic type, GENERIC_TYPE_STATIC_CONTROLLER 01 = node specific type, SPECIFIC_TYPE_PORTABLE_REMOTE_CONTROLLER 01 = param length 21 = COMMAND_CLASS_CONTROLLER_REPLICATION
// wait for ACK
________________________________________________________________
Second command: /** Reset to factory default. */
01 04 00 42 01 B8
00 = request 42 = FUNC_ID_ZW_SET_DEFAULT 01 = Callback FunctionID
Answer:
06 01 04 00 42 01 B8
06 = ACK
01 = SOF 04 = Length 00 = Request 42 = FUNC_ID_ZW_SET_DEFAULT 01 = Callback FunctionID B8 = checksum
Framing
Serial PDUs are framed with a simple framing protocol. Byte value 0x01 is start of frame, or SOF. The second octet is the length in bytes of the frame, excluding the SOF or the length octet. Assume that value was n for this frame. The next n - 1 octets are the framed payload. The last octet is a checksum computed by xoring a 0xff seed with all octets of the payload. The checksum includes the length field, but not the SOF byte or the checksum byte itself.
Each frame is acknowledged by the remote end with 0x06.
NOTE: if you look at an ascii table (man ascii) you see the following: 0x01 SOH (start of heading) 0x06 ACK (acknowledge) 0x15 NAK (negative ack.) 0x18 CAN (cancel)
This information is derived from the pluto source code, along with observation of the serial protocol from existing commercial software.
Truth Table XOR A ⊕ B
A B Result
0 0 0
0 1 1
1 0 1
1 1 0
XORING description for the zwave (z-wave) checksum calculation let s say you have the frame 01 08 00 04 00 0A 02 84 07 78 You will have to take 08 XOR 00 XOR 04 XOR 00 XOR 0A XOR 02 XOR 84 XOR 07= 87 NOT 87 => 78 So in that case your checksum will be 78
'Checksum code for c/c++ char checksum(char *buf, int len) { int ret = 0xff;
for (int i=0;i<len;i++) ret ^= buf[i]; return ret;
}
'Checksum (XORING NOT) code for visual basic 2008 express Public Function checksumZ(ByVal chaine As String) As String Dim result As Integer Dim resultS As String Dim result2 As Integer Dim result2s As String resultS = Replace(chaine, " ", "") chaine = resultS resultS = Mid(chaine, 3, 2) result = Val("&H" & resultS) For i = 5 To (Len(chaine)) Step 2 result2s = (Mid(chaine, i, 2)) result2 = Val("&H" & result2s) result = result Xor result2 Next result = Not (result) resultS = Hex(result) checksumZ = Mid(resultS, Len(resultS) - 1, 2) End Function
Capturing your own sample transactions
These notes are for Microsoft Windows. Linux should be easier.
Get a copy of Device Monitoring Studio. These instructions were written with version 5.11. Use an HA22 device or other serial or usb-to-serial Z-wave dongle. Monitor the serial port for an event. Add the "Request" view in DMS. Do your operations in the software that will interact with the HA22. No click on the "complete" tab in the request view. Right click and choose "export". Save the .htm file that results.
The resulting HTML is pretty verbose. Some simple regexps can pull out interesting details. That results in transcriptions like the ones you see below.
Here's a session with an established Homeseer installation starting up:
W: 01 03 00 02 fe R: 06 R: 01 25 01 02 04 04 1d ff 00 R: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 02 38
the 29 bytes after 1d (length, thats 29 in decimal) represent a node bitmask (29*8 = 232 devices).
W: 06 W: 01 04 00 41 01 bb
now it's iterating over the nodes and asking for supported classes
R: 06 01 09 01 41 12 06 00 01 01 01 a3 W: 06 W: 01 04 00 41 02 b8 R: 06 01 09 01 41 c9 0c 00 04 11 04 62 W: 06 W: 01 04 00 41 03 b9 R: 06 01 09 01 41 c9 0c 00 04 11 04 62 W: 06 W: 01 04 00 41 04 be R: 06 01 09 01 41 c9 0c 00 04 11 04 62 W: 06 W: 01 04 00 41 05 bf R: 06 01 09 01 41 c9 0c 00 04 11 04 62 W: 06 W: 01 04 00 41 06 bc R: 06 01 09 01 41 c9 0c 00 04 10 03 64 W: 06 W: 01 04 00 41 07 bd R: 06 01 09 01 41 c9 0c 00 04 10 03 64 W: 06 W: 01 04 00 41 08 b2 R: 06 01 09 01 41 ca 06 00 02 02 00 7a W: 06 W: 01 07 00 03 01 02 00 00 f8 R: 06 W: 01 03 00 20 dc R: 06 01 08 01 20 00 98 a2 94 08 70
00 98 a2 94 == home id 08 == node id
W: 06 W: 01 03 00 07 fb R: 06 01 20 01 07 02 2d 00 00 00 01 00 01 7f 80 fe 00 8f 00 00 00 7b 9f ff 00 87 00 00 00 00 00 80 00 00 64 W: 06
Here's the first bits of what HomeZiX did when started:
W: 01 03 00 15 e9 R: 06 01 10 01 15 5a 2d 57 61 76 65 20 32 2e 30 39 00 01 9d W: 06 W: 01 05 00 06 0f 0a f9 R: 06 01 05 01 06 96 0f 64 W: 06 W: 01 04 00 17 00 ec R: 06 01 04 01 17 00 ed W: 06 W: 01 03 00 07 fb R: 06 01 20 01 07 02 2d 00 00 00 01 00 01 7f 80 fe 00 8f 00 00 00 7b 9f ff 00 87 00 00 00 00 00 80 00 00 R: 64 W: 06 W: 01 03 00 20 dc R: 06 01 08 01 20 00 7a 7a af 02 7b W: 06 W: 01 03 00 02 fe R: 06 R: 01 25 01 02 04 04 1d 87 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 02 40 W: 06 W: 01 03 00 56 aa R: 06 01 04 01 56 00 ac W: 06 W: 01 04 00 41 01 bb R: 06 01 09 01 41 c9 04 00 03 10 00 68 W: 06 W: 01 04 00 41 02 b8 R: 06 01 09 01 41 ca 06 00 02 02 01 7b W: 06 W: 01 04 00 41 03 b9 R: 06 01 09 01 41 c9 04 00 03 10 00 68 W: 06 W: 01 04 00 41 08 b2 R: 06 01 09 01 41 c9 04 00 03 10 00 68 W: 06 W: 01 05 00 21 00 00 db R: 06 01 04 01 21 42 99 W: 06 W: 01 05 00 21 00 01 da R: 06 01 04 01 21 06 dd W: 06 W: 01 06 00 23 00 02 06 de R: 06 01 09 01 23 21 72 86 82 2b 87 2f W: 06 W: 01 08 00 13 ff 01 00 00 01 1b R: 06 01 04 01 13 01 e8 W: 06 R: 01 05 00 13 01 00 e8 W: 06 W: 01 05 00 50 ff 01 54 R: 06 R: 01 07 00 50 01 01 ef 00 47 W: 06
References
http://www.basshome.com/leviton_z-wave_documentation_1970_ctg.htm (dead link, redirects to home page)
http://zwaveworld.com/forum/index.php?showtopic=237
http://www.eilhk.com/en/product/Datasheet/Zensys/SDS10243-2%20-%20Z-Wave%20Protocol%20Overview.pdf
or
http://www.smarthus.info/support/download/zwave/Z-Wave%20Protocol%20Overview.pdf
or
http://www.smarthus.info/support/download/zwave/Z-Wave%20Node%20Type%20Overview%20and%20Network.pdf
http://www.smarthus.info/support/download/zwave/Z-Wave%20Configuration%20Information.pdf
http://www.ddj.com/embedded/193104353
http://www.elec-solutions.com/docs/motor_controls/abmhz/ABMHZ_v1+1_Advanced_User_Manual.pdf (since pulled, but still visible as of April 26, 2008 in the Google cache)
Tools used
http://sourceforge.net/projects/slsnif/
Links
http://www.intouchcontrolsforum.com/forums/showthread.php?t=41&page=2
http://www.elec-solutions.com/docs/motor_controls/dbmz/DBMZ_v1+1_Advanced_User_Manual.pdf
http://zwaveworld.com/forum/index.php?showtopic=227&st=20