MQTT

The MQTT connector can be used as both a field connector and an enterprise connector. It subscribes to MQTT topics for input properties and publishes to MQTT topics for output properties.

Connection settings

Setting	Description
Host	Hostname or IP address of the MQTT broker.
Port	Broker port.
TLS	Enables encrypted MQTT connections.
Validate certificate	Verifies the broker certificate when TLS is enabled.
Use self-signed certificate	Allows a custom CA certificate to be supplied when certificate validation is enabled.
Certificate	PEM certificate content for a self-signed trust chain.
Authentication	Enables username/password authentication.
Username	MQTT username.
Password	MQTT password.

Adding properties

Every MQTT property requires at least:

• Name
• Topic
• Direction
• Type

Additional options depend on the direction:

• Input properties subscribe to the configured topic.
• Input properties can use JSON Path to extract one value from a JSON payload.
• Output properties publish to the configured topic.
• Output properties can set MQTT QoS and Retain.

Input behavior

Input properties are updated whenever a message is received on the subscribed topic.

If JSON Path is filled in, Reniway parses the payload as JSON and extracts the selected token before updating the property value.

Output behavior

Output properties publish the new value when data is written to the property from a flow or data mapper.

If JSON Path is configured on an output property, Reniway builds a JSON object and writes the value into that path before publishing.

Notes

• Wildcard subscriptions follow standard MQTT topic rules.
• Avoid mixing read and write behavior on the same JSON object/topic combination, because writes can overwrite the payload structure you are also reading from.