Contains miscellaneous identifiers used throughout the Qt MQTT module. More…
This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE
The payload format provides information on the content of a message. This can help other clients to handle the message faster.
The format is not specified.
The payload of the message is formatted as UTF-8 Encoded Character Data.
This enum type specifies the available states of a message. Depending on the QoS and role of the client, different message statuses are expected.
The message status is unknown.
The client received a message for one of its subscriptions. This applies to QoS levels 1 and 2.
A message has been acknowledged. This applies to QoS 1 and states that the message handling has been finished from the client side.
A message has been received. This applies to QoS 2.
A message has been released. This applies to QoS 2. For a publisher the message handling has been finished.
A message has been completed. This applies to QoS 2 and states that the message handling has been finished from the client side.
This enum type specifies the available error codes.
The specified action has succeeded.
A subscription with QoS level 0 has been created.
A subscription with QoS level 1 has been created.
A subscription with QoS level 2 has been created.
The message has been accepted by the server, but there are no subscribers to receive this message. A broker may send this reason code instead of Success.
No matching Topic Filter is being used by the Client.
Continue the authentication with another step.
Initiate a re-authentication.
An unspecified error occurred.
The packet sent to the server is invalid.
A protocol error has occurred. In most cases, this will cause the server to disconnect the client.
The packet is valid, but the recipient rejects it.
The requested protocol version is not supported by the server.
The client ID is invalid.
The username or password specified is invalid.
The client is not authorized for the specified action.
The server to connect to is not available.
The server to connect to is not available. The client is asked to try at a later time.
The client has been banned from the server.
The authentication method specified is invalid.
The topic filter specified is invalid.
The topic name specified is invalid.
The message ID used in the previous packet is already in use.
The message ID used in the previous packet has not been found.
The packet received is too large. See also
An administratively imposed limit has been exceeded.
The payload format is invalid. See also
The server does not support retained messages. See also
The QoS level requested is not supported. See also
The server the client tries to connect to is not available. See also
The server the client tries to connect to has moved to a new address. See also
Shared subscriptions are not supported. See also
The connection rate limit has been exceeded.
Subscription IDs are not supported. See also
Subscriptions using wildcards are not supported by the server. See also
Not all values are available in every use case. Especially, some servers will reject a reason code not suited for a specific command. See below table to highlight expected reason codes for specific actions.