add support for MQTT

This commit adds support for MQTT in the cloud module.

Signed-off-by: Simen S. Røstad <simen.rostad@nordicsemi.no>

Author: simensrostad

.github/actions/build-step/action.yml

@@ -57,6 +57,11 @@ runs:
             -d build \
             -p --sysbuild \
             -- -DEXTRA_CONF_FILE="overlay-debug-att.conf" 2>&1 | tee ../../artifacts/build_output_${{ inputs.short_board }}_debug.log
+        elif [[ "${{ inputs.mqtt }}" == "true" ]]; then
+          west build -b ${{ inputs.board }} \
+            -d build \
+            -p --sysbuild \
+            -- -DEXTRA_CONF_FILE="$(PWD)/../examples/modules/cloud/overlay-mqtt.conf" 2>&1 | tee ../../artifacts/build_output_${{ inputs.short_board }}_mqtt.log
         else
           west build -b ${{ inputs.board }} \
             -d build \

.github/workflows/build.yml

@@ -188,6 +188,16 @@ jobs:
           version: ${{ env.VERSION }}-patched
           path: asset-tracker-template/app
 
+      # Asset Tracker Template firmware build with MQTT cloud moduel for Thingy91x
+      - name: Build thingy91x firmware with MQTT cloud module
+        if: ${{ github.event_name != 'pull_request' }}
+        uses: ./asset-tracker-template/.github/actions/build-step
+        with:
+          board: thingy91x/nrf9151/ns
+          short_board: thingy91x
+          version: ${{ env.VERSION }}-mqtt
+          path: asset-tracker-template/app
+
       - name: Upload artifacts
         uses: actions/upload-artifact@v4
         with:

.github/workflows/target-test.yml

@@ -206,6 +206,27 @@ jobs:
           MEMFAULT_PROJECT_SLUG: ${{ vars.MEMFAULT_PROJECT_SLUG }}
           APP_BUNDLEID: ${{ env.APP_BUNDLEID }}
 
+      - name: Test MQTT Firmware
+        if: ${{ matrix.device == 'thingy91x' && endsWith(inputs.artifact_fw_version, '-mqtt') }}
+        working-directory: asset-tracker-template/tests/on_target
+        run: |
+          pytest -v \
+            --junit-xml=results/test-results-mqtt.xml \
+            --html=results/test-results-mqtt.html --self-contained-html \
+            tests/test_functional/test_mqtt.py
+        shell: bash
+        env:
+          SEGGER: ${{ env.RUNNER_SERIAL_NUMBER }}
+          DUT_DEVICE_TYPE: ${{ vars.DUT_DEVICE_TYPE }}
+          UUID: ${{ env.UUID }}
+          NRFCLOUD_API_KEY: ${{ secrets.NRF_CLOUD_API_KEY }}
+          LOG_FILENAME: att_test_log_mqtt
+          TEST_REPORT_NAME: ATT MQTT Firwmare Test Report
+          MEMFAULT_ORGANIZATION_TOKEN: ${{ secrets.MEMFAULT_ORGANIZATION_TOKEN }}
+          MEMFAULT_ORGANIZATION_SLUG: ${{ vars.MEMFAULT_ORGANIZATION_SLUG }}
+          MEMFAULT_PROJECT_SLUG: ${{ vars.MEMFAULT_PROJECT_SLUG }}
+          APP_BUNDLEID: ${{ env.APP_BUNDLEID }}
+
       - name: Generate and Push Power Badge
         if: ${{ matrix.device }} == ppk_thingy91x
         continue-on-error: true

CMakeLists.txt

@@ -4,7 +4,4 @@
 # This CMake file is picked by the Zephyr build system because it is defined
 # as the module CMake entry point (see zephyr/module.yml).
 
-
-zephyr_include_directories(include)
-
-add_subdirectory(drivers)
+add_subdirectory(examples/modules/cloud)

Kconfig

@@ -0,0 +1,8 @@
+# Copyright (c) 2025 Nordic Semiconductor ASA
+# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
+#
+# This Kconfig file is picked by the Zephyr build system because it is defined
+# as the module Kconfig entry point (see zephyr/module.yml). You can browse
+# module options by going to Zephyr -> Modules in Kconfig.
+
+rsource "examples/modules/cloud/Kconfig.cloud_mqtt"

app/CMakeLists.txt

@@ -15,7 +15,10 @@ target_include_directories(app PRIVATE src/common)
 # Add main application source
 target_sources(app PRIVATE src/main.c)
 
-# Include mandatory module source folders
+# Module source folders
+add_subdirectory(src/modules/location)
+add_subdirectory(src/modules/cloud)
+add_subdirectory(src/modules/fota)
 add_subdirectory(src/modules/network)
 add_subdirectory(src/modules/button)
 add_subdirectory(src/cbor)
@@ -24,6 +27,3 @@ add_subdirectory(src/cbor)
 add_subdirectory_ifdef(CONFIG_APP_POWER src/modules/power)
 add_subdirectory_ifdef(CONFIG_APP_ENVIRONMENTAL src/modules/environmental)
 add_subdirectory_ifdef(CONFIG_APP_LED src/modules/led)
-add_subdirectory_ifdef(CONFIG_APP_LOCATION src/modules/location)
-add_subdirectory_ifdef(CONFIG_APP_CLOUD src/modules/cloud)
-add_subdirectory_ifdef(CONFIG_APP_FOTA src/modules/fota)

app/src/modules/cloud/CMakeLists.txt

@@ -4,7 +4,7 @@
 # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
 #
 
-target_sources(app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/cloud.c)
+target_sources_ifdef(CONFIG_APP_CLOUD app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/cloud.c)
 target_sources_ifdef(CONFIG_APP_CLOUD_SHELL app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/cloud_shell.c)
 target_include_directories(app PRIVATE .)
 

app/src/modules/fota/CMakeLists.txt

@@ -4,5 +4,5 @@
 # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
 #
 
-target_sources(app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/fota.c)
+target_sources_ifdef(CONFIG_APP_FOTA app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/fota.c)
 target_include_directories(app PRIVATE .)

app/src/modules/location/CMakeLists.txt

@@ -4,5 +4,5 @@
 # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
 #
 
-target_sources(app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/location.c)
+target_sources_ifdef(CONFIG_APP_LOCATION app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/location.c)
 target_include_directories(app PRIVATE .)

docs/common/customization.md

@@ -424,3 +424,66 @@ The dummy module is now ready to use. It provides the following functionality:
 To test the module, send a `DUMMY_SAMPLE_REQUEST` message to its zbus channel. The module will respond with a `DUMMY_SAMPLE_RESPONSE` containing the incremented counter value.
 
 This dummy module serves as a template that you can extend to implement more complex functionality. You can add additional message types, state variables, and processing logic as needed for your specific use case.
+
+## Using a different Cloud
+
+To connect to a generic MQTT server using the Asset Tracker Template, you can use the example cloud module provided under `examples/modules/cloud`. This module replaces the default nRF Cloud CoAP-based cloud integration with a flexible MQTT client implementation.
+
+### Overview
+
+- **Location and FOTA**: These features are deactivated when using the example MQTT module because they depend on nRF Cloud CoAP.
+- **FOTA and LOCATION channels**: The MQTT cloud module provides stub channel declarations for FOTA and LOCATION to avoid build errors. You can implement your own FOTA and LOCATION modules based on your chosen cloud service if needed.
+- **MQTT Client default configurations:**
+
+    - **Broker hostname:** mqtt.nordicsemi.academy
+    - **Port:** 8883
+    - **TLS:** Yes
+    - **Authentication:** Server only
+    - **CA:** modules/examples/cloud/creds/ca-cert.pem
+    - **Device ID** IMEI
+    - **Subscribed topic** imei/att-pub-topic
+    - **Publishing toptic** imei/att-sub-topic
+
+The default configuration does not require/enable mutual authentication meaning that the device does not authenticate itself to the server.
+That would require a device certificate/private key pair. However, the server is authenticated using the server certificate `ca-cert.pem`located in the module example folder.
+
+Configurations for the MQTT stack can be set in the `overlay-mqtt.conf` file and Kconfig options defined in `examples/modules/cloud/Kconfig.cloud_mqtt`.
+
+### How to use the MQTT Cloud Example
+
+1. **Build and flash with the MQTT overlay**
+
+   In the template's `app` folder, run:
+
+   ```sh
+   west build -p -b thingy91x/nrf9151/ns -- -DEXTRA_CONF_FILE="$(PWD)/../examples/modules/cloud/overlay-mqtt.conf" && west flash --erase --skip-rebuild
+   ```
+
+2. Observe that the device connects to the broker
+
+3. **Test using shell commands**
+
+4. **Shell module for testing**
+
+   The MQTT cloud module includes a shell module/commands for testing cloud publishing much like the default CoAP configuration.
+   To implement custom cloud shell commands this module can be used `examples/modules/cloud/cloud_mqtt_shell.c`
+
+### **Module State Machine**
+
+The cloud MQTT module uses a state machine to manage connection and reconnection logic. Below is a mermaid diagram representing the module's states:
+
+   ```mermaid
+   stateDiagram-v2
+       [*] --> STATE_RUNNING
+       STATE_RUNNING --> STATE_DISCONNECTED : NETWORK_DISCONNECTED
+       STATE_DISCONNECTED --> STATE_CONNECTING : NETWORK_CONNECTED
+       STATE_CONNECTING --> STATE_CONNECTING_ATTEMPT
+       STATE_CONNECTING_ATTEMPT --> STATE_CONNECTING_BACKOFF : CLOUD_CONN_FAILED
+       STATE_CONNECTING_BACKOFF --> STATE_CONNECTING_ATTEMPT : CLOUD_BACKOFF_EXPIRED
+       STATE_CONNECTING_ATTEMPT --> STATE_CONNECTED : CLOUD_CONN_SUCCESS
+       STATE_CONNECTED --> STATE_DISCONNECTED : NETWORK_DISCONNECTED
+       STATE_CONNECTED --> STATE_CONNECTED : PAYLOAD_CHAN / send_data()
+       STATE_CONNECTED --> STATE_CONNECTED : <module>_SAMPLE_RESPONSE / send_<module>_data()
+       STATE_CONNECTED --> STATE_CONNECTED : NETWORK_CONNECTED / (noop)
+       STATE_CONNECTED --> STATE_DISCONNECTED : exit / mqtt_helper_disconnect()
+   ```