Generic MQTT client
This library provides MQTT protocol client API that allows devices to talk to MQTT servers.
Mongoose OS implements MQTT 3.1.1 client functionality, and works with all popular MQTT server implementations, like AWS IoT, Google IoT Core, Microsoft Azure, IBM Watson, HiveMQ, Mosquitto, etc.
In order to talk to an MQTT server, configure MQTT server settings - see Configuration section below. Once configured, Mongoose OS keeps that connection alive by reconnecting and re-subscribing to all topics after disconnections - you do not need to implement the reconnection logic.
If you want to use TLS, set mqtt.ssl_ca_cert=ca.pem. Make sure that ca.pem
file has required CA certificates. If you want to use mutual TLS, set
mqtt.ssl_cert=CLIENT_CERT.pem and mqtt.ssl_key=PRIVATE_KEY.pem.
See example video (don't forget to set mqtt.enable=true before you try it):
Configuration
The MQTT library adds mqtt section to the device configuration:
{
"clean_session": true, // Clean session info stored on server
"client_id": "", // If not set, device.id is used
"enable": false, // Enable MQTT functionality
"keep_alive": 60, // How often to send PING messages in seconds
"pass": "", // User password
"reconnect_timeout_min": 2, // Minimum reconnection timeout in seconds
"reconnect_timeout_max": 60, // Maximum reconnection timeout in seconds
"server": "iot.eclipse.org", // Server to connect to. if `:PORT` is not specified,
// 1883 or 8883 is used depending on whether SSL is enabled.
"ssl_ca_cert": "", // Set this to file name with CA certs to enable TLS
"ssl_cert": "", // Client certificate for mutual TLS
"ssl_cipher_suites": "", // TLS cipher suites
"ssl_key": "", // Private key for the client certificate
"ssl_psk_identity": "", // If set, a preshared key auth is used
"ssl_psk_key": "", // Preshared key
"user": "", // MQTT user name, if MQTT auth is used
"will_message": "", // MQTT last will message
"will_topic": "" // MQTT last will topic
}Reconnect behavior and backup server
It is possible to have a "backup" server that device will connect to if it fails to connect to the primary server.
Backup server is configured under the mqtt1 section which contains exactly the same parameters as mqtt described above.
Device will first try to connect to the main server configured under mqtt.
It will keep connecting to it, increasing the reconnection interval from reconnect_timeout_min to reconnect_timeout_max.
Reconnection interval is doubled after each attempt so for values above there will be
connection attempts after 2, 4, 8, 16, 32 and 60 seconds.
After reaching the maximum reconnect interval and if mqtt1.enable is set, it will switch to the mqtt1
configuration and reset the reconnect interval, so it will try to connect to mqtt1 the same way.
If that works, it will stay connected to mqtt1. If connection drops, it will try to reconnect to mqtt1
in the same way. If connection to backup server fails, it will go back to the main server and so on.