Registering Command Passthrough
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
- During startup configuration, register Command Passthrough for desired cluster(s).
- Set up Network.
- Join Device.
- Bind Device to Coordinator.
- (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.
ZLL Remotes usually require more steps to join to an HA 1.2 or ZB 3.0 network. Please refer to Remote user manual for joining process.
Bind Device To Controller
Please follow Step 2 of this guide to bind the device cluster to the coordinator.
Legal Notices
Copyright © 2020 MMB Networks, Inc. All rights reserved.
Confidential materials prepared and delivered by MMB Networks for receipt and review only by any partner subject to a valid and enforceable MMB Networks confidentiality agreement. Any receipt, review, or misuse of any of the content exchanged hereunder by any party not a party to this confidential exchange shall be subject to any and all rights available under the law. All rights, title and interest to the materials shall remain with MMB Networks.
Any suggestions provided to MMB Networks with respect to MMB Networks' products or services shall be collectively deemed “Feedback.” You, on behalf of yourself, or if you are providing Feedback on behalf of your employer or another entity, represent and warrant that you have full legal authority to bind such entity to these terms, agree to grant and hereby grant to MMB Networks a nonexclusive, perpetual, irrevocable, royalty free, worldwide license to use and otherwise exploit such Feedback within any MMB Networks products and services.