That could work but only when the MQTT server is running on the same server where you installed the Experience Service. The best will be when you have some MQTT server which could be access via REST API so that you can use the standard rest API in Home.js and you do not need to use any additional libraries. I think the best approach is to install every thing in node.js server on the same location where you Experience Service is running . So you can install there also you MQTT clients etc and integrate in a WebServer which you can access then vom Studio where the standard REST api calls are supported. But all that is is not part of the supported functionality. I di not have examples for that - Possibly somebody else could provide a help
Here is samples for the node.js server npm - MQTT.js e.g. what I found when I searched
https://www.npmjs.com/package/mqtt#example
https://stackoverflow.com/questions/58852141/showing-mqtt-response-on-a-node-server-api
https://stackoverflow.com/questions/66506976/sending-mqtt-data-via-api
https://iot.stackexchange.com/questions/5828/how-to-make-a-mqtt-broker-and-a-rest-api-communicate
Also a test in chat AI toolsDeepSeek whiere simple I tested , did provide the following resuts (below):
Could you provide a code what access a MQTT brocker and will provide an node.js server where I could request the MQTT invormaton via REST api requests
Here's a Node.js example that connects to an MQTT broker and provides REST API endpoints to access MQTT information:
require('dotenv').config();
const express = require('express');
const mqtt = require('mqtt');
const cors = require('cors');
const app = express();
const port = process.env.SERVER_PORT || 3000;
const mqttUrl = process.env.MQTT_URL || 'mqtt://broker.hivemq.com';
const mqttTopics = process.env.MQTT_TOPICS ? process.env.MQTT_TOPICS.split(',') : ['test/topic'];
const mqttOptions = {
clientId: `mqtt_${Math.random().toString(16).substr(2, 8)}`,
clean: true,
connectTimeout: 4000,
reconnectPeriod: 1000,
};
const mqttDataStore = {};
const mqttClient = mqtt.connect(mqttUrl, mqttOptions);
mqttClient.on('connect', () => {
console.log('Connected to MQTT Broker');
mqttClient.subscribe(mqttTopics, (err) => {
if (!err) {
console.log(`Subscribed to topics: ${mqttTopics.join(', ')}`);
}
});
});
mqttClient.on('message', (topic, message) => {
console.log(`Received message on ${topic}: ${message.toString()}`);
mqttDataStore[topic] = {
message: message.toString(),
timestamp: new Date().toISOString()
};
});
mqttClient.on('error', (err) => {
console.error('MQTT Error:', err);
});
app.use(cors());
app.use(express.json());
app.get('/api/mqtt', (req, res) => {
res.json({
status: 'success',
data: mqttDataStore
});
});
app.get('/api/mqtt/:topic', (req, res) => {
const topic = req.params.topic;
if (mqttDataStore[topic]) {
res.json({
status: 'success',
data: mqttDataStore[topic]
});
} else {
res.status(404).json({
status: 'error',
message: 'Topic not found'
});
}
});
app.listen(port, () => {
console.log(`REST API server running on port ${port}`);
});
process.on('SIGINT', () => {
mqttClient.end();
process.exit();
});
To use this code:
-
Install required dependencies:
npm install express mqtt dotenv cors
-
Create a .env file with your configuration:
MQTT_URL=mqtt://your-broker-url
MQTT_TOPICS=topic1,topic2,topic3
SERVER_PORT=3000
-
Start the server:
Key features:
-
Connects to MQTT broker and subscribes to specified topics
-
Stores last received message for each topic
-
Provides REST API endpoints:
-
Handles MQTT connection errors and reconnections
-
Uses environment variables for configuration
Example usage with curl:
curl http://localhost:3000/api/mqtt
curl http://localhost:3000/api/mqtt/your/topic
To test with MQTT publishing (using mosquitto_pub):
mosquitto_pub -h broker.hivemq.com -t "test/topic" -m "Hello World"
Potential improvements you could add:
-
Authentication for both MQTT and REST API
-
History storage (not just last message)
-
WebSocket support for real-time updates
-
QoS configuration for MQTT
-
Message validation
-
Rate limiting for API endpoints
Remember to:
-
Keep your MQTT broker secure
-
Handle sensitive data appropriately
-
Add proper error handling for production use
-
Implement proper CORS configuration for your needs
-
Add request validation for the API endpoints
