Lonbridge commands for input messages – Echelon LonBridg Server User Manual
Page 33
LonBridge Server User’s Guide
27
posProperty--;
}
}
LonBridge Commands for Input Messages
The LonBridge Server sends messages to a LonBridge application for either of
the following reasons:
• In response to specific LonBridge command
• To notify the LonBridge application of events, such as device discovery or
a property update
An application cannot send input messages.
The LonBridge XML for input messages includes the following XML elements:
<error>
The <error> message allows the LonBridge application to specify error
conditions, for example, for a GUI.
Table 4 lists the attributes for the <error> message.
Table 4. Attributes for the <error> Message
Attribute
Description
Required?
code
Specifies the error code.
Optional
description
Specifies the error description.
Optional
<is>
The <is> message announces the current value of the attributes for a device.
This message is used only for devices with a non-empty domain.
The attributes for the <is> message vary depending on the device and the
original output message for which this message is the response. The reported
attributes include a fixed set of attributes that identify the device, followed
by the attributes defined within the <device> element in the devices.xml file.
The fixed and variable attributes are defined in
on page
<is_new>
The <is_new> message announces new devices.
The attributes for the <is_new> message vary depending on the device. The
reported attributes include a fixed set of attributes that identify the device,
followed by the attributes defined within the <device> element in the
devices.xml file. For example, the device name comes from the name
attribute. The fixed and variable attributes are defined in
on page 16.
<is_pending>
The <is_pending> message announces the value of an object before any
change has occurred. This message allows the LonBridge Server to
acknowledge receipt of an output message so that a LonBridge application