Changelog

We have supported the ability to configure your Node-RED instances with custom node catalogues for some time now. This feature allows you to access alternative NPM registries to use nodes that have not been made publicly available.

We have now extended this to work with your Node-RED devices, giving them the same ability to access private node catalogues, and deploy them across your fleet of devices.

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.

The new pricing scheme is as follows:

• Starter Tier: Remains unchanged
• Teams Tier: Availability limited to Small $25 and Medium $50 Instances
• Enterprise Tier: Availability limited to Medium $50 and Large $250 Instances

We are also pleased to offer volume discounts. For more details, please contact us.

#  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.

With our latest release of Node-RED Dashboard 2.0, we've made some big improvements to the onboarding experience.

We're seeing over 2,000 people download Dashboard 2.0 per week, and are seeing a great buzz in the community of brand new Node-RED users, experienced Node-RED users that haven't explored a UI solution previously and existing users migrating from Dashboard 1.0.

So, with that in mind, we wanted to offer a new "Getting Started" guide that will help you get up and running with building custom user interfaces and data visualizations in Node-RED.

We've introduced new configuration options to enhance the control of your HTTP requests and debugging process. These updates allow you to configure limits on the sizes of incoming HTTP messages and how many characters of a message are included in debug messages in the editor sidebar.

This feature is available to all our Teams and Enterprise Tier customers. You can access these new configuration options in the Instance Settings under the "Editor" menu.

We're excited to announce the introduction of the Instance Protection Mode, an enhancement in our efforts to provide a secure and controlled environment for managing production instances on FlowFuse. This feature empowers Team Owners with the exclusive ability to restrict modifications to production instances, ensuring that any changes are made with careful oversight and authorization.

A key aspect of Instance Protection Mode is the exclusive control it grants Owners over the execution of DevOps pipelines targeting protected instances. This means: Only Owners can initiate and execute pipelines.

The Instance Protection option can be found under the Instance settings view for all our Teams and Enterprise Tier customers.

Bearer Token Authentication for Node-RED Instances, allows FlowFuse users to securely access their Node-RED HTTP endpoints, ensuring enhanced security and ease of implementation. Now, you can confidently manage your HTTP endpoints with the assurance that your connections are protected using FlowFuse's robust authentication mechanism.

$ curl -H "Authorization: Bearer ffhttp_FKc_S4qlTBV1H411hmhneHcSJ6F_FGNQLPYbnoD3-B0" https://healthy-rook-4329.flowforge.cloud/test
HelloWorld
$

This feature is available for our Teams and Enterprise Tier customers. You can find the configuration under the Security tab in your instance settings.

The latest version of the FlowFuse device agent now supports remotely restarting your Node-RED flows from the FlowFuse platform. This brings it more inline with what the platform lets you do with your hosted Node-RED instances.

This removes the need to manually connect to your device to restart Node-RED, streamlining your workflow and offering a more seamless and efficient user experience.

We have added quick access buttons to help you navigate to your Dashboard 2.0 UI in a single click.

Dashboard button is displayed alongside the Open Editor button when an instance has @flowfuse/node-red-dashboard installed.

Click the link to learn more about Flowfuse Dashboard 2.0

Two weeks ago, we introduced auto snapshots for devices to help ensure you can always rollback to a previous version of your Node-RED flows. We're extended that ability to the hosted Node-RED instances as well.

Whenever you deploy a change to the flows, a snapshot will be taken automatically. We'll keep the last 10 auto-generated snapshots on a first-in, first-out basis. Older auto-generated snapshots will be automatically cleaned up for you - unless they are marked as a target snapshot for your devices.

Click the following links to learn more about instances and snapshots.

Included in the v2.1.0 release the Helm Chart now uses 14.10.0-debian-11-r30 tag of the Bitnami PostgreSQL container.

This container tag includes images for both AMD64 and ARM64 allowing FlowFuse to be deployed to now fully ARM64 based Kubernetes clusters when using local PostgreSQL database.

FlowFuse V2.1 introduces Auto Snapshots for your Application Assigned Devices.

When you deploy a change to the device flows, a snapshot will be taken automatically.

The last 10 Auto Snapshots will be kept on a first in first out basis. Older Auto Snapshots will be automatically cleaned up for you.

Click the following links to learn more about devices and snapshots.

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. The new pricing scheme is as follows:

• Starter Tier: No change
• Teams Tier: Devices are now priced at $25 each.
• Enterprise Tier: Devices are priced at $50 each.

We are also pleased to offer volume discounts. For more details, please contact us.

#  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.

With the recent introduction of the Device audit log, we've now updated the Device Agent to start logging events from the Node-RED instance running on your device.

This brings closer parity with the logging you get from a hosted instance.

The audit log events include details of the flows being updated, nodes being added or removed from the palette and other changes to the configuration.

Update to Device Agent v2.2 to start receiving the events.

Hot on the heals of our recent onboarding improvements and streamlining, we have now introduced a new, simpler and faster way of getting your devices configured and connected to the FlowFuse platform.

Now, when you create a device on the platform, you will be offered a simple "Setup command". Run this command in a terminal and the let the Device Agent do all the hard work for you.

To learn more about this, head to the FlowFuse Device Agent documentation.

This week has seen the release of the first major version of Node-RED Dashboard 2.0, with it, we've made available a new FlowFuse-exclusive feature, personalised multi-user dashboards.

This new feature will allow you to build applications that provide unique data to each user, build admin-only views, and track user activity, to name but a few. We're really excited to see what the Node-RED Community and our FlowFuse customers can do with such a powerful and flexible framework.

Back in June 2023 we announced that FlowFuse would be investing into building out the next generation of Node-RED Dashboard, the most popular UI framework for Node-RED.

We followed this up with the first release (0.0.1) in July, just one month later, and today, we are pleased to announce that we have reached a major milestone in this journey, with the release of our first major version (1.0.0) of Node-RED Dashboard 2.0.

To start editing flows on a device, it needs to be assigned to an application in your team. Up until now this has been a two step process; creating the device and then assigning it. This wasn't as intuitive as it needed to be.

To help streamline the user experience, you can now assign a device to an application when you create it. It's a small update, but it helps users get to where they want to be much quicker.

We have added some new blueprints to FlowFuse Cloud to help users get started with a range of common manufacturing scenarios.

They are available to all users on FlowFuse Cloud. Additionally, upon request, all our Teams and Enterprise Self-Hosted customers gain access to this collection.

List of new Blueprints:

• Andon Live
• CRUD for Mongo DB
• 5S Manufacturing checklist
• Performance Operator Terminal

Curious about what Blueprints are? Read our recent blog post that introduced Blueprints to FlowFuse.

For an overview of all available Blueprints check out our Blueprint Library.

The v2.0 release of the FlowFuse Helm Chart includes a breaking change for deployments making use of the forge.localPostgresql setting when upgrading. This is where the helm chart installs a dedicated PostgreSQL database instance.

With v2.0 we have updated the version of the Bitnami PostgreSQL Helm sub-chart we bundle and the upgrade process will require some manual intervention to ensure things work correctly. A fresh install should not require any extra steps.

The steps are documented on the Upgrade instructions page, please read them carefully before upgrading

Also included in this release is the ability to set resource constraints and Pod Security Context on the FlowFuse application, File-Server Application and MQTT broker containers if required. Details of how to set those can be found in the Helm Chart README.md