mosquitto_sub — an MQTT version 5/3.1.1/3.1 client for subscribing to topics
--retained-only ] [
] | [
mosquitto_sub is a simple MQTT version 5/3.1.1 client that will subscribe to topics and print the messages that it receives.
In addition to subscribing to topics,
mosquitto_sub can filter out received messages
so they are not printed (see the
-T option) or
unsubscribe from topics (see the
Unsubscribing from topics is useful for clients connecting with
clean session set to false.
mosquitto_sub supports TLS encrypted connections. It is strongly recommended that you use an encrypted connection for anything more than the most basic setup.
To enable TLS connections when using x509 certificates, one of
be provided as an option.
Alternatively, if the
-p 8883 option is used
then the OS provided certificates will be loaded and neither
To enable TLS connections when using TLS-PSK, you must use the
--psk and the
The options below may be given on the command line, but may also
be placed in a config file located at
$HOME/.config/mosquitto_sub with one pair of
per line. The values in the config file will be used as defaults
and can be overridden by using the command line. The exceptions to
-T, which if
given in the config file will not be overridden. Note also that
currently some options cannot be negated, e.g.
-S. Config file lines that have a
# as the first character are treated as comments
and not processed any further.
Bind the outgoing connection to a local ip address/hostname. Use this argument if you need to restrict network communication to a particular interface.
Disable 'clean session' / enable persistent client mode. When this argument is used, the broker will be instructed not to clean existing sessions for the same client id when the client connects, and sessions will never expire when the client disconnects. MQTT v5 clients can change their session expiry interval with the
When a session is persisted on the broker, the subscriptions for the client will be maintained after it disconnects, along with subsequent QoS 1 and QoS 2 messages that arrive. When the client reconnects and does not clean the session, it will receive all of the queued messages.
If using this option, the client id must be set manually with
Define the path to a file containing PEM encoded CA certificates that are trusted. Used to enable SSL communication.
Define the path to a directory containing PEM encoded CA certificates that are trusted. Used to enable SSL communication.
--capathto work correctly, the certificate files must have ".crt" as the file ending and you must run "openssl rehash <path to capath>" each time you add/remove a certificate.
Define the path to a file containing a PEM encoded certificate for this client, if required by the server.
Disconnect and exit the program immediately after the given count of messages have been received. This may be useful in shell scripts where on a single status value is required, for example.
-Rto print only the first set of fresh messages (i.e. that does not have the retained flag set), or with
-Tto filter which topics are processed.
Enable debug messages.
Use an MQTT v5 property with this publish. If you use this option, the client will be set to be an MQTT v5 client. This option has two forms:
-D command identifier value
-D command identifier name value
commandis the MQTT command/packet identifier and can be one of CONNECT, PUBACK, PUBREC, PUBCOMP, SUBSCRIBE, UNSUBSCRIBE, DISCONNECT, AUTH, or WILL. The properties available for each command are listed in the Properties section.
identifieris the name of the property to add. This is as described in the specification, but with '-' as a word separator. For example:
payload-format-indicator. More details are in the Properties section.
valueis the value of the property to add, with a data type that is property specific.
nameis only used for the
user-propertyproperty as the first of the two strings in the string pair. In that case,
valueis the second of the strings in the pair.
If this option is given, mosquitto_sub will exit immediately that all of its subscriptions have been acknowledged by the broker. In conjunction with
-cthis allows a durable client session to be initialised on the broker for future use without requiring any messages to be received.
Specify output printing format. This option allows you to choose what information from each message is printed to the screen. See the Output Format section below for full details.
This option overrides the
-voption, but does not override the
Display usage information.
Specify the host to connect to. Defaults to localhost.
The id to use for this client. If not given, a client id will be generated depending on the MQTT version being used. For v3.1.1/v3.1, the client generates a client id in the format
mosq-XXXXXXXXXXXXXXXXXX, where the
Xare replaced with random alphanumeric characters. For v5.0, the client sends a zero length client id, and the server will generate a client id for the client.
This option cannot be used at the same time as the
Provide a prefix that the client id will be built from by appending the process id of the client. This is useful where the broker is using the clientid_prefixes option. Cannot be used at the same time as the
When using certificate based encryption, this option disables verification of the server hostname in the server certificate. This can be useful when testing initial server configurations but makes it possible for a malicious third party to impersonate your server through DNS spoofing, for example. Use this option in testing only. If you need to resort to using this option in a production environment, your setup is at fault and there is no point using encryption.
The number of seconds between sending PING commands to the broker for the purposes of informing it we are still connected and functioning. Defaults to 60 seconds.
Define the path to a file containing a PEM encoded private key for this client, if required by the server.
Specifies the type of private key in use when making TLS connections.. This can be "pem" or "engine". This parameter is useful when a TPM module is being used and the private key has been created with it. Defaults to "pem", which means normal private key files are used.
Specify specify user, password, hostname, port and topic at once as a URL. The URL must be in the form: mqtt(s)://[username[:password]@]host[:port]/topic
If the scheme is mqtt:// then the port defaults to 1883. If the scheme is mqtts:// then the port defaults to 8883.
Do not append an end of line character to the payload when printing. This allows streaming of payload data from multiple messages directly to another application unmodified. Only really makes sense when not using
Disable Nagle's algorithm for the socket. This means that latency of sent messages is reduced, which is particularly noticeable for small, reasonably infrequent messages. Using this option may result in more packets being sent than would normally be necessary.
Connect to the port specified. If not given, the default of 1883 for plain MQTT or 8883 for MQTT over TLS will be used.
Provide a password to be used for authenticating with the broker. Using this argument without also specifying a username is invalid when using MQTT v3.1 or v3.1.1. See also the
When using the JSON output format %j or %J, the default is to print in an unformatted fashion. Specifying
--prettyprints messages in a prettier, more human readable format.
Specify a SOCKS5 proxy to connect through. "None" and "username" authentication types are supported. The
socks-urlmust be of the form
socks5h://[username[:password]@]host[:port]. The protocol prefix
socks5hmeans that hostnames are resolved by the proxy. The symbols %25, %3A and %40 are URL decoded into %, : and @ respectively, if present in the username or password.
If username is not given, then no authentication is attempted. If the port is not given, then the default of 1080 is used.
Provide the hexadecimal (no leading 0x) pre-shared-key matching the one used on the broker to use TLS-PSK encryption support.
--psk-identitymust also be provided to enable TLS-PSK.
The client identity to use with TLS-PSK support. This may be used instead of a username if the broker is configured to do so.
The QoS is identical for all topics subscribed to in a single instance of mosquitto_sub.
If this argument is given, no runtime errors will be printed. This excludes any error messages given in case of invalid user input (e.g. using
--portwithout a port).
If this argument is given, messages that are received that have the retain bit set will not be printed. Messages with retain set are "stale", in that it is not known when they were originally published. When subscribing to a wildcard topic there may be a large number of retained messages. This argument suppresses their display.
This option can be used to reduce the proportion of messages that mosquitto_sub prints. The default behaviour is to print all incoming messages. Setting the
chanceto a floating point value between 0.1 and 100.0 will ensure that on average that percentage of messages will be printed.
If this argument is given, the when mosquitto_sub receives a message with the retained bit set, it will send a message to the broker to clear that retained message. This applies to all received messages except those that are filtered out by the
-Toption. This option still takes effect even if
-Ris used. See also the
Remove all retained messages on the server, assuming we have access to do so, and then exit:
mosquitto_sub -t '#' --remove-retained --retained-onlyExample 2.
Remove a whole tree, with the exception of a single topic:
mosquitto_sub -t 'bbc/#' -T bbc/bbc1 --remove-retained
If this argument is given, only messages that are received that have the retain bit set will be printed. Messages with retain set are "stale", in that it is not known when they were originally published. With this argument in use, the receipt of the first non-stale message will cause the client to exit. See also the
If this argument is given, the subscriptions will have the "retain as published" option set. This means that the retain flag on an incoming message will be exactly as set by the publishing client, rather than indicating whether the message is fresh/stale.
This option is not valid for MQTT v3.1/v3.1.1 clients.
Use SRV lookups to determine which host to connect to. Performs lookups to
_mqtt._tcp.<host>when used in conjunction with
-h, otherwise uses
_mqtt._tcp.<local dns domain>.
This option may be repeated to subscribe to multiple topics.
Suppress printing of topics that match the filter. This allows subscribing to a wildcard topic and only printing a partial set of the wildcard hierarchy.
For example, subscribe to the BBC tree, but suppress output from Radio 3:
This option may be repeated to filter out multiple topics or topic trees.
Provide a protocol to use when connecting to a broker that has multiple protocols available on a single port, e.g. MQTT and WebSockets.
A valid openssl engine id. These can be listed with openssl engine command.
SHA1 of the private key password when using an TLS engine. Some TLS engines such as the TPM engine may require the use of a password in order to be accessed. This option allows a hex encoded SHA1 hash of the password to the engine directly, instead of the user being prompted for the password.
If used, this will load and trust the OS provided CA certificates. This can be used in conjunction with
--capathand can be used on its own to enable TLS mode. This will be set by default if
-L mqtts://...is used, or if port is 8883 and no other certificate options are used.
Choose which TLS protocol version to use when communicating with the broker. Valid options are
tlsv1.1. The default value is
tlsv1.2. Must match the protocol version used by the broker.
Provide a username to be used for authenticating with the broker. See also the
Connect to a broker through a local unix domain socket instead of a TCP socket. This is a replacement for
-L. For example:
mosquitto_pub --unix /tmp/mosquitto.sock ...
socket_domainoption in mosquitto.conf (5) to configure Mosquitto to listen on a unix socket.
A topic that will be unsubscribed from. This may be used on its own or in conjunction with the
--topicoption and only makes sense when used in conjunction with
If used with
--topicthen subscriptions will be processed before unsubscriptions.
Note that it is only possible to unsubscribe from subscriptions that have previously been made. It is not possible to punch holes in wildcard subscriptions. For example, subscribing to
sensors/#and then unsubscribing from
sensors/+/temperatureas shown below will still result in messages matching the
sensors/+/temperaturebeing delivered to the client.
Note also that because retained messages are published by the broker on receipt of a SUBSCRIBE command, subscribing and unsubscribing to the same topic may result in messages being received at the client.
This option may be repeated to unsubscribe from multiple topics.
Print received messages verbosely. With this argument, messages will be printed as "topic payload". When this argument is not given, the messages are printed as "payload".
Specify which version of the MQTT protocol should be used when connecting to the remote broker. Can be
31, or the more verbose
mqttv31. Defaults to
Provide a timeout as an integer number of seconds. mosquitto_sub will stop processing messages and disconnect after this number of seconds has passed. The timeout starts just after the client has connected to the broker.
Specify a message that will be stored by the broker and sent out if this client disconnects unexpectedly. This must be used in conjunction with
The QoS to use for the Will. Defaults to 0. This must be used in conjunction with
If given, if the client disconnects unexpectedly the message sent out will be treated as a retained message. This must be used in conjunction with
The topic on which to send a Will, in the event that the client disconnects unexpectedly.
Set the session-expiry-interval property on the CONNECT packet. Applies to MQTT v5 clients only. Set to 0-4294967294 to specify the session will expire in that many seconds after the client disconnects, or use -1, 4294967295, or ∞ for a session that does not expire. Defaults to -1 if -c is also given, or 0 if -c not given.
If the session is set to never expire, either with -x or -c, then a client id must be provided.
There are three ways of formatting the output from mosquitto_sub.
In all cases a new-line character is appended for each message
received unless the
-N argument is passed to
Payload-only is the default output format and will print the payload exactly as it is received.
Verbose mode is activated with
-v and prints the
message topic and the payload, separated by a space.
The final option is formatted output, which allows the user to
define a custom output format. The behaviour is controlled with
-F format-string option. The format string is
a free text string where interpreted sequences are replaced by
different parameters. The available interpreted sequences are
Three characters are used to start an interpreted sequence:
Sequences starting with
% are either parameters
related to the MQTT message being printed, or are helper sequences
to avoid the need to type long date format strings for example.
Sequences starting with
@ are passed to the
function (with the @ replaced with a % - note that only the
character immediately after the @ is passed to strftime). This
allows the construction of a wide variety of time based outputs.
The output options for strftime vary from platform to platform, so
please check what is available for your platform. mosquitto_sub
does provide one extension to strftime which is
@N, which can be used to obtain the number of
nanoseconds passed in the current second. The resolution of this
option varies depending on the platform. The final sequence
\, which is used to input some
characters that would otherwise be difficult to enter.
The parameters %A, %C, %E, %F, %I, %l, %m, %p, %R, %S, %t, %x, and %X can have optional flags immediately after the % character.
The value should be zero padded. This applies to the parameters %A, %E, %F, %l, %m, %S, %X, and %x. It will be ignored for other parameters. If used with the
0flag will be ignored.
The value will be left aligned to the field width, padded with blanks. The default is right alignment, with either 0 or blank padding.
Some of the MQTT related parameters can be formatted with an option to set their field width in a similar way to regular printf style formats, i.e. this sets the minimum width when printing this parameter. This applies to the options %A, %C, %E, %F, %I, %l, %m, %p, %R, %S, %t, %x, %X.
%10t would set the minimum topic
field width to 10 characters.
Some of the MQTT related parameters can be formatted with an option to set a maximum field width in a similar way to regular printf style formats. This applies to the options %C, %I, %R, %t.
%10.10t would set the minimum topic
field width to 10 characters, and the maximum topic width to
10 characters, i.e. the field will always be exactly 10
MQTT related parameters
%%a literal %.
%Athe MQTT v5 topic-alias property, if present.
%Cthe MQTT v5 content-type property, if present.
%Dthe MQTT v5 correlation-data property, if present. Note that this property is specified as binary data, so may produce non-printable characters.
%Ethe MQTT v5 message-expiry-interval property, if present.
%Fthe MQTT v5 payload-format-indicator property, if present.
%lthe length of the payload in bytes.
%mthe message id (only relevant for messages with QoS>0).
%Pthe MQTT v5 user-property property, if present. This will be printed in the form key:value. It is possible for any number of user properties to be attached to a message, and to have duplicate keys.
%pthe payload raw bytes (may produce non-printable characters depending on the payload).
%qthe message QoS.
%Rthe MQTT v5 response-topic property, if present.
%rthe retained flag for the message.
%Sthe MQTT v5 subscription-identifier property, if present.
%tthe message topic.
%xthe payload with each byte as a hexadecimal number (lower case).
%Xthe payload with each byte as a hexadecimal number (upper case).
%IISO-8601 format date and time, e.g. 2016-08-10T09:47:38+0100
%jJSON output of message parameters and timestamp, with a quoted and escaped payload. For example
%JJSON output of message parameters and timestamp, with a non-quoted and non-escaped payload - this means the payload must itself be valid JSON. For example:
If the payload is not valid JSON, then the error message "Error: Message payload is not valid JSON on topic <topic>" will be printed to stderr.
%IISO-8601 format date and time, e.g. 2016-08-10T09:47:38+0100
%UUnix timestamp with nanoseconds, e.g. 1470818943.786368637
Time related parameters
@@a literal @.
@Xpass the character represented by
Xto the strftime function as
%X. The options supported are platform dependent.
@Nthe number of nanoseconds that have passed in the current second, with varying timing resolution depending on platform.
\\a literal \.
\ethe escape sequence, which can be used with ANSI colour codes to provide coloured output for example.
\nend of line.
The minimum requirement for this is to use
specify which topic the will should be sent out on. This will result in
a non-retained, zero length message with QoS 0.
--will-qos arguments to
modify the other will parameters.
allows adding properties to different stages of the mosquitto_sub
run. The properties supported for each command are as
authentication-data(binary data - note treated as a string in mosquitto_sub)
maximum-packet-size(32-bit unsigned integer)
receive-maximum(16-bit unsigned integer)
request-problem-information(8-bit unsigned integer)
request-response-information(8-bit unsigned integer)
session-expiry-interval(32-bit unsigned integer, note use
topic-alias-maximum(16-bit unsigned integer)
user-property(UTF-8 string pair)
correlation-data(binary data - note treated as a string in mosquitto_sub)
message-expiry-interval(32-bit unsigned integer)
payload-format-indicator(8-bit unsigned integer)
user-property(UTF-8 string pair)
will-delay-interval(32-bit unsigned integer)
mosquitto_sub returns zero on success, or non-zero on error. If the connection is refused by the broker at the MQTT level, then the exit code is the CONNACK reason code. If another error occurs, the exit code is a libmosquitto return value.
MQTT v3.1.1 CONNACK codes:
1Connection refused: Bad protocol version
2Connection refused: Identifier rejected
3Connection refused: Server unavailable
4Connection refused: Bad username/password
5Connection refused: Not authorized
MQTT v5 CONNACK codes:
131Implementation specific error
132Unsupported protocol version
133Client ID not valid
134Bad username or password
139Server shutting down
140Bad authentication method
141Keep alive timeout
142Session taken over
143Topic filter invalid
144Topic name invalid
147Receive maximum exceeded
148Topic alias invalid
149Packet too large
148Message rate too high
153Payload format invalid
154Retain not supported
155QoS not supported
156Use another server
158Shared subscriptions not supported
159Connection rate exceeded
160Maximum connect time
161Subscription IDs not supported
162Wildcard subscriptions not supported
Note that these really are examples - the subscriptions will work if you run them as shown, but there must be something publishing messages on those topics for you to receive anything.
Subscribe to temperature information on localhost with QoS 1:
Subscribe to hard drive temperature updates on multiple machines/hard drives. This expects each machine to be publishing its hard drive temperature to sensors/machines/HOSTNAME/temperature/HD_NAME.
Subscribe to all broker status messages:
Specify the output format as "ISO-8601 date : topic : payload in hex"
Specify the output format as "seconds since epoch.nanoseconds : retained flag : qos : mid : payload length"
-F '%@[email protected] : %r : %q : %m : %l'
Topic and payload output, but with colour where supported.
-F '\e[92m%t \e[96m%p\e[0m'
Configuration file for default options.
mosquitto bug information can be found at https://github.com/eclipse/mosquitto/issues
See Alsomqtt(7) , mosquitto_pub(1) , mosquitto_rr(1) , mosquitto(8) , libmosquitto(3) , mosquitto-tls(7)