MQTT is a dominant communication protocol in IoT and edge scenarios, used by major products and services in manufacturing, automotive and other industries. Objective of this repo is to provide a robust plugin/trigger to receive MQTT messages in the Spin based wasm components.
This plugin is a trigger plugin i.e. it is activated when message is received on a configured MQTT topic. The plugin then instantiates a Wasm component and injects the message to the component, which in turn process the message and can optionally publish the messages to any of the available targets in Spin e.g. MQTT, Redis, Http endpoints.
Install MQTT Plugin:
spin plugin install --url https://github.com/spinkube/spin-trigger-mqtt/releases/download/canary/trigger-mqtt.json --yes
[Note: release management for multiple versions of this plugin/trigger will be added soon]
If you want to learn more about Spin's plugin model, read here.
Spin templates allow a Spin developer to quickly create the skeleton of an application or component, ready for the application logic to be filled in. As part of this repo, a new template is created to help build applications which make use of MQTT as a communication protocol/trigger.
Install MQTT Template:
spin templates install --git https://github.com/spinkube/spin-trigger-mqtt --upgrade
spin new -t mqtt-rust mqtt-app
The address
, username
, password
and topic
support the ability to be configured using Spin variables. An example of configuring the password using env variables:
#spin.toml
spin_manifest_version = 2
[application]
name = "mqtt-app"
version = "0.1.0"
description = "Demo app to receive MQTT messages."
authors = ["Suneet Nangia <[email protected]>"]
[variables]
password = { required = true }
[application.trigger.mqtt]
address = "mqtt://localhost:1883"
username = "user"
password = "{{ password }}"
keep_alive_interval = "30"
...
To inject the Spin variable using environment variables:
SPIN_VARIABLE_PASSWORD=password spin up
To skip authentication, set the username
and password
fields to empty strings:
[application.trigger.mqtt]
address = "mqtt://localhost:1883"
username = "admin"
password = "public"
keep_alive_interval = "30"
- Authenticates using anonymous and username/password to MQTT server.
- Receive messages from an MQTT topic per configured QoS.
[more MQTT client/subscription attributes will be available soon]
Download MQTTX CLI
brew install emqx/mqttx/mqttx-cli
Run the EMQX broker: https://mqttx.app/docs/get-started
docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8883:8883 -p 8084:8084 -p 18083:18083 emqx/emqx
The default username and password of the broker is admin
and public
.
Alternatively, use Mosquitto's public MQTT broker without authentication by setting the broker hostname to
test.mosquitto.org
.
For this simple dev loop, make sure you have access to an MQTT broker. The following steps assume you followed the section to run an MQTT broker locally.
- Open the repo in Dev Container or in pre-configured GitHub Codespace
- Run
make
to build and install the plugin locally. - Update
examples/mqtt-app/spin.toml
to reflect your MQTT server details and ensure it's accessible on the network. - Run
spin build --up --from examples/mqtt-app/spin.toml
to run the example Spin app. - Run
mqttx pub -t 'messages-in01' -h 'localhost' -p 1883 -u 'admin' -P 'public' -m 'Hello to MQTT Spin Component!'
with the hostname and credentials for your server, to publish the message which is then received by Spin app. - Optionally, run
make clean
to clean up and rebuild and install the plugin locally.