MQTT Publisher

Node ID: mqttPublisher · Role: Sink · Realtime config: no

Description

Publishes pipeline data to an MQTT broker topic as JSON. Useful for integrating FusionHub with IoT dashboards, remote consumers, or message-based architectures.

Inputs / Outputs

Inputs: (none)
Outputs: (none)

Config aliases

MqttSink, mqttSink, mqttPublisher

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).

Key	Label	Type	Default	Description / Notes
`host`	Host	`string`	`localhost`	Hostname or IP of the MQTT broker.
`port`	Port	`number`	`1883`	MQTT broker TCP port.
`topic`	Topic	`string`	`fusionhub/output`	Topic to publish incoming data to.

Example node definition

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

{
  "sinks": {
    "mqttPublisher": {
      "inputEndpoints": [],
      "settings": {
        "host": "localhost",
        "port": 1883,
        "topic": "fusionhub/output"
      }
    }
  }
}

Field reference

Field	Purpose
`inputEndpoints`	List of upstream endpoints this node connects to (`outEndpoint` / `dataEndpoint` values from upstream nodes).
`inputDataFilter`	Optional whitelist of data types. Messages whose type isn’t in the list are dropped at the subscriber.
`settings`	All 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…