User`s manual

Ordinarily a different request would be sent to each gateway, since the thermostat

addresses on the two networks are different. However, since a THERMOSTAT alias is

defined on each gateway for its local thermostat, the same request can be sent to both.

<request_name>

<param1>value</param1>

<param2>value</param2>

</request_name>

To manage aliases defined on the gateway, use the add_alias, remove_alias, and

list_aliases RPC requests. (See “add_alias” on page 114, “remove_alias” on page 114

and “list_aliases” on page 115.)

Request Identifier

All RPC requests take an optional request_identifier parameter which can be used to

match requests with later responses. The request identifier can be of any simple type but

typically is an integer.

Broadcasts

RPC requests that specify a destination address can sometimes send the corresponding

ZigBee command as a broadcast rather than a unicast. For example, the ZCL Identify

command is either unicast to a single device or broadcast to all devices on the network.

To specify a broadcast, set the destination address to 00:00:00:00:00:00:FF:FF.

Synchronous Requests

Any RPC request sent to the gateway can be made synchronous by adding the attribute

synchronous=”TRUE” to the RPC request tag. Synchronous requests block until the

response is generated or a timeout occurs (See the definition entry for

RPC_Manager.synchronous_request_timeout in the Registry on page 45.) The

response is then returned in the RCI Reply instead of being pushed to iDigi or queued in

an asynchronous response buffer. In the case of a timeout, the response will be returned

asynchronously. Only one request can be processed at a time, and the RCI target

The request that needs to be performed has the following structure:

<request_name>

<destination_address>value</destination_address>

<param1>value</param1>

<param2>value</param2>

</request_name>