Connect to the configured broker, write received Publish messages to the cPublished channel and handle commands from the cCommands channel.

Exceptions are propagated.

Reasons for why the connection was terminated.

Close the connection after sending a Disconnect message.

See also: Will

The various options when establishing a connection. See below for available accessors.

Defaults for Config, connects to a server running on localhost.

The communication channel used by publish, subscribe, etc.

Create a new Commands channel.

There should be one channel per MQTT connection. It might be reused by subsequent connections, but never by multiple connections concurrently.

Hostname of the broker.

Port of the broker.

Should the server forget subscriptions and other state on disconnects?

Optional Will message.

Optional username used for authentication.

Optional password used for authentication.

Time (in seconds) after which a PingReq is sent to the broker if no regular message was sent. Nothing means no limit.

Client ID used by the server to identify clients.

Function for debug-level logging.

The channel received Publish messages are written to.

The channel used by publish, subscribe, etc.

Maximum number of bytes read from the network at once.

Subscribe to the Topics with the corresponding QoS. Returns the QoS that were granted (lower or equal to the ones requested) in the same order.

The Topics may contain wildcards.

Unsubscribe from the given Topics.

Publish a message to the given Topic at the requested QoS level. The payload can be any sequence of bytes, including none at all. True means the server should retain the message for future subscribers to the topic.

The Topic must not contain wildcards.