The “UDP :: Abstract JSON” device adapter will accept JSON encoded ASCII data from devices via UDP datagrams and it can send data to devices via UDP datagrams.
A device will generate a message that is sent to the Fusion Connect platform via an “Inbound” message. The Fusion Connect server can be configured to send a message to the device using a device directive which will result in an outbound message to be sent to the device via a UDP datagram.
See JSON Encoded Data for more information.
Directive Messaging Examples This adapter will require the hostname (or IP address) and port number of where to send the UDP datagram and that is given to the adapter via a field in the directive message with a field code value of “remoteaddress” (with the trailing underscore character). This is a required field for this adapter so it will know where to send the message data. When you create an outbound message definition it must contain a text field with this field code value.
The routine that generates the directive message must supply a value for the “remoteaddress” field that is in the following format:
your.hostname.here:port
ip_address:port
A colon “:” character is used to separate the port number value from the IP address or hostname portion of the field value.
The port number specified is the port number the device is listening for inbound UDP datagrams from the Fusion Connect device adapter. The Fusion Connect Connect device adapter must be able to access the specified remote address via the public internet or a private VPN connection.
Here’s an example of an outbound message definition in an UDP :: Abstract JSON device profile. This message is sending Boolean, Calendar, Integer, Number, Location, and Text fields.