Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A customer can register Command Passthrough to receive commands sent by a remote device(Dimmer Switch, Alarm Device) and pass commands through to Host Micro, RapidHA automatically processing the command payload.

This is typically done so that the command payload and corresponding action can be handled by the Host Micro-controller.

Step-by-step guide

Summary 

  1. Setup Register Command Passthrough for desired cluster during startup config.
  2. Setup Network.
  3. Join Device.
  4. Bind Device to Coordinator.
  5. (If using RapidHA Desktop) Close/open com port





Register Command Passthrough

For this, a customer without a working host micro can use the RapidHA Serial Log feature to send the command-passthru frames during startup configuration.

  • Start RapidHA Desktop and open the Serial Log
  • Open comport and set the desired configuration
  • Take note of frames passed from Host to Module
    1. Example :

      [09:57:31]: F1 03 00 B9 02 00 00 BE 00 [RHADeviceTypeWrite]
      [09:57:31]: F1 03 30 BA 00 ED 00 [RHAClearEndpointConfig]

      ...... 

  • Resend frames but add the /wiki/spaces/SPRHA15/pages/37093429 before sending StartupSyncComplete frame. This can be done using RapidHA Desktop by parsing the Frames and manually enter using the Serial Log

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

    Please see the "Registering Command Passthrough" 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.

    Setup Network

    This is done as normal

    Join Device

    This is done as normal.

    Info

    ZLL Remotes can take usually require more work steps to join to a ZBHA1.2 or ZB3.0 network. Please refer to Remote user manual for joining process.

    Bind Device To Controller

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



    Style
    {style}
      .wiki-content h1 { 
    	font-family: 'Helvetica Neue', sans-serif; font-size: 30px; font-weight: bold; color: #7ab800; letter-spacing: 1px; line-height: 1; text-align: left;
        #border-bottom: 1px solid #98bddd !important; 
      }
    .wiki-content h2 { 
    	font-family: 'Helvetica Neue', sans-serif; font-size: 20px; font-weight: normal; color: #a1cd4c; letter-spacing: 1px; line-height: 1; text-align: left;
      }
    .wiki-content h3 { 
    	font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; color: #a7a9ac; letter-spacing: 1px; line-height: 1; text-align: left;
      }
    .wiki-content h4 { 
    	font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; color:#a7a9ac; letter-spacing: 1px; line-height: 1; text-align: left;
      }
    #title-text{
     font-family: 'Helvetica Neue', sans-serif; font-size: 40px; font-weight: 500; letter-spacing: 1px; line-height: 1; text-align: left;
    }
    {style}