MQTT use cases span almost every industry that connects machines, vehicles or buildings to software. This guide walks through 15 real-world patterns grouped by industry, showing for each one the topic structure, the MQTT features that make it work and the broker scale it needs, so you can map your own project onto a proven design.
Why MQTT Keeps Showing Up
MQTT was born in industrial telemetry (the story of who invented MQTT starts on an oil pipeline), and the same properties make it fit far beyond that: small packets, push delivery over an outbound connection, QoS levels per message, retained "last known value" messages, and Last Will for presence. Wherever many devices produce data that several applications need to consume, the broker-centric model fits. If you are new to the protocol, start with our beginner MQTT tutorial.
MQTT Use Cases in Manufacturing
1. Machine monitoring and OEE
CNC machines, presses and packaging lines publish state, counts and alarms through PLC gateways. Dashboards and OEE calculators subscribe. Retained state messages mean a newly opened dashboard instantly shows every machine's current status.
Topic example: acme/izmir/machining/line1/cnc1/status
2. Unified Namespace
Instead of point-to-point integrations, every system (PLCs, MES, ERP, quality) publishes to one ISA-95-structured topic tree. Consumers subscribe to the branches they need. Sparkplug B adds standard payloads and birth/death state. See Sparkplug B and Unified Namespace for the full pattern.
3. Predictive maintenance
Vibration, temperature and current sensors publish high-frequency summaries. A separate analytics service subscribes, scores the data and publishes alerts back to the broker for maintenance dashboards. QoS 0 suits raw summaries; QoS 1 suits the alerts.
4. Multi-site aggregation
Each plant runs a local broker for autonomy and bridges a curated set of topics to a central cloud broker, so headquarters sees every site in one tree. Our guide to MQTT bridging shows the Mosquitto and Node-RED configs.
Energy and Utilities
5. Solar and battery monitoring
Inverters and battery management systems report power, state of charge and faults. Homeowners and installers watch live values in an app; the installer's backend subscribes across many sites with wildcards.
6. Smart metering and submetering
Building submeters publish consumption at intervals for tenant billing and energy dashboards. Persistent sessions and QoS 1 protect readings across short network outages.
7. EV charging stations
Chargers publish session state and receive commands (start, stop, power limits) on separate command topics. Last Will marks a charger offline immediately when it drops off the network. MQTT 5 message expiry keeps stale commands from executing after a reconnect.
Automotive and Logistics
8. Fleet and vehicle tracking
Vehicles publish GPS position, speed and ignition state over cellular. MQTT's small overhead keeps data costs down, and the persistent connection lets dispatch push messages instantly. The MQTT vehicle tracking guide covers topic design and payload sizing.
9. Cold chain monitoring
Temperature loggers in trucks and warehouses publish readings and threshold alerts. Retained messages show the latest reading per container; alerts go out the moment a limit is crossed. Pair this with an external historian subscriber so every reading is stored for compliance audits.
10. Warehouse automation
Conveyors, scanners and autonomous carts coordinate through the broker. Shared subscriptions spread incoming scan events across several worker services, so throughput scales by adding workers.
Smart Home and Buildings
11. Home automation
Home Assistant, Node-RED and Zigbee or Wi-Fi devices exchange states and commands through a broker. The publish/subscribe model means a light switch, a voice assistant and an automation rule can all control the same lamp.
12. Building management
HVAC controllers, occupancy sensors and lighting publish to a per-floor topic tree. Facility dashboards subscribe with wildcards, and threshold alerts flag rooms that drift out of comfort range.
Agriculture, Health and Consumer Products
13. Smart agriculture and irrigation
Soil moisture and weather sensors, often on battery or solar power, publish infrequently. Irrigation controllers subscribe to commands. Low bandwidth and tolerance of intermittent links are exactly what MQTT was designed for.
14. Remote patient and equipment monitoring
Medical-adjacent devices and lab equipment send status and readings to monitoring apps. TLS, unique credentials per device and careful topic design keep data private. Never use a public broker for anything sensitive.
15. Connected products and mobile apps
Appliances, wearables and consumer gadgets use MQTT to receive commands from a mobile app in real time. Browsers and apps connect over secure WebSocket, while devices use TLS on 8883.
Common Building Blocks Across MQTT Use Cases
Looking across these 15 examples, the same features appear again and again:
- Hierarchical topics from general to specific, often following ISA-95 in industry.
- Retained messages for current state.
- Last Will for reliable online/offline status.
- QoS 0 for frequent telemetry, QoS 1 for commands and alerts.
- Separate command and telemetry branches to keep permissions and loops under control.
- External tools as clients (Node-RED, Telegraf, Python services, Home Assistant) for storage, analytics and integrations.
Choosing a ConnectMQ Plan for Each Scale
These patterns differ mostly in scale and isolation requirements. Here is how they map to ConnectMQ plans, based on each plan's documented limits:
| Plan | Key limits and features | Fits use cases like |
|---|---|---|
| Serverless (Free) | Shared cluster, up to 25 connections, QoS 0 and 1, 256 KB messages | Prototypes, home automation, a single machine or small greenhouse |
| Serverless (Paid) | Up to 1,000 connections, QoS 2, 1 MB messages, shared subscriptions | Small fleets, charger networks, building monitoring, warehouse workers |
| Dedicated | Isolated cluster | Plant-wide Unified Namespace, multi-site aggregation |
| BYOC | Runs in your own cloud account, managed for you | Data residency or cloud-account policies |
| Self Managed Enterprise | Run it yourself | Fully on-premises or air-gapped requirements |
For industrial projects, ConnectMQ also detects ISA-95 and Unified Namespace topics, decodes Sparkplug B, and can republish Sparkplug B data into readable ISA-95 topics. The cloud MQTT broker guide compares hosting choices in more depth.
Try a Use Case in Five Minutes
Pick any example above and simulate it on the free public MQTT broker. Here is the machine-monitoring case with a retained status and a live temperature stream:
# Subscriber: a "dashboard" watching one line
mosquitto_sub -h broker.connectmq.com -p 1883 -i uc-dash-3a8f \
-t "connectmq/demo/3a8f/line1/+/#" -v
# Publisher: a "machine" reporting retained status and readings
mosquitto_pub -h broker.connectmq.com -p 1883 -i uc-cnc-3a8f \
-t "connectmq/demo/3a8f/line1/cnc1/status" -m "RUNNING" -r -q 1
for t in 61.2 62.0 63.5; do
mosquitto_pub -h broker.connectmq.com -p 1883 -i uc-cnc-3a8f \
-t "connectmq/demo/3a8f/line1/cnc1/spindle_temp" -m "$t"
sleep 1
done
Restart the subscriber and the retained RUNNING status appears immediately. To adapt the demo to another use case, change only the topic tree and payloads: a charger might publish site4/charger2/session, a greenhouse zone1/soil_moisture. The broker, the commands and the client code stay the same, which is exactly why one MQTT skill set transfers across industries. Data on the public broker is visible to everyone, so use made-up values only.
Get Started with ConnectMQ
Turn your use case into a private, authenticated deployment. Sign up at app.connectmq.com, start on the free Serverless plan with no credit card, and use the portal's dashboard, devices view and threshold alert rules to watch your first devices come online.
Frequently Asked Questions
What is MQTT mostly used for?
Telemetry and control between devices and software: machine monitoring, energy and fleet tracking, smart homes and buildings, and any scenario where many devices push data to multiple consumers.
Is MQTT suitable for real-time control?
It is well suited to supervisory control and commands with sub-second to second-level timing over good networks. Hard real-time control loops should stay on local fieldbuses.
Can MQTT handle video or large files?
MQTT can carry binary payloads up to the broker's message size limit, but it is not designed for video streaming. Send metadata or links over MQTT and media through a dedicated service.
Which MQTT features matter most for industrial use cases?
Hierarchical topics, retained state, Last Will, QoS 1 for events, and conventions like Sparkplug B or a Unified Namespace for consistent data models.
