Get desktop application:
View/edit binary Protocol Buffers messages
MQTT CONNECT packet's properties (MQTT v5.0) It should be empty on MQTT v3.1.1/v3.1 or others protocol
Used in:
Used in:
Used in:
, , , , , , , , , , , , , ,common name of client TLS cert
subject of client TLS cert
Used in:
,Used as response type in: HookProvider.OnClientConnack, HookProvider.OnClientConnect, HookProvider.OnClientConnected, HookProvider.OnClientDisconnected, HookProvider.OnClientSubscribe, HookProvider.OnClientUnsubscribe, HookProvider.OnMessageAcked, HookProvider.OnMessageDelivered, HookProvider.OnMessageDropped, HookProvider.OnProviderUnloaded, HookProvider.OnSessionCreated, HookProvider.OnSessionDiscarded, HookProvider.OnSessionResumed, HookProvider.OnSessionSubscribed, HookProvider.OnSessionTakenover, HookProvider.OnSessionTerminated, HookProvider.OnSessionUnsubscribed
(message has no fields)
Used in:
The registered hooks name Available value: "client.connect", "client.connack" "client.connected", "client.disconnected" "client.authenticate", "client.authorize" "client.subscribe", "client.unsubscribe" "session.created", "session.subscribed" "session.unsubscribed", "session.resumed" "session.discarded", "session.takenover" "session.terminated" "message.publish", "message.delivered" "message.acked", "message.dropped"
The topic filters for message hooks
Used in:
, , , ,The key of header can be: - username: * Readonly * The username of sender client * Value type: utf8 string - protocol: * Readonly * The protocol name of sender client * Value type: string enum with "mqtt", "mqtt-sn", ... - peerhost: * Readonly * The peerhost of sender client * Value type: ip address string - allow_publish: * Writable * Whether to allow the message to be published by emqx * Value type: string enum with "true", "false", default is "true" Notes: All header may be missing, which means that the message does not carry these headers. We can guarantee that clients coming from MQTT, MQTT-SN, CoAP, LwM2M and other natively supported protocol clients will carry these headers, but there is no guarantee that messages published by other means will do, e.g. messages published by HTTP-API
Used in:
, , ,Used in:
, , , , , , , , , , , , , , , , , , , ,Used in:
The QoS level
The group name for shared subscription
The Retain Handling option (MQTT v5.0) 0 = Send retained messages at the time of the subscribe 1 = Send retained messages at subscribe only if the subscription does not currently exist 2 = Do not send retained messages at the time of the subscribe
The Retain as Published option (MQTT v5.0) If 1, Application Messages forwarded using this subscription keep the RETAIN flag they were published with. If 0, Application Messages forwarded using this subscription have the RETAIN flag set to 0. Retained messages sent when the subscription is established have the RETAIN flag set to 1.
The No Local option (MQTT v5.0) If the value is 1, Application Messages MUST NOT be forwarded to a connection with a ClientID equal to the ClientID of the publishing
Used in:
,Used as response type in: HookProvider.OnClientAuthenticate, HookProvider.OnClientAuthorize, HookProvider.OnMessagePublish
Boolean result, used on the 'client.authenticate', 'client.authorize' hooks
Message result, used on the 'message.*' hooks
The responded value type - contiune: Use the responded value and execute the next hook - ignore: Ignore the responded value - stop_and_return: Use the responded value and stop the chain executing
Used in: