This page describes the commands supported by the RapidHA serial protocol. The payload byte values are detailed in the command descriptions. Some commands have no payloads.
...
Note | ||
---|---|---|
| ||
New sleep control frames under the Utility command group (PH: 0x55) provide the user with a wake-up handshaking scheme, as well as total and accurate control of application sleep cycles. |
Table of Contents | ||||
---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
The Reset command is sent from the Host to the Module, and prompts the Module to reboot. The command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Module Info Request commandis sent from the Hostto the Module to query the Module’s version and application type. This command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Module Info Responsecommand is sent from the Module to the Hostin response to a Module Info Request command.
...
Anchor | ||||
---|---|---|---|---|
|
The Bootloader Version Response is sent by the Module after it is queried by the Host with a Bootloader Version Request. The Response contains advanced information about the current application bootloader running on the Module.
...
Anchor | ||||
---|---|---|---|---|
|
The Application Version Count Request is sent from the Host to the Module to query the number of Application Version Strings available from the running application. The command has no payload.
...
AnchorApplication Version Count Response Application Version Count Response
Application Version Count Response - ( PH:0x55, SH:0x07 )
Application Version Count Response | |
Application Version Count Response |
The Application Version Count Response is sent from the Module to the Host. The response payload length is 1 octet.
Payload for Application Version Count Response Command
Byte Index | Field Name | Notes |
---|---|---|
0 | Version String Count | A count of the total number of Application Version Strings available from the running application. |
Expected Host Action
None.
Anchor | ||||
---|---|---|---|---|
|
The Application Version Request is sent from the Host to the Module to query a given Application Version String describing either the Application Bootloader Version, the core RapidHA Version or the Virtual Host Application Version. The request payload length is 1 octet.
Payload for Application Version Request Command
Byte Index | Field Name | Notes |
---|---|---|
0 | Version Index | 0x00 - Retrieve Bootloader Version |
Effect on Receipt
The Module will respond with an Application Version Response.
Anchor | ||||
---|---|---|---|---|
|
The Application Version Response is sent from the Module to the Host. The response payload length is variable.
Payload of Application Version Response Command
Byte Index | Field Name | Notes |
---|---|---|
0 | Version String Index | The array index (0 based) that this command relates to. |
1 | Version Type | The type of version string returned. See Version Types. |
2..(n + 3) | Version | The version being returned. The length n is specified in the first octet of the field. A total of n bytes will follow this length byte containing data which shall be interpreted based on the Version Type. |
Expected Host Action
None.
Anchor Application Version Types Application Version Types
Version Types
Application Version Types | |
Application Version Types |
Type ID | Type Name | Length (Octets) |
---|---|---|
0x00 | LSB Binary Type | 4 |
0x01 | MSB Binary Type | 4 |
0x02 | String Type | Variable |
0x03 | LSB Binary Type | 2 |
0x04 - 0xFE | Reserved | N/A |
0xFF | Invalid | N/A |
LSB Binary Type
A type value of LSB Binary Type indicates that the version string is being provided as a series of binary encoded bytes that represent the version string in a dotted version format with the least significant byte provided first. For example, a binary value of 0x01,0x02,0x03,0x04 provided using this encoding would be translated to 4.3.2.1 (or possibly 4.3.2rc1) when displayed to the user. This is the default encoding for version numbers.
MSB Binary Type
A type value of MSB Binary Type indicates that the version string is being provided as a series of binary encoded bytes that represent the version string in a dotted version format with the most significant byte provided first. For example, a binary value of 0x05,0x06,0x07, 0x08 provided using this encoding would be translated to 5.6.7.8 (or possibly 5.6.7rc8) when displayed to the user.
String Type
A type value of String Type indicates that the version string is being provided as an ASCII encoded string of length n. The value will not be null terminated as the length is provided. For example, a binary value of 0x31,0x2e,0x32,0x2e,0x30,0x72,0x63,0x31 provided using this encoding would be translated to 1.2.0rc1.
Invalid
A type value of Invalid indicates that the requested element is invalid. Typically this indicates that a request was made for an index which lies outside of the valid range of version string indices.
Anchor | ||||
---|---|---|---|---|
|
The Restore Defaults frame is sent from the Host to the Module and serves to restore the Module to its factory default settings. The command has no payload.
Effect on Receipt
The Module restores all non-volatile elements to their factory default settings, leaves the network if it is joined to one or dissolves the network if it has formed one, and then reboots.
Anchor | ||||
---|---|---|---|---|
|
The Host shall send the Host Startup Ready command to the Module after it starts up and is ready for communication. The command has no payload.
Effect on Receipt
On receiving the command, the Module will respond with the Startup Sync Request command. If the Module is in the Already Running state (see payload for Startup Sync Request ), it signifies that this command was received due to an unexpected reset of the Host. In this case, the Module will have retained all its application cache and attribute values, but will suspend network operations and return to the Startup Synchronization phase.
Anchor | ||||
---|---|---|---|---|
|
The Startup Sync Request command is sent by the Module on startup or as a response to the Host Startup Ready command. Upon issuing this command, the Module suspends execution of the full application until the Host has completed all desired configuration and updates against it.
The Module resends this command every five seconds until the Host sends the Startup Sync Complete command in response, signaling the completion of the configuration and update process.
Payload for Startup Sync Request Command
Byte Index | Field Name | Notes |
---|---|---|
0 | Running State | 0x00 = Starting Up |
1 | Configuration State | 0x00 = Factory Default |
The Running State indicates whether the Module has just powered up or is already running. If the Running State indicates the latter, it signifies that the Host experienced a unilateral reset.
The Configuration State indicates the application configuration state of the Module. The Factory Default state indicates that the Module is operating for the first time post-production, or subsequent to the reception of the Restore to Default command from the Host. The Needs Endpoint Configuration state indicates that the Module has restored all default configurations (Manufacturer ID, etc.), but still requires the Host to configure application endpoints, clusters and attributes. This state will occur after a soft or hard reset of the Module, regardless of the amount of non-volatile memory available.
Expected Host Action
The Host may receive the Startup Sync Request either during a synchronized power up or after a unilateral reset of the Module. The Host shall process both scenarios in the same manner.
If the Running State of the Module is Already Running the Host is not required to configure endpoints, clusters and attributes and perform updates on the values of the latter. Instead, the Host should query attribute values and cached event data from the Module in order to synchronize its internal state with that of the application.
If the Configuration State of the Module is Factory Default, the Host shall perform a full configuration of the application, specifying the IEEE functional device type, security configuration, endpoints, etc. If the Configuration State is Needs Endpoint Configuration, the Host shall configure the application endpoints, clusters and attributes accordingly. If Configuration State is Fully Configured, no further configuration action is required of the Host.
Anchor | ||||
---|---|---|---|---|
|
The Host shall send the Startup Sync Complete command to the Module in response to a Startup Sync Request and upon completion of all startup configurations and updates to the latter. The command has no payload.
Effect on Receipt
The Module acknowledges reception of the command with a Status Response indicating Success, after which it runs the full application. If the Module was previously joined to a network it will rejoin that network. Additionally, application configurations are backed up to non-volatile memory for restoration on the next startup.
Please note that Host configurations for endpoints, clusters and attributes are not preserved in non-volatile memory; thus they must be reconfigured after any soft or hard reset of the Module.
Status Response to Startup Sync Complete Command
Status Response | Enum | Description |
---|---|---|
Success | 0x00 | Module received the command and will start the full application. |
Anchor | ||||
---|---|---|---|---|
|
The Antenna Configuration Request is sent by the Host to the Module and serves to query the Module about the hardware antenna configuration when the application is operating on the MMB Hornet platform. The command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Antenna Configuration Response is sent by the Module after it is queried by the Host with an Antenna Configuration Request. The payload contains the hardware antenna configuration of the MMB Hornet platform. If the application is not operating on that platform, the response indicates that antenna configuration is not supported.
...
AnchorAntenna Configuration Write Antenna Configuration Write
Antenna Configuration Write Command - ( PH:0x55, SH:0x25 )
Antenna Configuration Write | |
Antenna Configuration Write |
The Antenna Configuration Write command is sent by the Host to the Module to select the hardware antenna configuration of the MMB Hornet platform.
...
AnchorLED Configuration Request LED Configuration Request
LED Configuration Request Command - ( PH:0x55, SH:0x26 )
LED Configuration Request | |
LED Configuration Request |
The LED Configuration Request is sent by the Host to the Module and serves to query the LED behavior configuration of the Telegesis LRS USB Stick or the MMB Hornet-based MMB USB Stick platforms. On these platforms, the LED may be configured to act as an indicator of the application Network State. The Module responds with an LED Configuration Response. The command has no payload.
...
AnchorLED Configuration Response LED Configuration Response
LED Configuration Response Command - ( PH:0x55, SH:0x27 )
LED Configuration Response | |
LED Configuration Response |
The LED Configuration Response is received from the Module once queried by the Host with an LED Configuration Request. It conveys the LED behavior configuration of the Telegesis LRS USB Stick or MMB Hornet-based MMB USB Stick platforms. On these platforms, the LED may be configured to act as an indicator of the application Network State.
...
AnchorLED Configuration Write LED Configuration Write
LED Configuration Write Command - ( PH:0x55, SH:0x28 )
LED Configuration Write | |
LED Configuration Write |
The LED Configuration Write command is sent by the Host to the Module to set the LED behavior behaviour configuration of the Telegesis LRS USB Stick or Hornet-based MMB USB Stick platforms. On these platforms, the LED may be configured to act as an indicator of the application Network State.
...
AnchorSerial ACK Config Write Serial ACK Config Write
Serial ACK Config Write Command - ( PH:0x55, SH:0x30 )
Serial ACK Config Write | |
Serial ACK Config Write |
The Serial ACK Config Write command is sent by the Host to the Module in order to enable or disable mandatory serial acknowledgements.
...
Anchor | ||||
---|---|---|---|---|
|
The Serial ACK Config Request command is sent by the Host to the Module in order to query the application Serial ACK Configuration. The command has no payload.
...
AnchorSerial ACK Config Response Serial ACK Config Response
Serial ACK Config Response Command - ( PH:0x55, SH:0x32 )
Serial ACK Config Response | |
Serial ACK Config Response |
The Serial Ack Config Response is sent by the Module to the Host in response to a Serial ACK Config Request. The command conveys the current Serial ACK Configuration of the application indicating whether serial acknowledgements between the Host and Module are mandatory or not.
...
Anchor | ||||
---|---|---|---|---|
|
The Manufacturer ID Request is sent by the Host to the Module to query the application Manufacturer ID. This ID is included in the application Node Descriptor and is also applied when querying an OTA server for new firmware images. This command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Manufacturer ID Response is sent by the Module to the Host in response to a Manufacturer ID Request. The command conveys the Manufacturer ID of the application.
...
Anchor | ||||
---|---|---|---|---|
|
The Manufacturer ID Write command is sent by the Host to the Module to set the Manufacturer ID of the application. This ID is included in the application Node Descriptor and is also applied when querying an OTA server for new firmware images. The command payload is equivalent to the Manufacturer ID Response.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleepy Parameters Request CMD command is sent by the Host to the Module to query the application’s sleepy parameters. The command has no payload. See Sleepy Devices for more information about the Module’s sleepy behavior.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleepy Parameters Response CMD command is sent by the Module to the Host in response to a Sleepy Parameters Request CMD. The command conveys the sleepy parameters of the application. See Sleepy Devices for more information about the Module’s sleepy behavior.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleepy Parameters Write CMD command is sent by the Host to the Module to modify the sleepy parameters. The command allows for multiple attributes to be written for a device in one operation. The value 0xFF is an invalid parameter for all byte fields in the payload; it will not be written. See Sleepy Devices for more information about the Module’s sleepy behaviorbehaviour.
Payload for Sleepy Parameters Write CMD Command
...
Anchor | ||||
---|---|---|---|---|
|
The Sleepy Hibernate Duration Request CMD command is sent by the Host to the Module to query only the App Hibernate Duration parameter. This command is provided to read the App Hibernate Duration parameter without reading the other sleepy parameters. The command has no payload. See Sleepy Devices for more information about the Module’s sleepy behavior.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleepy Hibernate Duration Response CMD is sent by the Module to the Host in response to a Sleepy Hibernate Duration Request CMD. The command conveys the Module's hibernation duration; i.e., the App Hibernate Duration parameter. See Sleepy Devices for more information about the Module’s sleepy behavior.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleep Hibernate Duration Write Command is sent by the Host to the Module to modify the parameter App Hibernate Duration. See Sleepy Devices for more information about the Module’s sleepy behavior.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleep Control Stay Awake Duration Write command is issued by the Host to the Module and serves to impose a duration for which the application will stay awake. This allows the Host to override the standard sleep cycle of the application when desired.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleep Control Stay Awake Duration Read command is issued by the Host to the Module to query the Stay Awake Duration of the application. The command has no payload.
Anchor | ||||
---|---|---|---|---|
|
The Sleep Control Stay Awake Duration Read Response is issued by the Module to the Host in response to a Sleep Control Stay Awake Duration Read command. It conveys the remaining Stay Awake Duration of the application, in milliseconds.
...
Anchor | ||||
---|---|---|---|---|
|
The Status Response command may be issued either by the Module to the Host, or by the Host to the Module, in order to acknowledge the reception of a command.
...
Anchor | ||||
---|---|---|---|---|
|
The Sleep Control Wakeup frame is issued by the Host to the Module to wake the application when it is sleeping. On reception, the application will stay awake for a default duration of 50ms. It is expected that the Host will stuff the 19-byte payload with all 0xFF’s.
...
Anchor | ||||
---|---|---|---|---|
|
The Error frame is sent by the Module to the Host to report an application error.
...
Error conditions are reported for diagnostic purposes. Depending on the given error received, there may or may not be an expected action for the Host to take in response.
...
Back to Top
Anchor | ||||
---|---|---|---|---|
|
The Network Commissioning command set allows the Host to prompt the Module to either form a network or join an existing network. A third option exists for performing HA 1.2 EZ-Mode Commissioning, defined as an automated process that prompts the application to join an existing network and, failing to find one, to form its own.
...
Anchor | ||||
---|---|---|---|---|
|
The Join Network command is sent by the Host to the Module to prompt the Module to scan for and join an existing network.
...
Anchor | ||||
---|---|---|---|---|
|
The Form Network command is sent by the Host to the Module to prompt the latter to form a network. Additionally on reception of this command, the application ZigBee Device Type is set to Coordinator.
...
Anchor | ||||
---|---|---|---|---|
|
The Permit Join command is sent by the Host to the Module in order to prompt the Module to open its Permit Join window for a given duration.
...
Anchor | ||||
---|---|---|---|---|
|
The Leave Network command is sent by the Host to the Module in order to prompt the Module to leave the network to which it is currently joined. The command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Rejoin Network command is sent by the Host to the Module in order to prompt the latter to rejoin the network to which it is currently joined. Though the Module may automatically engage in Rejoin behavior when having lost the connection to the network (i.e., as determined by the Network Heartbeat), this command provides facilities for the Host to manually engage the process (i.e., to re-initiate Service Discovery and Binding). The command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Network Status Request is sent by the Host to the Module to query the application Network State. The Host is not required to issue this command, as the Module will automatically issue a Network Status Response on any change of the application Network State. The command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Network Status Response is sent by the Module to the Host, either as a response to the Network Status Requestcommand, or automatically upon a change to the application Network State or Permit Join Duration (i.e., on transition from non-zero to zero or vice versa).
...
Anchor | ||||
---|---|---|---|---|
|
When the application ZigBee device type is configured as a coordinator and a network has been formed, the Trust Center Device Update command is sent by the Module to the Host when any device attempts to join or leave that network.
...
Anchor | ||||
---|---|---|---|---|
|
The Network Auto Join command is sent by the Host to the Module to prompt the Module to scan all channels for X number of retries and with Y number of seconds delay between each scan.
...
Anchor | ||||
---|---|---|---|---|
|
The Network Reset Auto Join command is sent by the Host to the Module to prompt it to leave any network to which it may be joined and then scan all channels for X number of retries and with Y number of seconds of delay between each scan.
...
Status Response | Enum | Description |
---|---|---|
Success | 0x00 | The Module successfully processed the command, and shall start the scan and join sequence. |
...
Back to Top
Anchor | ||||
---|---|---|---|---|
|
This section describes commands that set and report on security keys.
...
Anchor | ||||
---|---|---|---|---|
|
The Preconfigured Key Option Write command is sent by the Host to the Module and serves to dictate which key the application will use when attempting to join a network; either the Preconfigured Link Key or the key derived from Installation Code.
...
Anchor | ||||
---|---|---|---|---|
|
The Preconfigured Key Option Request is sent by the Host to the Module to query the current application Preconfigured Key Option. The Module will respond with a Preconfigured Key Option Response. The command has no payload.
Anchor | ||||
---|---|---|---|---|
|
The Preconfigured Key Option Response is sent by the Module to the Host when queried with a Preconfigured Key Option Request. The command has the same payload as the Preconfigured Key Option Writecommand.
...
Anchor | ||||
---|---|---|---|---|
|
The Install Code Request frame is sent by the Host to the Module to query the application Installation Code. The Module responds with an Install Code Response. It should be noted that the Installation Code is assigned to the Module at production time and cannot be modified. The command has no payload.
Anchor | ||||
---|---|---|---|---|
|
The Install Code Response frame is sent by the Module to the Host when queried with an Install Code Request.
...
Anchor | ||||
---|---|---|---|---|
|
The Link Key Write command is sent by the Host to the Module in order to set the application Preconfigured Link Key. The Host may only set the Preconfigured Link Key while the application is in the Network Down state.
...
Anchor | ||||
---|---|---|---|---|
|
The Link Key Request is sent by the Host to the Module to request the current application Link Key. The Module responds with a Link Key Response. When the Module is configured as a coordinator, it will return the Global Trust Center Link Key. When the Module is otherwise configured and not joined to a network, it will return the Preconfigured Link Key and likewise, when joined to a network, it returns the current Trust Center Link Key assigned to it. The command has no payload.
Anchor | ||||
---|---|---|---|---|
|
The Link Key Response is sent by the Module to the Host when queried with a Link Key Request. The command has the same payload as the Link Key Write command.
...
Anchor | ||||
---|---|---|---|---|
|
The Network Key Write command is sent by the Host to the Module in order to set the application Preconfigured Network Key. The Host may only set the Network Key while the application is in the Network Down state, after which the key will be automatically randomized.
...
Anchor | ||||
---|---|---|---|---|
|
The Network Key Request command is sent by the Host to the Module to query the application Network Key. The Module will respond with a Network Key Response. If the application has not formed a network, the response will convey the Preconfigured Network Key. Otherwise, the response will convey the current Network Key. The command has no payload.
Anchor | ||||
---|---|---|---|---|
|
The Network Key Response command is sent by the Module to the Host when queried with a Network Key Request. The command has the same payload as Network Key Write command.
...
Byte Index | Field Name | Notes |
---|---|---|
0..15 | Network Key |
...
Back to Top
Anchor | ||||
---|---|---|---|---|
|
This section describes the commands used to configure RapidHA’s IEEE functional device type, as well as the endpoints, clusters and attributes that will logically exist on that device.
...
Anchor | ||||
---|---|---|---|---|
|
The Device Type Write command is sent by the Host to the Module in order to configure the application’s IEEE functional device type. The Host is only required to issue this command once after synchronizing with a factory default Module for the first time, as the configuration is preserved in the application’s non-volatile memory.
...
Anchor | ||||
---|---|---|---|---|
|
The Device Type Requestis sent by the Host to the Module in order to query the application IEEE functional device type. The command has no payload.
...
Anchor | ||||
---|---|---|---|---|
|
The Device Type Response is sent by the Module to the Host in response to a Device Type Request.
...
AnchorAdd Endpoint Add Endpoint
Add Endpoint Command - ( PH:0x03, SH:0x10 )
Add Endpoint | |
Add Endpoint |
The Add Endpoint command is sent by the Host to the Module in order to configure an application endpoint. This includes defining the Endpoint ID, Profile ID, Device ID, Device Version and the lists of server and client clusters supported on that endpoint.
...
AnchorEndpoint List Request Endpoint List Request
Endpoint List Request Command - ( PH:0x03, SH:0x11 )
Endpoint List Request | |
Endpoint List Request |
The Endpoint List Request is sent by the Host to the Module in order to query the application endpoint list. The Host may apply this command to verify the configuration of application endpoints after having created them. The command has no payload.
...
AnchorEndpoint List Response Endpoint List Response
Endpoint List Response Command - ( PH:0x03, SH:0x12 )
Endpoint List Response | |
Endpoint List Response |
The Endpoint List Response is sent by the Module to the Host in response to an Endpoint List Request. The command conveys the Endpoint ID’s of all the configured endpoints supported by the application.
...
AnchorEndpoint Descriptor Request Endpoint Descriptor Request
Endpoint Descriptor Request Command - ( PH:0x03, SH:0x13 )
Endpoint Descriptor Request | |
Endpoint Descriptor Request |
The Endpoint Descriptor Request is sent by the Host to the Module in order to query the definition of a given application endpoint. The Host may apply this command to verify the full configuration of an application Endpoints after having creating it.
...
AnchorEndpoint Descriptor Response Endpoint Descriptor Response
Endpoint Descriptor Response Command - ( PH:0x03, SH:0x14 )
Endpoint Descriptor Response | |
Endpoint Descriptor Response |
The Endpoint Descriptor Response is sent by the Module to the Host in response to an Endpoint Descriptor Request.
...
AnchorAdd Attributes to Cluster Add Attributes to Cluster
Add Attributes to Cluster Command - ( PH:0x03, SH:0x20 )
Add Attributes to Cluster | |
Add Attributes to Cluster |
The Add Attribute to Cluster command is sent by the Host to the Module in order to append attribute definitions to a configured application cluster. The command may specify as many attributes as the maximum payload capacity of a RapidHA frame allows. For a cluster with large number of attributes, the command may be issued as many times as required.
...
AnchorAttribute List Request Attribute List Request
Attribute List Request Command - ( PH:0x03, SH:0x21 )
Attribute List Request | |
Attribute List Request |
The Attribute List Request is sent by the Host to the Module in order to query the attributes on a given application cluster and endpoint.
...
AnchorAttribute Request Attribute Request
Attribute Request Command - ( PH:0x03, SH:0x23 )
Attribute Request | |
Attribute Request |
The Attribute Request is sent by the Host to the Module in order to query the definition and value of an attribute on a given cluster and endpoint.
...
AnchorAttribute Response Attribute Response
Attribute Response Command - ( PH:0x03, SH:0x24 )
Attribute Response | |
Attribute Response |
An Attribute Response is sent by the Module to the Host in response to an Attribute Request.
...
AnchorAttribute Write Attribute Write
Attribute Write Command - ( PH:0x03, SH:0x25 )
Attribute Write | |
Attribute Write |
The Attribute Write command is sent by the Host to the Module in order to set the value of an existing attribute residing on a target cluster and endpoint.
...
Anchor | ||||
---|---|---|---|---|
|
The Attribute Report Passthrough Control message is sent from the Host to the Module. The payload length is 1 octet.
Payload for Attribute Report Passthrough Control
Byte Index | Field Name | Notes |
---|---|---|
0 | Attribute Passthrough Control | 0x00 = Disabled |
...
Anchor | ||||
---|---|---|---|---|
|
The Clear Endpoint Config command is sent by the Host to the Module in order to wipe all applied configurations of endpoints, clusters, attributes and registered pass-through commands. The command has no payload.
...
AnchorRegister Commands Passthru Register Commands Passthru
Register Commands Passthru Command - ( PH:0x03, SH:0x80 )
Register Commands Passthru | |
Register Commands Passthru |
The Register Commands Passthru message is sent by the Host to the Module to create an index of those cluster commands that the Module should pass through directly to the Host without additional processing. That is, the Host may specify supported commands that would otherwise result in additional action being taken by the Moduleon their reception, or commands not supported by the Module that would otherwise not be passed to the Host on their reception.
...
Status Response | Enum | Description |
---|---|---|
Success | 0x00 | Commands were successfully registered. |
Storage Full | 0x04 | There was insufficient storage for the registration list. |
Incorrect Length | 0x07 | The size of the attribute value does not match what is expected. |
Endpoint Not Found | 0x08 | The endpoint cannot be found. |
Cluster Not Found | 0x09 | The cluster cannot be found. |
...
Back to Top
Anchor | ||||
---|---|---|---|---|
|
This section describes the two ways, unicast and broadcast, for the Host to send a ZDO command. It also describes the commands sent by the Module to communicate ZDO-level information to the Host.
...
Anchor | ||||
---|---|---|---|---|
|
The Send ZDO Unicast command is sent by the Host to the Module in order to prompt the Module to send a ZDO message to a single destination node. The command configures the following options:
...
- (Indicating Level 100, Transition Time 0, On/Off Status ON) F1 12 25 BB 05 16 64 00 00 01 72 01 [RHAMoveToLevel]
Anchor | ||||
---|---|---|---|---|
|
...