MQTT Configuration

MQTT is a standard messaging protocol for the Internet of Things (IoT). It is designed as an extremely lightweight publish/subscribe messaging transport that is ideal for connecting remote devices with a small code footprint and minimal network bandwidth.

EMQX is 100% MQTT 5.0 and 3.x compliant, this section will introduce the basic configuration items for MQTT-related features, covering topics like basic MQTT settings, subscription settings, session settings, force shutdown settings, and forced garbage collection settings.

Basic MQTT Configurations

This section will introduce the configuration settings that determine how the MQTT protocol will behave in terms of packet size, client ID length, topic levels, quality of service (QoS), topic alias, and retention.

TIP

You can also find the corresponding configuration items in EMQX Dashboard (Management -> MQTT Settings -> General). Once you configured these items with the Dashboard, your settings will override the same configuration items in emqx.conf.

Example Code:

mqtt {
  max_packet_size = 1MB
  max_clientid_len = 65535
  max_topic_levels = 128
  max_qos_allowed = 2
  max_topic_alias = 65535
  retain_available = true
}

Where,

Configuration Items	Dashboard UI	Description	Default value	Optinal Values
max_packet_size	Max Packet Size	MQTT packets are used to send messages between MQTT clients and EMQX. This sets the maximum MQTT packet size allowed.	1MB
max_clientid_len	Max Client ID Length	This sets the maximum length of an MQTT client ID. It can help to prevent clients from using excessively long client IDs that could cause issues.	65535	23 - 65535
max_topic_levels	Max Topic Levels	MQTT topics are used to organize and categorize messages. This sets the maximum number of levels allowed in an MQTT topic.	128	1 - 35
max_qos_allowed	Max QoS	QoS levels determine the level of reliability and delivery assurance for messages. This sets maximum quality of service (QoS) level that is allowed for MQTT messages.
max_topic_alias	Max Topic Alias	Topic aliases are a way to reduce the size of MQTT packets by using a shorter alias instead of the full topic name. This sets the maximum number of topic aliases that can be used in an MQTT session.	65535	1 - 65535
retain_available	Retain Available	Retained messages are used to store the last message published to a topic, so that new subscribers to the topic can receive the most recent message. This sets whether to enable retained messages feature in MQTT.	true	true, false

Subscription Settings

In EMQX, subscription refers to the process of a client subscribing to a topic on EMQX. When a client subscribes to a topic, it is indicating that it wants to receive messages published to that topic.

This section introduces how to configure shared subscription, wildcard subscription, and exclusive subscription.

TIP

You can also find the corresponding configuration items in EMQX Dashboard (Configuration -> MQTT -> General). Once you configured these items with the Dashboard, your settings will override the same configuration items in emqx.conf.

Example code:

mqtt {
	wildcard_subscription = true
  exclusive_subscription = false
  shared_subscription = true
  shared_subscription_strategy  =  round_robin
}

Where,

Configuration Items	Dashboard UI	Description	Default value	Optinal Values
wildcard_subscription	Wildcard Subscription Available	Wildcard subscriptions allow MQTT clients to subscribe to multiple topics using a single subscription, using wildcards such as + and #. This sets whether to enable wildcard subscription.	true	true, false
exclusive_subscription	Exclusive Subscription	Exclusive subscriptions allow only one MQTT client to subscribe to a topic at a time. This sets whether to enable exclusive subscriptions.	true	true, false
shared_subscription	Shared Subscription Available	Shared subscriptions allow multiple MQTT clients to share a subscription to a topic. This sets whether to enable shared subscriptions in MQTT.	true	true, false
shared_subscription_strategy		This setting defines the strategy for distributing messages among MQTT clients that share a subscription. Needed only shared_subscription is set to true.	round_robin	- random (Dispatch the message to a random selected subscriber) - round_robin (Select the subscribers in a round-robin manner) - sticky (Always use the last selected subscriber to dispatch, until the subscriber disconnects.) - hash (Select the subscribers by the hash of clientIds)

Delayed Publish Settings

The Delayed Publish feature allows clients to delay the publishing of a message to a topic for a specified amount of time. This feature is useful for scenarios where messages need to be published at specific times or when a certain condition is met.

This section introduces how to enable delayed publishing and how to set the maximum of delayed messages allowed:

Example code:

delay {
  delayed_publish_enabled = true
  max_delayed_messages = 0
}

Where,

• delayed_publish_enabled sets whether to enable the Delayed Publish feature in EMQX; default value: true, optional values: true, false.
• max_delayed_messages sets the maximum number of delayed messages allowed; default value: 0.

Keep Alive Settings

Keep Alive is the mechanism that ensures that a connection between an MQTT client and EMQX remains active even if no data is transmitted. This is how it works: when an MQTT client creates a connection to EMQX, it can set the Keep Alive variable header field in the connection request protocol packet to a non-zero value. For details about how Keep Alive works, see What is the MQTT Keep Alive parameter for?.

For clients with Keep Alive enabled, you can continue to customize the coefficient EMQX uses to confirm whether the keep alive duration of the client expires.

keepalive_backoff = 0.75

Where, Keep Alive Backoff (keepalive_backoff) is the coefficient EMQX uses to confirm whether the keep alive duration of the client expires. Default: 0.75. The calculation formular is as follows: $$ Keep Alive * Backoff * 2 $$

Session Settings

In MQTT, a session refers to the connection between a client and a broker. As in EMQX, When a client connects to EMQX, it establishes a session that allows it to subscribe to topics and receive messages, as well as publish messages to EMQX.

This section introduces how to configure sessions.

Example code:

session {
    max_subscriptions = infinity
    upgrade_qos = false
    max_inflight = 32
    retry_interval = 30s
    max_awaiting_rel = 100
    await_rel_timeout = 300s
    session_expiry_interval = 2h
    max_mqueue_len = 1000
    mqueue_priorities = disabled
    mqueue_default_priority = lowest
    mqueue_store_qos0 = true
    
    force_shutdown {
      max_message_queue_len = 1000
      max_heap_size = 32MB
    }

    force_gc {
      count  =  16000
      bytes  =  16MB
    }
  }

Where,

Configuration Item	Dashboard UI	Description	Default Value	Optional Values
max_subscriptions	Max Subscriptions	This sets the maximum number of subscriptions that the client is allowed to have	infinity	1 - infinity
upgrade_qos	Upgrade QoS	This sets whether the client is allowed to upgrade the QoS (Quality of Service) level of a message after it has been published.	false (disabled)	true, false
max_inflight	Max Inflight	This sets the maximum number of QoS 1 and QoS 2 messages that can be in flight (i.e., sent but not yet acknowledged) at any given time	32	1 - 65535
retry_interval	Retry Interval	This sets the interval at which the client should retry sending a QoS 1 or QoS 2 message.	30s unit: s	--
max_awaiting_rel	Max Awaiting PUBREL	This sets the pending QoS 2 messages in each session until either PUBREL is received or timed out. After reaching this limit, new QoS 2 PUBLISH requests will be rejected with error code 147(0x93). In MQTT, PUBREL is a control packet used in the message flow for QoS 2, which provides guaranteed message delivery.	100	1 - infinity
await_rel_timeout	Max Awaiting PUBREL TIMEOUT	This sets the amount of time to wait for a release of a QoS 2 message before receiving PUBREL. After reaching this limit, EMQX will release the packet ID and also generate a warning level log. Note: EMQX will forwarding of the received QoS 2 message whether it has received the PUBREL or not.	300s unit: s	--
session_expiry_interval	Session Expiry Interval	This sets the amount of time that a session can be idle before it is automatically closed. Note: For non-MQTT 5.0 clients only.	2h
max_mqueue_len	Max Message Queue Length	This sets the maximum allowed queue length when persistent clients are disconnected or inflight window is full.	1000	0 - infinity
mqueue_priorities	Topic Priorities	This sets the topic priorities, the configuration here will override that defined in mqueue_default_priority.	disabled The session uses the priority set by mqueue_default_priority.	disabled or 1 - 255
mqueue_default_priority	Default Topic Priorities	This sets the default topic priority.	lowest	highest， lowest
mqueue_store_qos0	Store QoS 0 Message	This sets whether to store QoS 0 message in the message queue when the connection is down but the session remains.	true	true, false
force_shutdown	--	This sets whether to enable the force shutdown feature if the queue length (max_message_queue_le) or heap size (max_heap_size) reaches the specified value.	true	true, false
force_shutdown.max_message_queue_le	--	This sets the maximum queue length to trigger a forced shutdown.	1000	1 - infinity
force_shutdown.max_heap_size	--	This sets the maximum heap size to trigger a forced shutdown.	32MB	--
force_gc	--	This sets whether to enable forced garbage collection if the specified message number (count) or byte received (bytes) is reached:	true	true, false
force_gc.count	--	This sets the received message number that will trigger the forced garbage collection.	16000	0 - infinity
force_gc.bytes	--	This sets the received byte number that will trigger the forced garbage collection.	16MB Unit: MB	--

TIP

To Configure MQTT via Dashboard, click Configuration -> MQTT on the left navigation menu of the Dashboard. Once you configured these items with the Dashboard, your settings will override the same configuration items in emqx.conf.

EMQX has offered more configuration items to serve customized needs better. For details, see Configuration Manual.