MQTT configuration

In Configuration → MQTT the MQTT connection can be enabled and configured.

When setting up a new broker connection, you need to configure the following parameters:

• Uri: the URI where the broker is located.
  By clicking on the protocol button in the URI textbox you can switch between the supported MQTT protocols:

  • mqtt://
  • mqtts://
  • ws://
  • wss://

• Port: the port at which the broker is listening.
  

• Use credentials: whether the broker requires a username and a password for the client.
• Advanced settings: it is strongly suggested to leave the adavanced settings at the default values.
  • Data encoding: encoding protocol for the data trasmitted through MQTT;
  • Network timeout: time (seconds) for how long to wait for a network responce before timing-out. Higher values can be used for networks with higher latencies;
  • Message retransmit timeout: time (seconds) after which the message will be retransmitted;
  • Reconnect timeout: time (seconds) after which the MQTT client will try to reconnect to the broker after the connection is lost.

If a secure protocol is selected (mqtts:// or wss://), the broker host Root CA certificate is mandatory.

If the gateway can reach the internet, the Root CA certificate of the broker could be automatically recovered from the gateway using the CA certificate button, otherwise you need to manually upload the Root CA certificate in PEM format.
To retrieve your broker Root CA Certificate you can also use the web utility that BlueUp has made available to its clients (see Root CA Certificates section).

If the gateway is able to resolve the Root CA certificate, it will be shown in the textbox.

Client certificate is optional (depending on your broker settings).

After pressing the Save button, a confirmation pop-up will appear.

After confirmation, in order to apply the new MQTT configuration, the gateway must be rebooted by pressing button on top right.

After the gateway has been rebooted, in Device panel Status section, all the services should appear configured and running.

Once Sink and MQTT configurations are completed, the gateway starts working as Wirepas Mesh Gateway on the configured Wirepas network.