RaftMQTTManagerSysMod

MQTTManager SysMod

Built-in SysMod that connects to an MQTT broker and exposes per-topic Comms Channels. Inbound MQTT messages on subscribed topics enter the channel system as if they had arrived over BLE or HTTP; outbound publishes are emitted on the corresponding topic.

Source: RaftSysMods/components/MQTTManager/

What it provides

• Single-connection MQTT client (RaftMQTTClient) with auto-reconnect.
• Per-topic channel registration: each entry in topics becomes one channel, named after the topic.
• Bridge from MQTT subscribe → comms channel inbound, and channel outbound → MQTT publish.

SysType configuration

{
    "name": "MQTTManager",
    "enable": 1,
    "brokerHostname": "broker.example.com",
    "brokerPort": 1883,
    "clientID": "",
    "topics": [
        {
            "name": "devices/in",
            "inbound": true,
            "protocol": "RICJSON"
        },
        {
            "name": "devices/out",
            "inbound": false,
            "protocol": "RICJSON"
        }
    ]
}

Top-level key	Default	Meaning
enable	false	Master switch
brokerHostname	""	MQTT broker hostname
brokerPort	1883	Broker port
clientID	system unique string	MQTT client identifier
topics	[]	Per-topic configuration array

Topic key	Default	Meaning
name	topic<n>	MQTT topic
inbound	true	If true, subscribe; messages enter the comms channel as inbound. If false, the topic is publish-only.
protocol	impl-defined	Codec to attach (RICJSON is typical for MQTT)

REST endpoints exposed

None — MQTTManager is purely a transport.

Related

• Comms Channels
• Network Manager SysMod — required for an active network connection