Susi Server

MQTT Source

Node ID: mqttSource · Role: Source · Realtime config: no

Description

Subscribes to an MQTT broker topic and injects received messages into the pipeline as typed sensor data. Useful for ingesting data from IoT gateways or remote sensors.

Inputs / Outputs

Config aliases

MqttSource, mqttSource, mqttSubscriber

Properties

The following fields are exposed in the node’s Properties panel in the UI. Types map to UI widgets (e.g. string → text input, number → numeric, boolean → toggle, select → dropdown, json → JSON editor).

KeyLabelTypeDefaultDescription / Notes
hostHoststring192.168.1.200Hostname or IP of the MQTT broker to subscribe to.
portPortnumber1883MQTT broker TCP port (typically 1883 for plain, 8883 for TLS).
topicTopicstringtestTopicTopic to subscribe to. MQTT wildcards (+ and #) are supported.
clientIdClient IDstringFusionHubSubscriberClient identifier presented to the broker. Must be unique within the broker.
qosQoSnumber0MQTT Quality-of-Service level: 0 (at most once), 1 (at least once), or 2 (exactly once).

Example node definition

A full node definition in config.json looks like the block below. Paste it under the sources key of your config, keyed by the node’s instance name (any identifier; it doesn’t have to match the node ID).

{
  "sources": {
    "mqttSource": {
      "outEndpoint": "inproc://mqttSource_data",
      "settings": {
        "clientId": "FusionHubSubscriber",
        "host": "192.168.1.200",
        "port": 1883,
        "qos": 0,
        "topic": "testTopic"
      }
    }
  }
}

Field reference

FieldPurpose
outEndpointZMQ / inproc endpoint this source binds to publish its output. The runtime auto-generates one if omitted.
settingsAll user-configurable fields — see the Properties table above.

Connections can also be declared at the top-level connections array when settings.explicitConnections is true, as an alternative to filling inputEndpoints on each node.

Loading documentation…