Skip to content

Broker ​

Advanced → Broker manages the MQTT broker connections that ThinkLink uses as message transport. A broker record defines where to connect (host, port, TLS certificates) and optionally a username/password. Forwarder rules then reference brokers as their source or target.

Broker management page

Broker Types ​

TypeDescription
ASThe built-in ThinkLink Application Server MQTT broker
ThinkLinkAnother ThinkLink deployment's broker (inter-instance bridging)
CustomizeAny third-party MQTT broker — fill in host, port, credentials, and TLS certs manually

Configuration Fields ​

FieldDescription
NameIdentifier for this broker record, referenced by Forwarder rules
TypeAS / ThinkLink / Customize — determines which extra fields appear
EnabledToggle to activate or suspend this broker connection without deleting it
usernameMQTT username (optional, depends on broker auth config)
URLmqtt:// or mqtts:// — host, port (default 1883), and optional path
caCA certificate for TLS verification (upload a .pem / .crt file)
certClient certificate for mutual TLS authentication

Actions ​

ButtonEffect
+ AddOpen the Broker dialog to create a new broker record
Details (row)View and edit an existing broker's configuration
More (row)Additional row-level actions (e.g. delete)

Column Reference ​

ColumnMeaning
IDBroker record ID
ErrMsgLast connection error message, if any; blank when the connection is healthy
OperationRow-level actions: Details / More
  • Using brokers in message routing rules → Forwarder

Custom Client ID (2.00.099) ​

Broker creation/editing supports optional options.client_id for Customize, AS and ThinkLink. A non-blank string is used unchanged as MQTT clientId. Omitted, null, empty or whitespace-only values use ${tenant_code}.${name}_${timestamp} automatically; the list displays “Auto-generated”. Generated values are not saved as custom configuration; clearing a custom value restores automatic generation on the next connection. No database migration is required.

json
{
  "options": {
    "client_id": "tenantA-forwarder-main"
  }
}

This is an options fragment, not a full save request; preserve other options when editing. Saving a change disconnects and rebuilds the connection through the existing workflow, potentially interrupting forwarding briefly. Avoid unintended duplicate IDs on the same Broker, which can replace each other's connections. A fixed ID alone guarantees neither session recovery nor reliability. Verify reconnect, SUBACK, subscription restoration, shared topics across scripts, and actual target messages. An offline target adds no buffering or replay guarantee; RUNNING alone is insufficient. MQTT redelivery can still duplicate messages; use business message IDs for deduplication.