Set a device LED
device://device-01/led/command/set
{
"on": true
}
IoT connector
MQTT Device Bridge
MQTT Device Bridge will map device, firmware, backend and frontend actions to shared URI routes. The goal is to control firmware and read telemetry without a separate SDK per layer.
What it does
- Publish firmware commands from a backend flow.
- Use the same device URI from frontend and host.
- Bridge telemetry into the registry runtime.
URI schemes
mqtt://
device://
Requirements
mqtt broker
Routes
Examples
Install command
curl -fsSL 'https://connect.ifuri.com/install?connectors=mqtt' | bash
This connector is planned. The installer is visible for contract design, but execution is disabled until the connector package is available.
Registry entry
{
"id": "mqtt",
"name": "MQTT Device Bridge",
"status": "planned",
"uriSchemes": [
"mqtt",
"device"
],
"routes": [
"mqtt://broker/topic/command/publish",
"device://device-01/led/command/set"
],
"install": {
"mode": "planned",
"pipSpec": "urirun-connectors-mqtt"
},
"hubUrl": "https://connect.ifuri.com/connectors/mqtt"
}