By default, RapidConnect firmware is configured to interpret and respond to ZCL commands with minimal interaction from a Host Microcontroller. In some cases, it is desirable for the Host to handle these command as they are received, rather than the Module. For example, consider the following scenario:

• You would like to test some security sensors (i.e. IAS Zone devices).
• You would like to use a RapidConnect USB Stick to form a Zigbee network and communicate with the sensors.
• To configure the RapidConnect USB Stick as a Coordinator, you may use a PC running RapidConnect Desktop. This is referred to as the Host.
• The security sensors can be configured to report state changes (i.e. alarm conditions) to the Coordinator. The RapidConnect firmware does not perform any action when it receives the IASZone state change message. Instead, it acknowledges receipt of the message and then discards it. The module will not inform the Host (i.e. RapidConnect Desktop) of the message it received.
• If you'd like to see the sensor state changes reflected in RapidConnect Desktop and/or respond with an action, you must register a Command Passthrough. The Command Passthrough tells the Module that it should pass the message directly to the Host application rather than handling/discarding the message.

Step-by-step guide

Summary 

1. During startup configuration, register Command Passthrough for desired cluster(s).
2. Set up Network.
3. Join Device.
4. Bind Device to Coordinator.
5. (If using RapidHA Desktop) Close/open com port.

Register Command Passthrough

A Command Passthrough must be registered in the RapidConnect Firmware before the device is fully configured. 

Please see the "Registering Command Passthrough" section within the "Advanced Device Configuration" section of this guide for instructions on how this is done. If this step is not performed, any command received by the the RapidConnect Module will be discarded and no action taken.

Set up Network

This is done as normal.

Join Device

This is done as normal.

Bind Device To Controller

Please follow Step 2 of this guide to bind the device cluster to the coordinator.