From e9547db82a65aace246551af4bb51dc0c02993de Mon Sep 17 00:00:00 2001 From: Jan Bouwhuis Date: Thu, 17 Nov 2022 21:12:35 +0100 Subject: [PATCH] Add section for setting MQTT protocol v5 (#24975) --- source/_integrations/mqtt.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/mqtt.markdown b/source/_integrations/mqtt.markdown index d85f6a56b25..569790bc3ce 100644 --- a/source/_integrations/mqtt.markdown +++ b/source/_integrations/mqtt.markdown @@ -88,6 +88,10 @@ The time in seconds between sending keep alive messages for this client. The def To enable a secure the broker certificate should be validated. If your broker uses a trusted certificate then choose `auto`. This will allow validation against certifite CAs bundled certificates. If a self-signed certificate is used, select `Custom`. A custom PEM encoded CA-certificate can be uploaded. Click `NEXT` to show the control to upload the CA certificate. If the server certificate does not match the hostname then validation will fail. To allow a connection without the verification of the hostname, turn the `Ignore broker certificate validation` switch on. +#### MQTT Protocol + +The MQTT protocol setting defaults to version `3.1.1`. If your MQTT broker supports MQTT version 5 you can set the protocol setting to `5`. + #### Securing the the connection With a secure broker connection it is possible to use a client certificate for authentication. To set the client certificate and private key turn on the option `Use a client certificate` and click "Next" to show the controls to upload the files. Only a PEM encoded client certificates together with a PEM encoded private key can be uploaded. Make sure the private key has no password set.