TCP Client
uniflow.plugin.tcpclient •
Category: Generic Protocol •
Version: v1.0.3
TCP Client Plugin Reference Manual
1. Overview
Plugin Name: TCP Client
Type: Generic Protocol
Identifier: uniflow.plugin.tcpclient
Description
Receive data from external systems via raw TCP sockets.
2. Configuration Parameters
The following configuration fields are available in the User Interface for this plugin:
| Configuration Setting | Description |
|---|---|
| Target Host / IP Address | Specifies the target host / ip address. |
| Port | Numeric value specifying the port. |
| Connect Timeout (ms) | Numeric value specifying the connect timeout (ms). |
| Reconnect Delay (ms) | Specifies the reconnect delay (ms). |
3. Exposed Routes & Data Types
The following routes are available in the Uniflow catalog for this plugin:
| Display Name | Route ID | Kind | Category | Access | Data Type | |
|---|---|---|---|---|---|---|
| ? | ? | ? | ? | Read | Variant | |
| Data Received | DataReceivedItemId | Event | ? | Listen | Event Object | |
| Last Received | LastReceivedItemId | Value | ? | Read | String | |
| Send Data | SendDataItemId | Value | ? | Write | Execute | Json |
Route Parameters: Send Data
This route requires the following parameters when executing commands or writes.
| Parameter Name | Display Name | Type | Required |
|---|---|---|---|
message | Message | String | true |
WriteTypeParam | Write Type | String | true |
4. Usage Examples
Scenario A: Reading/Monitoring Data
To monitor data from TCP Client, add the corresponding Input Node in the Rule Editor and select the desired property from the catalog. Link its output to any logical comparison or directly to an Action Node.
Scenario B: Triggering Actions
If the plugin supports writable properties or actions, use an Action Node in the Rule Editor. Configure the Target property to point to the TCP Client action, and supply any required parameters mapping from your rule's logic.