[{"data":1,"prerenderedAt":345},["ShallowReactive",2],{"blog-\u002Fblog\u002Fmqtt":3,"blog-all-for-related":4,"blog-all-mqtt":5},null,[],[6,27,43,58,77,93,108,125,139,154,176,190,210,225,239,262,279,301,315,330],{"path":7,"title":8,"date":9,"tags":10,"authors":14,"description":16,"meta":17,"image":26},"\u002Fblog\u002F2026\u002F06\u002Fmqtt-vs-sparkplug-b","MQTT vs Sparkplug B: Which One (or Both) Do You Need?","2026-06-11",[11,12,13],"post","mqtt","sparkplug",[15],"sumit-shinde","A practical guide to choosing between plain MQTT and Sparkplug B for industrial IoT: where MQTT's flexibility turns into a topic-namespace mess, what Sparkplug B's structure, binary payloads, and birth\u002Fdeath certificates fix, the QoS 0 trade-off nobody mentions, and why most large deployments end up running both.",{"keywords":18,"excerpt":19},"mqtt vs sparkplug b, sparkplug b, mqtt, industrial pub sub, mqtt topic namespace, sparkplug birth death certificate, mqtt qos, protobuf vs json, unified namespace, scada mqtt, iiot messaging, report by exception",{"type":20,"value":21},"minimark",[22],[23,24,25],"p",{},"MQTT is everywhere in industrial setups. It has been the default for moving sensor data and machine states around for a long time now, mostly because it's lightweight and it just works on almost anything.","\u002Fblog\u002F2026\u002F06\u002Fimages\u002Fmqtt-vs-sparkplug.png",{"path":28,"title":29,"date":30,"tags":31,"authors":33,"description":34,"meta":35,"image":42},"\u002Fblog\u002F2026\u002F02\u002Fmqtt-influxdb-tutorial","How to Build an MQTT-to-InfluxDB Data Pipeline (2026)","2026-02-26",[32,12],"flowfuse",[15],"Learn how to build a reliable MQTT-to-InfluxDB data pipeline using FlowFuse and Node-RED. No custom scripts, no glue code, just a visual flow that is easy to maintain and hand off.",{"keywords":36,"excerpt":37},"MQTT, InfluxDB, IIoT, FlowFuse, Node-RED, Sensor telemetry, Time-series database",{"type":20,"value":38},[39],[23,40,41],{},"An MQTT to InfluxDB is one of the most common and most critical pipelines in IIoT. Every timestamped telemetry event that drives decisions on the floor needs to land somewhere it can be queried, trended, and acted on.","\u002Fblog\u002F2026\u002F02\u002Fimages\u002Fmqtt-to-influxdb.png",{"path":44,"title":45,"date":46,"tags":47,"authors":48,"description":49,"meta":50,"image":57},"\u002Fblog\u002F2026\u002F02\u002Fmqtt-vs-coap","MQTT vs CoAP: Measure Your Constraints or Pick Wrong","2026-02-05",[32,12],[15],"Learn whether MQTT or CoAP fits your IoT deployment. Learn how device constraints, power budgets, and network architecture determine the right protocol for reliable, efficient IoT systems.",{"keywords":51,"excerpt":52},"MQTT, CoAP, IoT protocols, constrained devices, edge computing, message broker, pub\u002Fsub, request\u002Fresponse, IoT architecture",{"type":20,"value":53},[54],[23,55,56],{},"The MQTT vs CoAP debate is mostly noise. One protocol assumes you have infrastructure and want centralized coordination. The other assumes you don't and can't. If you're still debating which is \"better,\" you haven't measured what matters.","\u002Fblog\u002F2026\u002F02\u002Fimages\u002Fcoap-vs-mqtt.png",{"path":59,"title":60,"date":61,"tags":62,"authors":64,"description":65,"meta":66,"image":76},"\u002Fblog\u002F2026\u002F01\u002Fopcua-vs-mqtt","MQTT vs OPC UA: Why This Question Never Has a Straight Answer","2026-01-21",[32,63,12],"opcua",[15],"MQTT vs OPC UA isn't a real choice; they solve different problems. Learn when to use each protocol based on your actual requirements, not vendor marketing.",{"keywords":67,"excerpt":68},"MQTT vs OPC UA, MQTT protocol, OPC UA protocol, industrial communication, IIoT architecture, OPC UA PubSub, MQTT Sparkplug",{"type":20,"value":69},[70,73],[23,71,72],{},"The question itself is broken.",[23,74,75],{},"MQTT moves messages. OPC UA defines meaning. They operate at different layers of the stack. Comparing them is like comparing TCP to JSON.","\u002Fblog\u002F2026\u002F01\u002Fimages\u002Fopcua-vs-mqtt.png",{"path":78,"title":79,"date":80,"tags":81,"authors":83,"description":84,"meta":85,"image":92},"\u002Fblog\u002F2025\u002F12\u002Fkafka-vs-mqtt","MQTT vs Kafka: Complete Comparison Guide 2026","2025-12-17",[32,12,82],"kafka",[15],"MQTT vs Kafka comparison guide: Discover the key differences between Apache Kafka and MQTT messaging protocols. Learn which is best for IoT, industrial automation, and real-time data streaming with practical examples and use cases",{"keywords":86,"excerpt":87},"Kafka vs MQTT, MQTT vs Kafka, Apache Kafka, MQTT protocol, IoT messaging, message broker comparison, pub-sub messaging, event streaming, industrial IoT, real-time messaging, IoT protocols, messaging protocol comparison, Kafka MQTT differences",{"type":20,"value":88},[89],[23,90,91],{},"Building IoT systems means making hard choices about how messages flow through your infrastructure. Apache Kafka and MQTT couldn't be more different in their approaches. MQTT came from the world of sensors and resource-constrained devices. Kafka was designed to push massive data streams between backend systems. Getting this choice right early determines whether your architecture scales smoothly or hits a wall.","\u002Fblog\u002F2025\u002F12\u002Fimages\u002Fkafka-vs-mqtt.png",{"path":94,"title":95,"date":96,"tags":97,"authors":98,"description":99,"meta":100,"image":107},"\u002Fblog\u002F2025\u002F11\u002Fcsv-mqtt-database-dashboard-flowfuse","How to Ingest CSV Logs into MQTT, Databases, and Dashboards","2025-11-10",[32,12],[15],"Learn how to ingest CSV logs from PLCs and SCADA systems into MQTT brokers, databases, and dashboards. Build real-time and batch processing pipelines with Node-RED and FlowFuse.",{"keywords":101,"excerpt":102},"CSV ingestion, MQTT broker, Node-RED, FlowFuse, industrial data, PLC logging, SCADA systems, real-time data pipeline, batch processing, database integration, data visualization, manufacturing data, Node-RED dashboard, sensor data, time-series data, industrial IoT, data orchestration, legacy systems integration",{"type":20,"value":103},[104],[23,105,106],{},"If you work in manufacturing, you likely have gigabytes of data in CSV files, temperature logs, production counts, machine status records. The data exists and is organized, but it's not accessible to the systems that need it.","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fhow-to-ingest-csv-logs.png",{"path":109,"title":110,"date":111,"tags":112,"authors":115,"description":116,"meta":117,"image":124},"\u002Fblog\u002F2025\u002F10\u002Fplc-to-mqtt-using-flowfuse","How to Connect Any PLC to MQTT in Under an Hour","2025-10-27",[32,113,12,114],"modbus","plc",[15],"Learn how to extract data from Siemens, Allen-Bradley, Omron, Mitsubishi, OPC UA, and Modbus, transform it, and publish to MQTT using FlowFuse, without expensive gateways or consultants.",{"keywords":118,"excerpt":119},"MQTT, PLC, Siemens, S7, Allen-Bradley, EtherNet\u002FIP, Omron, FINS, Mitsubishi, MC Protocol, Modbus, Modbus-RTU, Modbus-TCP, OPC-UA, FlowFuse, Node-RED, Industrial IoT, IIoT",{"type":20,"value":120},[121],[23,122,123],{},"Getting PLC data into systems where it can be monitored, analyzed, and acted upon is essential for modern manufacturing. MQTT has become the standard for moving this data. It's lightweight, handles unreliable networks well, and excels at real-time streaming. Once your PLC data is published to MQTT, it creates a common pipeline that IT systems understand, flowing easily to cloud platforms, analytics tools, dashboards, and eliminating protocol translation headaches.","\u002Fblog\u002F2025\u002F10\u002Fimages\u002Fplc-to-mqtt.png",{"path":126,"title":127,"date":128,"tags":129,"authors":130,"description":131,"meta":132,"image":138},"\u002Fblog\u002F2025\u002F03\u002Fmanaging-mqtt-connections-at-scale-in-flowfuse","Managing MQTT Connections at Scale in FlowFuse","2025-03-28",[32,12],[15],"Learn how to configure MQTT brokers dynamically in FlowFuse using environment variables at both instance and device group levels. Streamline deployments across pipeline stages and monitor MQTT topics efficiently.",{"excerpt":133},{"type":20,"value":134},[135],[23,136,137],{},"FlowFuse makes it easy to deploy Node-RED flows at scale using DevOps pipelines and device groups. However, different stages in a pipeline may need different MQTT brokers, for example, one for development and another for production. Manually configuring each stage can be time-consuming, especially when a stage has multiple remote instances (devices).","\u002Fblog\u002F2025\u002F03\u002Fimages\u002Fscaling-mqtt-connections.png",{"path":140,"title":141,"date":142,"tags":143,"authors":145,"description":146,"meta":147,"image":153},"\u002Fblog\u002F2025\u002F01\u002Fdesigning-topic-hierarchy-for-your-uns","Designing a Clear Topic Structure for Your UNS","2025-01-31",[32,144,12],"unified-namespace",[15],"Learn why topic structuring is crucial for your UNS’s performance and scalability. This post explores best practices and strategies to design an effective topic hierarchy for your system.",{"excerpt":148},{"type":20,"value":149},[150],[23,151,152],{},"Topic structuring is not just a technical concern when building a high-performance Unified Namespace (UNS) for manufacturing environments; it's a strategic design choice that can determine the system's scalability, efficiency, and overall effectiveness.","\u002Fblog\u002F2025\u002F01\u002Fimages\u002Funs-topic-structer.png",{"path":155,"title":156,"date":157,"tags":158,"authors":160,"description":161,"meta":162,"image":175},"\u002Fblog\u002F2025\u002F01\u002Fmqtt-frontrunner-for-uns-part-2","MQTT: The Frontrunner for Your UNS Broker - Part 2","2025-01-13",[12,159,144],"uns",[15],"Learn why MQTT is the top choice for Unified Namespace (UNS) brokers and explore the ideal platform that simplifies the connection of devices and services while providing a reliable MQTT broker service.",{"keywords":163,"excerpt":164},"mqtt unified namespace, why use mqtt in uns, mqtt in a unified namespace, mqtt data modeling UNS, Best protocols for UNS IoT, Implementing UNS with MQTT, Unified Namespace protocols",{"type":20,"value":165},[166],[23,167,168,169,174],{},"In ",[170,171,173],"a",{"href":172},"\u002Fblog\u002F2025\u002F01\u002Fmqtt-frontrunner-for-uns\u002F","Part 1",", we discussed the  reasons behind MQTT's popularity as a choice for Unified Namespace (UNS) implementations; focusing on its lightweight design, low latency, and reliable message delivery. In this second part, we’ll explore additional factors that further establish MQTT as the leading protocol for UNS brokers, diving into its connectivity, scalability, structured topic management.","\u002Fblog\u002F2025\u002F01\u002Fimages\u002Fmqtt-for-uns-2.png",{"path":177,"title":178,"date":179,"tags":180,"authors":181,"description":161,"meta":182,"image":189},"\u002Fblog\u002F2025\u002F01\u002Fmqtt-frontrunner-for-uns","MQTT: The Frontrunner for Your UNS Broker - Part 1","2025-01-07",[12,159,144],[15],{"keywords":183,"excerpt":184},"mqtt unified namespace, why use mqtt in uns, mqtt in a unified namespace, mqtt data modeling UNS, best protocols for UNS IoT, implementing UNS with MQTT, unified namespace protocols",{"type":20,"value":185},[186],[23,187,188],{},"Choosing the right broker for your UNS is crucial. It must support real-time data, scale easily, and integrate seamlessly with devices and services. MQTT often comes out as the best choice for these needs.","\u002Fblog\u002F2025\u002F01\u002Fimages\u002Fmqtt-for-uns-1.png",{"path":191,"title":192,"date":193,"tags":194,"authors":195,"description":196,"meta":197,"image":209},"\u002Fblog\u002F2024\u002F11\u002Fbuilding-uns-with-flowfuse","Building a Unified Namespace (UNS) with FlowFuse","2024-11-28",[32,144,12],[15],"Discover how FlowFuse helps you build a Unified Namespace (UNS) effortlessly, streamlining industrial data sharing, improving operational efficiency, and enabling real-time insights for smarter decision-making.",{"keywords":198,"excerpt":199},"building unified namespace using nodered, nodered uns, uns nodered",{"type":20,"value":200},[201],[23,202,203,204,208],{},"As systems and devices become more connected, managing data from different sources can be tricky. A ",[170,205,207],{"href":206},"\u002Fsolutions\u002Funs\u002F","Unified Namespace (UNS)"," solves this by centralizing all your data in one place, making it easy to access and use.","\u002Fblog\u002F2024\u002F11\u002Fimages\u002Fbuilding-uns-with-flowfuse.png",{"path":211,"title":212,"date":213,"tags":214,"authors":215,"description":216,"meta":217,"image":224},"\u002Fblog\u002F2024\u002F11\u002Fwhy-point-to-point-connection-is-dead","The Death of Point-to-Point: Why You Need a Unified Namespace","2024-11-26",[32,12,144],[15],"Learn why point-to-point connections are outdated in modern manufacturing and how a Unified Namespace (UNS) simplifies system integration, enhances data sharing, and improves scalability and security.",{"keywords":218,"excerpt":219},"uns, cons of p2p, cons of point-to-point connection, drawbacks of point-to-point connection, publish-subscribe, mqtt",{"type":20,"value":220},[221],[23,222,223],{},"Manufacturing has changed significantly over the years, driven by new technology and the need for better communication between systems. In the past, point-to-point (P2P) connections, where devices communicate directly with each other, were the standard. However, as factories become more complex, P2P connections are no longer practical. This article explains why P2P connections are outdated and how a Unified Namespace (UNS) offers a better, more flexible solution.","\u002Fblog\u002F2024\u002F11\u002Fimages\u002Fthe-death-of-point-to-point.png",{"path":226,"title":227,"date":228,"tags":229,"authors":230,"description":231,"meta":232,"image":238},"\u002Fblog\u002F2024\u002F11\u002Fgetting-the-most-out-of-mqtt-for-industrial-iot","Getting the Most Out of MQTT for Industrial IoT","2024-11-25",[11,32,12],[15],"Learn how to optimize MQTT for industrial IoT with best practices for data consistency, security, performance, and scalability. Discover how FlowFuse enhances your IoT system with streamlined MQTT communication and robust features.",{"keywords":3,"excerpt":233},{"type":20,"value":234},[235],[23,236,237],{},"MQTT is a go-to protocol for industrial IoT, known for its efficiency, scalability, and ease of use. While it offers great flexibility in handling real-time data, there are key factors to consider in order to get the most out of it. From ensuring data consistency to addressing security and performance concerns, these factors can significantly enhance MQTT’s effectiveness in industrial settings.","\u002Fblog\u002F2024\u002F11\u002Fimages\u002Fmqtt-common-pitfalls.png",{"path":240,"title":241,"date":242,"tags":243,"authors":244,"description":245,"meta":246,"image":261},"\u002Fblog\u002F2024\u002F11\u002Fwhy-pub-sub-in-uns","Why UNS needs Pub\u002FSub","2024-11-19",[32,12,144],[15],"Explore why integrating Publish\u002FSubscribe (Pub\u002FSub) with Unified Namespace (UNS) is key to optimizing manufacturing data flow. Learn how this combination reduces latency, improves scalability, and enables real-time decision-making in IIoT systems.",{"keywords":247,"excerpt":248},"unified namespace, pub\u002Fsub, mqtt, iiot, manufacturing, real-time data, event-driven, scalability, smart factory, flowfuse, iot integration",{"type":20,"value":249},[250,253],[23,251,252],{},"As the manufacturing industry evolves and becomes increasingly connected through the Industrial Internet of Things (IIoT), the concept of a Unified Namespace (UNS) has emerged as a critical architecture for centralizing and organizing data. UNS serves as a central reference point where all operational data, from machines to the enterprise, can be accessed in a consistent and structured way. Over time, more and more manufacturers have adopted UNS to simplify data integration and improve real-time visibility across systems.",[23,254,255,256,260],{},"If you're unfamiliar with UNS, please read our ",[170,257,259],{"href":258},"\u002Fblog\u002F2023\u002F12\u002Fintroduction-to-unified-namespace\u002F","Introduction to Unified Namespace"," for a basic understanding of UNS.","\u002Fblog\u002F2024\u002F11\u002Fimages\u002Fwhy-uns-needs-pub-sub.png",{"path":263,"title":264,"date":265,"tags":266,"authors":269,"description":270,"meta":271,"image":278},"\u002Fblog\u002F2024\u002F11\u002Fesp32-with-node-red","Interacting with ESP32 Using Node-RED and MQTT (2026)","2024-11-14",[267,268,12],"node-red","how-to",[15],"Learn how to connect an ESP32 to Node-RED using MQTT in 2026. Step-by-step guide covering the MQTT broker setup, Arduino IDE code, and building a dashboard to control your IoT device remotely, ideal for beginners and IoT hobbyists.",{"keywords":272,"excerpt":273},"esp32 with node red, node red esp32, connect esp32 to node red, esp node red, esp32 mqtt node red, esp32 node red, esp32 node red mqtt, mqtt esp32 node red, mqtt node red esp32, node red mqtt esp32, node red with esp32",{"type":20,"value":274},[275],[23,276,277],{},"The ESP32 is an affordable and powerful microchip that combines Wi-Fi and Bluetooth in one small package. It's commonly used in smart devices like home automation systems, wearables, and other IoT projects. Despite its low cost (around $6), it offers strong performance, and low power consumption, and is compatible with popular platforms like Arduino. Whether you're a hobbyist or a business, the ESP32 provides great value, making it easy to create wireless devices without a big investment. This tutorial demonstrates how to set up communication between the ESP32 and Node-RED using MQTT, along with an interactive dashboard via FlowFuse for a user-friendly interface.","\u002Fblog\u002F2024\u002F11\u002Fimages\u002Fesp32-with-node-red.png",{"path":280,"title":281,"date":282,"tags":283,"authors":286,"description":288,"meta":289,"image":300},"\u002Fblog\u002F2024\u002F10\u002Fannouncement-mqtt-broker","MQTT Service Now Available on FlowFuse","2024-10-31",[284,285,32,267,12],"posts","news",[287],"joe-pavitt","We are thrilled to announce a significant milestone for FlowFuse, we now offer our very own MQTT service, built-in and ready to use with your Node-RED applications.",{"excerpt":290},{"type":20,"value":291},[292],[23,293,294,295,299],{},"In our ",[170,296,298],{"href":297},"\u002Fblog\u002F2024\u002F10\u002Fflowfuse-release-2-10","recent product update"," we have added our very own MQTT service, built-in and ready to use alongside your Node-RED applications. We are always engaging with users and prospective customers and this has been a highly requested feature, and so we are delighted to announce that this is now live on FlowFuse Cloud for our Pro and Enterprise teams.","\u002Fblog\u002F2024\u002F10\u002Fimages\u002Fff-mqtt.png",{"path":302,"title":303,"date":304,"tags":305,"authors":306,"description":307,"meta":308,"image":3},"\u002Fblog\u002F2024\u002F08\u002Fusing-mqtt-sparkplugb-with-node-red","MQTT Sparkplug B Implementation: Protocol, Architecture & Best Practices","2024-08-22",[284,267,12],[15],"Learn how to implement MQTT Sparkplug B with Node-RED for standardized, reliable Industrial IoT data flows and scalable production deployments.",{"keywords":309,"excerpt":310},"node red, mqtt sparkplug, industrial IoT",{"type":20,"value":311},[312],[23,313,314],{},"Connected devices can generate a lot of data, but without a standardized format, managing and consuming it can be tricky. MQTT certainly simplifies getting your messages delivered but it does not enforce any structure. This is where MQTT Sparkplug B helps by providing a clear, standardized format for data. In this guide, we’ll show you how to use MQTT Sparkplug B with Node-RED to make managing your device data easier and more organized.",{"path":316,"title":317,"date":318,"tags":319,"authors":320,"description":321,"meta":322,"image":329},"\u002Fblog\u002F2024\u002F08\u002Fopc-ua-to-mqtt-with-node-red","Bridging OPC UA Data to MQTT with Node-RED (2026)","2024-08-13",[284,267,12,63,268],[15],"Learn how to bridge OPC UA data to MQTT using Node-RED for seamless industrial IoT integration and real-time data flow.",{"keywords":323,"excerpt":324},"opc ua gateway, opc ua example, node-red-contrib-opcua, nodered opcua, opc ua mqtt, opc ua over mqtt, opc ua to mqtt gateway, mqtt to opc ua, mqtt and opc ua, opc ua and mqtt, opc ua via mqtt, opcua to mqtt",{"type":20,"value":325},[326],[23,327,328],{},"Have you ever found yourself trying to connect old industrial systems with new IoT tools? This is a common scenario when trying to digitally transform while setting up your Unified Name Space. Maybe you have machinery that uses OPC UA, but your data is sent through MQTT. How do you make these systems work together smoothly?","\u002Fblog\u002F2024\u002F08\u002Fimages\u002Fbrdging-opcua-to-mqtt.png",{"path":331,"title":332,"date":333,"tags":334,"authors":335,"description":336,"meta":337,"image":344},"\u002Fblog\u002F2024\u002F06\u002Fhow-to-use-mqtt-in-node-red","Working with MQTT in Node-RED: Complete Guide (2026)","2024-06-05",[284,267,12,268],[15],"Complete MQTT Node-RED tutorial: configure brokers, implement pub\u002Fsub messaging, use mqtt-in and mqtt-out nodes, and create dynamic subscriptions for IoT",{"keywords":338,"excerpt":339},"node red mqtt, mqtt node red, mqtt in node red, node red mqtt in, node red mqtt out, node red mqtt broker, mqtt broker node red, node-red-contrib-mqtt-broker, node red mqtt dynamic subscription, node red mqtt example, mqtt dynamic subscription, mqtt in\u002Fout nodes, mqtt broker setup",{"type":20,"value":340},[341],[23,342,343],{},"MQTT handles the messaging layer for most IoT deployments. Node-RED provides built-in nodes that connect to MQTT brokers, subscribe to topics, and publish messages, all through a visual interface.","\u002Fblog\u002F2024\u002F06\u002Fimages\u002Fworking-with-mqtt.jpg",1785929975997]