Intermatic HA07 Wireless Master Controller ZWave

Standalone ZWave master controller or can be used as secondary controller.

Tested with Smartthings

First, do a full reset on the remote (to disassociate it with any previous controller). On the HA09, that consists of:

  1. Press and hold INCLUDE and DELETE buttons at the same time for 10 seconds. The red and green LED’s
    will flash.
  2. Hold the Channel 1 ON/DIM and OFF/DIM buttons until the green LED turns solid.

To add HA07 controller

Turn on include on Smartthings hub
Press and hold INCLUDE for 5 seconds COPY will flash
Release the INCLUDE button
Press and release Channel 1 OFF/DIM on the HA07 controller
The display will show “RA” (wait a few min for ST to add it)
Add modules to HA07

add devices to channels on the remote (‘Include’):

  1. On the remote controller, simultaneously press and hold the ON and OFF buttons of the desired channel. Both red and green LED’s will flash. Release the ON and OFF buttons.
  2. Press and hold the INCLUDE
    button. While still holding the INCLUDE
    button, press the program button on the module (switch, lamp module, etc).
    Choose a light level holding the module PROGRAM button.
  3. After setting your desired light level, release the
    INCLUDE button on the remote controller. The green
    LED’s on the controller and module will flash. The
    module LED will turn solid green.
  4. To include additional devices to the channel, repeat

Difference between SUC and SIS controller

Static Update-Controller (SUC)

The Static update controller (SUC) is a special function of a static controller. Most static controllers (a controller with fixed location and powered by mains) can perform as an SUC. However, the function typically needs to be activated first. The SUC receives the updated routing table from the primary controller and offers this routing table to all other controllers in the network. Because the SUC is a static controller and therefore always active in the network, any other controller can frequently request an updated routing table from the SUC. To make sure that all other nodes and particularly other controllers are aware of the presence of a SUC in the network, the Node ID of an activated SUC is communicated within the network periodically.

Having an active SUC in the network allows you to keep the primary controller role on a portable controller. Every change of the network caused by inclusion or exclusion of a node by the primary controller will be reported to the SUC and is then available to all other controllers, even if the primary controller is not active.

Since most of the controllers are battery operated and therefore not active all the time, these controllers have to request an updated routing table periodically or at least when woken up, by pressing a button. To perform this task the mobile battery operated controllers need to be informed about the presence of a SUC in the network. If the original – mobile – battery operated primary controller is lost or damaged, the SUC can assign the primary privilege to a new mobile controller, protecting the user from re-establishing the whole network with a brand new primary controller, and having a different Home ID.

Static ID Server (SIS)

Even a SUC in the system does not solve the problem that only one controller has the primary privilege and can include new device. This limitation is overcome by enhancing the SUC functionality by another function called SIS = Static ID Server.

The SIS acts as depot for new Node IDs that can be as signed by mobile controllers . Having an SIS present in the network allows every controller in the network to include a further device. The controller will just request a new node ID from the SIS and assign this new Node I D to the server. With the SI S it is made sure that no two nodes get as signed the same node ID. The only requirement is a mobile controller needs to fulfil in order to include new devices, is that it has a network connection to the SIS server to request a node ID.

This kind of configuration with server SIS has the following advantages and disadvantages:

Advantages:

  • The actual network topology and the information about all nodes are saved in a static controller and are therefore better protected than within a mobile battery powered device.
  • All controllers in a network can integrate new devices.
  • The network configuration and handling becomes very flexible.

Disadvantages:

  • Function is available only from the firmware version 3.40. It is possible that there are some devices in the network with older firmware that do not support this configuration.
  • Inclusion controller can integrate only devices if it has a wireless connection to the SIS.
  • With the SIS there exists a “Single Point of Failure”. A damaged SIS result in a complete new network setup.

Since the SUC/SIS functionality is already included in the firmware of most modern static controller, or a USB dongle, most Z-Wave networks can take advantage of these functions if a static controller is present. However, this function needs to be activated.

A static controller can also be a primary controller, as well as have SUC/SIS functionality. This configuration is typical in real networks.

SmartThings and GE 45631 Z-Wave Wireless Keypad Controller

This device provides control of 4 Groups and 4 Scenes. Up to 32 Z-Wave devices can be included in each of the Groups and Scenes. It is a secondary controller only and cannot function as a primary controller. Associate a device to the remote 1. Press and hold the Add and Remove buttons at the same time until the Orange LED blinks twice, then release 2. Press and release the Add button. 3. Press and release the Group button. Press and release the right side (ON) of the Group/Scene button (1, 2, 3 or 4) that you want to assign the device to. The Orange LED will start blinking. Press and release the button on the device you wish to add. The Green LED will blink twice to show that you have successfully Added a device to a Scene

ZWave Dossier

z-wave
Not open proprietary protocol from Sigma Designs outside NDA.
Chips are only avaible from Sigma Designs and the partner Mistumi.
Z-Wave (PHY Layer) is a sub-1Ghz protocol.
Controller devices and slave devices with a reliable power source participate in message forwarding up to four hops and they are always listening.

Application Layer
Header[1B] – Cmd. class[1B] – cmd.[1B] – Command class data [xB]
COMMAND_CLASS_BASIC
COMMAND_CLASS_BATTERY
COMMAND_CLASS_WAKE_UP
COMMAND_CLASS_CONTROLLER_REPLICATION
COMMAND_CLASS_SWITCH_MULTILEVEL
COMMAND_CLASS_SWITCH_ALL
COMMAND_CLASS_SENSOR_BINARY
COMMAND_CLASS_ALARM
COMMAND_CLASS_MULTI_CMD
COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE
COMMAND_CLASS_CLOCK
COMMAND_CLASS_ASSOCIATION
COMMAND_CLASS_CONFIGURATION
COMMAND_CLASS_MANUFACTURER_SPECIFIC
COMMAND_CLASS_SCENE_ACTIVATION
COMMAND_CLASS_SCENE_ACTUATOR_CONF 0x2C
COMMAND_CLASS_MANUFACTURER_SPECIFIC 0x72
COMMAND_CLASS_VERSION 0x86
COMMAND_CLASS_MANUFACTURER_PROPRIETARY 0x91
COMMAND_CLASS_NODE_NAMING
COMMAND_CLASS_POWERLEVEL
COMMAND_CLASS_MARK 0xEF
COMMAND_CLASS_HAIL 0x82
COMMAND_CLASS_MULTI_INSTANCE 0x60
COMMAND_CLASS_SENSOR_MULTILEVEL 0x31
COMMAND_CLASS_SWITCH_BINARY 0x25

General Device classes:

Hex ValueValueDescriptionKey
0x011General controllerBASIC TYPE CONTROLLER
0x022Static cont rollerSTATIC CONTROLLER
0x033BASIC TYPE SLAVE
0x044BASIC TYPE ROUTING SLAVE
0x088ThermostatGENERIC TYPE THERMOSTAT
0x1016Binary switchBINARY SWITCH
0x1117Multi level switchMULTI LEVEL SWITCH
0x1218GENERIC TYPE SWITCH REMOTE
0x1319GENERIC TYPE SWITCH TOGGLE
0x1723GENERIC TYPE SECURITY PANEL
0x2032Binary sensorBINARY SENSOR
0x2133Multilevel-SensorMULTILEVEL SENSOR
0x3149MeterMETER
64GENERIC TYPE ENTRY CONTROL

ZWave Protocol Commands

NameHexDec
NO OPERATION0x000
NODE INFO0x011
REQUEST NODE INFO0x022
ASSIGN IDS0x033
FIND NODES IN RANGE0x044
GET NODES IN RANGE0x055
RANGE INFO0x066
CMD COMPLETE0x077
TRANSFER PRESENTATION0x088
TRANSFER NODE INFO0x099
TRANSFER RANGE INFO0x0A10
TRANSFER END0x0B11
ASSIGN RETURN ROUTE0x0C12
NEW NODE REGISTERED0x0D13
NEW RANGE REGISTERED0x0E14
TRANSFER NEW PRIMARY COMPLETE0x0F15
AUTOMATIC CONTROLLER UPDATE START0x1016
SUC NODE ID0x1117
SET SUC0x1218
SET SUC ACK0x1319
ASSIGN SUC RETURN ROUTE0x1420
STATIC ROUTE REQUEST0x1521
LOST0x1622
ACCEPT LOST0x1723
NOP POWER0x1824
RESERVE NODE IDS0x1925
RESERVED IDS0x1A26
UNKNOWN0x1B-0x1F27-31

Devices declare the supported command classes during the inclusion process, as part of the node information frame that is sent as a broadcast any time the node action button is pressed or as a response to a controller “get node information” command.