TCP & UDP Binding
The TCP and UDP bindings provide basic support for simple ASCII-based protocols. They send and receive data as ASCII strings. Data sent out is by default padded with a CR/LF. This should be sufficient for many home automation devices that take simple ASCII-based control commands, or that send back text-based status messages.
The TCP part of the binding has a built-in mechanism to keep connections to remote hosts alive, and will reset connections at regular intervals to overcome the limitation of "stalled" connections or remote hosts.
The TCP & UDP Bindings act as a network client or as a network server.
The TCP and UDP bindings can be configured in the files
Note: This is optional for the configuration and not necessary for receiving data. Item-defintions are enough for receiving data. (Developer confirm? 20150128). There's a bug in the binding that requires at least one udp configuration to be defined or the binding will not send UDP messages.
The indicated default values apply to both bindings unless otherwise noted.
|refreshinterval||only for receiving data||Refresh interval in milliseconds for polling data. Example: |
|port||only for receiving data||Port to listen on for incoming connections|
|addressmask||false||No||Set to |
|reconnectcron||Cron-like string to reconnect remote ends, e.g for unstable connection or remote ends. Example: |
|retryinterval||No||Interval between reconnection attempts when recovering from a communication error, in seconds. Example: |
|queue||false||No||Queue data whilst recovering from a connection problem (TCP only)|
|buffersize||1024||No||Maximum buffer size whilst reading incoming data|
|preamble||No||Pre-amble string that will be put in front of data being sent|
|postamble|| ||No||Post-amble that will be appended to data being sent|
|blocking||false`||No||Perform all write/read (send/receive) operations in a blocking mode, e.g. the binding will wait for a reply from the remote end after data has been sent|
|timeout||3000||No||Timeout, in milliseconds, to wait for a reply when initiating a blocking write/read operation|
|updatewithresponse||false||No||Update the status of items using the response received from the remote end (if the remote end sends replies to commands)|
|itemsharedconnections||false||No||Set to |
|bindingsharedconnections||false||No||Set to |
|directionssharedconnections||true||No||Set to |
The syntax for the TCP & UDP binding configuration string is explained here:
Note: The examples here below are for the TCP protocol. UDP binding configuration are exactly the same, one only has to substitute
The format of the binding configuration is simple and looks like this:
tcp="<direction>[<command>:<ip address>:<port>:<transformationrule>], <direction>[<command>:<ip address>:<port>:<transformationrule>], ..."
<direction> is one of the following values:
<for inbound-triggered communication, whereby the openHAB runtime will act as a server and listen for incoming connections from the specified
>for outbound-triggered communication, whereby the openHAB runtime will act as a client and establish an outbound connection to the specified
<command> is the openHAB command. For String items,
<command>: can be omitted.
<ip address> is the hostname or IP address in dotted notation of the remote host.
<transformationrule> can be one of:
- a string in the form of
TEXT1(TEXT2), and then it goes through the transformation
TEXT1with the argument
- empty or the string
default, and then it returns the State or the Command as a String;
- anything else and it sends back the
<transformationrule>field will be stripped of its single quotes if they are present; this means that in any case,
'TEXT'is treated the same way as
Here are some examples of valid binding configuration strings:
tcp=">[ON:192.168.0.1:3000:'MAP(my.device.map)'], >[OFF:192.168.0.1:3000:'MAP(my.device.map)']" // for a Switch Item where values are converted using the my.device.map tcp="<[192.168.0.2:3000:'REGEX((.*))']" // for a String Item that captures some state of a remote device that connects to openHAB