MQTT Flex with LARA-R6, SARA-R5 and SARA-R422
Our first release of MQTT Flex utilises the DTLS support within the native MQTT-SN client on the u-blox LARA-R6, SARA-R5 and SARA-R422x modules.
For SARA-R5, "00B" module versions are not supported. "01B" or newer modules with at least firmware version 03.14,A00.01 are needed. For SARA-R422x, a SARA-R422S or SARA-R422M8S module with firmware version 00.12,A00.00 or newer is needed.
You can follow the instructions in the AT Commands Manual for how to use the MQTT-SN Client and security profiles.:
Some simple examples to get you up and running quickly are listed below.
Configure the module
Specify the client key and certificate to be used
This example assumes you have saved the client key and certificate generated by the Thingstream platform for your Flex Thing to the file system of the SARA module using the AT+UDWNFILE command using the file names device.pem for the certificate and device.key for the key.
Configure the DTLS security profile
The following commands set up the DTLS security profile which the MQTT-SN client will make use of.
Set the profile ID to use. This examples uses profile 0:
Set the certificate validation level:
Set profile 0 to accept TLS v1.2:
Set the cipher suite:
Set the client key and certificate to be used (as created in the previous step):
Configure the MQTT-SN client to use your MQTT Flex thing with the security profile
Set the client ID (copy from Thingstream portal):
Configure the MQTT-SN gateway endpoint:
Set the client to use the required DTLS profile:
Using the MQTT-SN Client
Once you have completed the MQTT-SN client configuration, you will need to set up the packet switched data configuration to use the APN specified by your MNO. You can then proceed with the MQTT-SN commands e.g.
Expect +UUMQTTSNC: 1,1 as a response to confirm you are connected. You should also see a green dot next to your Thing in the management console.
Register a topic
Before you can publish to a normal topic, you need to register with with the broker and get back a topic ID.
Expect +UUMQTTSNC: 2,1,1 as a response to confirm the registration. The final argument in the response is the topic ID to use when you publish.
Expect +UUMQTTSNC: 4,1 as a response to confirm the publish. You will also now see a new device originated message in the activity tab for your Thing in the management console.
To receive messages on your module, you need to subscribe to a topic.
Expect +UUMQTTSNC: 5,1,0,1 as a response to confirm you have subscribed. You will also now see a new subscription in the activity tab for your Thing in the management console.
Now if you publish a message to "my/subscribe/topic " you will see it arrive on the module. You can use the "Send Message" function in the management console to send a test message. Check out the guide here to see how.
Read a received message
When the message arrives, you'll see +UUMQTTSNC: 9,1 in the terminal. You can read the message with the following command.
In this section
IoT Communication-as-a-Service plans
Thingstream Management Console
Still need help?
If you need more help or have any questions, please send an email to firstname.lastname@example.org.