The subscribe with a context subscribes the currently active context client to the given topics. By default it doesn’t block the console like the Subscribe without a context does. To enable this behavior you can use the -s option.
client@host> sub -t <topics> [-t <topics>]... [-q <qos>]... [-oc] [-of <receivedMessagesFile>] [-b64] [-J] [-T] [-up <userProperties>]... [-s] [-h]
|The MQTT topic the client will subscribe to.|
|Use a defined quality of service level on all topics if only one QoS is specified. You can define a specific QoS level for every topic. The corresponding QoS levels will be matched in order to the given topics.|
|If this flag is set the output will be printed to the console.|
|If a file is given print the received publishes to the specified output file. If the file is not present it will be created.|
|If set the received publish messages will be base64 encoded.|
|Print the received publishes in pretty JSON format.|
|Prepend the specific topic name to the received publish.|
|A user property of the subscribe message.|
|The subscribe emulates the same behavior as the subscribe command in non-shell mode. |
Note: the subscriptions will be unsubscribed afterwards.
To cancel the command simply press Enter.
Subscribe to test topic on default settings (output will be written to Logfile. See Logging):
mqtt> con -i myClient myClient@localhost> sub -t test