UDP Server
The UDP Server remote receives remote control commands as UDP packets. Unlike TCP, no connection needs to be established, which makes UDP a good choice for devices that send short, single messages, e.g. GPIO-to-network converters or broadcast consoles with “UDP trigger” functions.
Configuration
In the configuration app or Control Panel, go to Remote Control and add an interface of type UDP Server (Network category).
- Bind IP: The local IP address(es) to listen on, separated by commas. Leave empty to listen on all network interfaces.
- Port: The UDP port to listen on. The default is 9303.
Usage
Each UDP packet must contain exactly one command, as UTF-8 encoded text, e.g.
PLAYER 1-1 START. There is no authentication, and no reply is sent.
As there is no authentication, anybody who can reach the UDP port can control mAirList. Use the Bind IP setting and a firewall to restrict access.
Scripts can send UDP packets with the UDPSendString(Server, Port, Text) procedure,
e.g. to control another mAirList instance.