[{"data":1,"prerenderedAt":1165},["ShallowReactive",2],{"blog-\u002Fblog\u002F2024\u002F11\u002Fgetting-the-most-out-of-mqtt-for-industrial-iot":3,"featureCatalog":235,"changelog-titles":630,"blog-all-for-related":1164},{"id":4,"title":5,"authors":6,"body":8,"cta":209,"date":213,"description":214,"extension":215,"features":216,"image":217,"lastUpdated":218,"meta":219,"navigation":224,"path":225,"release":216,"seo":226,"sitemap":227,"stem":228,"subtitle":229,"tags":230,"tldr":216,"video":216,"__hash__":234},"blog\u002Fblog\u002F2024\u002F11\u002Fgetting-the-most-out-of-mqtt-for-industrial-iot.md","Getting the Most Out of MQTT for Industrial IoT",[7],"sumit-shinde",{"type":9,"value":10,"toc":195},"minimark",[11,15,18,23,26,29,38,42,45,48,51,54,58,61,64,67,90,93,96,100,103,106,109,112,115,119,122,125,128,132,135,138,141,144,147,150,154,157,160,163,166,170,173,179,182,185,188,192],[12,13,14],"p",{},"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.",[12,16,17],{},"This post dives into how to optimize MQTT for industrial IoT, covering best practices and key considerations. It also highlights how FlowFuse can help streamline MQTT communication, improving data reliability, security, and integration across devices and systems.",[19,20,22],"h2",{"id":21},"standardizing-data-formats-for-better-quality-and-consistency","Standardizing Data Formats for Better Quality and Consistency",[12,24,25],{},"Industrial data is generated by a wide variety of devices, machines, and systems, making it highly valuable. However, to fully leverage this data, it needs to be standardized and formatted in a way that ensures seamless processing across different systems, especially since it can come in a variety of formats.",[12,27,28],{},"One of MQTT’s key strengths is its flexibility in handling various data formats. While this is an advantage, it can sometimes require additional effort to ensure that the data is structured consistently and in a way that’s easy to use. Standardizing data formats helps organizations streamline processes, making data easier to interpret, analyze, and act upon. Without a consistent approach, data inconsistencies may arise, slowing down insights or causing compatibility issues.",[12,30,31,32,37],{},"Frameworks like ",[33,34,36],"a",{"href":35},"\u002Fblog\u002F2024\u002F08\u002Fusing-mqtt-sparkplugb-with-node-red\u002F","Sparkplug B"," are designed to help address this by providing a standardized way to handle MQTT payloads. By adopting such frameworks, companies can ensure that data is delivered in a consistent, well-structured format, improving compatibility and making it easier to analyze. This not only simplifies integration across diverse systems but also enables more reliable decision-making and efficient operations.",[19,39,41],{"id":40},"optimizing-payloads-and-bandwidth-for-efficient-mqtt-communication","Optimizing Payloads and Bandwidth for Efficient MQTT Communication",[12,43,44],{},"MQTT is designed for lightweight, efficient messaging, which makes it ideal for many IIoT applications. However, in cases where large amounts of data or high-frequency messages need to be transmitted, bandwidth constraints can sometimes impact performance.",[12,46,47],{},"While the MQTT protocol supports large message payloads (up to 250 MB), transmitting large files such as high-resolution images or detailed sensor data can slow down communication. Fortunately, there are simple yet effective strategies to keep your MQTT network running smoothly, even when dealing with sizable payloads.",[12,49,50],{},"To optimize performance, consider compressing your data before sending it, which reduces the overall size of the payload and makes transmission faster and more efficient. For even larger files, such as video or binary data, a great approach is to store these files externally (e.g., in cloud storage like AWS S3) and send only a reference or pointer to the data. This avoids the need to transmit large files over MQTT while ensuring data accessibility.",[12,52,53],{},"By using these strategies, you can optimize MQTT performance and ensure that your system runs efficiently, even when handling large or high-frequency data. These techniques allow MQTT to continue providing fast, reliable, and scalable communication, regardless of the data size or frequency.",[19,55,57],{"id":56},"ensuring-reliable-data-delivery-with-mqtts-qos-levels","Ensuring Reliable Data Delivery with MQTT’s QoS Levels",[12,59,60],{},"In industrial environments, the accuracy and timeliness of data transmission are crucial for maintaining operational efficiency and safety. MQTT’s publish-subscribe model is designed for lightweight, real-time messaging, but it’s important to understand how to leverage its features to ensure the reliability and integrity of the data flow.",[12,62,63],{},"While the protocol is generally robust, in some cases, challenges such as network disruptions or temporary communication failures can occur. These can lead to issues such as message loss or delivery out of order. Fortunately, MQTT provides built-in mechanisms to address these challenges and ensure that messages reach their intended destination reliably.",[12,65,66],{},"One of the key feature for managing message delivery is Quality of Service (QoS), which defines how MQTT handles message delivery:",[68,69,70,78,84],"ul",{},[71,72,73,77],"li",{},[74,75,76],"strong",{},"QoS 0",": Messages are delivered at most once, with no guarantee of delivery or order. This level is ideal for scenarios where occasional message loss is acceptable and minimizing network overhead is critical.",[71,79,80,83],{},[74,81,82],{},"QoS 1",": Guarantees that messages are delivered at least once, although duplicates may occur. This is useful when data consistency is important, but some duplication can be handled by the system.",[71,85,86,89],{},[74,87,88],{},"QoS 2",": Ensures messages are delivered exactly once and in the correct order. This highest level of QoS is suitable for scenarios where data integrity and sequencing are paramount, such as in robotic control systems or safety-critical operations.",[12,91,92],{},"By choosing the right QoS level, you can align MQTT’s behavior with the operational needs of your system, balancing between performance, data reliability, and system resources. For real-time applications, a lower QoS level may be sufficient, while in more critical situations, the higher QoS levels offer a stronger guarantee of data delivery and integrity.",[12,94,95],{},"With these options, MQTT allows you to fine-tune message delivery to meet the specific requirements of your industrial IoT environment, ensuring that data flows smoothly and reliably, even in challenging network conditions.",[19,97,99],{"id":98},"implementing-acknowledgment-mechanisms-in-mqtt","Implementing Acknowledgment Mechanisms in MQTT",[12,101,102],{},"One important consideration when working with MQTT is the lack of built-in acknowledgment mechanisms. Unlike traditional request-response communication models, where the receiver explicitly confirms the receipt of a message, MQTT doesn't natively offer a direct way for the receiver to acknowledge successful message receipt.",[12,104,105],{},"This lack of visibility can pose challenges in scenarios where it’s crucial to ensure that data has been transmitted successfully and processed as expected. In some industrial systems, failure to confirm receipt of messages could lead to operational uncertainty or potential errors.",[12,107,108],{},"However, while MQTT does not provide this feature out-of-the-box, it is possible to implement acknowledgment mechanisms to enhance reliability. we can use a separate topic where the receiver sends a confirmation message (such as “ack” or “received”) back to the sender, indicating that the message was successfully processed.",[12,110,111],{},"This allow you to implement acknowledgment functionality, but they do require additional planning and development effort. Ensuring that these mechanisms are correctly designed and integrated can improve system reliability by providing the necessary feedback loop for confirming message receipt and processing.",[12,113,114],{},"By incorporating acknowledgment systems, you can enhance the visibility and confidence in data transmission, ensuring that your industrial IoT system operates smoothly and that no critical messages are missed or lost.",[19,116,118],{"id":117},"optimizing-mqtt-for-resource-constrained-environments","Optimizing MQTT for Resource-Constrained Environments",[12,120,121],{},"While MQTT’s use of TCP\u002FIP ensures reliable message delivery, it can introduce challenges in environments where devices have limited resources. Maintaining persistent TCP connections can consume significant processing power and memory, which may be a concern for low-power or resource-constrained devices.",[12,123,124],{},"To address this, some IoT systems use MQTT-SN (MQTT for Sensor Networks), a variant that operates over UDP and is specifically designed for devices with limited resources. MQTT-SN reduces the overhead associated with maintaining a TCP connection, making it a better fit for battery-powered or embedded devices that need to conserve energy. However, it's important to note that MQTT-SN is distinct from the standard MQTT specification, as it involves different message formats and communication mechanisms.",[12,126,127],{},"By carefully selecting the appropriate protocol and architecture for your specific use case, you can continue to leverage MQTT-like messaging capabilities, while optimizing performance in environments with limited resources.",[19,129,131],{"id":130},"ensuring-security-in-mqtt-deployments","Ensuring Security in MQTT Deployments",[12,133,134],{},"Security is essential when using MQTT in industrial environments. While MQTT offers powerful features like encryption and authentication, it's crucial to configure these elements correctly to maximize security. A properly secured MQTT deployment ensures that your system remains protected from risks such as data interception, unauthorized access, or man-in-the-middle attacks, while ensuring that your communication remains secure and reliable.",[12,136,137],{},"To begin, implementing encryption (SSL\u002FTLS) is an important step to protect the data transmitted between devices and brokers. This ensures that sensitive information is kept confidential and is shielded from unauthorized access. By enabling encryption, you create a secure communication pathway that prevents eavesdropping and data tampering.",[12,139,140],{},"Next, consider authentication for all devices and users. By using mechanisms such as usernames, passwords, or client certificates, you can ensure that only authorized devices and users can connect to your MQTT broker. This access control mechanism ensures that only the right people and devices have access to the network, safeguarding it from potential threats.",[12,142,143],{},"Topic-level access control is another key aspect of securing your MQTT deployment. By managing who can publish or subscribe to specific topics, you can prevent unauthorized access to sensitive data or critical commands. For example, you can restrict which devices or users are allowed to subscribe to specific topics that control industrial equipment or monitor sensitive processes. This level of control ensures that only trusted entities can interact with certain parts of your system, reducing the risk of malicious actions.",[12,145,146],{},"In addition to restricting access to topics, it's also important to regularly monitor your MQTT traffic for any unusual activity or anomalies. By staying vigilant and analyzing traffic patterns, you can identify potential security threats early and take action to prevent any disruptions.",[12,148,149],{},"By configuring your MQTT setup with encryption, authentication, topic-level access control, and ongoing monitoring, you can create a secure, reliable, and scalable IoT system. A well-secured MQTT deployment not only reduces risks but also enhances the efficiency and safety of industrial operations, providing peace of mind as your system grows.",[19,151,153],{"id":152},"minimizing-risks-of-single-point-of-failure-and-vendor-lock-in","Minimizing Risks of Single Point of Failure and Vendor Lock-In",[12,155,156],{},"When using MQTT for industrial operations, it’s important to address the potential risks associated with a single point of failure, specifically the central broker. While the broker is crucial for managing message delivery, its failure could disrupt the entire data flow, impacting operations. However, this challenge can be effectively managed with strategies like high availability, load balancing, and robust backup solutions. By implementing these best practices, you ensure that your system remains reliable and resilient, even in the event of a failure.",[12,158,159],{},"Another consideration is vendor lock-in, which can occur when businesses become reliant on a specific MQTT broker or service. While this may seem convenient at first, it can make future changes or migrations difficult due to proprietary features or configurations that aren't easily compatible with other systems. This is a scenario that can be easily avoided with careful planning.",[12,161,162],{},"Although MQTT is an open standard, some cloud services may not fully adhere to the MQTT 3.1.1 specification. This can sometimes lead companies to rely on proprietary software development kits (SDKs) for sending MQTT messages. While these tools can work well initially, they can limit your ability to switch vendors or integrate with other systems down the road.",[12,164,165],{},"To maintain flexibility and avoid vendor lock-in, it's crucial to choose an MQTT broker that fully supports MQTT's open standards. Brokers that follow standards like MQTT 3.1.1 or MQTT 5.0 ensure compatibility and interoperability, making it easier to switch providers or integrate new technologies as your needs evolve.",[19,167,169],{"id":168},"how-flowfuse-enhances-your-industrial-iot-system","How FlowFuse Enhances Your Industrial IoT System",[12,171,172],{},"FlowFuse is an industrial data platform that streamlines the management, scaling, and security of IoT applications. Built on Node-RED at its core, FlowFuse offers seamless integration with various industrial protocols, including MQTT, ensuring reliable communication between devices. With its robust feature set, FlowFuse makes it easier to build secure, scalable, and efficient IoT solutions for industrial environments",[12,174,175,176,178],{},"A key strength of FlowFuse is its ability to standardize data before sending it to the MQTT broker. Using Node-RED’s intuitive low-code programming capabilities, you can define consistent data formats and topics across all connected devices. This ensures smooth integration between diverse systems and maintains data consistency, allowing everything to work together seamlessly. FlowFuse also supports frameworks like ",[33,177,36],{"href":35},", providing additional structure for more reliable communication with MQTT payloads.",[12,180,181],{},"Security is another area where FlowFuse excels. It allows you to configure MQTT nodes with SSL\u002FTLS encryption, username\u002Fpassword authentication, and other security measures to ensure secure communication between devices. This protects sensitive data from unauthorized access and ensures that your system’s communications remain confidential.",[12,183,184],{},"FlowFuse also simplifies the creation of acknowledgment mechanisms. With Node-RED, you can design custom workflows to track message receipt and processing, ensuring data integrity and improving operational transparency. This level of control guarantees that your system operates smoothly and reliably.",[12,186,187],{},"Additionally, FlowFuse provides its own MQTT broker service that follows open standards, helping you avoid vendor lock-in and offering the flexibility to scale and adapt as your needs evolve. With built-in high availability, load balancing, and access control mechanisms, FlowFuse ensures continuous and reliable and secure data flow. And you can scale its capabilities by contacting FlowFuse support to meet the growing demands of your industrial IoT system.",[19,189,191],{"id":190},"conclusion","Conclusion",[12,193,194],{},"Getting the most out of MQTT for industrial IoT is all about smart strategies and the right tools. By focusing on data consistency, security, and performance, you can build a resilient and efficient IoT ecosystem. With FlowFuse, you get a powerful, flexible platform that not only streamlines MQTT communication but also helps you stay ahead of challenges like security risks and vendor lock-in. Whether you're optimizing payloads, enhancing security, or scaling your system, FlowFuse makes it easier to unlock the full potential of your industrial IoT operations.",{"title":196,"searchDepth":197,"depth":197,"links":198},"",4,[199,201,202,203,204,205,206,207,208],{"id":21,"depth":200,"text":22},2,{"id":40,"depth":200,"text":41},{"id":56,"depth":200,"text":57},{"id":98,"depth":200,"text":99},{"id":117,"depth":200,"text":118},{"id":130,"depth":200,"text":131},{"id":152,"depth":200,"text":153},{"id":168,"depth":200,"text":169},{"id":190,"depth":200,"text":191},{"type":210,"title":211,"description":212},"demo","Get More Out of MQTT in Your Industrial Environment","FlowFuse gives you a built-in MQTT broker, Node-RED integration, SSL\u002FTLS security, and centralized device management, everything you need to run reliable, scalable industrial IoT communication.","2024-11-25","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.","md",null,"\u002Fblog\u002F2024\u002F11\u002Fimages\u002Fmqtt-common-pitfalls.png","2025-07-23",{"keywords":216,"excerpt":220},{"type":9,"value":221},[222],[12,223,14],{},true,"\u002Fblog\u002F2024\u002F11\u002Fgetting-the-most-out-of-mqtt-for-industrial-iot",{"title":5,"description":214},{"loc":225},"blog\u002F2024\u002F11\u002Fgetting-the-most-out-of-mqtt-for-industrial-iot","Best Practices for Optimizing MQTT in Industrial IoT Systems",[231,232,233],"post","flowfuse","mqtt","MBX6ZcA5otxtSLzqCxoRTBniLvlqLObDf8h6JMoDxVc",{"id":236,"extension":237,"meta":238,"sections":239,"stem":628,"__hash__":629},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[240,291,392,454,531,610],{"id":241,"title":242,"features":243},"ai-automation","AI & Automation",[244,254,264,274,280,286],{"id":245,"title":246,"description":247,"docsLink":248,"changelog":249,"tiers":253},"flowfuse-expert-ai","FlowFuse Expert AI","Build industrial apps with agents, and query the state of the factory with an agent. Adapt your current hardware and machines so agentic work can be done against them, without ripping and replacing what's already on the plant floor.","\u002Fdocs\u002Fuser\u002Fexpert\u002F",[250],{"url":251,"release":252},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":224,"hub":224,"fleet":224},{"id":255,"title":256,"description":257,"docsLink":258,"changelog":259,"subfeature":224,"showOnPricing":262,"tiers":263},"flowfuse-expert-support-mode","Support Mode","Chat-based assistance for FlowFuse and Node-RED, including Node-RED instance management through natural language.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#support-mode",[260],{"url":261,"release":252},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":224,"hub":224,"fleet":224},{"id":265,"title":266,"description":267,"docsLink":268,"changelog":269,"subfeature":224,"showOnPricing":262,"tiers":273},"flowfuse-expert-application-building","Application Building","Describe what you want to build and FlowFuse Expert assembles it on your workspace, adding tabs, wiring nodes, and configuring properties.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F",[270],{"url":271,"release":272},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":224,"hub":224,"fleet":224},{"id":275,"title":276,"description":277,"docsLink":278,"subfeature":224,"beta":224,"showOnPricing":262,"tiers":279},"flowfuse-expert-insights-mode","Insights Mode","Connects FlowFuse Expert to MCP servers in your Node-RED instances, enabling real-time data queries and actions through a single chat interface.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#insights-mode",{"edge":224,"hub":224,"fleet":224},{"id":281,"title":282,"description":283,"docsLink":284,"tiers":285},"mcp-servers","Agentic Operations","Expose your Node-RED flows as tools an AI agent can call directly, so agents can query the state of the factory or trigger actions without custom integration work.","\u002Fnode-red\u002Fflowfuse\u002Fmcp\u002F",{"edge":224,"hub":224,"fleet":224},{"id":287,"title":288,"description":289,"tiers":290},"onnx-integration","ONNX Integration","Run trained machine learning models directly in your flows, including on edge hardware, without sending data out to an external inference service.",{"edge":224,"hub":224,"fleet":224},{"id":292,"title":293,"features":294},"build","Build",[295,301,307,317,323,329,333,339,345,353,359,363,367,376,384],{"id":296,"title":297,"description":298,"docsLink":299,"tiers":300},"edge-development","Edge Development","Develop and test Node-RED flows directly on edge devices with a remote editor proxy.","\u002Fdocs\u002Fdevice-agent\u002Fquickstart\u002F",{"edge":224,"hub":262,"fleet":224},{"id":302,"title":303,"description":304,"docsLink":305,"tiers":306},"private-npm-registry","Custom Node-RED Nodes","Create and manage your own private npm registry for Node-RED nodes, so you can share custom nodes across your team and devices without publishing them publicly.","\u002Fdocs\u002Fuser\u002Fcustom-npm-packages\u002F",{"edge":224,"hub":224,"fleet":224},{"id":308,"title":309,"description":310,"docsLink":311,"changelog":312,"tiers":316},"flowfuse-tables","FlowFuse Tables","A managed PostgreSQL database for every application, so you can store and query structured data without standing up and maintaining your own database.","\u002Fdocs\u002Fuser\u002Fff-tables\u002F",[313],{"url":314,"release":315},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":224,"hub":224,"fleet":224},{"id":318,"title":319,"description":320,"docsLink":321,"tiers":322},"persistent-files","File Storage","Store and retrieve files from your Node-RED flows, with automatic replication and backup across your devices and hosted instances.","\u002Fdocs\u002Finstall\u002Ffile-storage\u002F",{"edge":224,"hub":224,"fleet":224},{"id":324,"title":325,"description":326,"docsLink":327,"showOnPricing":262,"tiers":328},"persistent-context","Persistent Context","In-memory values defined in a Node-RED flow persist across project restarts and upgrades.","\u002Fdocs\u002Fuser\u002Fpersistent-context\u002F",{"edge":224,"hub":224,"fleet":224},{"id":330,"title":331,"showOnPricing":262,"tiers":332},"static-assets","Static Assets",{"edge":224,"hub":224,"fleet":224},{"id":334,"title":335,"description":336,"docsLink":337,"tiers":338},"team-library","Team Library","Set up standard nodes and flows that can be shared with all team members across your organisation.","\u002Fdocs\u002Fuser\u002Fshared-library\u002F",{"edge":224,"hub":224,"fleet":224},{"id":340,"title":341,"description":342,"docsLink":343,"tiers":344},"personalised-multi-user-dashboards","Personalised Multi-User Dashboards","Build applications that provide unique data to each logged-in user using personalised multi-user dashboards.","https:\u002F\u002Fdashboard.flowfuse.com\u002Fuser\u002Fmulti-tenancy.html",{"edge":224,"hub":224,"fleet":224},{"id":346,"title":347,"description":348,"changelog":349,"subfeature":224,"showOnPricing":262,"tiers":352},"dashboards-view","Dashboards View","Browse and open every dashboard across your team from a dedicated Dashboards view, at both team and application level, without leaving FlowFuse.",[350],{"url":351,"release":315},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":224,"hub":224,"fleet":224},{"id":354,"title":355,"description":356,"docsLink":357,"tiers":358},"blueprints-converge","Blueprints","Ready-made starting points for your apps, from cross-team Converge templates to OT and IT specific blueprints.","\u002Fdocs\u002Fuser\u002Fconcepts\u002F#blueprint",{"edge":224,"hub":224,"fleet":224},{"id":360,"title":361,"subfeature":224,"showOnPricing":262,"tiers":362},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":224,"hub":262,"fleet":224},{"id":364,"title":365,"subfeature":224,"showOnPricing":262,"tiers":366},"blueprints-it-apps","Blueprints - IT APPS",{"edge":262,"hub":224,"fleet":262},{"id":368,"title":369,"description":370,"changelog":371,"showOnPricing":262,"tiers":375},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[372],{"url":373,"release":374},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":224,"hub":224,"fleet":224},{"id":377,"title":378,"description":379,"changelog":380,"showOnPricing":262,"tiers":383},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[381],{"url":382,"release":272},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":224,"hub":224,"fleet":224},{"id":385,"title":386,"description":387,"changelog":388,"showOnPricing":262,"tiers":391},"embedded-editor-tab-title","Embedded Editor Browser Tab Title","The browser tab title updates to reflect the active Node-RED canvas tab when working in the embedded editor.",[389],{"url":390,"release":374},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":224,"hub":224,"fleet":224},{"id":393,"title":394,"features":395},"deploy","Deploy",[396,402,411,417,423,429,435,441,446],{"id":397,"title":398,"description":399,"docsLink":400,"tiers":401},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":224,"hub":224,"fleet":224},{"id":403,"title":404,"description":405,"docsLink":406,"changelog":407,"tiers":410},"edge-devices","Edge Instances","Deploy and mange your Node-RED instances on edge PLCs and gateways, with full visibility and control from the cloud.","\u002Fdocs\u002Fdevice-agent\u002Fintroduction\u002F",[408],{"url":409,"release":252},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":224,"hub":262,"fleet":224},{"id":412,"title":413,"description":414,"docsLink":415,"tiers":416},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":262,"hub":224,"fleet":262},{"id":418,"title":419,"description":420,"docsLink":421,"tiers":422},"mqtt-broker","MQTT Broker","Manage and create MQTT clients to transport data for efficient messaging and communication within your applications.","\u002Fdocs\u002Fuser\u002Fteambroker\u002F",{"edge":224,"hub":262,"fleet":224},{"id":424,"title":425,"description":426,"docsLink":427,"showOnPricing":262,"tiers":428},"project-nodes","Project Nodes aka seamless project comms","FlowFuse Project Nodes enable the passing of data and messages between your Node-RED projects.","\u002Fdocs\u002Fuser\u002Fprojectnodes\u002F",{"edge":224,"hub":224,"fleet":224},{"id":430,"title":431,"description":432,"docsLink":433,"tiers":434},"devops-pipelines","DevOps Pipelines","Set up different environments for development, testing, and production Node-RED instances to support a full software delivery lifecycle.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F",{"edge":224,"hub":224,"fleet":224},{"id":436,"title":437,"description":438,"docsLink":439,"tiers":440},"git-integration","Git Integration","Back up your flows to a remote Git repository through a DevOps Pipeline. Supports GitHub and Azure DevOps repositories.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F#git-repository-stage",{"edge":262,"hub":224,"fleet":262},{"id":442,"title":443,"description":444,"docsLink":439,"subfeature":224,"showOnPricing":262,"tiers":445},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":262,"hub":224,"fleet":262},{"id":447,"title":448,"description":449,"docsLink":439,"changelog":450,"subfeature":224,"showOnPricing":262,"tiers":453},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[451],{"url":452,"release":374},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":262,"hub":224,"fleet":262},{"id":455,"title":456,"features":457},"operate-maintain","Operate & Maintain",[458,464,470,475,483,487,491,496,502,508,513,519,523,527],{"id":459,"title":460,"description":461,"docsLink":462,"tiers":463},"snapshots","Snapshots & Version History","Automatic snapshots on remote devices and hosted instances, plus a full version history timeline so you can roll back to any prior state.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F",{"edge":224,"hub":224,"fleet":224},{"id":465,"title":466,"description":467,"docsLink":468,"subfeature":224,"showOnPricing":262,"tiers":469},"auto-snapshot-remote","Auto Snapshot (Remote)","Automatically capture a snapshot every time a remote instance is deployed, so you always have a recoverable history of what was running on each device.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F#auto-snapshots",{"edge":224,"hub":224,"fleet":224},{"id":471,"title":472,"description":473,"docsLink":468,"subfeature":224,"showOnPricing":262,"tiers":474},"auto-snapshot-hosted","Auto Snapshot (Hosted)","Automatically capture a snapshot every time a hosted instance is deployed, so you always have a recoverable history of what was running.",{"edge":224,"hub":224,"fleet":224},{"id":476,"title":477,"description":478,"changelog":479,"subfeature":224,"showOnPricing":262,"tiers":482},"snapshot-comparison","Snapshot Comparison","Compare two snapshots side-by-side with a navigable diff view. Step through every changed, added, or deleted node and see property and code diffs.",[480],{"url":481,"release":374},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":224,"hub":224,"fleet":224},{"id":484,"title":485,"subfeature":224,"showOnPricing":262,"tiers":486},"version-history-timeline","Version History Timeline",{"edge":224,"hub":224,"fleet":224},{"id":488,"title":489,"tiers":490},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":224,"hub":224,"fleet":224},{"id":492,"title":493,"description":494,"tiers":495},"device-fleet-updates","Device Fleet Updates","Connect to edge devices to quickly assess and update logic. Debug one device and roll out improvements to your fleet in minutes, securely without requiring full device access for your whole organisation.",{"edge":224,"hub":262,"fleet":224},{"id":497,"title":498,"description":499,"docsLink":500,"tiers":501},"device-group-management","Device Group Management","Logically group devices assigned to an application and integrate device groups into your DevOps Pipeline for coordinated fleet updates.","\u002Fdocs\u002Fuser\u002Fdevice-groups\u002F",{"edge":224,"hub":262,"fleet":224},{"id":503,"title":504,"description":505,"docsLink":506,"tiers":507},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":262,"hub":224,"fleet":262},{"id":509,"title":510,"description":511,"tiers":512},"performance-monitoring","Performance Monitoring & Alerts","Track CPU, memory, and event loop performance across your instances and devices, with email alerts when something needs your attention.",{"edge":224,"hub":224,"fleet":224},{"id":514,"title":515,"description":516,"docsLink":517,"subfeature":224,"showOnPricing":262,"tiers":518},"instance-monitoring","Instance Monitoring","Enable alerts to be sent via email when your Node-RED instances encounter issues.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#alerts",{"edge":224,"hub":224,"fleet":224},{"id":520,"title":521,"subfeature":224,"showOnPricing":262,"tiers":522},"email-alerts","Email Alerts",{"edge":224,"hub":224,"fleet":224},{"id":524,"title":525,"showOnPricing":262,"tiers":526},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":224,"hub":224,"fleet":224},{"id":528,"title":529,"tiers":530},"protected-instances","Protected Instances",{"edge":262,"hub":224,"fleet":262},{"id":532,"title":533,"features":534},"govern-secure","Govern and Secure",[535,544,550,556,561,567,573,579,587,593,599,605],{"id":536,"title":537,"description":538,"docsLink":539,"changelog":540,"tiers":543},"single-sign-on","Single Sign-On (SSO)","Configure FlowFuse to work with your own SSO provider, allowing users to access FlowFuse with a single set of login credentials.","\u002Fdocs\u002Fadmin\u002Fsso\u002F",[541],{"url":542,"release":315},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":224,"hub":224,"fleet":224},{"id":545,"title":546,"description":547,"docsLink":548,"tiers":549},"two-factor-authentication","Two-Factor Authentication","Two-factor authentication adds an extra layer of security to your FlowFuse account.","\u002Fdocs\u002Fuser\u002Fuser-settings\u002F#two-factor-authentication",{"edge":224,"hub":224,"fleet":224},{"id":551,"title":552,"description":553,"docsLink":554,"tiers":555},"certified-nodes-it","Certified Nodes - IT","IT certified node bundle includes: Redis, MQTT, HTTP Request, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server","\u002Fblog\u002F2025\u002F07\u002Fcertified-nodes-v2\u002F",{"edge":262,"hub":224,"fleet":224},{"id":557,"title":558,"description":559,"tiers":560},"certified-nodes-ot","Certified OT Connections - OPC-UA, Modbus, etc.","OT certified node bundle includes: OPC-UA, Modbus TCP & RTU, RTSP, EtherNet\u002FIP, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server",{"edge":224,"hub":262,"fleet":262},{"id":562,"title":563,"description":564,"docsLink":565,"tiers":566},"audit-log","Audit Log","Keep track of everything going on in your Node-RED instances and FlowFuse. Audit Logs provide details on what actions have taken place, when they happened, and who did them.","\u002Fdocs\u002Fuser\u002Flogs\u002F#audit-log",{"edge":224,"hub":224,"fleet":224},{"id":568,"title":569,"description":570,"docsLink":571,"tiers":572},"role-based-access-control","Role-Based Access Control","Control who can do what at both the team and application level, from viewers to admins.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F",{"edge":224,"hub":224,"fleet":224},{"id":574,"title":575,"description":576,"docsLink":577,"subfeature":224,"showOnPricing":262,"tiers":578},"application-level-rbac","Application-Level RBAC","Fine-grained access control per application, allowing team members to have different permission levels across different applications without requiring separate teams.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F#application-level-rbac",{"edge":224,"hub":224,"fleet":224},{"id":580,"title":581,"description":582,"changelog":583,"subfeature":224,"showOnPricing":262,"tiers":586},"scoped-personal-access-tokens","Scoped Personal Access Tokens","Restrict a Personal Access Token to specific teams, limit it to read-only operations, or control whether it carries admin privileges.",[584],{"url":585,"release":315},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":224,"hub":224,"fleet":224},{"id":588,"title":589,"description":590,"docsLink":591,"showOnPricing":262,"tiers":592},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":224,"hub":224,"fleet":224},{"id":594,"title":595,"description":596,"docsLink":597,"showOnPricing":262,"tiers":598},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":224,"hub":224,"fleet":224},{"id":600,"title":601,"description":602,"docsLink":603,"tiers":604},"baa-for-hipaa","BAA for HIPAA","FlowFuse can sign a Business Associate Agreement to ensure proper safeguarding of protected health information handled on your behalf.","\u002Fhandbook\u002Fsales\u002Fsubscription-agreement-1.5\u002F",{"edge":262,"hub":224,"fleet":262},{"id":606,"title":607,"description":608,"tiers":609},"sbom","Software Bill of Materials","A complete list of all software components used in your Node-RED instances and hosted applications, including version numbers and license information.",{"edge":262,"hub":224,"fleet":262},{"id":611,"title":612,"features":613},"support","Support",[614,619,623],{"id":615,"title":616,"docsLink":617,"tiers":618},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":224,"hub":224,"fleet":224},{"id":620,"title":621,"showOnPricing":262,"tiers":622},"live-chat-support","Live Chat Support",{"edge":224,"hub":224,"fleet":224},{"id":624,"title":625,"docsLink":626,"tiers":627},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":224,"hub":224,"fleet":224},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[631,634,637,640,643,646,648,651,654,657,660,662,665,668,671,674,677,680,683,686,689,692,695,698,701,704,707,710,713,716,719,722,725,728,731,734,737,740,743,746,749,752,755,758,761,764,767,770,773,775,778,781,784,787,790,793,796,798,801,804,807,810,813,815,818,821,824,827,830,833,836,839,842,845,847,850,853,856,859,862,865,868,871,874,877,880,883,886,889,891,894,897,900,903,906,909,912,915,918,921,924,927,930,933,936,939,942,945,947,950,953,956,959,962,965,968,970,973,976,979,982,985,988,991,994,997,1000,1003,1006,1009,1012,1015,1018,1021,1024,1027,1030,1033,1036,1039,1042,1045,1048,1051,1054,1057,1060,1063,1066,1069,1072,1075,1078,1081,1084,1087,1090,1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1122,1125,1128,1131,1134,1137,1140,1143,1146,1149,1152,1155,1158,1161],{"path":632,"title":633},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":635,"title":636},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":638,"title":639},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":641,"title":642},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":644,"title":645},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":647,"title":355},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":649,"title":650},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":652,"title":653},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":655,"title":656},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":658,"title":659},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":661,"title":546},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":663,"title":664},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":666,"title":667},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":669,"title":670},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":672,"title":673},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":675,"title":676},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":678,"title":679},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":681,"title":682},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":684,"title":685},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":687,"title":688},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":690,"title":691},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":693,"title":694},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":696,"title":697},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":699,"title":700},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":702,"title":703},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":705,"title":706},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":708,"title":709},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":711,"title":712},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":714,"title":715},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":717,"title":718},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":720,"title":721},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":723,"title":724},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":726,"title":727},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":729,"title":730},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":732,"title":733},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":735,"title":736},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":738,"title":739},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":741,"title":742},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":744,"title":745},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":747,"title":748},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":750,"title":751},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":753,"title":754},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":756,"title":757},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":759,"title":760},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":762,"title":763},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":765,"title":766},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":768,"title":769},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":771,"title":772},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":774,"title":772},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":776,"title":777},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":779,"title":780},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":782,"title":783},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":785,"title":786},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":788,"title":789},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":791,"title":792},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":794,"title":795},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":797,"title":795},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":799,"title":800},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":802,"title":803},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":805,"title":806},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":808,"title":809},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":811,"title":812},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":814,"title":812},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":816,"title":817},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":819,"title":820},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":822,"title":823},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":825,"title":826},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":828,"title":829},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":831,"title":832},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":834,"title":835},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":837,"title":838},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":840,"title":841},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":843,"title":844},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":846,"title":485},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":848,"title":849},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":851,"title":852},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":854,"title":855},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":857,"title":858},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":860,"title":861},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":863,"title":864},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":866,"title":867},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":869,"title":870},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":872,"title":873},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":875,"title":876},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":878,"title":879},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":881,"title":882},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":884,"title":885},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":887,"title":888},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":890,"title":485},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":892,"title":893},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":895,"title":896},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":898,"title":899},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":901,"title":902},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":904,"title":905},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":907,"title":908},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":910,"title":911},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":913,"title":914},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":916,"title":917},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":919,"title":920},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":922,"title":923},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":925,"title":926},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":928,"title":929},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":931,"title":932},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":934,"title":935},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":937,"title":938},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":940,"title":941},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":943,"title":944},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":946,"title":944},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":948,"title":949},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":951,"title":952},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":954,"title":955},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":957,"title":958},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":960,"title":961},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":963,"title":964},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":966,"title":967},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":969,"title":309},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":971,"title":972},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":974,"title":975},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":977,"title":978},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":980,"title":981},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":983,"title":984},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":986,"title":987},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":989,"title":990},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":992,"title":993},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":995,"title":996},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":998,"title":999},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1001,"title":1002},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1004,"title":1005},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1007,"title":1008},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1010,"title":1011},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1013,"title":1014},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1016,"title":1017},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1019,"title":1020},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1022,"title":1023},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1025,"title":1026},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1028,"title":1029},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1031,"title":1032},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1034,"title":1035},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1037,"title":1038},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1040,"title":1041},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1043,"title":1044},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1046,"title":1047},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1049,"title":1050},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1052,"title":1053},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1055,"title":1056},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1058,"title":1059},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1061,"title":1062},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1064,"title":1065},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1067,"title":1068},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1070,"title":1071},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1073,"title":1074},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1076,"title":1077},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1079,"title":1080},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1082,"title":1083},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1085,"title":1086},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1088,"title":1089},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1091,"title":1092},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1094,"title":1095},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1097,"title":1098},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1100,"title":1101},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1103,"title":1104},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1106,"title":1107},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1109,"title":1110},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1112,"title":1113},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1115,"title":1116},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1118,"title":1119},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1121,"title":378},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1123,"title":1124},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1126,"title":1127},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1129,"title":1130},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1132,"title":1133},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1135,"title":1136},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1138,"title":1139},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1141,"title":1142},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1144,"title":1145},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1147,"title":1148},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1150,"title":1151},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1153,"title":1154},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1156,"title":1157},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1159,"title":1160},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1162,"title":1163},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105889467]