Practical guides on MQTT, managed brokers and connected products from the ConnectMQ team.
A hands-on tutorial for real-time OEE monitoring: machines publish states and counts over MQTT, a Python service calculates availability, performance and quality every minute and publishes live OEE for any dashboard.
How to use MQTT for wellheads, pipelines and tank batteries over cellular and satellite links, with keep alive, session, QoS and report-by-exception settings tuned for expensive, intermittent connections.
Managed MQTT services bill on very different units: connections, session minutes, messages, traffic or dedicated capacity. Learn how each model works, which workloads it favours and how to estimate your usage before comparing quotes.
Track downtime on any machine, old or new: an ESP32 with a clamp-on current sensor publishes run and stop states over MQTT, and a Python logger records every stop with its duration and reason.
Stop hard-coding credentials: let users enter Wi-Fi plus MQTT host, port, client ID, username and password in a WiFiManager captive portal, store them with Preferences and connect to broker.connectmq.com by default.
Replace the blocking reconnect loop from most examples with a non-blocking state machine for Wi-Fi and MQTT, with exponential backoff, jitter, resubscribe and an offline buffer, then prove it by rebooting your router.
A practical blueprint for an MQTT-based andon: how operators raise calls, how call states are modelled with retained messages, how escalation works by time, and how response-time breaches become alerts.
Browsers cannot open raw TCP sockets, so web apps speak MQTT over WebSocket. Build a working browser client and a Node.js client against broker.connectmq.com and learn how to fix the most common connection errors.
Create a reusable useMqtt hook around MQTT.js, connect React to a broker over secure WebSocket, and render live sensor values without re-render storms, StrictMode surprises or leaked connections.
A complete, tested path from a bare Raspberry Pi Pico W to a connected MQTT device. Flash MicroPython, install umqtt.simple, publish the onboard temperature sensor, switch the LED from anywhere and keep the connection alive through Wi-Fi drops.
A device that drops Wi-Fi for three seconds should not page your on-call engineer. MQTT 5's will delay interval holds the Last Will message back long enough for a quick reconnect.
Build a Python subscriber that stores every MQTT message in SQLite with a timestamp, topic, QoS and retain flag, using batched writes and WAL mode, then query history, hourly averages and latest values with plain SQL.
Stream MQTT messages from a broker into pandas DataFrames without blocking the network loop, then compute rolling means, per-minute resamples, stale-device checks and simple anomaly flags.
Build a Python logger that subscribes to MQTT topics, writes every message to CSV, rotates files by day and size, and produces data you can open straight in Excel, pandas or a notebook.
MQTT runs over TCP, either directly, inside TLS, or inside WebSocket. Learn why the protocol depends on an ordered, reliable stream, where MQTT-SN and QUIC fit, and which ports to open for a ConnectMQ broker.
Trigger ESP32 firmware updates with an MQTT command, download the binary over HTTPS with HTTPUpdate, and publish progress and results to a retained status topic so you always know which version each device runs.
Wire several DS18B20 probes to a single ESP32 GPIO, discover their ROM addresses, read them without blocking and publish each probe to its own topic on broker.connectmq.com.
A practical comparison of edge AI hardware from microcontrollers to GPU modules, with a decision checklist and a benchmark script that publishes your own model's latency over MQTT so you can compare boards fairly.
A hands-on MQTT security checklist covering TLS, credentials, client IDs, topic design, payload validation, rate limits and certificate checks, plus how ConnectMQ handles each point.
Build ESP32 leak sensors that publish retained MQTT alarms, and a valve controller that shuts off the water supply automatically and stays latched until someone resets it.
MQTT-SN adapts MQTT for battery-powered sensors on UDP, Zigbee and other non-TCP networks. Learn topic IDs, sleeping clients and gateways, and how to forward MQTT-SN traffic into a standard MQTT broker.
Cellular links change the rules for MQTT. Learn how to estimate monthly data usage, choose keep alive values that survive carrier NAT, reduce TLS handshake costs and pick between LTE-M and NB-IoT.
MQTT 5 lets a publisher say how long a message stays valid. Learn how the message expiry interval works with persistent sessions and retained messages, and how to stop late devices from executing stale commands.
Where does MQTT latency come from? This guide breaks down network, TLS, QoS and broker processing delays and gives you a Python script to measure round-trip time against broker.connectmq.com.
Write a Python Modbus TCP to MQTT bridge that polls holding and input registers, decodes 32-bit floats, scales values and publishes only meaningful changes to a cloud MQTT broker.
Automate a greenhouse with MQTT: sensors publish climate data, a Node-RED flow decides when to vent, heat or mist using hysteresis, and relay nodes act with local failsafes.
Move a servo from MQTT commands with an ESP32 and the ESP32Servo library, ramp it smoothly to the target angle and publish position feedback that dashboards can display.
Read a NEO-6M GPS module with the ESP32, publish position, speed and fix quality over MQTT only when the device moves, and display the track live on a Leaflet map over secure WebSocket.
A hands-on tutorial that turns requests like "dim the kitchen lights to 30 percent" into validated MQTT commands, using an LLM with function calling, a device registry and a strict validation layer.
Mutual TLS lets an MQTT broker authenticate devices by X.509 certificate. Learn how it works, how to set it up on Mosquitto, what it costs to operate, and when credentials over TLS are the better fit.
Create an account, get your broker credentials and connect your first device — no servers to install, patch or scale.
