diff --git a/nuxt/components/content/ProductUpdateNote.vue b/nuxt/components/content/ProductUpdateNote.vue new file mode 100644 index 0000000000..b338f53805 --- /dev/null +++ b/nuxt/components/content/ProductUpdateNote.vue @@ -0,0 +1,17 @@ + + + diff --git a/src/blog/2023/07/influxdb-historical-data.md b/src/blog/2023/07/influxdb-historical-data.md index 01e96d381a..503c2cd391 100644 --- a/src/blog/2023/07/influxdb-historical-data.md +++ b/src/blog/2023/07/influxdb-historical-data.md @@ -3,7 +3,7 @@ title: Creating a Historical Data Dashboard with InfluxDB and Node-RED subtitle: Detailed instructions on how to create a Node-RED dashboard that shows historical data. description: Discover how to build a Historical Data Dashboard with InfluxDB and Node-RED. Capture, store, and visualize data for insightful analysis. date: 2023-07-18 -lastUpdated: 2025-07-14 +lastUpdated: 2026-08-13 authors: ["andrew-lynch"] image: /blog/2023/07/images/historical-data-dashboard.png keywords: Node-RED InfluxDB, Time-series data, Industrial dashboard, Historical data visualization, IoT dashboard, Serial port sensor data, Live and historical charts @@ -16,6 +16,9 @@ Every new dashboard is met with the fast-following request, “can we save this +::product-update-note +:: + Edge devices are often polling sensors at regular intervals and are a perfect candidate to be paired with a database purpose-built for time-series data, like InfluxDB. Let’s capture some data, create a live chart, store the data, and then create a GUI for retrieving the data. Here’s a screenshot of the dashboard we will create, which is divided into two sections. The first section displays live data, while the second section consists of fields that enable users to query the database and retrieve historical data. Looking at the live data, the chart depicts a sinusoidal graph that represents the scale measurements used for quality assurance in the aggregate production process at an automated mining operation. The graph showcases fluctuations in weight over time, indicating variations in the samples being weighed. This monitoring process ensures the quality and consistency of the aggregates being produced. The historical data shows a snippet of this information that was retrieved from InfluxDB. diff --git a/src/blog/2023/08/flowfuse-1-11-release.md b/src/blog/2023/08/flowfuse-1-11-release.md index 264130ead0..ba4c20de10 100644 --- a/src/blog/2023/08/flowfuse-1-11-release.md +++ b/src/blog/2023/08/flowfuse-1-11-release.md @@ -3,6 +3,7 @@ title: FlowFuse 1.11 makes it easier to get started with FlowFuse and Node-RED subtitle: Our latest release includes a new starter tier for FlowFuse Cloud, Personal Access Tokens for API access and improvements to device management. description: The new FlowFuse 1.11 release includes a new starter tier for FlowFuse Cloud, Personal Access Tokens for API access and improvements to device management. date: 2023-08-31 +lastUpdated: 2026-08-13 authors: ["ian-skerrett"] image: /blog/2023/08/images/release-1-11-graphic.png tags: @@ -14,6 +15,10 @@ tags: FlowFuse 1.11 introduces a new starter tier for FlowFuse Cloud that makes it easier to get started with FlowFuse and Node-RED. + +::product-update-note +:: + ## New FlowFuse Cloud Starter Tier [#2328](https://github.com/FlowFuse/flowfuse/issues/2328) It is now easier for Node-RED developers to get started with FlowFuse and Node-RED. The new starter tier allows developers to use two Node-RED instances and two remote device deployments. Ideal for creating proof of concepts or running a home automation system with Node-RED. diff --git a/src/blog/2023/09/community-news-09.md b/src/blog/2023/09/community-news-09.md index ed3313fd56..5a46127607 100644 --- a/src/blog/2023/09/community-news-09.md +++ b/src/blog/2023/09/community-news-09.md @@ -3,6 +3,7 @@ title: Community News September 2023 subtitle: Your monthly update for the FlowFuse and Node-RED communities description: "A roundup of September 2023 news from the FlowFuse and Node-RED communities, covering platform updates and community highlights." date: 2023-09-09 +lastUpdated: 2026-08-13 authors: ["ian-skerrett"] image: "/images/blog/community-news.jpeg" tags: @@ -18,6 +19,9 @@ The big news this month is that [FlowForge is now FlowFuse](/blog/2023/08/flowfo +::product-update-note +:: + ## New Releases * Node-RED 3.1 has been [released](https://nodered.org/blog/2023/09/06/version-3-1-released). Among the changes are Mermaid chart support, locking flows, and much more. diff --git a/src/blog/2024/06/dashboard-multi-tenancy.md b/src/blog/2024/06/dashboard-multi-tenancy.md index 02d5c44034..8e17335c0b 100644 --- a/src/blog/2024/06/dashboard-multi-tenancy.md +++ b/src/blog/2024/06/dashboard-multi-tenancy.md @@ -3,6 +3,7 @@ title: Multi-Tenancy available for everyone with FlowFuse's Dashboard 2.0 subtitle: With a recent update in Node-RED Dashboard 2.0, we've made some significant changes to the multi-tenancy feature set. Discover what's new and how it can benefit your projects. description: "With a recent Dashboard 2.0 update, discover what's new in multi-tenancy and how it can benefit your team's ongoing projects." date: 2024-06-21 +lastUpdated: 2026-08-13 authors: ["joe-pavitt"] image: /blog/2024/06/images/tile-dashboard-2-multi-tenancy.png tags: @@ -22,6 +23,9 @@ Having taken that feedback on board, we've made some significant changes to how +::product-update-note +:: + A quick summary of the changes are as follows: - **Socket constraints moved to core Dashboard:** The ability to constrain communications to a specific client (using the `msg._client.socketId`) has been moved to the core of Dashboard 2.0, and is no longer a feature of the FlowFuse User Addon. As such, it's available to _all_ users, for _all_ node types. @@ -101,4 +105,4 @@ A huge thanks to Fred Loucks ([@fullmetal-fred](https://github.com/fullmetal-fre ## Build Multi Tenant Dashboards with FlowFuse Cloud -Start by following our [Getting Started Guide](https://dashboard.flowfuse.com/user/multi-tenancy.html#building-multi-tenant-dashboards). \ No newline at end of file +Start by following our [Getting Started Guide](https://dashboard.flowfuse.com/user/multi-tenancy.html#building-multi-tenant-dashboards). diff --git a/src/blog/2024/06/how-to-use-mqtt-in-node-red.md b/src/blog/2024/06/how-to-use-mqtt-in-node-red.md index 188cff0bbb..af62446b49 100644 --- a/src/blog/2024/06/how-to-use-mqtt-in-node-red.md +++ b/src/blog/2024/06/how-to-use-mqtt-in-node-red.md @@ -2,7 +2,7 @@ title: "Working with MQTT in Node-RED: Complete Guide (2026)" subtitle: "Connect, subscribe, and publish MQTT messages in Node-RED" description: "Complete MQTT Node-RED tutorial: configure brokers, implement pub/sub messaging, use mqtt-in and mqtt-out nodes, and create dynamic subscriptions for IoT" -lastUpdated: 2026-06-03 +lastUpdated: 2026-08-13 date: 2024-06-05 authors: ["sumit-shinde"] image: /blog/2024/06/images/working-with-mqtt.jpg @@ -61,6 +61,9 @@ MQTT handles the messaging layer for most IoT deployments. Node-RED provides bui +::product-update-note +:: + This guide walks through the configuration steps and common patterns you'll need for working implementations. ## What You'll Need diff --git a/src/blog/2024/10/announcement-mqtt-broker.md b/src/blog/2024/10/announcement-mqtt-broker.md index 20e1471f4d..0272c42d7d 100644 --- a/src/blog/2024/10/announcement-mqtt-broker.md +++ b/src/blog/2024/10/announcement-mqtt-broker.md @@ -3,6 +3,7 @@ title: "MQTT Service Now Available on FlowFuse" subtitle: 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. description: "FlowFuse now offers its own built-in MQTT service, ready to use with your Node-RED applications right out of the box today." date: 2024-10-31 +lastUpdated: 2026-08-13 authors: ["joe-pavitt"] image: /blog/2024/10/images/ff-mqtt.png tags: @@ -17,6 +18,9 @@ In our [recent product update](/blog/2024/10/flowfuse-release-2-10) we have adde +::product-update-note +:: + The MQTT Service is available now on [FlowFuse Cloud](https://app.flowfuse.com/account/create/). FlowFuse permits you to setup your own secure clients to begin publishing and subscribing to your own topics. You can now use FlowFuse to manage your own MQTT Clients alongside your Node-RED instances, making it easier to build full-stack, event-driven applications within FlowFuse. @@ -83,4 +87,4 @@ Each client that you create can be constrained in two ways: - **Action**: You can limit clients to whether than can _only_ subscribe, _only_ publish, or conduct both actions. - **Topic**: You can control which topics a given client can interact with. -These constraints are particularly useful to ensure security throughout your MQTT network, and to ensure that data is only being sent and received by the correct components. \ No newline at end of file +These constraints are particularly useful to ensure security throughout your MQTT network, and to ensure that data is only being sent and received by the correct components. diff --git a/src/blog/2024/12/flowfuse-release-2-12.md b/src/blog/2024/12/flowfuse-release-2-12.md index 5a5d5c1de4..0f0d0896e2 100644 --- a/src/blog/2024/12/flowfuse-release-2-12.md +++ b/src/blog/2024/12/flowfuse-release-2-12.md @@ -40,6 +40,9 @@ The new Free plan on FlowFuse Cloud will allow you to manage two remote instance +::product-update-note +:: + FlowFuse is an industrial data platform that enables engineers to build, manage, scale, and secure their Node-RED solutions for digitalizing processes and operations. More fundamentally though, it's a great platform to manage multiple instances of Node-RED. diff --git a/src/blog/2024/12/publishing-modbus-data-to-uns.md b/src/blog/2024/12/publishing-modbus-data-to-uns.md index 2761608a22..c7c9890f38 100644 --- a/src/blog/2024/12/publishing-modbus-data-to-uns.md +++ b/src/blog/2024/12/publishing-modbus-data-to-uns.md @@ -3,7 +3,7 @@ title: "How to Bridge Modbus to MQTT: Step-by-Step Guide" subtitle: Build a Production-Ready Modbus to MQTT Bridge with Node-RED description: Learn how to bridge Modbus data to MQTT in 2026 and publish it to a Unified Namespace (UNS) using FlowFuse for real-time monitoring and cloud integration. date: 2024-12-04 -lastUpdated: 2025-12-19 +lastUpdated: 2026-08-13 authors: ["sumit-shinde"] image: /blog/2024/12/images/how-to-bridge-modbus-to-mqtt.png keywords: modbus to mqtt, mqtt to modbus, node-red as gateway, bridging modbus to mqtt, modbus to uns, modbus data to unified namespace @@ -38,6 +38,9 @@ Converting Modbus to MQTT unlocks the value trapped in legacy industrial equipme +::product-update-note +:: + We've built Modbus to MQTT bridges for manufacturing plants ranging from small production lines to enterprise-scale facilities, and the root problem is always the same protocol mismatch. Modbus requires a master-slave architecture with polling, one device requests data, another responds. MQTT enables publish-subscribe messaging, devices push data to a central broker where any authorized application can subscribe. These are fundamentally incompatible communication patterns. The proven solution is protocol bridging with Node-RED. This guide shows you how to build a reliable Modbus to MQTT gateway that reads holding registers from your devices, transforms raw sensor readings into human-readable formats, and publishes structured data to a Unified Namespace using FlowFuse's integrated MQTT broker. You'll bridge the OT/IT gap and enable cloud integration, real-time monitoring, and data-driven decision-making across your operations. diff --git a/src/blog/2025/01/flowfuse-release-2-13.md b/src/blog/2025/01/flowfuse-release-2-13.md index a275ff9cf3..bc648f4a3d 100644 --- a/src/blog/2025/01/flowfuse-release-2-13.md +++ b/src/blog/2025/01/flowfuse-release-2-13.md @@ -15,6 +15,9 @@ Happy New Year everyone! We're back with another release of FlowFuse, and whilst +::product-update-note +:: + ## Hosted & Remote Instances This release you'll notice that we've changed the terminology of two of our key concepts in FlowFuse: diff --git a/src/blog/2025/01/how-to-choose-right-iot-device-management-tool.md b/src/blog/2025/01/how-to-choose-right-iot-device-management-tool.md index b5e1fac506..ff7b9fc31d 100644 --- a/src/blog/2025/01/how-to-choose-right-iot-device-management-tool.md +++ b/src/blog/2025/01/how-to-choose-right-iot-device-management-tool.md @@ -3,6 +3,7 @@ title: How to Choose the Right IIoT Device Management Software for Your Business subtitle: Key Features and Considerations for Effective IIoT Device Management description: Learn how to choose the right IIoT device management software for your business with this comprehensive guide. Key features and considerations explained. date: 2025-01-24 +lastUpdated: 2026-08-13 authors: ["sumit-shinde"] image: /blog/2025/01/images/choosing-iot-device-mangement-platform.png tags: @@ -17,6 +18,9 @@ With more devices being connected across industrial environments, managing them +::product-update-note +:: + This guide will take you through the key features and considerations to keep in mind when choosing IIoT device management software. Whether you’re just starting out with IIoT or looking to improve your current setup, we’ve got some helpful insights to point you in the right direction. ### 1. Vendor Reputation and Support @@ -131,4 +135,4 @@ Built on the flexible [Node-RED](/node-red) framework, FlowFuse easily integrate [Real-time collaboration is built into the platform](/blog/2024/12/flowfuse-team-collaboration/), enabling your team to work together on projects, monitor devices remotely, and deploy updates simultaneously, all within a secure environment. [Role-Based Access Control (RBAC)](/blog/2024/04/role-based-access-control-rbac-for-node-red-with-flowfuse/) ensures that each team member has appropriate permissions based on their role. For example, admins can make critical changes, while operators can only monitor or update devices. This helps maintain control over sensitive functions while allowing your team to collaborate effectively. Together with RBAC, FlowFuse maximizes both security and productivity by ensuring the right people have access to the right tasks, at the right time. -If things go awry, FlowFuse’s [snapshot](/blog/2024/09/node-red-version-control-with-snapshots/) feature lets you quickly revert to a previous stable state, minimizing downtime and keeping your systems running smoothly. Advanced monitoring tools continuously track device performance, sending alerts if issues like crashes or resource overloads arise, so your team can act before problems escalate. Detailed device logs and audit trails make troubleshooting straightforward, helping you quickly pinpoint issues and maintain a secure environment. \ No newline at end of file +If things go awry, FlowFuse’s [snapshot](/blog/2024/09/node-red-version-control-with-snapshots/) feature lets you quickly revert to a previous stable state, minimizing downtime and keeping your systems running smoothly. Advanced monitoring tools continuously track device performance, sending alerts if issues like crashes or resource overloads arise, so your team can act before problems escalate. Detailed device logs and audit trails make troubleshooting straightforward, helping you quickly pinpoint issues and maintain a secure environment. diff --git a/src/blog/2025/02/flowfuse-release-2-14.md b/src/blog/2025/02/flowfuse-release-2-14.md index cf150fc8d6..092ac9940d 100644 --- a/src/blog/2025/02/flowfuse-release-2-14.md +++ b/src/blog/2025/02/flowfuse-release-2-14.md @@ -3,6 +3,7 @@ title: "FlowFuse 2.14: Announcing Third-Party Broker Integration, UNS Schemas, E subtitle: A huge wave of new features in FlowFuse elevates your MQTT experience as well as providing improved Remote Instances security and version control too description: A huge wave of new features in FlowFuse elevates your MQTT experience as well as providing improved Remote Instances security and version control too date: 2025-02-11 +lastUpdated: 2026-08-13 authors: ["joe-pavitt"] image: /blog/2025/02/images/release-2-14.png tags: @@ -15,6 +16,9 @@ This release is full of highlights, which we’ll break down into two key areas +::product-update-note +:: + ## MQTT Experience in FlowFuse In [October we announced the FlowFuse MQTT Broker](/blog/2024/10/announcement-mqtt-broker/), included in our Starter, Team, and Enterprise tiers. It lets you setup your own secure clients to begin publishing and subscribing to your own topics, and building out your full event-driven applications. diff --git a/src/blog/2025/02/interacting-with-arduino-using-node-red.md b/src/blog/2025/02/interacting-with-arduino-using-node-red.md index 9bb70da03f..622d49b6c6 100644 --- a/src/blog/2025/02/interacting-with-arduino-using-node-red.md +++ b/src/blog/2025/02/interacting-with-arduino-using-node-red.md @@ -3,7 +3,7 @@ title: "Interacting with Arduino using Node-RED" subtitle: "Control and Automate Arduino with Node-RED" description: "Learn how to set up and control your Arduino remotely using Node-RED and FlowFuse. Explore the simplicity of automation flows" date: 2025-02-12 -lastUpdated: 2025-07-23 +lastUpdated: 2026-08-13 authors: ["sumit-shinde"] image: /blog/2025/02/images/arduino-with-node-red.png keywords: Arduino, Node-RED, Firmata, Node-RED IoT, automation, FlowFuse, LED control with Node-RED, IR sensor, input-output, serial communication, microcontroller, Arduino Uno, remote control, object detection, dashboard. @@ -16,6 +16,9 @@ Arduino is a popular open-source platform that lets you build cool electronics p +::product-update-note +:: + In this guide, I’ll show you how to control and automate your Arduino remotely using Node-RED and FlowFuse, all without writing any code. We’ll use the Firmata protocol to make it easy to send commands and get data from your Arduino. By the end of this tutorial, you’ll have a simple automation setup that you can control from anywhere. Just keep in mind, the Arduino will need to be connected to the device running Node-RED! diff --git a/src/blog/2025/03/flowfuse-release-2-15.md b/src/blog/2025/03/flowfuse-release-2-15.md index 8ae7071554..5123eaf0c2 100644 --- a/src/blog/2025/03/flowfuse-release-2-15.md +++ b/src/blog/2025/03/flowfuse-release-2-15.md @@ -19,6 +19,9 @@ Our three focal points for the latest release of FlowFuse have been: +::product-update-note +:: + ## Custom Node Catalogues ![Screenshot of the new "Custom Nodes" view in Team Library"](./images/screenshot-custon-catalog.png){data-zoomable} diff --git a/src/blog/2025/07/flowfuse-release-2-20.md b/src/blog/2025/07/flowfuse-release-2-20.md index 9d6c032289..c6fb99d872 100644 --- a/src/blog/2025/07/flowfuse-release-2-20.md +++ b/src/blog/2025/07/flowfuse-release-2-20.md @@ -3,6 +3,7 @@ title: "FlowFuse 2.20: AI-Assisted Node-RED & New Database Service" subtitle: "Introducing FlowFuse Tables for data storage, Tables nodes for database querying, Smart Suggestions in the Node-RED editor, More Powerful Instances, Retrieval Augmented Generation Blueprint for building intelligent applications, and a redesigned Applications page for better workspace management." description: "FlowFuse 2.20 introduces AI-assisted Node-RED and a brand new database service, plus Smart Suggestions in the flow editor." date: 2025-07-31 +lastUpdated: 2026-08-13 authors: ["greg-stoutenburg"] image: /blog/2025/07/images/release-2-20.png tags: @@ -16,6 +17,9 @@ This release represents a major leap forward in FlowFuse's data management and A +::product-update-note +:: + ## Introducing: FlowFuse Tables ![A screenshot of the new "Tables" view, now available in FlowFuse](./images/tables-ui-screenshot.png){data-zoomable} @@ -97,4 +101,4 @@ The quickest way to get started is with FlowFuse Cloud. ### Self-Hosted -Get FlowFuse running locally in under 30 minutes using [Docker](/docs/install/docker/) or [Kubernetes](/docs/install/kubernetes/). \ No newline at end of file +Get FlowFuse running locally in under 30 minutes using [Docker](/docs/install/docker/) or [Kubernetes](/docs/install/kubernetes/). diff --git a/src/blog/2025/08/annual_billing.md b/src/blog/2025/08/annual_billing.md index b91f917049..a2bb2d12ea 100644 --- a/src/blog/2025/08/annual_billing.md +++ b/src/blog/2025/08/annual_billing.md @@ -15,6 +15,9 @@ We're excited to announce that FlowFuse customers can now choose annual billing +::product-update-note +:: + ## How Annual Billing Works Switching to annual billing is straightforward: diff --git a/src/blog/2025/08/flowfuse-release-2-21.md b/src/blog/2025/08/flowfuse-release-2-21.md index bb0ecb0578..2f4a889585 100644 --- a/src/blog/2025/08/flowfuse-release-2-21.md +++ b/src/blog/2025/08/flowfuse-release-2-21.md @@ -3,6 +3,7 @@ title: "FlowFuse 2.21: AI-Assisted SQL, Low-Code Custom Nodes, and Remote Instan subtitle: "Introducing FlowFuse Expert functionality in Tables to do natural language queries of your databases, Remote Instance observability to improve performance monitoring, Team Broker nodes to make MQTT even easier to work with, a new Energy Monitoring Blueprint, Annual Billing for Self-Service, AI-Generated Snapshot Summaries, and new subflow version control to provide low-code development of custom nodes." description: "FlowFuse 2.21 introduces AI-assisted SQL, low-code custom nodes, and remote instance performance insights for engineering teams." date: 2025-08-28 +lastUpdated: 2026-08-13 authors: ["greg-stoutenburg"] image: /blog/2025/08/images/release-2.21.png tags: @@ -16,6 +17,9 @@ It's been a very busy release and we have many great new features available on F +::product-update-note +:: + ## Assistant Functionality in Tables Nodes ![Gif showing FlowFuse Expert in Tables](./images/tables.gif) _FlowFuse Expert in Tables recognizes table schema and turns natural language prompts into SQL queries_ @@ -98,4 +102,4 @@ The quickest way to get started is with FlowFuse Cloud. ### Self-Hosted -Get FlowFuse running locally in under 30 minutes using [Docker](/docs/install/docker/) or [Kubernetes](/docs/install/kubernetes/). \ No newline at end of file +Get FlowFuse running locally in under 30 minutes using [Docker](/docs/install/docker/) or [Kubernetes](/docs/install/kubernetes/). diff --git a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md index 79a20ed4e5..d4d4413794 100644 --- a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md +++ b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md @@ -2,7 +2,7 @@ title: "How to Connect Any PLC to MQTT in Under an Hour" subtitle: "Connect any PLC to MQTT without the typical complexity, costs, and expertise requirements" description: "Learn how to extract data from Siemens, Allen-Bradley, Omron, Mitsubishi, and Modbus, then publish it to MQTT using FlowFuse." -lastUpdated: 2026-06-17 +lastUpdated: 2026-08-13 date: 2025-10-27 keywords: MQTT, PLC, Siemens, S7, Allen-Bradley, EtherNet/IP, Omron, FINS, Mitsubishi, MC Protocol, Modbus, Modbus-RTU, Modbus-TCP, OPC-UA, FlowFuse, Node-RED, Industrial IoT, IIoT authors: ["sumit-shinde"] @@ -69,6 +69,9 @@ Getting PLC data into systems where it can be monitored, analyzed, and acted upo +::product-update-note +:: + The protocol itself is simple. But implementation in a real factory, with actual PLCs and production networks, is where things fall apart. Costs pile up, timelines drag on, and you end up needing expertise that's hard to find. This guide cuts through that complexity. You'll learn how to connect PLCs using MQTT without the typical headaches. We'll walk through extracting data from any PLC protocol, transforming it properly, and publishing it reliably, with working examples you can adapt to your own setup. @@ -108,7 +111,7 @@ As mentioned earlier, extracting data is the first and most complex step. Get th This is not just theory, Fortune 500 manufacturers are already running production systems on FlowFuse. Their consistent feedback? Massive cost savings compared to legacy systems, especially when deployed across multiple facilities. The enterprise features of FlowFuse handle the scale and security requirements large operations demand. -The Node-RED ecosystem that powers FlowFuse offers comprehensive protocol support. You'll find nodes available for every major PLC manufacturer, including: +The Node-RED ecosystem that powers FlowFuse offers comprehensive tocol support. You'll find nodes available for every major PLC manufacturer, including: - `node-red-contrib-modbus` – Modbus RTU/TCP PLCs and devices - `node-red-contrib-s7` – Siemens S7-300/400/1200/1500 diff --git a/src/blog/2025/11/flowfuse-release-2-24.md b/src/blog/2025/11/flowfuse-release-2-24.md index d04ccc05c5..70f16ee8e0 100644 --- a/src/blog/2025/11/flowfuse-release-2-24.md +++ b/src/blog/2025/11/flowfuse-release-2-24.md @@ -3,6 +3,7 @@ title: "FlowFuse 2.24: FlowFuse Expert in the Node-RED Editor, Scheduled Updates subtitle: "FlowFuse 2.24: FlowFuse Expert in the Node-RED Editor, Scheduled Updates, Simpler Edge Device Addition, Store and Forward Blueprint, and what's next!" description: "FlowFuse 2.24: FlowFuse Expert in the Node-RED Editor, Scheduled Updates, Simpler Edge Device Addition, Store and Forward Blueprint, and what's next!" date: 2025-11-20 +lastUpdated: 2026-08-13 authors: ["greg-stoutenburg"] image: /blog/2025/11/images/2.24-release.png video: cYwa08W-2eI @@ -17,6 +18,9 @@ This release unlocks several new abilities for our users, speeding your developm +::product-update-note +:: + ## FlowFuse Expert ![Image of FlowFuse Expert UI](./images/ff-expert-ui.png) _[FlowFuse Expert UI]_ diff --git a/src/blog/2026/02/mqtt-influxdb-tutorial.md b/src/blog/2026/02/mqtt-influxdb-tutorial.md index a0d93a986e..349ae71a9f 100644 --- a/src/blog/2026/02/mqtt-influxdb-tutorial.md +++ b/src/blog/2026/02/mqtt-influxdb-tutorial.md @@ -2,7 +2,7 @@ title: "How to Build an MQTT-to-InfluxDB Data Pipeline (2026)" subtitle: "From MQTT broker to InfluxDB bucket, the right way." description: "Learn how to build a reliable MQTT-to-InfluxDB data pipeline using FlowFuse and Node-RED, with no custom scripts required." -lastUpdated: 2026-06-19 +lastUpdated: 2026-08-13 date: 2026-02-26 keywords: MQTT, InfluxDB, IIoT, FlowFuse, Node-RED, Sensor telemetry, Time-series database authors: ["sumit-shinde"] @@ -59,6 +59,9 @@ An MQTT to InfluxDB is one of the most common and most critical pipelines in IIo +::product-update-note +:: + The typical approach is a custom Python script that subscribes to the broker, parses the payload, and writes to InfluxDB. It works until a sensor changes its payload format, or the script quietly dies over a weekend and nobody notices until Monday. Now you're debugging a process nobody else fully understands, with no visibility into what failed or when. Others stitch together multiple tools, each with its own config, its own failure modes, and its own logs to dig through at 2am. The complexity ends up hidden in places that are hard to see, hard to debug, and hard to hand off. This article takes a different approach. Using FlowFuse (the enterprise platform built on [Node-RED](/)), you'll build the entire pipeline as a visual flow covering MQTT subscription, payload transformation, and InfluxDB write. Every step is visible, editable, and easy to hand off. diff --git a/src/changelog/2023/09/introduction-enterprise-tier.md b/src/changelog/2023/09/introduction-enterprise-tier.md index ee9abcc6b2..1a0a3e3026 100644 --- a/src/changelog/2023/09/introduction-enterprise-tier.md +++ b/src/changelog/2023/09/introduction-enterprise-tier.md @@ -2,11 +2,15 @@ title: Introducing the Enterprise Tier description: Introducing FlowFuse's new Enterprise Tier. Upgrade via Team Settings for Cloud customers or by license for self-hosted. Find features and pricing details on our website. date: 2023-09-28 12:00:00.1 +lastUpdated: 2026-08-13 authors: ["marian-demme"] tags: - changelog --- +::product-update-note +:: + We are excited to officially announce the implementation and introduction of our new Enterprise Tier. Starting today, all FlowFuse Cloud customers have the option to upgrade their tier directly through **Team Settings** -> **Danger** -> **Change Team Type**. For those who self-host FlowFuse, the differentiation between the Enterprise and Teams Tiers is now available as well, via license type. -Comprehensive details about the features included in each tier can be found on our [pricing page](/pricing/). \ No newline at end of file +Comprehensive details about the features included in each tier can be found on our [pricing page](/pricing/). diff --git a/src/changelog/2023/10/certified-nodes.md b/src/changelog/2023/10/certified-nodes.md index b3526a7361..5c154d1053 100644 --- a/src/changelog/2023/10/certified-nodes.md +++ b/src/changelog/2023/10/certified-nodes.md @@ -2,11 +2,15 @@ title: Certified Nodes description: "FlowFuse now offers certified nodes: tested with proactive security measures to ensure system integrity and reliability, enhancing workflow efficiency and security." date: 2023-10-26 12:00:00.0 +lastUpdated: 2026-08-13 authors: ["marian-demme"] tags: - changelog --- +::product-update-note +:: + Teams Tier customers can now leverage a curated selection of certfied Node-RED nodes, enhancing workflow efficiency and security. - Quality Assurance: Each certified node undergoes testing, ensuring it's free from harmful components, aligning with our commitment to reliability. - Proactive Security Measures: While prioritizing immediate resolutions for detected vulnerabilities, we maintain the discretion to revoke a node's certified status, ensuring system integrity. Affected customers will receive prompt notifications. @@ -15,4 +19,4 @@ Teams Tier customers can now leverage a curated selection of certfied Node-RED n How? You can find all certified nodes in your Node-RED palette manager or on the [dedicated page](/integrations/?certified=1) on our website. -![Certified Nodes Screenshot](./images/certified-nodes.png) \ No newline at end of file +![Certified Nodes Screenshot](./images/certified-nodes.png) diff --git a/src/changelog/2023/11/devices-in-pipelines.md b/src/changelog/2023/11/devices-in-pipelines.md index 8cf97ab19e..0c1e26b10e 100644 --- a/src/changelog/2023/11/devices-in-pipelines.md +++ b/src/changelog/2023/11/devices-in-pipelines.md @@ -2,12 +2,17 @@ title: Devices in DevOps Pipelines description: "FlowFuse's latest update: Devices can now integrate into DevOps Pipelines, enhancing management flexibility and efficiency" date: 2023-11-23 12:00:00.0 +lastUpdated: 2026-08-13 authors: ["marian-demme"] tags: - changelog --- + +::product-update-note +:: + Building on our [previous release](/blog/2023/08/flowfuse-1-11-release/#usability-improvements-to-device-management-%232294) that enabled the management of devices independently of instances. Now, the integration of individual devices into DevOps Pipelines is possible. This update marks a significant step towards more flexible and efficient device management within FlowFuse. In our ongoing efforts, we are also developing features to group devices, aiming to streamline and improve the overall device management experience. ![Devices in DevOps Pipelines](./images/devices-in-pipelines.png) -Devices in DevOps Pipelines are available for every customer who has access to DevOps Pipelines. This includes all Cloud customers and those from the Pro Tier onwards for our self-hosted version. \ No newline at end of file +Devices in DevOps Pipelines are available for every customer who has access to DevOps Pipelines. This includes all Cloud customers and those from the Pro Tier onwards for our self-hosted version. diff --git a/src/changelog/2023/12/email-alerting-node-red-crash.md b/src/changelog/2023/12/email-alerting-node-red-crash.md index 64050c78ce..418fb1eb07 100644 --- a/src/changelog/2023/12/email-alerting-node-red-crash.md +++ b/src/changelog/2023/12/email-alerting-node-red-crash.md @@ -2,11 +2,15 @@ title: Email Alerts for Audit Log Events description: "FlowFuse update: Now receive email alerts for Audit Log events, ensuring timely notifications for Node-RED instance crashes." date: 2023-12-21 12:00:00.0 +lastUpdated: 2026-08-13 authors: ["marian-demme"] tags: - changelog --- +::product-update-note +:: + The newly introduced feature offers email notifications tied to particular Audit log events, available to all users with Pro Tier access or higher. This feature is designed to facilitate immediate notification and action in response to Node-RED Instance crashes. For detailed information and guidance on this functionality, please refer to our [documentation](/docs/user/instance-settings/#alerts). ![](./images/alerts.png) diff --git a/src/changelog/2024/02/device-pricing-change.md b/src/changelog/2024/02/device-pricing-change.md index 0584db761f..a2fc8d34ca 100644 --- a/src/changelog/2024/02/device-pricing-change.md +++ b/src/changelog/2024/02/device-pricing-change.md @@ -2,11 +2,15 @@ title: Pricing change for Devices description: "FlowFuse Cloud introduces a simplified pricing structure: Devices are now priced at $25 each for Teams Tier and $50 each for Enterprise Tier." date: 2024-02-09 13:00:00.0 +lastUpdated: 2026-08-13 authors: ["marian-demme"] tags: - changelog --- +::product-update-note +:: + Starting today, we have introduced a simplification of the pricing structure for devices on FlowFuse Cloud, effective immediately. All information is available on our [pricing page](/pricing/). The new pricing scheme is as follows: - Starter Tier: No change @@ -18,4 +22,4 @@ We are also pleased to offer volume discounts. For more details, please [contact ## Important Note for Existing Teams If a team currently in either tier already has devices (or has had devices in the past), any additions or removals of devices will be billed according to the previous pricing structure. -For teams without any prior device history, the addition of devices will be billed at the new rates. \ No newline at end of file +For teams without any prior device history, the addition of devices will be billed at the new rates. diff --git a/src/changelog/2024/04/pricing-change.md b/src/changelog/2024/04/pricing-change.md index 09a62c1a91..a5bdee0de5 100644 --- a/src/changelog/2024/04/pricing-change.md +++ b/src/changelog/2024/04/pricing-change.md @@ -2,11 +2,15 @@ title: Pricing change Enterprise & Teams Tier description: FlowFuse Cloud updates pricing for Enterprise and Teams tiers, effective immediately, with options tailored to varying instance needs. date: 2024-04-03 13:00:00.0 +lastUpdated: 2026-08-13 authors: ["marian-demme"] tags: - changelog --- +::product-update-note +:: + We're updating our pricing model for the Enterprise and Teams tiers on FlowFuse Cloud, with changes taking effect immediately. All information is available on our [pricing page](/pricing/). The new pricing scheme is as follows: @@ -18,4 +22,4 @@ We are also pleased to offer volume discounts. For more details, please [contact ## Important Note for Existing Teams -Teams that are currently subscribed to any tier and are using Instances will continue to be billed according to the previous pricing structure. Customers who have separate contracts with us will not be affected by these changes. \ No newline at end of file +Teams that are currently subscribed to any tier and are using Instances will continue to be billed according to the previous pricing structure. Customers who have separate contracts with us will not be affected by these changes. diff --git a/src/changelog/2025/01/free-tier-onboarding.md b/src/changelog/2025/01/free-tier-onboarding.md index 77204dd0aa..66e4f40632 100644 --- a/src/changelog/2025/01/free-tier-onboarding.md +++ b/src/changelog/2025/01/free-tier-onboarding.md @@ -2,14 +2,18 @@ title: New Onboarding Tour for Free Tier Users description: For new, free-tier users on FlowFuse Cloud, we have a new onboarding tour to help you get started date: 2025-01-07 14:00:00.0 +lastUpdated: 2026-08-13 authors: ["joe-pavitt"] tags: - changelog --- +::product-update-note +:: + ![Screenshot from the new onboarding tour for "Free" tier FlowFuse Cloud users](./images/free-tier-onboarding.png){data-zoomable} _Screenshot from the new onboarding tour for "Free" tier FlowFuse Cloud users_ Following from our new "Free" tier on FlowFuse Cloud, we've also published a new onboarding tour to help users get started with their new team. -This tour will guide you through the process of setting up your first Remote Instance, and show you how to access your Node-RED instance through FlowFuse Cloud, using the remote access tools. \ No newline at end of file +This tour will guide you through the process of setting up your first Remote Instance, and show you how to access your Node-RED instance through FlowFuse Cloud, using the remote access tools. diff --git a/src/changelog/2025/03/free-tier.md b/src/changelog/2025/03/free-tier.md index db93d8a56e..51d7548593 100644 --- a/src/changelog/2025/03/free-tier.md +++ b/src/changelog/2025/03/free-tier.md @@ -2,15 +2,19 @@ title: Free Tier now more accessible to all description: Signing up to our Free Tier no longer requires a credit card date: 2025-03-06 12:00:00.0 +lastUpdated: 2026-08-13 authors: ['nick-oleary'] tags: - changelog --- +::product-update-note +:: + We introduced the Free tier on FlowFuse Cloud [back in December](/blog/2024/12/flowfuse-release-2-12/). This allows you to manage two remote instances using the FlowFuse Device Agent completely free of charge. Since its launch we had many users sign-up and start connecting their remote instances to the platform. We've also had feedback on the fact it required you to enter credit card details to get fully set up. We're please to announce that, as of today, you no longer need a credit card to sign-up to our Free tier - you can jump straight into getting your remote instances connected. -Check out the [original announcement blog post](/blog/2024/12/flowfuse-release-2-12/) on how to get started with the Free tier. \ No newline at end of file +Check out the [original announcement blog post](/blog/2024/12/flowfuse-release-2-12/) on how to get started with the Free tier. diff --git a/src/changelog/2025/07/team-to-pro-plan-rename.md b/src/changelog/2025/07/team-to-pro-plan-rename.md index a8e8a80f1c..df8e9168bb 100644 --- a/src/changelog/2025/07/team-to-pro-plan-rename.md +++ b/src/changelog/2025/07/team-to-pro-plan-rename.md @@ -2,11 +2,15 @@ title: "Team Plan Renamed to Pro Plan" description: "The Team tier has been renamed to Pro tier to better reflect the plan's capabilities and target audience" date: 2025-08-04 12:00:00.0 +lastUpdated: 2026-08-13 authors: ["greg-stoutenburg"] tags: - changelog --- +::product-update-note +:: + We've renamed our Team tier to Pro tier to better reflect what it's truly designed for: using Node-RED professionally to build applications, replace and augment software in your organization, and scale professional Node-RED deployments. The Pro plan empowers developers and engineers to move beyond collaboration and into production-ready industrial applications that optimize operations and drive real business value. @@ -17,4 +21,4 @@ What's new: - A name that better represents professional Node-RED application development - Clearer positioning for organizations ready to scale their Node-RED implementations -Ready to build professional Node-RED applications? [Get started with Pro]({% include "sign-up-url.njk" %}) or [contact us](/contact-us) to learn more. \ No newline at end of file +Ready to build professional Node-RED applications? [Get started with Pro]({% include "sign-up-url.njk" %}) or [contact us](/contact-us) to learn more. diff --git a/src/changelog/2025/12/scheduled-maintenance.md b/src/changelog/2025/12/scheduled-maintenance.md index 25938aed9c..fc47ffa9fc 100644 --- a/src/changelog/2025/12/scheduled-maintenance.md +++ b/src/changelog/2025/12/scheduled-maintenance.md @@ -2,6 +2,7 @@ title: Scheduled Maintenance Mode description: Schedule time and day of the week to apply Node-RED updates date: 2025-12-19 12:00:00.0 +lastUpdated: 2026-08-13 authors: ['ben-hardill'] tags: - changelog @@ -9,6 +10,9 @@ issues: - "https://github.com/FlowFuse/flowfuse/issues/5554" --- +::product-update-note +:: + Included in the FlowFuse 2.25.0 release is the ability to schedule times and days of the week for Hosted Node-RED instances to upgrade to the latest available version. @@ -28,4 +32,4 @@ FlowFuse Cloud Starter Tier users will have this enabled by default and it will at weekends. ![TeamType Scheduled Maintenance Settings](./images/scheduled-maintenance-admin.png) -_TeamType Scheduled Maintenance Settings_ \ No newline at end of file +_TeamType Scheduled Maintenance Settings_ diff --git a/src/changelog/2026/03/march-scheduled-maintenance.md b/src/changelog/2026/03/march-scheduled-maintenance.md index f19284876b..7291ca08d1 100644 --- a/src/changelog/2026/03/march-scheduled-maintenance.md +++ b/src/changelog/2026/03/march-scheduled-maintenance.md @@ -2,11 +2,15 @@ title: "Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026" description: Keeping the FlowFuse Cloud up to date with critical server maintenance. date: 2026-03-12 12:00:00.0 +lastUpdated: 2026-08-13 authors: ['nick-oleary'] tags: - changelog --- +::product-update-note +:: + As part of our ongoing efforts to maintain our infrastructure, we need to update some of our servers that host Node-RED instances. This will require restarting any hosted Node-RED instances running on those servers, leading to a short downtime whilst they restart. Remote instances on the edge are unaffected. diff --git a/src/changelog/2026/06/july-scheduled-maintenance.md b/src/changelog/2026/06/july-scheduled-maintenance.md index 0b9dbada20..a7a6c67194 100644 --- a/src/changelog/2026/06/july-scheduled-maintenance.md +++ b/src/changelog/2026/06/july-scheduled-maintenance.md @@ -2,11 +2,15 @@ title: "Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026" description: Keeping the FlowFuse Cloud up to date with critical server maintenance. date: 2026-06-15 12:00:00.0 +lastUpdated: 2026-08-13 authors: ['nick-oleary'] tags: - changelog --- +::product-update-note +:: + As part of our ongoing efforts to maintain our infrastructure, we need to update some of our servers that host Node-RED instances. This will require restarting any hosted Node-RED instances running on those servers, leading to a short downtime whilst they restart. Remote instances on the edge are unaffected. diff --git a/src/node-red/hardware/armxy-bl340.md b/src/node-red/hardware/armxy-bl340.md index b09c35fce7..540c7b3739 100644 --- a/src/node-red/hardware/armxy-bl340.md +++ b/src/node-red/hardware/armxy-bl340.md @@ -25,6 +25,10 @@ The BLIIOT ARMxy BL340 is a high-performance single-board computer designed for Integrating this powerful hardware with FlowFuse not only enhances its capabilities but also simplifies the management and deployment process. +{% note %} +Exciting Update! FlowFuse is now available as three different products: [FlowFuse Edge for OT teams](/product/edge/), [FlowFuse Hub for IT teams](/product/hub/), and [FlowFuse Fleet](/product/fleet/) for managing devices at scale. Visit the [FlowFuse Product Page](/product/) to learn how the platform enables you to build and manage industrial apps at scale. +{% endnote %} + ## Prerequisites Before proceeding with the installation, ensure you have the following: