This topic describes the new features, feature optimizations, and important bug fixes in each release of Message Queue for MQTT and provides references to help you understand the updates of Message Queue for MQTT.


Feature Description Type References
Subscription cleanup Subscriptions can be cleared for a specified topic in the Message Queue for MQTT console. If a subscriber client keeps offline for a period of time that exceeds the specified limit, Message Queue for MQTT deletes the subscription between the subscriber and the topic. New Clear subscriptions for a topic


Feature Description Type References
New version of the console The Message Queue for MQTT console is updated to improve user experience. Optimization


Feature Description Type References
Unique-certificate-per-device authentication
  • Message Queue for MQTT issues a unique device access credential to each client. The client can apply for access to Message Queue for MQTT by using the access credential.
  • API operations related to the unique-certificate-per-device feature are added. These operations can be used to manage device access credentials.


Feature Description Type References
Change of the billing method from subscription to pay-as-you-go The billing method of a Message Queue for MQTT instance can be changed from subscription to pay-as-you-go. New Change the billing method of an instance from subscription to pay-as-you-go


Feature Description Type References
API operation for sending messages from a backend application The API operation for sending messages from a backend application is added. New SendMessage
API operation for Message Queue for MQTT client status query The status of one or more Message Queue for MQTT clients can be queried at a time. New


Feature Description Type References
Kernel version upgrade The versions before and after the kernel version of an instance is upgraded are differentiated. The versions before the upgrade are unified to V2.x.x and those after the upgrade are unified to V3.x.x. New Changes in instance management
Cross-service data exchange rules
  • Data can be exchanged across cloud services based on rules, including data inbound rules, data outbound rules, and rules for client status notification.
  • These rules can be managed by using the console or by calling API operations.
Independent storage Starting from V3.x.x, Message Queue for MQTT no longer uses Message Queue for Apache RocketMQ to store messages, and topics of the two services are no longer interconnected by default. To exchange data between the two services, you must create and use data exchange rules. Message Queue for MQTT V3.x.x provides separate API operations to manage topics. New


Feature Description Type References
OpenAPI Tokens can be obtained by calling API operations. New List of operations by function