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:
Press and hold INCLUDE and DELETE buttons at the same time for 10 seconds. The red and green LED’s will flash.
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’):
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.
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.
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.
To include additional devices to the channel, repeat
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:
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.
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.
The zwave USB stick ZW090-A from Aeotec is a fine piece of hardware but it seem pretty sensible to whatever receive from the USB port and it get stuck into the apocalypse rainbow error mode: regular color cycle.
Remote [Hold Setup] : RED/GREEN LED flash twice Remote  : GREEN LED flashes twice.
ADD Remote to SmartThing network
SmartThings APP: [+] [+ Connect New Device] -> Searching… Remote: [Hold Setup] : (RED/GREEN LED blink twice) Remote:  : (GREED LED rapid blink) till the connection SmartThings APP: Complete the installation naming the device
ADDING A LIGHT (DEVICE / NODE) TO YOUR REMOTE
The “light (aka power switch)” must already be part of the SmartThings infrastructure. You can add a maximum of 18 lights to your remote so that they can be controlled individually.
The devices should always be reset prior new ‘inclusion’:
Remote: [Hold Setup] until both the RED/GREEN LEDs blink twice. Remote: [DELETE] (Red Blink) Remote: [Light] (flashes green rapidly). Device: [configuration button] reset is complete when green stops flashing.
(the green led blink 2 time faster as succes confirmation feedback). Remote: [hold SETUP] until both the RED/GREEN LEDs blink twice. Remote: [ADD] once. (RED LED blinks once) Remote: [LIGHT] once. (RED LED blinks once) Remote: Press a digit [1…9] (GREEN LED blinks rapidly)
for the device button you wish to add. Press SHIFT and the digit [1…9] if you are adding devices 10 through 18. Device: [configuration button] on the device so that it sends its information to the remote and receives information from the remote.
When the GREEN LED blinks twice, you have successfully added the device to your remote control.
NOTE: If the RED LED emits one long, steady blink, you have pressed an
invalid key or the device has not been successfully added to your
Please make sure the remote is within two feet of the device and try again.
Complete list of the 45600 “magic key sequences”:
add this controller as primary/secondary controller (LEARN)
add another secondary controller (device and network information)
add another secondary controller (network information only)
make another remote primary controller (device and network information)
make another remote primary controller (network information only)
To activate the above MKS press and hold the SETUP key until both the red and green LEDs blink twice before typing the code.
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
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.
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.