[{"data":1,"prerenderedAt":9467},["ShallowReactive",2],{"changelog-all":3},[4,72,139,206,280,610,684,868,948,1018,1091,1134,1177,1225,1288,1335,1372,1417,1470,1525,1586,1631,1688,1755,1795,2012,2040,2092,2152,2207,2241,2310,2357,2417,2461,2563,2613,2693,2725,2775,2809,2848,2872,2976,3011,3157,3256,3300,3608,3687,3728,3771,3835,3884,3942,3977,4015,4048,4094,4133,4184,4222,4267,4335,4386,4495,4565,4625,4745,4838,4872,4933,4967,5011,5069,5102,5219,5309,5359,5395,5438,5485,5543,5592,5623,5651,5677,5715,5741,5768,5817,5851,5881,5927,5978,6025,6064,6135,6169,6198,6229,6271,6292,6333,6372,6404,6435,6472,6508,6549,6588,6656,6685,6719,6765,6885,6924,6970,7001,7031,7076,7170,7201,7234,7264,7363,7410,7460,7494,7530,7574,7631,7664,7738,7779,7824,7852,7906,7931,7958,7995,8033,8071,8125,8154,8228,8253,8280,8320,8356,8401,8427,8473,8508,8549,8577,8644,8686,8714,8757,8815,8852,8886,8920,8946,8973,9009,9036,9070,9095,9128,9161,9206,9231,9261,9296,9321,9350,9375,9411,9434],{"id":5,"title":6,"authors":7,"body":9,"date":57,"description":58,"extension":59,"issues":60,"meta":62,"navigation":65,"path":66,"seo":67,"sitemap":68,"stem":69,"subtitle":70,"__hash__":71},"changelog\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding.md","Getting started with FlowFuse straight from the terminal",[8],"nick-oleary",{"type":10,"value":11,"toc":54},"minimark",[12,16,19,22,33,46],[13,14,15],"p",{},"FlowFuse Device Agent allows you to remotely manage Node-RED instances running on your hardware, for example, devices on your factory floor.",[13,17,18],{},"Getting your own hardware into FlowFuse meant working backwards. You signed up, found the remote instance section, learned what the Device Agent was, created the instance in the platform, copied its connection details, and only then ran the installer with that code in hand.",[13,20,21],{},"Now you can start where the hardware already is. Run the installer from your terminal and it walks you through registering — including setting up an account if you need one — ending with your machine registered as a remote instance and ready to build on. If something's in the way — like port 1880 already being in use — the installer tells you up front instead of failing partway through.",[13,23,24,25,32],{},"Check the ",[26,27,31],"a",{"href":28,"rel":29},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Fquickstart\u002F",[30],"nofollow","Device Agent Quick Start guide"," to get connected.",[13,34,35,42],{},[36,37],"img",{"alt":38,"dataZoomable":39,"src":40,"style":41},"The installer running in a terminal, walking through sign-up and connection to FlowFuse","","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fdevice-agent-install.gif","border: 2px solid #E5E7EB;",[43,44,45],"em",{},"Sign-up and registration happen in one uninterrupted flow — no jumping back to the platform.",[13,47,48,52],{},[36,49],{"alt":50,"dataZoomable":39,"src":51,"style":41},"The interactive registration takes you straight through to the Node-RED editor once connected","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fdevice-agent-registration.png",[43,53,50],{},{"title":39,"searchDepth":55,"depth":55,"links":56},4,[],"2026-07-30","Onboard a remote instance directly from your terminal with a new interactive setup","md",[61],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Fissues\u002F678",{"tags":63},[64],"changelog",true,"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding",{"title":6,"description":58},{"loc":66},"changelog\u002F2026\u002F07\u002Fdevice-agent-onboarding",null,"O2b8S8itC249DaAH2k624XwmRnP4G4UVFZIPzAg1SI0",{"id":73,"title":74,"authors":75,"body":77,"date":128,"description":129,"extension":59,"issues":130,"meta":132,"navigation":65,"path":134,"seo":135,"sitemap":136,"stem":137,"subtitle":70,"__hash__":138},"changelog\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation.md","FlowFuse Expert Can Now Work With Your Tables",[76],"andrea-palmieri",{"type":10,"value":78,"toc":126},[79,82,90,99,110,123],[13,80,81],{},"FlowFuse Expert can now look up your FlowFuse Tables databases directly. Ask it to list the databases on your team, show you the tables in a database, or describe a table's schema, and it calls the right tools and reports back, without you needing to open the Tables view yourself. It can also preview a table's data: up to 10 rows, exactly as stored.",[13,83,84,85,89],{},"This is a fixed, read-only preview, not a query engine: there's no filtering, sorting, or paging through it, and no writes. For anything beyond that quick look, the Expert can help you build it as a flow with the ",[86,87,88],"code",{},"tables-query"," node instead.",[13,91,92,96],{},[36,93],{"alt":94,"dataZoomable":39,"src":95},"The Expert listing the tables in a FlowFuse Tables database, grouped by schema","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fchat.png",[43,97,98],{},"The Expert listing a database's tables, grouped by schema",[13,100,101,102,105,106,109],{},"Alongside this, FlowFuse Tables now correctly supports tables that live in a schema other than ",[86,103,104],{},"public",". Previously, viewing data for a table outside the default schema could fail. Tables and their schema now show up correctly throughout the Tables UI: next to each table name in the list, and as ",[86,107,108],{},"schema_name.table_name"," (with a copy button) in the table detail view.",[13,111,112,116],{},[36,113],{"alt":114,"dataZoomable":39,"src":115},"The Tables explorer showing each table's schema next to its name, and the qualified schema.table name with a copy button in the header","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Ftables-view.png",[43,117,118,119,122],{},"The schema label beside each table name, and the qualified ",[86,120,121],{},"schema.table"," name with a copy button in the header",[13,124,125],{},"This feature is available to FlowFuse Hub and FlowFuse Edge customers on Cloud and Self Hosted from v2.33",{"title":39,"searchDepth":55,"depth":55,"links":127},[],"2026-07-28","The Expert can now list your FlowFuse Tables databases, inspect table schemas, and preview a sample of a table's rows on your behalf, and Tables now works correctly with schemas other than public.",[131],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7989",{"tags":133},[64],"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation",{"title":74,"description":129},{"loc":134},"changelog\u002F2026\u002F07\u002Fexpert-tables-automation","Cb4qhm3EjSp7AF9wlMBln0yMWtOiUVe7AmduedFo7a4",{"id":140,"title":141,"authors":142,"body":144,"date":195,"description":196,"extension":59,"issues":197,"meta":199,"navigation":65,"path":201,"seo":202,"sitemap":203,"stem":204,"subtitle":70,"__hash__":205},"changelog\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards.md","A Dedicated Home for Your Dashboards",[143],"noley-holland",{"type":10,"value":145,"toc":191},[146,157,160,169,174,177,186],[13,147,148,149,153,154,156],{},"Your dashboards now have a home. A new ",[150,151,152],"strong",{},"Dashboards"," entry in the team navigation lists every dashboard across your hosted instances in one place. Open one and it loads right inside FlowFuse, not in a separate browser tab. Each application also has its own ",[150,155,152],{}," tab, showing just the dashboards from that application's instances.",[13,158,159],{},"Until now, dashboards were tucked behind an \"Open Dashboard\" button on individual instance pages. Finding the one you wanted meant hunting through instances, and each one opened in a new tab. Now you get one place that shows them all, at the team or application level.",[13,161,162,166],{},[36,163],{"alt":164,"dataZoomable":39,"src":165},"The Dashboards view listing all dashboards across the team","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fteam-dashboards.png",[43,167,168],{},"Every dashboard in the team, each showing whether its instance is currently running",[170,171,173],"h2",{"id":172},"switch-between-dashboards-in-place","Switch between dashboards in place",[13,175,176],{},"A drawer lets you switch to any other dashboard in a single click, without returning to the list. Jump from your \"Line 3 OEE\" dashboard to \"Energy Monitoring\" and back without losing your place. Instance status updates live in the drawer, so you can see at a glance which dashboards are ready.",[13,178,179,183],{},[36,180],{"alt":181,"dataZoomable":39,"src":182},"An embedded dashboard with the drawer open to switch between dashboards","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fdashboard-drawer.png",[43,184,185],{},"The drawer stays open alongside the dashboard, so switching doesn't cover what you're viewing",[13,187,188],{},[43,189,190],{},"This feature is available to all users of FlowFuse Cloud and all Self Hosted users from v2.33.",{"title":39,"searchDepth":55,"depth":55,"links":192},[193],{"id":172,"depth":194,"text":173},2,"2026-07-22","Browse and open every dashboard across your team from a new Dashboards view, without leaving FlowFuse.",[198],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7665",{"tags":200},[64],"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards",{"title":141,"description":196},{"loc":201},"changelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","cJ_6FJG9x11-C52tpKQfl3bD7sCl4JAcJI72vUyRI3Q",{"id":207,"title":208,"authors":209,"body":211,"date":269,"description":270,"extension":59,"issues":271,"meta":273,"navigation":65,"path":275,"seo":276,"sitemap":277,"stem":278,"subtitle":70,"__hash__":279},"changelog\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups.md","Application Roles from SSO Groups",[210],"ben-hardill",{"type":10,"value":212,"toc":267},[213,216,219,228,250,264],[13,214,215],{},"Application level Role overrides can now be managed by SSO Group membership.",[13,217,218],{},"As well as Team wide Role membership additional groups can be used to apply Role overrides to specific Applications.",[13,220,221,222,227],{},"This works for both SAML and LDAP based SSO, the documentation outlining the required group naming can be found ",[26,223,226],{"href":224,"rel":225},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fadmin\u002Fsso",[30],"here",".",[13,229,230,231,234,235,238,239,242,243,246,247,249],{},"For example for a Team with the slug ",[86,232,233],{},"development"," and an application called ",[86,236,237],{},"test"," a user in the following groups would have ",[86,240,241],{},"member"," level access to the Team and ",[86,244,245],{},"owner"," level access to the ",[86,248,237],{}," Application.",[251,252,253,259],"ul",{},[254,255,256],"li",{},[86,257,258],{},"ff-development-member",[254,260,261],{},[86,262,263],{},"ff-development[test]-owner",[13,265,266],{},"This is available to FlowFuse Cloud Teams now and will be available to Self Hosted customers from version 2.33.0 onwards.",{"title":39,"searchDepth":55,"depth":55,"links":268},[],"2026-07-15","Control Application level Role overrides from SSO Groups",[272],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7396",{"tags":274},[64],"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups",{"title":208,"description":270},{"loc":275},"changelog\u002F2026\u002F07\u002Fapplication-sso-groups","Ai8qxgCGkacybac36MZJ1JbjFUhFFKEU4WIGJ4DncKo",{"id":281,"title":282,"authors":283,"body":286,"date":601,"description":602,"extension":59,"issues":70,"meta":603,"navigation":65,"path":605,"seo":606,"sitemap":607,"stem":608,"subtitle":70,"__hash__":609},"changelog\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements.md","FlowFuse Expert Enhancements",[284,285,76],"stephen-mclaughlin","serban-costin",{"type":10,"value":287,"toc":590},[288,292,295,306,314,322,331,335,338,355,358,362,365,368,377,381,384,389,392,398,424,427,436,440,443,446,457,467,476,480,483,486,506,509,518,530,539,573,582,585],[170,289,291],{"id":290},"insights","Insights",[13,293,294],{},"With the release of device-agent 4.0.0 and FlowFuse 2.32.0, FlowFuse Expert Insights Agent can now work with Remote Instances and Self Hosted Instances.",[296,297,298,303],"caution",{},[13,299,300],{},[150,301,302],{},"Important:",[13,304,305],{},"In order to achieve Insights on Remote Instances and Self Hosted Instances,  we had to modify how data is routed through the platform. Your old Hosted Instances on FlowFuse Cloud will require an update to the latest Launcher Version (2.23.0 or greater) to continue working.",[13,307,308,312],{},[36,309],{"alt":310,"dataZoomable":39,"src":311},"Resource from Hosted and Remote Instances can now be selected","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Finsights-1.png",[43,313,310],{},[13,315,316,320],{},[36,317],{"alt":318,"dataZoomable":39,"src":319},"Insights querying a Remote Instance","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Finsights-2.png",[43,321,318],{},[13,323,324,328],{},[36,325],{"alt":326,"dataZoomable":39,"src":327},"Insights in an action","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Finsights.gif",[43,329,330],{},"Insights in an action - querying a Remote Instance",[170,332,334],{"id":333},"platform-automations","Platform Automations",[13,336,337],{},"The Expert can now take action on your FlowFuse platform directly. Instead of telling you which buttons to click, it can create instances, register devices, take snapshots, and manage applications on your behalf. You can ask the Expert to:",[251,339,340,343,346,349,352],{},[254,341,342],{},"Create hosted instances with the right type, stack, and template, optionally starting from a flow blueprint",[254,344,345],{},"Register remote instances (devices) and assign them to applications",[254,347,348],{},"Take and list snapshots of both hosted and remote instances",[254,350,351],{},"Create applications, list what's running inside them, and check their audit logs",[254,353,354],{},"Look up live status and logs for any hosted instance, or query a remote instance's state over MQTT",[13,356,357],{},"Behind the scenes, FlowFuse exposes over 30 automation tools covering instances, devices, applications, snapshots, teams, and configuration. When you ask the Expert to do something, it picks the right tools, calls them with your permissions, and reports back.",[170,359,361],{"id":360},"better-formatted-replies","Better Formatted Replies",[13,363,364],{},"Expert replies now render markdown more fully in the chat panel. Tables, ordered lists, blockquotes, and checklists all display with proper formatting instead of falling back to plain text, making longer, more structured answers much easier to scan.",[13,366,367],{},"Tables come with a copy button that copies the contents as tab-separated values, ready to paste straight into a spreadsheet.",[13,369,370,374],{},[36,371],{"alt":372,"dataZoomable":39,"src":373},"An Expert reply showing a formatted table, ordered list, and checklist","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fmarkdown-rendering.png",[43,375,376],{},"A formatted reply with the tab-separated copy button in the table's top-right corner",[170,378,380],{"id":379},"support-agent","Support Agent",[13,382,383],{},"We have added three ways to stay in control of what the Expert does while it works alongside you in the editor.",[385,386,388],"h3",{"id":387},"plan-mode","Plan Mode",[13,390,391],{},"The Expert can now propose a plan before it changes anything, so you can review the approach before it touches your flows.",[13,393,394,395,397],{},"Turn on ",[150,396,388],{}," with the toggle in the chat composer. Instead of acting straight away, the Expert lays out what it intends to do as a plan you can read through. From there you can:",[251,399,400,406,412,418],{},[254,401,402,405],{},[150,403,404],{},"Approve",": the Expert proceeds with the plan.",[254,407,408,411],{},[150,409,410],{},"Edit",": open the plan in the composer, adjust the wording yourself, and send it back.",[254,413,414,417],{},[150,415,416],{},"Request changes",": describe what you would like to be different, and the Expert proposes an updated plan.",[254,419,420,423],{},[150,421,422],{},"Reject",": discard the plan and start again.",[13,425,426],{},"This is ideal for larger or unfamiliar changes, where you want to agree on the approach before any work happens.",[13,428,429,433],{},[36,430],{"alt":431,"dataZoomable":39,"src":432},"The Expert proposing a plan, with Approve, Edit, Request changes, and Reject actions","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fplan.png",[43,434,435],{},"The Expert proposes a plan and waits for your approval before making any changes",[385,437,439],{"id":438},"clarifying-questions","Clarifying Questions",[13,441,442],{},"The Expert now asks clarifying questions when a request could go more than one way, rather than guessing and building the wrong thing.",[13,444,445],{},"When it needs more detail, the Expert presents up to four questions in a single turn, each as a set of options you pick from, either single choice or multiple choice. You answer them all together, and it uses your answers to get the result right the first time. For example:",[251,447,448,451,454],{},[254,449,450],{},"Which flow should this run in?",[254,452,453],{},"Should the incoming payload be stored, forwarded, or both?",[254,455,456],{},"Which of these nodes should trigger the alert?",[13,458,459,460,463,464,227],{},"You can revisit and change your answers before continuing, and you decide the pace: use the follow-up questions setting in the composer menu to have the Expert ask everything ",[150,461,462],{},"all at once"," or ",[150,465,466],{},"one at a time",[13,468,469,473],{},[36,470],{"alt":471,"dataZoomable":39,"src":472},"The Expert asking grouped clarifying questions with single and multiple choice options","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fquestions.png",[43,474,475],{},"The Expert asks clarifying questions and collects your answers before acting",[385,477,479],{"id":478},"human-in-the-loop","Human in the Loop",[13,481,482],{},"You are now in charge of exactly which actions the Expert is allowed to take on your flows, so no change happens that you did not permit.",[13,484,485],{},"When the Expert wants to run an action that needs your sign-off, it pauses and shows an approval card in the chat. The card names the action, whether it reads, writes, or deletes, and the exact details of what it will do, with four choices:",[251,487,488,497],{},[254,489,490,463,493,496],{},[150,491,492],{},"Allow",[150,494,495],{},"Deny",": approve or refuse this one action.",[254,498,499,463,502,505],{},[150,500,501],{},"Always allow",[150,503,504],{},"Always deny",": apply your choice to every matching action.",[13,507,508],{},"The Expert waits for your decision however long you need, and you can cancel a pending action at any time with the stop button.",[13,510,511,515],{},[36,512],{"alt":513,"dataZoomable":39,"src":514},"An inline approval card showing the action, its type, and Allow, Always allow, Deny, and Always deny choices","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fapproval-card.png",[43,516,517],{},"The Expert pauses and asks for approval before running an action that needs your sign-off",[13,519,520,521,463,523,525,526,529],{},"An ",[150,522,501],{},[150,524,504],{}," you set from a card applies to the current chat only, and resets when you refresh or start over. If you want to keep it, click ",[150,527,528],{},"Make permanent"," to save that choice for future chats.",[13,531,532,536],{},[36,533],{"alt":534,"dataZoomable":39,"src":535},"Clicking Make permanent on a granted action to save it for future chats","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fmake-permanent.gif",[43,537,538],{},"Make a per-chat permission permanent so it carries over to future chats",[13,540,541,542,545,546,549,550,553,554,557,558,549,561,564,565,568,569,572],{},"You can also set your permissions ahead of time. Open ",[150,543,544],{},"Tool permissions"," in the Expert settings and choose a default for ",[150,547,548],{},"Read",", ",[150,551,552],{},"Write",", and ",[150,555,556],{},"Delete"," actions: ",[150,559,560],{},"always allow",[150,562,563],{},"ask",", or ",[150,566,567],{},"always deny",". Out of the box the Expert can read freely but asks before it writes or deletes anything. Flow building and platform actions each have their own defaults, and you can expand ",[150,570,571],{},"Individual tools"," to override the default for a specific action, which then stays put until you reset it. These settings are saved for you and persist across chats within the team you are working in; switching to another team starts from the defaults again.",[13,574,575,579],{},[36,576],{"alt":577,"dataZoomable":39,"src":578},"The Tool permissions panel in Expert settings, with default Read, Write, and Delete permissions for flow building and platform tools","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Ftools-permissions.png",[43,580,581],{},"Set default permissions per action type, and override individual tools where you need to",[583,584],"hr",{},[13,586,587],{},[43,588,589],{},"All of these new features are available to FlowFuse Cloud users and Self-Hosted users from v2.32.",{"title":39,"searchDepth":55,"depth":55,"links":591},[592,593,594,595],{"id":290,"depth":194,"text":291},{"id":333,"depth":194,"text":334},{"id":360,"depth":194,"text":361},{"id":379,"depth":194,"text":380,"children":596},[597,599,600],{"id":387,"depth":598,"text":388},3,{"id":438,"depth":598,"text":439},{"id":478,"depth":598,"text":479},"2026-07-02","FlowFuse Expert now supports Insights on your devices, Platform automations, Plan Mode, Human in the Loop and more...",{"tags":604},[64],"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements",{"title":282,"description":602},{"loc":605},"changelog\u002F2026\u002F07\u002Fexpert-enhancements","xAyhVzS9-iTHEPKGJdpA4yMFu6zcTml5E1qGtHl8hGc",{"id":611,"title":282,"authors":612,"body":613,"date":601,"description":602,"extension":59,"issues":675,"meta":677,"navigation":65,"path":679,"seo":680,"sitemap":681,"stem":682,"subtitle":70,"__hash__":683},"changelog\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats.md",[285],{"type":10,"value":614,"toc":669},[615,618,622,625,628,632,635,639,642,645,649,652,658,661],[13,616,617],{},"Personal Access Tokens now support fine-grained scoping. You can restrict a token to specific teams, limit it to read-only operations, or control whether it\ncarries admin privileges. This is especially useful when handing tokens to AI agents or MCP clients, where you want to limit what the token can reach.",[170,619,621],{"id":620},"team-scoping","Team scoping",[13,623,624],{},"You can now scope a token to one or more teams. A scoped token can only access resources within those teams. If you don't select any teams, the token works\nacross all teams you belong to, same as before.",[13,626,627],{},"When you're added to a new team, scoped tokens don't automatically pick it up. You need to explicitly add the new team to any token that should have access.",[170,629,631],{"id":630},"read-only-mode","Read-only mode",[13,633,634],{},"A new toggle lets you mark a token as read-only. When enabled, the token can only perform read operations across all resources it has access to. Any write\noperation will be rejected.",[170,636,638],{"id":637},"admin-opt-in","Admin opt-in",[13,640,641],{},"Tokens created by admin users no longer carry admin privileges by default. When you create a new token, it behaves as a regular user token, using your team\nroles instead of full admin access. If you need the token to have admin capabilities, you have to explicitly check the admin opt-in option.",[13,643,644],{},"Existing admin-owned tokens have been migrated with admin opt-in enabled, so they continue to work as before. Only newly created tokens default to\nnon-admin.",[170,646,648],{"id":647},"how-scoping-works","How scoping works",[13,650,651],{},"These options allow you to narrow the scope of a token's permissions; you cannot create a token with more access than your user has.",[13,653,654,655,227],{},"You can create and manage your tokens under ",[150,656,657],{},"User Settings > Security > Personal Access Tokens",[13,659,660],{},"This feature is available to FlowFuse Cloud users as of now and Self-Hosted users from v2.33.",[13,662,663,667],{},[36,664],{"alt":665,"dataZoomable":39,"src":666},"Creating a new scoped Personal Access Token","\u002Fchangelog\u002F2026\u002F07\u002Fimages\u002Fscoped-pats.png",[43,668,665],{},{"title":39,"searchDepth":55,"depth":55,"links":670},[671,672,673,674],{"id":620,"depth":194,"text":621},{"id":630,"depth":194,"text":631},{"id":637,"depth":194,"text":638},{"id":647,"depth":194,"text":648},[676],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7411",{"tags":678},[64],"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats",{"title":282,"description":602},{"loc":679},"changelog\u002F2026\u002F07\u002Fscoped-pats","SWS24JifltxnWHGl4jp189QGuolpRZWqNjTO-4o1UpI",{"id":685,"title":686,"authors":687,"body":688,"date":850,"description":851,"extension":59,"issues":852,"meta":854,"navigation":65,"path":862,"seo":863,"sitemap":864,"stem":865,"subtitle":866,"__hash__":867},"changelog\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released.md","Device Agent v4 released",[8],{"type":10,"value":689,"toc":842},[690,698,702,705,730,735,744,747,751,758,761,764,773,777,780,783,794,797,801,804,806,810,813,825,831,833],[13,691,692,693,697],{},"Device Agent v4 is a major release. It brings a modern Node.js runtime, structured logging for production observability, a new authentication method, and a more secure container deployment model. There are breaking changes - check the ",[26,694,696],{"href":695},"#upgrading-to-v4","upgrade notes"," before updating your remote instances.",[170,699,701],{"id":700},"nodejs-22-is-now-the-default-runtime","Node.js 22 is now the default runtime",[13,703,704],{},"The Device Agent installer and official Docker image now default to Node.js 22. Node.js 20 reached end-of-life in April 2026, and continuing to ship it as the default would leave devices running on an unsupported runtime without security patches. It is also the minimum version required by Node-RED v5.",[296,706,707,717,720,723,727],{},[13,708,709,712,713,716],{},[150,710,711],{},"Breaking change:"," The Device Agent Docker image tagged ",[86,714,715],{},"latest"," now uses a Node.js 22 base image. If you do not pin your container image to a specific version tag, review your deployment configuration before upgrading.\n{% endcaution %}",[13,718,719],{},"We also continue to build, and tag, containers for a range of Node.js versions - 18, 20, 22 and 24.",[13,721,722],{},"If you use the Device Agent installer, it will now default to Node.js 22. Existing installations using the installer will need to download the latest version and re-run the installer.",[170,724,726],{"id":725},"containers-now-run-as-an-unprivileged-user","Containers now run as an unprivileged user",[13,728,729],{},"The Device Agent Docker container no longer runs as the root user. Following best practices, processes inside the container now execute as an unprivileged user.",[13,731,732,734],{},[150,733,711],{}," If your container deployment mounts volumes or relies on file permissions set for the root user, you'll need to update those permissions to match the new unprivileged user.",[13,736,737,738,743],{},"More details are available in the ",[26,739,742],{"href":740,"rel":741},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Ftree\u002Fedf987872b7c93170b5ced56061b211619e7e106#docker",[30],"Device Agent readme",".\n{% endcaution %}",[13,745,746],{},"This is a security hardening change with no functional impact on normal Device Agent operation.",[170,748,750],{"id":749},"structured-json-logging","Structured JSON logging",[13,752,753,754,757],{},"The Device Agent now supports a JSON logging format, selectable via the ",[86,755,756],{},"--log-format json"," CLI flag.",[13,759,760],{},"Previously, all agent output was plain-text - readable in a terminal but difficult to ingest reliably into log aggregation tools like Grafana Loki, Elastic, or AWS CloudWatch. Parsing unstructured log lines with regex is fragile and breaks whenever the message format changes.",[13,762,763],{},"With JSON logging enabled, every log entry is a machine-readable object with consistent fields. Pipe agent output directly into your existing observability stack without any custom parsing rules.",[765,766,771],"pre",{"className":767,"code":769,"language":770},[768],"language-text","device-agent --log-format json\n","text",[86,772,769],{"__ignoreMap":39},[170,774,776],{"id":775},"bearer-token-authentication","Bearer token authentication",[13,778,779],{},"The Device Agent now supports bearer tokens as an authentication method for HTTP endpoints, alongside the existing credential model.",[13,781,782],{},"This allows you to create HTTP endpoints in your Node-RED flows that can be accessed securely by other applications without needing to manually authenticate first. This is a capability we've had in Hosted Instances for a while - this release makes it available to Remote Instances as well.",[13,784,785,786,789,790,793],{},"You can configure the tokens via the FlowFuse dashboard for your remote instance under the ",[86,787,788],{},"Settings->Security"," section. Enable the ",[86,791,792],{},"FlowFuse User Authentication"," option, then you can create and manage the tokens.",[13,795,796],{},"This requires the FlowFuse v2.32 release, coming later this week, when running in a self-hosted environment, but already available on FlowFuse Cloud.",[170,798,800],{"id":799},"editor-theme-fix","Editor theme fix",[13,802,803],{},"A bug caused the FlowFuse editor theme to fail to load in certain configurations - particularly when switching between Node-RED 5 and legacy versions. This is now resolved. The correct theme loads regardless of which Node-RED version the device is running.",[583,805],{},[170,807,809],{"id":808},"upgrading-to-v4","Upgrading to v4",[13,811,812],{},"Before upgrading, check the following:",[13,814,815,818,819,821,822,227],{},[150,816,817],{},"Docker users:"," The ",[86,820,715],{}," container image now uses a Node.js 22 base and runs as an unprivileged user. Review volume mount permissions and update any configurations that assume a root user or an earlier Node.js version. Details available in the ",[26,823,742],{"href":740,"rel":824},[30],[13,826,827,830],{},[150,828,829],{},"Installer users:"," Download the latest version of the installer and re-run it if you want to stay aligned with the new default.",[583,832],{},[13,834,835,836,841],{},"Device Agent v4 is available now. Update via the ",[26,837,840],{"href":838,"rel":839},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent",[30],"Device Agent installer"," or pull the latest Docker image.",{"title":39,"searchDepth":55,"depth":55,"links":843},[844,845,846,847,848,849],{"id":700,"depth":194,"text":701},{"id":725,"depth":194,"text":726},{"id":749,"depth":194,"text":750},{"id":775,"depth":194,"text":776},{"id":799,"depth":194,"text":800},{"id":808,"depth":194,"text":809},"2026-06-29","Device Agent v4 ships with Node.js 22 as the default runtime, structured JSON logging, bearer token authentication, and a hardened container security model. This is a major release with breaking changes - read on to know what to update before upgrading.",[853],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Fissues\u002F650",{"tags":855,"excerpt":856},[64],{"type":10,"value":857},[858],[13,859,692,860,697],{},[26,861,696],{"href":695},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released",{"title":686,"description":851},{"loc":862},"changelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Updated Node.js, JSON logging, bearer token auth, and a more secure container runtime.","mRrZn5UeaJmKpfaxohewP2cLPJ9DJDE60u2H7OkSoYE",{"id":869,"title":870,"authors":871,"body":872,"date":850,"description":938,"extension":59,"issues":939,"meta":941,"navigation":65,"path":943,"seo":944,"sitemap":945,"stem":946,"subtitle":70,"__hash__":947},"changelog\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support.md","Connect Pipelines to Any Git Server",[143],{"type":10,"value":873,"toc":936},[874,881,884,887,890,924,933],[13,875,876,877,880],{},"DevOps Pipeline Git Repository stages now connect to ",[150,878,879],{},"any Git server that speaks HTTPS",", GitLab, Bitbucket, Gitea, or a self-hosted instance, not just GitHub and Azure DevOps.",[13,882,883],{},"Previously, Git integration only worked with those two providers. If your team backs up flows to a self-hosted GitLab or an on-prem Bitbucket, you were stuck. Now you can point a pipeline at any HTTPS Git repository to back up and deploy your flows.",[13,885,886],{},"For servers that use a private certificate authority, you can paste in a CA certificate so FlowFuse trusts the connection, no infrastructure changes required.",[13,888,889],{},"To get started:",[891,892,893,899,910,917],"ol",{},[254,894,895,896,227],{},"Go to ",[150,897,898],{},"Team Settings → Integrations → Add Token",[254,900,901,902,905,906,909],{},"Choose ",[150,903,904],{},"Other",", then enter the repository ",[150,907,908],{},"username"," and a personal access token (or app password).",[254,911,912,913,916],{},"If your server uses a private CA, paste its certificate into the ",[150,914,915],{},"CA Certificate"," field.",[254,918,919,920,923],{},"Add a ",[150,921,922],{},"Git Repository"," stage to a pipeline, select your token, and enter the repository URL.",[13,925,926,930],{},[36,927],{"alt":928,"src":929},"The Add Git Token dialog showing the GitHub, Azure DevOps, and Other provider options, with the Other option selected and the username and CA certificate fields visible","\u002Fchangelog\u002F2026\u002F06\u002Fimages\u002Fgeneric-git-provider.png",[43,931,932],{},"Creating a generic Git token for a self-hosted server.",[13,934,935],{},"This feature is available to Team and Enterprise tier users of FlowFuse Cloud and Enterprise Licensed Self Hosted users from v2.32.",{"title":39,"searchDepth":55,"depth":55,"links":937},[],"DevOps Pipeline Git stages now push and pull snapshots to any HTTPS Git server, GitLab, Bitbucket, Gitea, or self-hosted, including servers behind a private certificate authority.",[940],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5294",{"tags":942},[64],"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support",{"title":870,"description":938},{"loc":943},"changelog\u002F2026\u002F06\u002Fgeneric-git-server-support","WslTXmfmPDTuF9mUsg8uiEDD8pysVlXy1cmhZkP_bt8",{"id":949,"title":950,"authors":951,"body":952,"date":1009,"description":1010,"extension":59,"issues":70,"meta":1011,"navigation":65,"path":1013,"seo":1014,"sitemap":1015,"stem":1016,"subtitle":70,"__hash__":1017},"changelog\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance.md","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",[8],{"type":10,"value":953,"toc":1005},[954,957,960,965,969,972,975,978,981,984,988,991,994,997],[13,955,956],{},"As part of our ongoing efforts to maintain our infrastructure, we need to update some of our servers that host Node-RED instances.",[13,958,959],{},"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.",[13,961,962],{},[150,963,964],{},"We will complete this migration during a 3 hour maintenance window starting at 8am UTC on Saturday 11th July 2026.",[385,966,968],{"id":967},"will-my-instances-be-affected","Will my instances be affected?",[13,970,971],{},"If your instance was created after 15th June 2026, or has been updated since that date, it will already be running on the new servers.",[13,973,974],{},"Otherwise, you can take action to migrate your instance before the scheduled maintenance window at your own convenience.",[13,976,977],{},"If you manually suspend and restart your instance, or apply any pending upgrade any time before the maintenance window, your instance will not need to be restarted and no further action will be needed.",[13,979,980],{},"You can find the \"Suspend\" option from the \"Actions\" drop down menu on the Instance Overview page. Once the Instance reports being in the Suspended state, you can select \"Start\" from the same drop down menu.",[13,982,983],{},"We will be emailing notifications to all team owners who have instances that require a restart.",[385,985,987],{"id":986},"enabling-scheduled-maintenance-mode","Enabling Scheduled Maintenance Mode",[13,989,990],{},"Keeping instances up to date is an important task to ensure they are running with the latest features and security fixes. FlowFuse provides the ability to select a time for updates to be automatically applied to your instances. You pick which day of the week and time the platform can schedule updates in. This removes the burden for keeping things up to date.",[13,992,993],{},"On FlowFuse Cloud, Starter teams already have this feature enabled for their instances to apply updates at the weekend.",[13,995,996],{},"Pro and Enterprise teams can opt-in on the Instance Settings - Maintenance page.",[13,998,999,1000,227],{},"More information is available in the ",[26,1001,1004],{"href":1002,"rel":1003},"https:\u002F\u002Fflowfuse.com\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance\u002F",[30],"scheduled maintenance changelog entry",{"title":39,"searchDepth":55,"depth":55,"links":1006},[1007,1008],{"id":967,"depth":598,"text":968},{"id":986,"depth":598,"text":987},"2026-06-15","Keeping the FlowFuse Cloud up to date with critical server maintenance.",{"tags":1012},[64],"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance",{"title":950,"description":1010},{"loc":1013},"changelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","iBXTcJTAaGuXVSQfT3AHa7fdoXzOEKUjupXP3Euczig",{"id":1019,"title":1020,"authors":1021,"body":1022,"date":1080,"description":1081,"extension":59,"issues":1082,"meta":1084,"navigation":65,"path":1086,"seo":1087,"sitemap":1088,"stem":1089,"subtitle":70,"__hash__":1090},"changelog\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode.md","Dark Mode",[143],{"type":10,"value":1023,"toc":1078},[1024,1027,1030,1033,1042,1045,1072,1075],[13,1025,1026],{},"FlowFuse now has a dark mode. 🦇 You can switch the whole app between Light, Dark, and System from your User Settings.",[13,1028,1029],{},"A bright white UI is fatiguing in low-light control rooms or on a night shift. Dark mode lets FlowFuse fit those environments.",[13,1031,1032],{},"By default, FlowFuse follows your operating system and flips live when it changes. Pick Light or Dark to lock it in, FlowFuse remembers your choice per browser.",[13,1034,1035,1039],{},[36,1036],{"alt":1037,"dataZoomable":39,"src":1038},"FlowFuse in dark mode, showing the Theme setting under User Settings","\u002Fchangelog\u002F2026\u002F06\u002Fimages\u002Fdark-mode.gif",[43,1040,1041],{},"The whole app re-themes live as you toggle, no reload needed.",[13,1043,1044],{},"To change your theme:",[891,1046,1047,1053,1069],{},[254,1048,1049,1050],{},"Open ",[150,1051,1052],{},"User Settings",[254,1054,1055,1056,1059,1060,549,1063,564,1066],{},"Under ",[150,1057,1058],{},"Theme",", choose ",[150,1061,1062],{},"Light",[150,1064,1065],{},"Dark",[150,1067,1068],{},"System",[254,1070,1071],{},"Save",[13,1073,1074],{},"A note on scope: dark mode covers the FlowFuse application itself. The embedded Node-RED editor and Dashboard iframes keep their own themes, Node-RED and your Dashboard configuration manage those separately.",[13,1076,1077],{},"This feature is available to all FlowFuse Cloud users and all Self-Hosted users from v2.32.",{"title":39,"searchDepth":55,"depth":55,"links":1079},[],"2026-06-02","FlowFuse now supports light and dark themes across the app, with a System option that follows your operating system preference.",[1083],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7307",{"tags":1085},[64],"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode",{"title":1020,"description":1081},{"loc":1086},"changelog\u002F2026\u002F06\u002Fdark-mode","RObOdSWV0KhDIvUuYmy3DL8xVB28M83XpKXl2GkItrE",{"id":1092,"title":1093,"authors":1094,"body":1095,"date":1123,"description":1124,"extension":59,"issues":1125,"meta":1127,"navigation":65,"path":1129,"seo":1130,"sitemap":1131,"stem":1132,"subtitle":70,"__hash__":1133},"changelog\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out.md","AI Feature Opt-Out for Teams",[285],{"type":10,"value":1096,"toc":1121},[1097,1100,1112,1115,1118],[13,1098,1099],{},"You can now turn off AI features for your team from the team settings page. When disabled, FlowFuse removes the Expert Assistant, inline code completions, and snapshot description generation for your team. Running instances will need a restart for the change to fully take effect.",[13,1101,1102,1106,1109],{},[36,1103],{"alt":1104,"dataZoomable":39,"src":1105},"AI Features toggle in team settings","\u002Fchangelog\u002F2026\u002F05\u002Fimages\u002Fai-opt-out-toggle.png",[1107,1108],"br",{},[43,1110,1111],{},"Opt out of AI features from the Danger section in team settings.",[13,1113,1114],{},"The toggle is on by default for all teams. Flipping it off shows a confirmation dialog so you don't accidentally disable it. If you change your mind later, just flip it back on.",[13,1116,1117],{},"Self Hosted Enterprise customers also get platform-level and team-type-level AI controls, so admins can control AI availability across the entire installation or per plan before it ever reaches team owners.",[13,1119,1120],{},"This feature is available to all FlowFuse Cloud users and Enterprise Self Hosted users from v2.31.",{"title":39,"searchDepth":55,"depth":55,"links":1122},[],"2026-05-28","Team owners and platform admins can now disable all AI features at the team level, so they can turn AI off when policy or compliance requires it.",[1126],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7316",{"tags":1128},[64],"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out",{"title":1093,"description":1124},{"loc":1129},"changelog\u002F2026\u002F05\u002Fai-opt-out","ytVb512e4DBzZQNHBwv0QMlIhh8baPSNU3a9BL7mwBk",{"id":1135,"title":1136,"authors":1137,"body":1139,"date":1168,"description":1169,"extension":59,"issues":70,"meta":1170,"navigation":65,"path":1172,"seo":1173,"sitemap":1174,"stem":1175,"subtitle":70,"__hash__":1176},"changelog\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building.md","FlowFuse Expert Builds Your Application",[1138],"dimitrie-hoekstra",{"type":10,"value":1140,"toc":1166},[1141,1144,1147,1156,1159],[13,1142,1143],{},"You can now describe what you want to build, and the FlowFuse Expert will assemble it for you directly on your Node-RED workspace. It adds tabs, drops in nodes, wires them together, and configures their properties, to help get you up and running.",[13,1145,1146],{},"Previously, the Expert could answer questions, suggest changes, and act on links you clicked. Turning those suggestions into a working OEE dashboard, MES handover screen, or Modbus-to-UNS bridge still meant placing every node and wire by hand. Now the Expert does that work for you, and you keep iterating in chat to shape the result around your real-world setup.",[13,1148,1149,1153],{},[36,1150],{"alt":1151,"dataZoomable":39,"src":1152},"FlowFuse Expert assembling flows on the Node-RED workspace from a chat prompt","\u002Fchangelog\u002F2026\u002F05\u002Fimages\u002Fexpert-application-building.gif",[43,1154,1155],{},"FlowFuse Expert assembling an application on the Node-RED workspace from a chat prompt.",[13,1157,1158],{},"Agentic Node-RED development is rolling out as a soft launch so we can fine-tune the experience before opening it up more widely. It is available on request to FlowFuse Cloud Team and Enterprise teams from v2.30. Self Hosted enablement follows shortly.",[13,1160,1161,1165],{},[26,1162,1164],{"href":1163},"\u002Fcontact-us\u002F?subject=FlowFuse%20Expert%20Application%20Building","Contact us"," to enable agentic Node-RED development for your FlowFuse Cloud team.",{"title":39,"searchDepth":55,"depth":55,"links":1167},[],"2026-05-07","Describe the application you want, and FlowFuse Expert assembles it on your Node-RED canvas: tabs, nodes, wires, and configuration.",{"tags":1171},[64],"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building",{"title":1136,"description":1169},{"loc":1172},"changelog\u002F2026\u002F05\u002Fexpert-application-building","Hx4pQLotgPnErzegObCoMdl9FJKv-n8wPJ7pN9BBbTc",{"id":1178,"title":1179,"authors":1180,"body":1181,"date":1168,"description":1215,"extension":59,"issues":1216,"meta":1218,"navigation":65,"path":1220,"seo":1221,"sitemap":1222,"stem":1223,"subtitle":70,"__hash__":1224},"changelog\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider.md","Single SSO provider for all users",[210],{"type":10,"value":1182,"toc":1213},[1183,1186,1189,1197,1203,1210],[13,1184,1185],{},"When running self hosted FlowFuse or embedding FlowFuse in a solution it may be\nrequired to send all user authentication requests to a single SAML SSO provider,\nrather than using the users email domain to pick the correct provider.",[13,1187,1188],{},"With the release of FlowFuse 2.30.0 it is now possible to pick a configured provider and all unauthenticated users will be automatically redirected to this provider.",[13,1190,1191,1195],{},[36,1192],{"alt":1193,"src":1194},"Admin settings for Automatic SSO Redirect","\u002Fchangelog\u002F2026\u002F05\u002Fimages\u002Fsingle-sso-provider.png",[43,1196,1193],{},[13,1198,1199,1200],{},"To prevent administrator lockout in the event of a SSO failure, admins can by pass this redirect and enter their normal username and password by accessing any page on the admin route, e.g. ",[86,1201,1202],{},"https:\u002F\u002Fforge.example.com\u002Fadmin",[13,1204,1205,1206],{},"Documentation is found ",[26,1207,226],{"href":1208,"rel":1209},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fadmin\u002Fsso\u002Fsaml#forcing-all-users-to-use-sso",[30],[13,1211,1212],{},"This feature is only available to Self Hosted Enterprise licensed FlowFuse Instances.",{"title":39,"searchDepth":55,"depth":55,"links":1214},[],"This allows admins to configure a Single SAML SSO provider for all users regardless of email domain.",[1217],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6319",{"tags":1219},[64],"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider",{"title":1179,"description":1215},{"loc":1220},"changelog\u002F2026\u002F05\u002Fsingle-sso-provider","qZD1YFVB47rD78O7X5nCeV7Sl2nBRnGhO7fxoYtz_oc",{"id":1226,"title":1227,"authors":1228,"body":1229,"date":1277,"description":1278,"extension":59,"issues":1279,"meta":1281,"navigation":65,"path":1283,"seo":1284,"sitemap":1285,"stem":1286,"subtitle":70,"__hash__":1287},"changelog\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer.md","Customisable Immersive Editor Drawer",[143],{"type":10,"value":1230,"toc":1275},[1231,1234,1243,1269,1272],[13,1232,1233],{},"The drawer in the immersive editor used to float over your canvas, blocking parts of your flow whenever it was open. Now it sits inside the editor layout, so FlowFuse tools stay visible alongside your work in Node-RED. You can also set it up the way you like, and it stays that way every time you come back:",[13,1235,1236,1240],{},[36,1237],{"alt":1238,"dataZoomable":39,"src":1239},"Pinning, moving, and full-screening the immersive editor drawer","\u002Fchangelog\u002F2026\u002F04\u002Fimages\u002Fimmersive-ui-drawer.gif",[43,1241,1242],{},"Pin, switch sides, or go full-screen from the drawer header, your settings persist between sessions.",[251,1244,1245,1251,1257,1263],{},[254,1246,1247,1250],{},[150,1248,1249],{},"Pin the drawer"," to dock it alongside the canvas, and the Node-RED editor resizes to fit.",[254,1252,1253,1256],{},[150,1254,1255],{},"Switch sides"," to move the drawer to the left or right of the screen.",[254,1258,1259,1262],{},[150,1260,1261],{},"Go full-screen"," to hide the FlowFuse topbar and give the canvas maximum space.",[254,1264,1265,1268],{},[150,1266,1267],{},"Resize the drawer"," to whatever width works best for you.",[13,1270,1271],{},"The drawer opens by default the first time you visit the editor. After that, your browser remembers your choices between sessions.",[13,1273,1274],{},"This feature is available to all FlowFuse Cloud users and Self Hosted users from v2.30.",{"title":39,"searchDepth":55,"depth":55,"links":1276},[],"2026-04-29","The immersive editor drawer is now pinnable, switchable, and resizable, with your preferences saved between sessions.",[1280],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6267",{"tags":1282},[64],"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"title":1227,"description":1278},{"loc":1283},"changelog\u002F2026\u002F04\u002Fimmersive-editor-drawer","hAM7X-HnIpHLWxDTWo6xySOm6HBs_0WqwsfyZ-iSCMY",{"id":1289,"title":1290,"authors":1291,"body":1292,"date":1326,"description":1327,"extension":59,"issues":70,"meta":1328,"navigation":65,"path":1330,"seo":1331,"sitemap":1332,"stem":1333,"subtitle":70,"__hash__":1334},"changelog\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links.md","FlowFuse expert action links",[284],{"type":10,"value":1293,"toc":1324},[1294,1297,1306,1314,1321],[13,1295,1296],{},"When interacting with the FlowFuse expert, you might be asked to search flows, select a node, or edit a node.\nPreviously, this was presented as a set of text instructions.\nAs of today, whenever possible, the Expert will provide clickable action links that will perform the operation for you.",[13,1298,1299,1303],{},[36,1300],{"alt":1301,"dataZoomable":39,"src":1302},"Selecting and editing nodes","\u002Fchangelog\u002F2026\u002F04\u002Fimages\u002Fexpert-action-links-select-edit.gif",[43,1304,1305],{},"Selecting and editing nodes.",[13,1307,1308,1312],{},[36,1309],{"alt":1310,"dataZoomable":39,"src":1311},"Searching your flows","\u002Fchangelog\u002F2026\u002F04\u002Fimages\u002Fexpert-action-links-search.gif",[43,1313,1310],{},[13,1315,1316,1317,1320],{},"This feature requires ",[150,1318,1319],{},"Node-RED Assistant v0.12.0"," or later.",[13,1322,1323],{},"This change is live on FlowFuse Cloud. Self-Hosted users will receive it in the next release (v2.29).",{"title":39,"searchDepth":55,"depth":55,"links":1325},[],"2026-04-09","When the Expert instructs you to select nodes or search flows, it now presents direct action links",{"tags":1329},[64],"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links",{"title":1290,"description":1327},{"loc":1330},"changelog\u002F2026\u002F04\u002Fexpert-action-links","LchqkNYwi2Zo9s3IhqRhtVUm9_aoqX3Qp8AgtDN9q8Y",{"id":1336,"title":1337,"authors":1338,"body":1339,"date":1361,"description":1362,"extension":59,"issues":1363,"meta":1365,"navigation":65,"path":1367,"seo":1368,"sitemap":1369,"stem":1370,"subtitle":70,"__hash__":1371},"changelog\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor.md","Developer Mode Now Accessible from the Immersive Editor",[143],{"type":10,"value":1340,"toc":1359},[1341,1344,1353,1356],[13,1342,1343],{},"The Developer Mode tab is now available directly in the immersive editor drawer when working with remote instances. You can toggle auto snapshot and create snapshots without leaving the editor.",[13,1345,1346,1350],{},[36,1347],{"alt":1348,"src":1349},"Developer Mode tab in the immersive editor drawer","\u002Fchangelog\u002F2026\u002F03\u002Fimages\u002Fdeveloper-mode-in-editor.png",[43,1351,1352],{},"The Developer Mode tab now appears directly in the immersive editor drawer, with options to create a snapshot and manage device flows.",[13,1354,1355],{},"Previously, accessing Developer Mode meant opening a second browser window and navigating to the standalone device view, breaking your flow inside the editor and adding unnecessary friction, especially when working through a staged dev, test, and promote rollout.",[13,1357,1358],{},"This feature is available to Enterprise tier users of FlowFuse Cloud and Enterprise Licensed Self Hosted users from v2.29.",{"title":39,"searchDepth":55,"depth":55,"links":1360},[],"2026-04-07","The Developer Mode tab is now available directly in the immersive editor drawer, so you can manage snapshots and auto snapshot settings without leaving the editor.",[1364],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7031",{"tags":1366},[64],"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor",{"title":1337,"description":1362},{"loc":1367},"changelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","bvd1S8GH4RchGi-e2qVY6iTQVUx1TDSAx7tUtGR5hJQ",{"id":1373,"title":1374,"authors":1375,"body":1376,"date":1361,"description":1407,"extension":59,"issues":1408,"meta":1410,"navigation":65,"path":1412,"seo":1413,"sitemap":1414,"stem":1415,"subtitle":70,"__hash__":1416},"changelog\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor.md","View Snapshot Details in the Immersive Editor",[143],{"type":10,"value":1377,"toc":1405},[1378,1381,1390,1393,1402],[13,1379,1380],{},"You can now open snapshot details from inside the immersive editor. Previously, clicking a snapshot from the Version History timeline or Snapshots list had no effect in the editor, the detail view was only available from the instance page in FlowFuse.",[13,1382,1383,1387],{},[36,1384],{"alt":1385,"src":1386},"Snapshot toggle inside the immersive editor","\u002Fchangelog\u002F2026\u002F03\u002Fimages\u002Fsnapshot-toggle.png",[43,1388,1389],{},"Access snapshots from the Version History timeline or Snapshots list inside the editor.",[13,1391,1392],{},"Snapshot details now open in a modal inside the immersive editor, so you can review and manage snapshots without leaving your editing session. The modal contains the same information as the snapshot detail view on the instance page.",[13,1394,1395,1399],{},[36,1396],{"alt":1397,"src":1398},"Snapshot detail modal open inside the immersive editor","\u002Fchangelog\u002F2026\u002F03\u002Fimages\u002Fsnapshot-modal-view.png",[43,1400,1401],{},"Snapshot details open in a modal inside the immersive editor.",[13,1403,1404],{},"This feature is available to all FlowFuse Cloud users and all Self Hosted users from v2.29.",{"title":39,"searchDepth":55,"depth":55,"links":1406},[],"You can now open and review snapshot details directly inside the immersive editor without leaving your editing session.",[1409],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7032",{"tags":1411},[64],"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor",{"title":1374,"description":1407},{"loc":1412},"changelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","ziNBkd7NqTbbdc-MCT4t4Fgk22t8cWqrB3hbtTep_Qo",{"id":1418,"title":1419,"authors":1420,"body":1421,"date":1361,"description":1460,"extension":59,"issues":1461,"meta":1463,"navigation":65,"path":1465,"seo":1466,"sitemap":1467,"stem":1468,"subtitle":70,"__hash__":1469},"changelog\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var.md","Hosted Instances know their own URL",[210],{"type":10,"value":1422,"toc":1458},[1423,1435,1444,1452,1455],[13,1424,1425,1426,1429,1430,1434],{},"Your hosted instance now knows its own URL. The ",[86,1427,1428],{},"FF_INSTANCE_URL"," ",[26,1431,1433],{"href":1432},"\u002Fdocs\u002Fuser\u002Fenvvar\u002F#standard-environment-variables","environment variable"," is automatically available to your flows, so you can reference the instance's address without hardcoding it.",[13,1436,1437,1441],{},[36,1438],{"alt":1439,"src":1440},"List of Hosted Instance Environment Variables","\u002Fchangelog\u002F2026\u002F04\u002Fimages\u002Fff-instance-url-env-var.png",[43,1442,1443],{},"FF_INSTANCE_URL in list of Instance Environment Variables",[13,1445,1446,1447,1451],{},"For Hosted Instances with a ",[26,1448,1450],{"href":1449},"\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F#custom-hostnames","Custom Hostname"," that will be returned rather than the default Instance hostname.",[13,1453,1454],{},"Existing instances will need to be restarted to pick up the new Environment Variable.",[13,1456,1457],{},"This will be available to Self Hosted users from v2.29.0",{"title":39,"searchDepth":55,"depth":55,"links":1459},[],"Hosted Instances now get an FF_INSTANCE_URL environment variable",[1462],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6984",{"tags":1464},[64],"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var",{"title":1419,"description":1460},{"loc":1465},"changelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","zuraXn_BRQWKOjkRU2kTAjpb5N_ZK6Fzd6G8qbhnt5c",{"id":1471,"title":1472,"authors":1473,"body":1474,"date":1361,"description":1514,"extension":59,"issues":1515,"meta":1518,"navigation":65,"path":1520,"seo":1521,"sitemap":1522,"stem":1523,"subtitle":70,"__hash__":1524},"changelog\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer.md","Richer snapshot comparison view",[76],{"type":10,"value":1475,"toc":1512},[1476,1479,1482,1496,1499,1506,1509],[13,1477,1478],{},"Previously, comparing snapshots only showed the two flow canvases overlaid at different opacities. You could see that something had changed, but not what or where.",[13,1480,1481],{},"Now when you compare two snapshots, a sidebar lists every changed, added, and deleted node. You can step through them one at a time, the canvas highlights and scrolls to the relevant node automatically. For each change you can see:",[251,1483,1484,1490],{},[254,1485,1486,1489],{},[150,1487,1488],{},"Property diffs",": each changed property is shown inline with the old and new value side by side.",[254,1491,1492,1495],{},[150,1493,1494],{},"Code diffs",": for function and template nodes, code changes appear as a line-level diff with red for removed lines and green for added, the same format you'd expect from a git diff.",[13,1497,1498],{},"Use the Prev \u002F Next buttons or the ← → arrow keys to navigate through changes.",[1500,1501],"lite-youtube",{"videoid":1502,"params":1503,"style":1504,"title":1505},"cNdGB-gksfQ","rel=0","width: 100%; aspect-ratio: 16\u002F9;","Snapshot Comparison, FlowFuse v2.29",[13,1507,1508],{},"For the first time, teams can review a snapshot diff before deployment and actually trust what they're seeing, not just look at it.",[13,1510,1511],{},"This feature is available to all FlowFuse Cloud and Self Hosted users from v2.29.",{"title":39,"searchDepth":55,"depth":55,"links":1513},[],"The snapshot comparison dialog now gives a full breakdown of every change between two snapshots, navigate node by node and see exactly what was added, removed, or modified.",[1516,1517],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7025","https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F7029",{"tags":1519},[64],"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer",{"title":1472,"description":1514},{"loc":1520},"changelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","rH6ePiBzvdn-I6ZpbYnKMrRl_tp2N5Em6XVDXDDpFuI",{"id":1526,"title":1527,"authors":1528,"body":1529,"date":1575,"description":1576,"extension":59,"issues":1577,"meta":1579,"navigation":65,"path":1581,"seo":1582,"sitemap":1583,"stem":1584,"subtitle":70,"__hash__":1585},"changelog\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title.md","Embedded Editor Now Shows Active Tab",[143],{"type":10,"value":1530,"toc":1573},[1531,1538,1541,1550,1557,1566,1571],[13,1532,1533,1534,1537],{},"Now the browser tab title updates as you navigate the embedded editor. If you're working on a tab called \"Sensor Flow\", your browser will show ",[86,1535,1536],{},"Node-RED: Sensor Flow - FlowFuse",". This works for both hosted and remote device instances, and also updates when you navigate into a subflow.",[13,1539,1540],{},"If you work with multiple editors open at once, you can now tell exactly what's open in each tab without clicking through.",[13,1542,1543,1547],{},[36,1544],{"alt":1545,"src":1546},"Browser tab showing \"Node-RED: Flow 1 - FlowFuse\" after the update","\u002Fchangelog\u002F2026\u002F03\u002Fimages\u002Fbrowser-title-after.png",[43,1548,1549],{},"The browser tab title showing \"Node-RED: Flow 1 - FlowFuse\" after navigating to the Flow 1 canvas tab.",[13,1551,1552,1553,1556],{},"Previously, the title stayed generic, something like ",[86,1554,1555],{},"Instance - Editor - FlowFuse",", regardless of which canvas tab was active. If you had multiple embedded editors open in different browser tabs, there was no way to tell them apart at a glance.",[13,1558,1559,1563],{},[36,1560],{"alt":1561,"src":1562},"Browser tab showing the old generic title \"Hosted Instance - Expert - FlowFuse\"","\u002Fchangelog\u002F2026\u002F03\u002Fimages\u002Fbrowser-title-before.png",[43,1564,1565],{},"The old generic title, showing \"Hosted Instance - Expert - FlowFuse\" regardless of which canvas tab was open.",[13,1567,1316,1568,1570],{},[150,1569,1319],{}," or later. If you are on an older version of the assistant, the title will not update.",[13,1572,1323],{},{"title":39,"searchDepth":55,"depth":55,"links":1574},[],"2026-03-31","The browser tab title now updates to reflect the active Node-RED canvas tab when working in the embedded editor.",[1578],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6713",{"tags":1580},[64],"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title",{"title":1527,"description":1576},{"loc":1581},"changelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Ltc4czsoeiS46PvxISC1RhFi-H1TOfY54jd840Ngz0E",{"id":1587,"title":1588,"authors":1589,"body":1590,"date":1620,"description":1621,"extension":59,"issues":1622,"meta":1624,"navigation":65,"path":1626,"seo":1627,"sitemap":1628,"stem":1629,"subtitle":70,"__hash__":1630},"changelog\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops.md","Azure DevOps Pipeline support",[210],{"type":10,"value":1591,"toc":1618},[1592,1600,1603,1606,1615],[13,1593,1594,1599],{},[26,1595,1598],{"href":1596,"rel":1597},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fdevops-pipelines",[30],"DevOps Pipeline"," Git Stages now support Azure DevOps repositories alongside GitHub.",[13,1601,1602],{},"If your team already uses Azure DevOps for CI and code review, you can now push and pull Snapshots directly as part of that workflow, no need to manage your Node-RED flows outside your existing tooling.",[13,1604,1605],{},"Add Personal Access Tokens under Team Settings → Integrations",[13,1607,1608,1612],{},[36,1609],{"alt":1610,"src":1611},"Dialog to create a new Azure DevOps Token","\u002Fchangelog\u002F2026\u002F03\u002Fimages\u002Fazure-token.png",[43,1613,1614],{},"The Azure DevOps token dialog under Team Settings → Integrations",[13,1616,1617],{},"Pro and Enterprise customers on FlowFuse Cloud and Enterprise licensed Self Hosted users can use Azure DevOps repositories in their Pipelines from v2.29.",{"title":39,"searchDepth":55,"depth":55,"links":1619},[],"2026-03-24","DevOps Pipeline Git Stages now support Azure DevOps repositories alongside GitHub",[1623],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5491",{"tags":1625},[64],"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops",{"title":1588,"description":1621},{"loc":1626},"changelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","28xZ575lhOdXii0uvJ4l7r7mDjJejNnyZzh1TP6cPxA",{"id":1632,"title":1633,"authors":1634,"body":1635,"date":1680,"description":1010,"extension":59,"issues":70,"meta":1681,"navigation":65,"path":1683,"seo":1684,"sitemap":1685,"stem":1686,"subtitle":70,"__hash__":1687},"changelog\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance.md","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",[8],{"type":10,"value":1636,"toc":1676},[1637,1639,1641,1646,1649,1651,1654,1656,1659,1661,1663,1665,1667,1669,1671],[13,1638,956],{},[13,1640,959],{},[13,1642,1643],{},[150,1644,1645],{},"We will complete this migration during a 2 hour maintenance window starting at 8am UTC on Saturday 28th March 2026.",[13,1647,1648],{},"Note: the original version of this post had the incorrect date. The mainteance is scheduled for Saturday 28th March.",[385,1650,968],{"id":967},[13,1652,1653],{},"If your instance was created after 11th March 2026, or has been updated to the 2.28 release, it will already be running on the new servers.",[13,1655,974],{},[13,1657,1658],{},"If you manually suspend and restart your instance, or upgrade to 2.28 at any time before the maintenance window, your instance will not need to be restarted and no further action will be needed.",[13,1660,980],{},[13,1662,983],{},[385,1664,987],{"id":986},[13,1666,990],{},[13,1668,993],{},[13,1670,996],{},[13,1672,999,1673,227],{},[26,1674,1004],{"href":1002,"rel":1675},[30],{"title":39,"searchDepth":55,"depth":55,"links":1677},[1678,1679],{"id":967,"depth":598,"text":968},{"id":986,"depth":598,"text":987},"2026-03-12",{"tags":1682},[64],"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance",{"title":1633,"description":1010},{"loc":1683},"changelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","gvQ2a1O1AVuHd69A7fmxJtNSyX6C0iCq42Y6SEZe2XM",{"id":1689,"title":1690,"authors":1691,"body":1692,"date":1744,"description":1745,"extension":59,"issues":1746,"meta":1748,"navigation":65,"path":1750,"seo":1751,"sitemap":1752,"stem":1753,"subtitle":70,"__hash__":1754},"changelog\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context.md","FlowFuse Expert: Helping you make sense of your debug log",[284],{"type":10,"value":1693,"toc":1742},[1694,1697,1700,1703,1708,1716,1724,1732,1735],[13,1695,1696],{},"As a flow developer, you know how frustrating it can be to have a bug or issue in your flows. You add a ton of debug nodes and add warning alerts to your functions to try and help you track it down. The logs can be a great source of information but you still need to figure out why it is happening! Why am I getting this error? Where did this log come from?",[13,1698,1699],{},"Now, you can ask the Expert!",[13,1701,1702],{},"We have added the ability to include individual log entries and a quick-add selection on the Resource Selector. Adding these logs alongside the related flows can further focus the AI on the issue and help you solve it.",[13,1704,1705],{},[150,1706,1707],{},"Key Highlights:",[251,1709,1710,1713],{},[254,1711,1712],{},"Laser Focus: Select individual log entries to provide specific context.",[254,1714,1715],{},"Quick Add: Use the Resource Selector button to instantly pull in logs.",[13,1717,1718,1722],{},[36,1719],{"alt":1720,"dataZoomable":39,"src":1721},"FlowFuse Expert Debug Log Context in Action","\u002Fchangelog\u002F2026\u002F02\u002Fimages\u002Fexpert-debug-context.gif",[43,1723,1720],{},[13,1725,1726,1730],{},[36,1727],{"alt":1728,"dataZoomable":39,"src":1729},"FlowFuse Expert Focused Debug Log Context","\u002Fchangelog\u002F2026\u002F02\u002Fimages\u002Fexpert-debug-log-specific.gif",[43,1731,1728],{},[13,1733,1734],{},"We are sure you will love this feature - and there is more to come too!",[13,1736,1737,1738,227],{},"For more details, see ",[26,1739,1741],{"href":1740},"\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#debug-context","Debug Context",{"title":39,"searchDepth":55,"depth":55,"links":1743},[],"2026-03-05","You can now send debug log entries to the FlowFuse Expert as context, making it easier to track down errors in your flows.",[1747],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fnr-assistant\u002Fissues\u002F137",{"tags":1749},[64],"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context",{"title":1690,"description":1745},{"loc":1750},"changelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","xz75D6z3ZPpnA9meOrgjZ9KxpoAqMlDTm2Qv13fEboE",{"id":1756,"title":1757,"authors":1758,"body":1759,"date":1784,"description":1785,"extension":59,"issues":1786,"meta":1788,"navigation":65,"path":1790,"seo":1791,"sitemap":1792,"stem":1793,"subtitle":70,"__hash__":1794},"changelog\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner.md","FlowFuse Expert: Never Miss an Update",[284],{"type":10,"value":1760,"toc":1782},[1761,1764,1767,1776],[13,1762,1763],{},"The Expert now shows a banner in the chat area when a newer version is available. One click and you are up to date.",[13,1765,1766],{},"FlowFuse Expert is updated regularly with new capabilities. This makes sure you always know when there is something new to try, without having to check manually.",[13,1768,1769,1773],{},[36,1770],{"alt":1771,"src":1772},"FlowFuse Expert update banner","\u002Fchangelog\u002F2026\u002F02\u002Fimages\u002Fff-expert-update-banner.gif",[43,1774,1775],{},"FlowFuse Expert lets you know when an update is available",[13,1777,1737,1778,227],{},[26,1779,1781],{"href":1780},"\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#keeping-expert-up-to-date","Keeping Expert up to date",{"title":39,"searchDepth":55,"depth":55,"links":1783},[],"2026-02-27","FlowFuse Expert now shows a banner when a new version is available, so you can update in one click.",[1787],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6763",{"tags":1789},[64],"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner",{"title":1757,"description":1785},{"loc":1790},"changelog\u002F2026\u002F02\u002Fff-expert-update-banner","YeLYUbtfi53vh0zAHjGKcVSJEtscBXWKWE_ruKfN2os",{"id":1796,"title":1797,"authors":1798,"body":1799,"date":2001,"description":2002,"extension":59,"issues":2003,"meta":2005,"navigation":65,"path":2007,"seo":2008,"sitemap":2009,"stem":2010,"subtitle":70,"__hash__":2011},"changelog\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options.md","Set Node.js Options for Remote Instances",[210],{"type":10,"value":1800,"toc":1996},[1801,1804,1807,1823,1826,1830,1837,1891,1899,1905,1986,1992],[13,1802,1803],{},"FlowFuse Device Agent v3.8.1 adds support for setting Node.js command line arguments for Remote Instances.",[13,1805,1806],{},"This allows things like:",[251,1808,1809,1812],{},[254,1810,1811],{},"Setting the Node.js heap size for memory-intensive flows",[254,1813,1814,1815,1818,1819,1822],{},"Enabling ",[86,1816,1817],{},"--use-openssl-ca"," (Linux) or ",[86,1820,1821],{},"--use-system-ca"," (Windows and macOS) to use private CA certificates",[13,1824,1825],{},"Node.js options can be configured in two ways:",[385,1827,1829],{"id":1828},"_1-via-the-device-agent-command-line","1. Via the device agent command line",[13,1831,1832,1833,1836],{},"Use the ",[86,1834,1835],{},"--node-options"," argument. This argument may be specified multiple times:",[765,1838,1842],{"className":1839,"code":1840,"language":1841,"meta":39,"style":39},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","flowfuse-device-agent -c \u002Fopt\u002Fflowfuse-device-agent\u002Fdevice.yml \\\n    --node-options='--max-old-space-size=256' \\\n    --node-options='--use-openssl-ca'\n","bash",[86,1843,1844,1864,1880],{"__ignoreMap":39},[1845,1846,1849,1853,1857,1860],"span",{"class":1847,"line":1848},"line",1,[1845,1850,1852],{"class":1851},"sBMFI","flowfuse-device-agent",[1845,1854,1856],{"class":1855},"sfazB"," -c",[1845,1858,1859],{"class":1855}," \u002Fopt\u002Fflowfuse-device-agent\u002Fdevice.yml",[1845,1861,1863],{"class":1862},"sTEyZ"," \\\n",[1845,1865,1866,1869,1873,1876,1878],{"class":1847,"line":194},[1845,1867,1868],{"class":1855},"    --node-options=",[1845,1870,1872],{"class":1871},"sMK4o","'",[1845,1874,1875],{"class":1855},"--max-old-space-size=256",[1845,1877,1872],{"class":1871},[1845,1879,1863],{"class":1862},[1845,1881,1882,1884,1886,1888],{"class":1847,"line":598},[1845,1883,1868],{"class":1855},[1845,1885,1872],{"class":1871},[1845,1887,1817],{"class":1855},[1845,1889,1890],{"class":1871},"'\n",[385,1892,1894,1895,1898],{"id":1893},"_2-via-the-deviceyml-file","2. Via the ",[86,1896,1897],{},"device.yml"," file",[13,1900,919,1901,1904],{},[86,1902,1903],{},"nodeOptions"," section:",[765,1906,1910],{"className":1907,"code":1908,"language":1909,"meta":39,"style":39},"language-yaml shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","deviceId: xxxxxxx\nforgeURL: https:\u002F\u002Fapp.flowfuse.com\ntoken: xxxxxxxx\ncredentialSecret: xxxxx\nnodeOptions:\n- '--max-old-space-size=256'\n- '--use-openssl-ca'\n","yaml",[86,1911,1912,1924,1934,1944,1954,1962,1975],{"__ignoreMap":39},[1845,1913,1914,1918,1921],{"class":1847,"line":1848},[1845,1915,1917],{"class":1916},"swJcz","deviceId",[1845,1919,1920],{"class":1871},":",[1845,1922,1923],{"class":1855}," xxxxxxx\n",[1845,1925,1926,1929,1931],{"class":1847,"line":194},[1845,1927,1928],{"class":1916},"forgeURL",[1845,1930,1920],{"class":1871},[1845,1932,1933],{"class":1855}," https:\u002F\u002Fapp.flowfuse.com\n",[1845,1935,1936,1939,1941],{"class":1847,"line":598},[1845,1937,1938],{"class":1916},"token",[1845,1940,1920],{"class":1871},[1845,1942,1943],{"class":1855}," xxxxxxxx\n",[1845,1945,1946,1949,1951],{"class":1847,"line":55},[1845,1947,1948],{"class":1916},"credentialSecret",[1845,1950,1920],{"class":1871},[1845,1952,1953],{"class":1855}," xxxxx\n",[1845,1955,1957,1959],{"class":1847,"line":1956},5,[1845,1958,1903],{"class":1916},[1845,1960,1961],{"class":1871},":\n",[1845,1963,1965,1968,1971,1973],{"class":1847,"line":1964},6,[1845,1966,1967],{"class":1871},"-",[1845,1969,1970],{"class":1871}," '",[1845,1972,1875],{"class":1855},[1845,1974,1890],{"class":1871},[1845,1976,1978,1980,1982,1984],{"class":1847,"line":1977},7,[1845,1979,1967],{"class":1871},[1845,1981,1970],{"class":1871},[1845,1983,1817],{"class":1855},[1845,1985,1890],{"class":1871},[13,1987,1737,1988,227],{},[26,1989,1991],{"href":1990},"\u002Fdocs\u002Fdevice-agent\u002Frunning\u002F#configuring-nodejs-options","Configuring Node.js Options",[1993,1994,1995],"style",{},"html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html pre.shiki code .sTEyZ, html code.shiki .sTEyZ{--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8}html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .swJcz, html code.shiki .swJcz{--shiki-light:#E53935;--shiki-default:#F07178;--shiki-dark:#F07178}",{"title":39,"searchDepth":55,"depth":55,"links":1997},[1998,1999],{"id":1828,"depth":598,"text":1829},{"id":1893,"depth":598,"text":2000},"2. Via the device.yml file","2026-02-13","FlowFuse Device Agent v3.8.1 adds support for passing Node.js command line arguments to Remote Instances, enabling custom heap sizes and private CA certificate support.",[2004],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Fissues\u002F571",{"tags":2006},[64],"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options",{"title":1797,"description":2002},{"loc":2007},"changelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","sCsMuusHNcwYD-A6eD40-M9hhWeWRIjfndO-QgF_JW4",{"id":2013,"title":2014,"authors":2015,"body":2016,"date":2029,"description":2030,"extension":59,"issues":2031,"meta":2033,"navigation":65,"path":2035,"seo":2036,"sitemap":2037,"stem":2038,"subtitle":70,"__hash__":2039},"changelog\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart.md","HA Hosted Instance Rolling Restart",[210],{"type":10,"value":2017,"toc":2027},[2018,2021,2024],[13,2019,2020],{},"As part of FlowFuse v2.27.0 release the behavior of Hosted Node-RED instances with HA enabled has been updated to reduce the down time experienced.",[13,2022,2023],{},"Any action that triggers a restart of the Node-RED instance (manually triggered or as part of a Pipeline deploy) will now restart them in sequence rather than in parallel. This means that there should be no down time for this instance.",[13,2025,2026],{},"This feature is available to Enterprise Licensed Self Hosted users and Enterprise tier users of FlowFuse Cloud.",{"title":39,"searchDepth":55,"depth":55,"links":2028},[],"2026-02-12","Hosted Instances with HA enabled will now restart one at a time",[2032],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6532",{"tags":2034},[64],"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart",{"title":2014,"description":2030},{"loc":2035},"changelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","0kIIzmOd6f0D5mksJCVoYetZTd3nLeVuMhosq9j8HyQ",{"id":2041,"title":2042,"authors":2043,"body":2044,"date":2029,"description":2082,"extension":59,"issues":2083,"meta":2085,"navigation":65,"path":2087,"seo":2088,"sitemap":2089,"stem":2090,"subtitle":70,"__hash__":2091},"changelog\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances.md","Restoring snapshots to developer-mode Remote Instances",[8],{"type":10,"value":2045,"toc":2080},[2046,2049,2052,2055,2058,2069,2072],[13,2047,2048],{},"Device Agent version 3.8.0 has been released which brings a significant workflow improvement when editing your flows.",[13,2050,2051],{},"When the ability to remotely edit flows was introduced - known as 'developer mode' - we blocked the ability to push snapshots to a remote instance whilst in this mode. This protection makes sense when you're working on a remote instance, but still need to push updates out to the rest of your fleet through a pipeline deployment - you don't want the deployment from overwriting the work you're in the middle of.",[13,2053,2054],{},"However, there are cases where you want to rollback changes you've been making to a remote instance. Previously that would involve taking the instance out of developer mode, restoring the snapshot, then putting it back into developer mode to continue working. This is a lot of unnecessary steps and not an obvious workflow.",[13,2056,2057],{},"With the new v3.8.0 release of the Device Agent, it is now possible to manually restore snapshots without leaving developer mode:",[251,2059,2060,2063,2066],{},[254,2061,2062],{},"Open the Version History tab for the Remote Instance and switch the Snapshots view",[254,2064,2065],{},"Click on the snapshot you want to use",[254,2067,2068],{},"Click on the restore button in the snapshot sidebar",[13,2070,2071],{},"The existing protection that blocks pipeline-driven deploys of snapshots is still in place.",[13,2073,2074,2078],{},[36,2075],{"alt":2076,"dataZoomable":39,"src":2077},"Restoring a snapshot to a Developer-Mode Remote Instance","\u002Fchangelog\u002F2026\u002F02\u002Fimages\u002Fsnapshot-restore.png",[43,2079,2076],{},{"title":39,"searchDepth":55,"depth":55,"links":2081},[],"A significant workflow improvement introduced by Device Agent v3.8.0",[2084],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6496",{"tags":2086},[64],"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances",{"title":2042,"description":2082},{"loc":2087},"changelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Ee8xXoWht32VTAg-DLNnCRipY5XBfis0PvmMCYYMfdY",{"id":2093,"title":2094,"authors":2095,"body":2096,"date":2141,"description":2142,"extension":59,"issues":2143,"meta":2145,"navigation":65,"path":2147,"seo":2148,"sitemap":2149,"stem":2150,"subtitle":70,"__hash__":2151},"changelog\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor.md","Immersive Mode for Remote Instances",[285],{"type":10,"value":2097,"toc":2139},[2098,2108,2119,2130],[13,2099,2100,2101,2104,2105,227],{},"You can now access ",[150,2102,2103],{},"Immersive Mode"," when working with ",[150,2106,2107],{},"Remote Instances",[13,2109,2110,2111,2114,2115,2118],{},"Immersive Mode gives you ",[150,2112,2113],{},"at-a-glance instance stats"," alongside the editor, while also enabling the ",[150,2116,2117],{},"FlowFuse Expert"," to help speed up development and debugging, especially when you’re working on the edge with remote devices.",[13,2120,2121,2122,2125,2126,2129],{},"Prefer the classic experience? The existing ",[150,2123,2124],{},"plain"," connection flow is still available: clicking the ",[150,2127,2128],{},"Open Editor"," dropdown selector includes an alternative option to be able to open the editor in the non-immersive mode.",[13,2131,2132,2136],{},[36,2133],{"alt":2134,"dataZoomable":39,"src":2135},"Immersive Mode on a Remote Instance","\u002Fchangelog\u002F2026\u002F02\u002Fimages\u002Fremote-instance-immersive.gif",[43,2137,2138],{},"Immersive Mode accessed from a remote instance",{"title":39,"searchDepth":55,"depth":55,"links":2140},[],"2026-02-11","Remote instances can now be accessed in Immersive Mode for a cleaner, distraction-free editing experience",[2144],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6599",{"tags":2146},[64],"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor",{"title":2094,"description":2142},{"loc":2147},"changelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Hf9qhwP7MHSU45sFwLwgjYSYQOhvtchiTWcewR_rFDo",{"id":2153,"title":2154,"authors":2155,"body":2157,"date":2198,"description":2199,"extension":59,"issues":70,"meta":2200,"navigation":65,"path":2202,"seo":2203,"sitemap":2204,"stem":2205,"subtitle":70,"__hash__":2206},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries.md","FlowFuse Expert: Palette Queries",[2156],"steve-mclaughlin",{"type":10,"value":2158,"toc":2196},[2159,2165,2168,2185,2188],[13,2160,2161,2162,227],{},"We are continuing to evolve the FlowFuse Expert by giving it deeper integration into your Node-RED environment. Starting today, the Expert has ",[150,2163,2164],{},"Palette Awareness",[13,2166,2167],{},"You can now ask the Expert about your installed nodes, versions, and available updates without leaving the chat interface or needing to manually input said context. For example:",[251,2169,2170,2173,2176,2179,2182],{},[254,2171,2172],{},"Do I have any nodes installed that can send Emails?",[254,2174,2175],{},"Are my palette nodes up to date?",[254,2177,2178],{},"Are any nodes on my palette disabled?",[254,2180,2181],{},"Can you suggest a node package that would replace this complex function code?",[254,2183,2184],{},"or any question related to your palette.",[13,2186,2187],{},"This is one of several steps we are taking to bring additional context directly into your FlowFuse Expert to augment its capabilities and improve your workflow.",[13,2189,2190,2194],{},[36,2191],{"alt":2192,"dataZoomable":39,"src":2193},"FlowFuse Expert integration with the Palette","\u002Fchangelog\u002F2026\u002F01\u002Fimages\u002Fff-expert-palette-context.gif",[43,2195,2192],{},{"title":39,"searchDepth":55,"depth":55,"links":2197},[],"2026-02-10","The FlowFuse Expert can now answer questions about your Node-RED palette.",{"tags":2201},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries",{"title":2154,"description":2199},{"loc":2202},"changelog\u002F2026\u002F01\u002Fff-expert-palette-queries","JuvwB4wMIQ78hsHsRluGcKmq22iRm4y_HAcOnZ7lGRg",{"id":2208,"title":2209,"authors":2210,"body":2211,"date":2232,"description":2233,"extension":59,"issues":70,"meta":2234,"navigation":65,"path":2236,"seo":2237,"sitemap":2238,"stem":2239,"subtitle":70,"__hash__":2240},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows.md","FlowFuse Expert: Ask about your flows",[2156],{"type":10,"value":2212,"toc":2230},[2213,2216,2219,2227],[13,2214,2215],{},"Need help with a specific flow?",[13,2217,2218],{},"The FlowFuse Expert now has the ability to include your flow selection as context, allowing you to ask specific questions about your logic and configuration.",[13,2220,2221,2225],{},[36,2222],{"alt":2223,"dataZoomable":39,"src":2224},"FlowFuse Expert with flows in context","\u002Fchangelog\u002F2026\u002F01\u002Fimages\u002Fff-expert-flows-in-context.gif",[43,2226,2223],{},[13,2228,2229],{},"We are continuously adding new features to improve your development workflow, with more updates for the FlowFuse Expert on the horizon. We hope this makes your building experience even smoother.",{"title":39,"searchDepth":55,"depth":55,"links":2231},[],"2026-01-30","The FlowFuse Expert can now use your selected flows as context for smarter troubleshooting.",{"tags":2235},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows",{"title":2209,"description":2233},{"loc":2236},"changelog\u002F2026\u002F01\u002Fff-expert-select-flows","B6skbAOgcPHs0DxylzwuqSM1i7lZV76pLSgN-0lWnw8",{"id":2242,"title":2243,"authors":2244,"body":2245,"date":2299,"description":2300,"extension":59,"issues":2301,"meta":2303,"navigation":65,"path":2305,"seo":2306,"sitemap":2307,"stem":2308,"subtitle":70,"__hash__":2309},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers.md","Device Agent Docker Containers updated",[210],{"type":10,"value":2246,"toc":2295},[2247,2250,2253,2262,2265,2269,2283,2287],[13,2248,2249],{},"We have started to see some Node-RED nodes dropping support for NodeJS v18. This is causing problems for users of our Device Agent docker container as that is still based on NodeJS v18.",[13,2251,2252],{},"To help move things forward, with the v3.7.2 release of the Device Agent, we are now publishing separate container images for both v18 and v20 under different tags.",[13,2254,2255,2256,2258,2259,2261],{},"The ",[86,2257,715],{}," tag will continue to point to the NodeJS v18 version for now for backwards compatibility. The next major release of the device agent will update the ",[86,2260,715],{}," tag to a newer NodeJS version - and may require a migration step if you are using the module cache feature. We'll share more details when that release arrives.",[13,2263,2264],{},"With this update, the following tags are now available:",[170,2266,2268],{"id":2267},"nodejs-18","NodeJS 18",[251,2270,2271,2274,2277,2280],{},[254,2272,2273],{},"flowfuse\u002Fdevice-agent:latest",[254,2275,2276],{},"flowfuse\u002Fdevice-agent:latest-18",[254,2278,2279],{},"flowfuse\u002Fdevice-agent:v3.7.2",[254,2281,2282],{},"flowfuse\u002Fdevice-agent:v3.7.2-18",[170,2284,2286],{"id":2285},"nodejs-20","NodeJS 20",[251,2288,2289,2292],{},[254,2290,2291],{},"flowfuse\u002Fdevice-agent:latest-20",[254,2293,2294],{},"flowfuse\u002Fdevice-agent:v3.7.2-20",{"title":39,"searchDepth":55,"depth":55,"links":2296},[2297,2298],{"id":2267,"depth":194,"text":2268},{"id":2285,"depth":194,"text":2286},"2026-01-27","Expanding the available NodeJS versions available",[2302],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Fissues\u002F555",{"tags":2304},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers",{"title":2243,"description":2300},{"loc":2305},"changelog\u002F2026\u002F01\u002Fdevice-agent-containers","EWf2zaFJ8wi-mc4Sosm_b-s6L5SK3j7RFd--lPEN1pk",{"id":2311,"title":2312,"authors":2313,"body":2314,"date":2348,"description":2349,"extension":59,"issues":70,"meta":2350,"navigation":65,"path":2352,"seo":2353,"sitemap":2354,"stem":2355,"subtitle":70,"__hash__":2356},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette.md","FlowFuse Expert: Enhanced Palette Integration",[2156],{"type":10,"value":2315,"toc":2346},[2316,2328,2335,2343],[13,2317,2318,2319,2322,2323,2327],{},"The FlowFuse Expert recently gained the ability to suggest and install ",[150,2320,2321],{},"node packages"," directly within your workflow (see our previous post on ",[26,2324,2326],{"href":2325},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions\u002F","FlowFuse Expert: Integration with Node-RED",").",[13,2329,2330,2331,2334],{},"Today, we've streamlined this experience. The Expert now detects if a suggested node is already present in your instance. Instead of a showing the \"Install\" button, you’ll now see a ",[150,2332,2333],{},"\"Manage\""," button that takes you directly to the Palette Manager.",[13,2336,2337,2341],{},[36,2338],{"alt":2339,"dataZoomable":39,"src":2340},"FlowFuse Expert integration with the Palette Manager","\u002Fchangelog\u002F2026\u002F01\u002Fimages\u002Fff-expert-manage-palette.png",[43,2342,2339],{},[13,2344,2345],{},"This improvement reduces friction when updating or configuring your existing nodes. These workflow integrations are just the beginning of our plans for the FlowFuse Expert. We're excited to see how much time they save you!",{"title":39,"searchDepth":55,"depth":55,"links":2347},[],"2026-01-26","The FlowFuse Expert now detects installed nodes and provides direct links to manage them.",{"tags":2351},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette",{"title":2312,"description":2349},{"loc":2352},"changelog\u002F2026\u002F01\u002Fff-expert-manage-palette","sbIOeviiwnztNLZIiGe_eMhrqrq2S4Xo1M-iC0CO_8I",{"id":2358,"title":2359,"authors":2360,"body":2361,"date":2408,"description":2409,"extension":59,"issues":70,"meta":2410,"navigation":65,"path":2412,"seo":2413,"sitemap":2414,"stem":2415,"subtitle":70,"__hash__":2416},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security.md","FlowFuse Expert: MCP-Powered Insights",[2156],{"type":10,"value":2362,"toc":2404},[2363,2366,2370,2373,2392,2396,2399],[13,2364,2365],{},"FlowFuse Expert Insights just got a little bit better.",[385,2367,2369],{"id":2368},"what-is-flowfuse-expert-insights","What is FlowFuse Expert Insights?",[13,2371,2372],{},"In case you are new to this feature, checkout out some of our previous blog posts:",[251,2374,2375,2381,2387],{},[254,2376,2377],{},[26,2378,2380],{"href":2379},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights\u002F","MCP-Powered Insights",[254,2382,2383],{},[26,2384,2386],{"href":2385},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs\u002F","MCP-Powered Insights with RBACs",[254,2388,2389],{},[26,2390,2391],{"href":2325},"Integration with Node-RED",[385,2393,2395],{"id":2394},"whats-new","What's new?",[13,2397,2398],{},"With this update, the MCP servers you protected behind FlowFuse User Authentication can now be accessed and queried in the FlowFuse Expert too.",[13,2400,2401],{},[43,2402,2403],{},"Note: The FlowFuse Expert Insights feature is currently in Beta. We are actively expanding its capabilities. We would love to hear how you are using MCP to extend your systems.",{"title":39,"searchDepth":55,"depth":55,"links":2405},[2406,2407],{"id":2368,"depth":598,"text":2369},{"id":2394,"depth":598,"text":2395},"2026-01-21","The FlowFuse expert can now access your secured Model Context Protocol (MCP) Tools and Resources",{"tags":2411},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security",{"title":2359,"description":2409},{"loc":2412},"changelog\u002F2026\u002F01\u002Fmcp-security","AXUgm119osr3AxPTsENeQabpxAqTWNUmUChoQylZtSM",{"id":2418,"title":2326,"authors":2419,"body":2420,"date":2452,"description":2453,"extension":59,"issues":70,"meta":2454,"navigation":65,"path":2456,"seo":2457,"sitemap":2458,"stem":2459,"subtitle":70,"__hash__":2460},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions.md",[2156],{"type":10,"value":2421,"toc":2450},[2422,2425,2439,2447],[13,2423,2424],{},"The FlowFuse Expert just got a lot more hands-on with your Node-RED editor:",[251,2426,2427,2433],{},[254,2428,2429,2432],{},[150,2430,2431],{},"Streamlined Node Installation:"," When the Expert suggests a node module, it can now automatically open the Palette Manager and filter for the correct package, leaving you just one click away from installation.",[254,2434,2435,2438],{},[150,2436,2437],{},"Direct Flow Imports:"," When the Expert provides demo flows, you no longer need to copy-paste JSON. The Expert can now inject those flows directly into your editor, ready for deployment.",[13,2440,2441,2445],{},[36,2442],{"alt":2443,"dataZoomable":39,"src":2444},"FlowFuse Expert Install Node","\u002Fchangelog\u002F2026\u002F01\u002Fimages\u002Fff-expert-install-node.gif",[43,2446,2339],{},[13,2448,2449],{},"These workflow integrations are just the start of our plans for the FlowFuse Expert. We’re excited to see how much time these save you!",{"title":39,"searchDepth":55,"depth":55,"links":2451},[],"2026-01-14","The FlowFuse Expert can now help you install nodes and import flows with a single click.",{"tags":2455},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions",{"title":2326,"description":2453},{"loc":2456},"changelog\u002F2026\u002F01\u002Fff-expert-nr-actions","BQua5IDQCXVbtQNXx_uVoWzQrNOley8msS3IdVUo1y4",{"id":2462,"title":2463,"authors":2464,"body":2465,"date":2452,"description":2555,"extension":59,"issues":70,"meta":2556,"navigation":65,"path":2558,"seo":2559,"sitemap":2560,"stem":2561,"subtitle":70,"__hash__":2562},"changelog\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs.md","FlowFuse Expert: MCP-Powered Insights with RBACs",[2156],{"type":10,"value":2466,"toc":2552},[2467,2474,2478,2481,2495,2505,2531,2534,2539,2547],[13,2468,2469,2470,2473],{},"Following on the the introduction of ",[26,2471,2472],{"href":2379},"FlowFuse Expert MCP-Powered Insights"," we have added annotations to the FlowFuse MCP nodes and linked them up with the FlowFuse roles.\nThis permits a level of control over who can access what. This is just a first step, we will be working in the area over the next few iterations.",[385,2475,2477],{"id":2476},"mcp-tools-node","MCP Tools Node",[13,2479,2480],{},"To facilitate a level of role based access control in the Expert, we have leveraged the new Granular RBACs and MCP annotations to introduce 2 means of filtering and control:",[891,2482,2483,2492],{},[254,2484,2485,2486,2491],{},"By ",[26,2487,2490],{"href":2488,"rel":2489},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fconcepts\u002F#application",[30],"application"," - as introduced in FlowFuse 1.5",[254,2493,2494],{},"By pre-defined role level mapping to the annotation hints. For instance, users with a 'Viewer' role will only be exposed to tools marked with the Read Only hint, while Destructive tools are reserved for 'Owners'. The screenshot below indicates more clearly what this mapping is.",[13,2496,2497,2498,2504],{},"To facilitate this, we have the next version of our (MCP Server Nodes)",[1845,2499,2500],{},[26,2501,2502],{"href":2502,"rel":2503},"https:\u002F\u002Fflowfuse.com\u002Fnode-red\u002Fflowfuse\u002Fmcp\u002F",[30]," will introduce the 4 MCP standard annotations:",[251,2506,2507,2513,2519,2525],{},[254,2508,2509,2512],{},[150,2510,2511],{},"Read Only Hint",": Lets the MCP Client know that the tool is read-only and does not modify any data or state. This hint can be used by LLMs to understand that invoking this tool will not have side effects, making it safe for exploratory queries or information retrieval.",[254,2514,2515,2518],{},[150,2516,2517],{},"Destructive Hint",": Lets the MCP Client know that the tool performs destructive actions that may modify or delete data. This hint can be used by LLMs to exercise caution when invoking this tool, as it may have irreversible effects.",[254,2520,2521,2524],{},[150,2522,2523],{},"Idempotent Hint",": Lets the MCP Client know that the tool is idempotent, meaning that multiple invocations with the same parameters will have the same effect as a single invocation. This hint can be used by LLMs to understand that it is safe to retry or repeat calls to this tool without causing unintended side effects.",[254,2526,2527,2530],{},[150,2528,2529],{},"Open World Hint",": Lets the MCP Client know that the tool operates in an open-world context, meaning it may interact with external systems or data sources beyond the immediate environment. This hint can be used by LLMs to understand that invoking this tool may involve uncertainties or dependencies on external factors.",[13,2532,2533],{},"These annotations are not exclusive to FlowFuse or FlowFuse Roles, they also are useful for your own Agents and LLMs.",[13,2535,2536],{},[43,2537,2538],{},"Note: Hints do not enforce behavior. The actual behavior of the tool depends on how it is used in your flows",[13,2540,2541,2545],{},[36,2542],{"alt":2543,"dataZoomable":39,"src":2544},"MCP Server Tool Node with new annotations","\u002Fchangelog\u002F2026\u002F01\u002Fimages\u002Fmcp-annotations.png",[43,2546,2543],{},[13,2548,2549],{},[43,2550,2551],{},"Note: This feature is currently in Beta. We are actively expanding these capabilities and would love to hear how you are using MCP to extend your systems.",{"title":39,"searchDepth":55,"depth":55,"links":2553},[2554],{"id":2476,"depth":598,"text":2477},"You can now limit which user roles see which Model Context Protocol (MCP) tools when querying your MCP servers with the FlowFuse Expert.",{"tags":2557},[64],"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs",{"title":2463,"description":2555},{"loc":2558},"changelog\u002F2026\u002F01\u002Fmcp-rbacs","DoiQx9_QCUBpn_k91u1NHWbYNOA_7tMW0Rt7_8KP9o0",{"id":2564,"title":2565,"authors":2566,"body":2567,"date":2602,"description":2603,"extension":59,"issues":2604,"meta":2606,"navigation":65,"path":2608,"seo":2609,"sitemap":2610,"stem":2611,"subtitle":70,"__hash__":2612},"changelog\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance.md","Scheduled Maintenance Mode",[210],{"type":10,"value":2568,"toc":2600},[2569,2572,2575,2583,2586,2589,2592],[13,2570,2571],{},"Included in the FlowFuse 2.25.0 release is the ability to schedule times and days of the\nweek for Hosted Node-RED instances to upgrade to the latest available version.",[13,2573,2574],{},"This ensures that fixes and security updates are applied promptly.",[13,2576,2577,2581],{},[36,2578],{"alt":2579,"src":2580},"Maintenance Section of Instance Settings","\u002Fchangelog\u002F2025\u002F12\u002Fimages\u002Fscheduled-maintenance.png",[43,2582,2579],{},[13,2584,2585],{},"You can select multiple days of the week and an hour of the day the update will take\nplace. The restart will be targeted in the first 30 minutes of the selected hour.",[13,2587,2588],{},"As well as scheduling upgrades, you can also enable scheduled restarts even if not update\nis available which may be useful to help with ensuring things run smoothly.",[13,2590,2591],{},"Self Hosted users can configure default restart\u002Fupgrade times at a TeamType level,\nFlowFuse Cloud Starter Tier users will have this enabled by default and it will run,\nat weekends.",[13,2593,2594,2598],{},[36,2595],{"alt":2596,"src":2597},"TeamType Scheduled Maintenance Settings","\u002Fchangelog\u002F2025\u002F12\u002Fimages\u002Fscheduled-maintenance-admin.png",[43,2599,2596],{},{"title":39,"searchDepth":55,"depth":55,"links":2601},[],"2025-12-19","Schedule time and day of the week to apply Node-RED updates",[2605],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5554",{"tags":2607},[64],"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance",{"title":2565,"description":2603},{"loc":2608},"changelog\u002F2025\u002F12\u002Fscheduled-maintenance","kPqcwG_1H7gmh-gLhZV8wBGt4-k_17cgarbIuzu1U5M",{"id":2614,"title":2615,"authors":2616,"body":2617,"date":2684,"description":2685,"extension":59,"issues":70,"meta":2686,"navigation":65,"path":2688,"seo":2689,"sitemap":2690,"stem":2691,"subtitle":70,"__hash__":2692},"changelog\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights.md","FlowFuse Expert: Now with MCP-Powered Insights",[2156],{"type":10,"value":2618,"toc":2680},[2619,2627,2631,2634,2638,2664,2667,2676],[13,2620,2621,2622,2626],{},"Recently, we introduced ",[26,2623,2625],{"href":2624},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes\u002F","MCP Server nodes"," which gave you the ability to infuse your Node-RED flows and data with AI. Today, we have given the FlowFuse Expert new powers by adding support for Model Context Protocol (MCP). This allows you to interact directly with your instances, tools, and data.",[385,2628,2630],{"id":2629},"bridging-the-gap-between-ai-and-your-data","Bridging the Gap Between AI and Your Data",[13,2632,2633],{},"By switching to the new Insights mode, the Expert gains the ability to use the MCP tools and resources you’ve built using FlowFuse MCP Server Nodes. This means you can now ask the Expert to analyze real-time data from your flows, query external databases, or trigger specific actions across your infrastructure.",[385,2635,2637],{"id":2636},"how-to-get-started","How to get started:",[251,2639,2640,2646,2652,2658],{},[254,2641,2642,2645],{},[150,2643,2644],{},"Deploy MCP Nodes",": Add MCP Tools or Resources to your Node-RED flows using our MCP Server nodes.",[254,2647,2648,2651],{},[150,2649,2650],{},"Switch to Insights",": Open the FlowFuse Expert interface and use the Mode Selector to switch from \"Chat\" to \"Insights.\"",[254,2653,2654,2657],{},[150,2655,2656],{},"Select your Server",": Choose the MCP Server you want to include in your session.",[254,2659,2660,2663],{},[150,2661,2662],{},"Gain Insights",": Ask questions about your live process data, system status, or connected databases.",[13,2665,2666],{},"Give it a try and see what your data has to tell you!",[13,2668,2669,2673],{},[36,2670],{"alt":2671,"dataZoomable":39,"src":2672},"FlowFuse Expert Insights","\u002Fchangelog\u002F2025\u002F12\u002Fimages\u002Fff-expert-mcp-demo.gif",[43,2674,2675],{},"Demonstrating FlowFuse Expert Insights",[13,2677,2678],{},[43,2679,2551],{},{"title":39,"searchDepth":55,"depth":55,"links":2681},[2682,2683],{"id":2629,"depth":598,"text":2630},{"id":2636,"depth":598,"text":2637},"2025-11-19","Connect FlowFuse Expert to your own tools and data using the Model Context Protocol (MCP).",{"tags":2687},[64],"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights",{"title":2615,"description":2685},{"loc":2688},"changelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","hx3pbMMYZ2j2-0Sfr2F7F2y_6J5Woc4gg6YTxCEkBp0",{"id":2694,"title":2695,"authors":2696,"body":2697,"date":2716,"description":2717,"extension":59,"issues":70,"meta":2718,"navigation":65,"path":2720,"seo":2721,"sitemap":2722,"stem":2723,"subtitle":70,"__hash__":2724},"changelog\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version.md","Node.js v20 Minimum Version Requirement",[285],{"type":10,"value":2698,"toc":2714},[2699,2705,2708],[13,2700,2701,2704],{},[150,2702,2703],{},"FlowFuse v2.24.0 requires Node.js v20 or higher."," If you are running an older version, you will need to upgrade Node.js before updating FlowFuse.",[13,2706,2707],{},"Node.js v18 reached end of life in April 2025 and no longer receives security updates. This change ensures FlowFuse continues to run on a supported and secure runtime.",[13,2709,2710,2711,227],{},"To check your current version, run ",[86,2712,2713],{},"node --version",{"title":39,"searchDepth":55,"depth":55,"links":2715},[],"2025-11-11","Minimum Node.js version bumped to v20 and above",{"tags":2719},[64],"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version",{"title":2695,"description":2717},{"loc":2720},"changelog\u002F2025\u002F11\u002Fminimum-nodejs-version","SArVG9y6o5mJrWKl7R_o3ZsKJPTRMWi-dSa1ks3kR0Q",{"id":2726,"title":2727,"authors":2728,"body":2730,"date":2764,"description":2765,"extension":59,"issues":2766,"meta":2768,"navigation":65,"path":2770,"seo":2771,"sitemap":2772,"stem":2773,"subtitle":70,"__hash__":2774},"changelog\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update.md","FlowFuse Expert Update",[2729],"greg-stoutenburg",{"type":10,"value":2731,"toc":2762},[2732,2735,2738,2741,2744,2753],[13,2733,2734],{},"The FlowFuse Expert just got a major improvement: you can now start a conversation on the flowfuse.com homepage and continue it inside of FlowFuse and the Node-RED editor!",[13,2736,2737],{},"Now, when you use the Expert, you can bring your application-building instructions with you as you navigate.",[13,2739,2740],{},"This work involved major and important changes to the Expert UI, and brings us even closer to being able to build Node-RED flows using natural language inputs.",[13,2742,2743],{},"Give it a try!",[13,2745,2746,2750],{},[36,2747],{"alt":2748,"src":2749},"Option to continue chat in FlowFuse","\u002Fchangelog\u002F2025\u002F11\u002Fimages\u002Fcontinue.png",[43,2751,2752],{},"Demo of option to continue chat in FlowFuse",[13,2754,2755,2759],{},[36,2756],{"alt":2757,"src":2758},"In-App Expert UI","\u002Fchangelog\u002F2025\u002F11\u002Fimages\u002Fin-app.png",[43,2760,2761],{},"Here is the in-app UI of the FlowFuse Expert",{"title":39,"searchDepth":55,"depth":55,"links":2763},[],"2025-11-07","FlowFuse Expert Now Available In-App",[2767],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6139",{"tags":2769},[64],"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update",{"title":2727,"description":2765},{"loc":2770},"changelog\u002F2025\u002F11\u002Fff-expert-update","JDD0O1IS1_xvqp-9c_VDAF7rFP3lI5WG4-hocQTHsZU",{"id":2776,"title":2777,"authors":2778,"body":2779,"date":2800,"description":2801,"extension":59,"issues":70,"meta":2802,"navigation":65,"path":2804,"seo":2805,"sitemap":2806,"stem":2807,"subtitle":70,"__hash__":2808},"changelog\u002Fchangelog\u002F2025\u002F11\u002Fsso-session.md","SSO control over Session life",[210],{"type":10,"value":2780,"toc":2798},[2781,2784,2792,2795],[13,2782,2783],{},"Customers on FlowFuse Cloud can now request custom Session Life times and Idle times. This allows the default times to be adjusted to match any in house policies that may be in place.",[13,2785,2786,2790],{},[36,2787],{"alt":2788,"src":2789},"SSO Session Expiry and Idle settings","\u002Fchangelog\u002F2025\u002F11\u002Fimages\u002Fsso-expiry-idle.png",[43,2791,2788],{},[13,2793,2794],{},"For existing FlowFuse Cloud customers please contact support if you would like to make changes to you existing configuration.",[13,2796,2797],{},"This will be available to Self Hosted customers in v2.24.0",{"title":39,"searchDepth":55,"depth":55,"links":2799},[],"2025-11-06","Individual SSO profiles can now override Session life and idle time",{"tags":2803},[64],"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session",{"title":2777,"description":2801},{"loc":2804},"changelog\u002F2025\u002F11\u002Fsso-session","NWVeR3u_H0irKKZhwKyRDMvTZm_rIheH_6a1cfbJj-Y",{"id":2810,"title":2811,"authors":2812,"body":2813,"date":2837,"description":2838,"extension":59,"issues":2839,"meta":2841,"navigation":65,"path":2843,"seo":2844,"sitemap":2845,"stem":2846,"subtitle":70,"__hash__":2847},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment.md","Easier Access to Bulk Device Group Management",[285],{"type":10,"value":2814,"toc":2835},[2815,2818,2821,2824],[13,2816,2817],{},"Managing device groups for multiple Remote Instances is now easier to handle. Bulk management already existed but was\ndifficult to use efficiently at larger scale.",[13,2819,2820],{},"This update refines that process. You can select multiple Remote Instances from the team or application remote instances\npages and bulk assign them to device groups with fewer steps.",[13,2822,2823],{},"The improved workflow reduces friction when organizing devices by location, environment, or function.",[13,2825,2826,2830,2832],{},[36,2827],{"alt":2828,"dataZoomable":39,"src":2829},"Bulk Device Group Management Interface","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fbulk-assign-device-groups.gif",[1107,2831],{},[43,2833,2834],{},"Bulk Device Group Management showing multi-select capabilities and group assignment options",{"title":39,"searchDepth":55,"depth":55,"links":2836},[],"2025-10-28","Bulk device group management is now more accessible, with clearer controls and faster organization of multiple Remote Instances.",[2840],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6156",{"tags":2842},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment",{"title":2811,"description":2838},{"loc":2843},"changelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","4x_weJnUpVxJIKzLr_lhbTS0iE69R2ELE05CBYMUev0",{"id":2849,"title":2850,"authors":2851,"body":2852,"date":2837,"description":2862,"extension":59,"issues":2863,"meta":2865,"navigation":65,"path":2867,"seo":2868,"sitemap":2869,"stem":2870,"subtitle":70,"__hash__":2871},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications.md","Duplicate Instances Across Different Applications",[285],{"type":10,"value":2853,"toc":2860},[2854,2857],[13,2855,2856],{},"As of today, you can now duplicate a hosted instance into a different application within your team.",[13,2858,2859],{},"It is a small (but important) improvement that just just makes things that little bit easier.",{"title":39,"searchDepth":55,"depth":55,"links":2861},[],"Instance duplication now works across applications, allowing you to copy existing instances to different applications within your team.",[2864],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5785",{"tags":2866},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications",{"title":2850,"description":2862},{"loc":2867},"changelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Y7fVbPFBT_5qSMFHYkBpfYoGHSuT8JfhmE948yf42M4",{"id":2873,"title":2874,"authors":2875,"body":2876,"date":2965,"description":2966,"extension":59,"issues":2967,"meta":2969,"navigation":65,"path":2971,"seo":2972,"sitemap":2973,"stem":2974,"subtitle":70,"__hash__":2975},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation.md","Import flows during instance creation",[285],{"type":10,"value":2877,"toc":2962},[2878,2881,2884,2887,2907,2910,2913,2917,2920,2946,2949,2952],[13,2879,2880],{},"Getting started with FlowFuse just became easier! When creating a new Node-RED instance, you can now import your existing flows directly during the setup process.",[13,2882,2883],{},"This new capability allows you to jumpstart your FlowFuse journey by bringing in flows you've already developed, whether they're from a local Node-RED installation, exported from another system, or shared by a colleague.",[13,2885,2886],{},"The import process is flexible and user-friendly:",[251,2888,2889,2895,2901],{},[254,2890,2891,2894],{},[150,2892,2893],{},"File upload",": Simply select and upload a JSON file containing your flows",[254,2896,2897,2900],{},[150,2898,2899],{},"Direct paste",": Copy and paste flow JSON directly into a text area",[254,2902,2903,2906],{},[150,2904,2905],{},"Live preview",": See your flows rendered in real-time as you import them",[13,2908,2909],{},"The flows import step seamlessly integrates with the existing multi-step instance creation workflow. You can choose to start with a blueprint from our library or import your own flows - giving you multiple pathways to get productive quickly.",[13,2911,2912],{},"This enhancement is particularly valuable for teams looking to migrate existing Node-RED projects to FlowFuse or developers who want to quickly prototype with flows they've developed elsewhere.",[170,2914,2916],{"id":2915},"important-considerations","Important considerations",[13,2918,2919],{},"When importing flows, keep these key points in mind:",[251,2921,2922,2928,2934,2940],{},[254,2923,2924,2927],{},[150,2925,2926],{},"Flow validation",": Imported flows aren't checked for validity, so invalid nodes may prevent your instance from starting",[254,2929,2930,2933],{},[150,2931,2932],{},"Third-party nodes",": External nodes aren't installed automatically but can be added once the instance is running",[254,2935,2936,2939],{},[150,2937,2938],{},"Credentials and secrets",": These aren't imported with flows but can be reconfigured after deployment",[254,2941,2942,2945],{},[150,2943,2944],{},"Environment variables",": Any required variables must be manually added to your environment after setup",[13,2947,2948],{},"Always verify the reliability of imported flows and avoid copying flows from untrusted sources.",[13,2950,2951],{},"To try it out, simply create a new instance and look for the new \"Flows\" step in the creation wizard!",[13,2953,2954,2958,2960],{},[36,2955],{"alt":2956,"dataZoomable":39,"src":2957},"Demo importing flows when creating a Hosted Instance","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fimport-flows-on-instance-creation.png",[1107,2959],{},[43,2961,2956],{},{"title":39,"searchDepth":55,"depth":55,"links":2963},[2964],{"id":2915,"depth":194,"text":2916},"2025-10-21","Making it easier to get started by importing existing Node-RED flows when creating new instances",[2968],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5751",{"tags":2970},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation",{"title":2874,"description":2966},{"loc":2971},"changelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","nnMva01devKZAskYQC8QaMtE7ELw7gtQX367L6PXklI",{"id":2977,"title":2978,"authors":2979,"body":2980,"date":2965,"description":3001,"extension":59,"issues":3002,"meta":3004,"navigation":65,"path":3006,"seo":3007,"sitemap":3008,"stem":3009,"subtitle":70,"__hash__":3010},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management.md","Device Group Management from Settings Page",[285],{"type":10,"value":2981,"toc":2999},[2982,2985,2988],[13,2983,2984],{},"Managing which device group your Remote Instance belong to just got a easier. Previously, if you wanted to move a device to a different group, you had to identify the group the Remote Instance belongs to, remove it, then find the group to assign it to, edit that group and add it. This was not optimal.",[13,2986,2987],{},"With this update, you can now see which group a Remote Instance belongs to directly from the overview page, and easily reassign it to a different group from the settings page without the hassle of searching through your entire group structure.",[13,2989,2990,2994,2996],{},[36,2991],{"alt":2992,"dataZoomable":39,"src":2993},"Device Group Management Interface","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fsettings-page-device-group-management.png",[1107,2995],{},[43,2997,2998],{},"Device Group Management Interface showing current group and reassignment options",{"title":39,"searchDepth":55,"depth":55,"links":3000},[],"Easily manage device groups directly from the Remote Instance settings page",[3003],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6006",{"tags":3005},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management",{"title":2978,"description":3001},{"loc":3006},"changelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","B2oRLkmCm5U9tLvkKM5optAVeMLQySrjRjNzRqAgh0w",{"id":3012,"title":3013,"authors":3014,"body":3015,"date":3148,"description":3149,"extension":59,"issues":70,"meta":3150,"navigation":65,"path":3152,"seo":3153,"sitemap":3154,"stem":3155,"subtitle":70,"__hash__":3156},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes.md","FlowFuse AI Nodes",[284],{"type":10,"value":3016,"toc":3142},[3017,3023,3027,3030,3033,3048,3052,3055,3081,3084,3087,3090,3097,3105,3109,3112,3122,3132],[13,3018,3019,3020,3022],{},"We’re excited to introduce ",[150,3021,3013],{},", a new contrib package that brings the ONNX Runtime to Node-RED.",[385,3024,3026],{"id":3025},"what-is-onnx","What is ONNX?",[13,3028,3029],{},"ONNX (Open Neural Network Exchange) is an open format built to represent machine learning models. It provides an interoperable framework for AI developers to use models across different frameworks and tools.",[13,3031,3032],{},"Sounds great, right? So what does this mean for you?",[13,3034,3035,3036,3041,3042,3047],{},"You can now run pre-trained machine learning models directly within your Node-RED flows using the new FlowFuse AI Nodes.\nThere are hundreds of pre-trained models available in the ",[26,3037,3040],{"href":3038,"rel":3039},"https:\u002F\u002Fonnx.ai\u002Fmodels\u002F",[30],"ONNX Model Zoo"," or from ",[26,3043,3046],{"href":3044,"rel":3045},"https:\u002F\u002Fhuggingface.co\u002Fmodels?library=transformers.js,onnx&sort=trending",[30],"Hugging Face",", covering a wide range of applications including image classification, object detection, natural language processing, Text to Speech, and more.",[385,3049,3051],{"id":3050},"what-can-you-do-with-flowfuse-ai-nodes","What can you do with FlowFuse AI Nodes?",[13,3053,3054],{},"In this first release, the FlowFuse AI Nodes package includes the following nodes:",[251,3056,3057,3063,3069,3075],{},[254,3058,3059,3062],{},[150,3060,3061],{},"ONNX Inference Node",": A bare node to run any model (including your own trained ONNX models). Just upload the model file and feed in the input data to get predictions.",[254,3064,3065,3068],{},[150,3066,3067],{},"Image Classification Node",": Classify images using pre-trained models like MobileNet, ResNet, or even use your own.",[254,3070,3071,3074],{},[150,3072,3073],{},"Object Detection Node",": Detect objects in images using models like YOLOv5, SSD, or your own.",[254,3076,3077,3080],{},[150,3078,3079],{},"Image Depth Estimation Node",": Estimate depth information from images.",[13,3082,3083],{},"With FlowFuse AI Nodes, you can easily integrate ONNX models into your Node-RED flows, enabling powerful AI capabilities without the need for extensive coding or machine learning expertise.",[385,3085,3086],{"id":2636},"How to Get Started",[13,3088,3089],{},"FlowFuse customers can install the new AI nodes today via the Node-RED Palette Manager from the FlowFuse Nodes catalog",[13,3091,3092,3093,3096],{},"We have included example flows directly inside the package to help you get started quickly.\nJust hit ",[86,3094,3095],{},"CTRL-I"," in the Node-RED editor to import the example flows from the FlowFuse AI Nodes package.",[13,3098,3099,3100],{},"Additionally, we have created a blog post detailing how you can train a simple image classification model to accompany the advanced example flow included in the package. You can read all about it here: ",[26,3101,3104],{"href":3102,"rel":3103},"https:\u002F\u002Fflowfuse.com\u002Fblog\u002F2025\u002F10\u002Fcustom-onnx-model\u002F",[30],"Deploy Custom-Trained AI Models: Using ONNX with Node-RED and FlowFuse",[385,3106,3108],{"id":3107},"screenshots","Screenshots",[13,3110,3111],{},"Here are a selection of screenshots of the built-in demo flows in action",[13,3113,3114,3118,3120],{},[36,3115],{"alt":3116,"dataZoomable":39,"src":3117},"Running your own custom trained ONNX Model","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fai-nodes-onnx-node-custom-model.png",[1107,3119],{},[43,3121,3116],{},[13,3123,3124,3128,3130],{},[36,3125],{"alt":3126,"dataZoomable":39,"src":3127},"Using a Text-to-Speech-model","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fai-nodes-onnx-node-tts.png",[1107,3129],{},[43,3131,3126],{},[13,3133,3134,3138,3140],{},[36,3135],{"alt":3136,"dataZoomable":39,"src":3137},"Performing Image Depth Estimation","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fai-nodes-image-depth-node.png",[1107,3139],{},[43,3141,3136],{},{"title":39,"searchDepth":55,"depth":55,"links":3143},[3144,3145,3146,3147],{"id":3025,"depth":598,"text":3026},{"id":3050,"depth":598,"text":3051},{"id":2636,"depth":598,"text":3086},{"id":3107,"depth":598,"text":3108},"2025-10-15","New FlowFuse nodes for ONNX Models running Inference in your flows",{"tags":3151},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes",{"title":3013,"description":3149},{"loc":3152},"changelog\u002F2025\u002F10\u002Fonnx-nodes","4GUsrcn1jmzr3EZE5Z4UVDSbePt3-IBk6xn4PJ4eg1Q",{"id":3158,"title":3159,"authors":3160,"body":3161,"date":3247,"description":3248,"extension":59,"issues":70,"meta":3249,"navigation":65,"path":3251,"seo":3252,"sitemap":3253,"stem":3254,"subtitle":70,"__hash__":3255},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes.md","FlowFuse MCP Server Nodes",[284],{"type":10,"value":3162,"toc":3241},[3163,3168,3179,3183,3189,3193,3196,3198,3208,3215,3221,3225],[13,3164,3019,3165,3167],{},[150,3166,3159],{},", a new contrib package that brings MCP Tools, Resources, and Prompts straight into Node-RED. With just a few nodes, you can design custom MCP-powered automations, connect dynamic resources, and return responses seamlessly in your flows. Whether you’re prototyping or extending integrations, these nodes make it faster than ever to put MCP to work in your applications.",[13,3169,3170,3171,3174,3175,3178],{},"Over the coming weeks, we’ll share use cases and demos to inspire you, but in the meantime, we’ve included some sample flows you can access directly in Node-RED via the import menu (",[86,3172,3173],{},"CTRL","+",[86,3176,3177],{},"I",") and some additional links below.",[385,3180,3182],{"id":3181},"what-is-mcp","What is MCP?",[13,3184,2255,3185,3188],{},[150,3186,3187],{},"Model Context Protocol (MCP)"," is an emerging open standard for connecting AI models with tools and data sources in a structured way. It defines how prompts, resources, and responses should be exchanged, making it easier to build reliable and reusable AI-powered workflows.",[385,3190,3192],{"id":3191},"why-is-mcp-important","Why is MCP important?",[13,3194,3195],{},"As AI adoption grows, developers need consistent ways to integrate models into real-world systems. MCP helps standardize this process, reducing boilerplate and ensuring interoperability across tools and platforms. With Node-RED support, FlowFuse makes it easier than ever for developers to experiment with MCP, build production-ready flows, and unlock the potential of AI-driven automation.",[385,3197,3108],{"id":3107},[13,3199,3200,3204,3206],{},[36,3201],{"alt":3202,"src":3203,"dataZoomable":39},"New MCP Nodes","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fmcp-nodes.png",[1107,3205],{},[43,3207,3202],{},[13,3209,3210,3211,3214],{},"FlowFuse customers can install the MCP Server nodes today via the Node-RED Palette Manager from the ",[150,3212,3213],{},"FlowFuse Nodes"," catalog",[13,3216,3217],{},[36,3218],{"alt":3219,"src":3220},"alt text","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fmcp-nodes-in-catalog.png",[385,3222,3224],{"id":3223},"additional-links","Additional links",[251,3226,3227,3234],{},[254,3228,3229],{},[26,3230,3233],{"href":3231,"rel":3232},"https:\u002F\u002Fflowfuse.com\u002Fblog\u002F2025\u002F10\u002Fbuilding-mcp-server-using-flowfuse\u002F",[30],"Blog article",[254,3235,3236],{},[26,3237,3240],{"href":3238,"rel":3239},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=troUvaF8V68",[30],"Youtube demonstration video",{"title":39,"searchDepth":55,"depth":55,"links":3242},[3243,3244,3245,3246],{"id":3181,"depth":598,"text":3182},{"id":3191,"depth":598,"text":3192},{"id":3107,"depth":598,"text":3108},{"id":3223,"depth":598,"text":3224},"2025-10-14","New FlowFuse nodes for creating MCP Server Tools, Resources and Prompts",{"tags":3250},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes",{"title":3159,"description":3248},{"loc":3251},"changelog\u002F2025\u002F10\u002Fmcp-nodes","wbJxsGkfhHgpEL5J1JddQZ_kHxFj9LSOmMb0UfNfzx8",{"id":3257,"title":3258,"authors":3259,"body":3260,"date":3289,"description":3290,"extension":59,"issues":3291,"meta":3293,"navigation":65,"path":3295,"seo":3296,"sitemap":3297,"stem":3298,"subtitle":70,"__hash__":3299},"changelog\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac.md","Application-level access control for Enterprise teams",[8],{"type":10,"value":3261,"toc":3287},[3262,3265,3268,3271,3274,3277],[13,3263,3264],{},"One of the super-powers FlowFuse brings is its role-based access control that gets applied across the team. This allows teams to have users with different levels of access to the Node-RED instances - from full editor access, to read-only access, to only being able to access the dashboards the instances create.",[13,3266,3267],{},"We've pushed this one step further today for Enterprise teams, allowing them to set a user's role on a per-Application basis. This finer-grained control gives teams more flexibility in how they can secure their resources.",[13,3269,3270],{},"For example, a team could create an Application dedicated to their production systems, with a limited set of users able to make changes - whilst having a Development application that is accessible to a broader group of user.",[13,3272,3273],{},"The roles for an application can be modified under the 'User Access' section of its settings. It shows what roles each user has for the application and where any application-specific overrides have been set. Here you can see I've reduced Ben to a Dashboard role for this application - sorry Ben!",[13,3275,3276],{},"As with managing the top level roles in a team, only Team Owners are able to modify the roles within an application.",[13,3278,3279,3283,3285],{},[36,3280],{"alt":3281,"dataZoomable":39,"src":3282},"Application RBAC Settings","\u002Fchangelog\u002F2025\u002F10\u002Fimages\u002Fapplication-rbac.png",[1107,3284],{},[43,3286,3281],{},{"title":39,"searchDepth":55,"depth":55,"links":3288},[],"2025-10-08","Giving you finer-grained control over who can do what in your team",[3292],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F3093",{"tags":3294},[64],"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac",{"title":3258,"description":3290},{"loc":3295},"changelog\u002F2025\u002F10\u002Fapplication-level-rbac","KRwcjvoGm4cx7wLffSgp3X2ltvFJRlqIwebmDmNOybA",{"id":3301,"title":3302,"authors":3303,"body":3304,"date":3597,"description":3598,"extension":59,"issues":3599,"meta":3601,"navigation":65,"path":3603,"seo":3604,"sitemap":3605,"stem":3606,"subtitle":70,"__hash__":3607},"changelog\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard.md","Allow SSO groups to be shared with the Node-RED Dashboard",[210],{"type":10,"value":3305,"toc":3595},[3306,3309,3316,3576,3582,3589,3592],[13,3307,3308],{},"A new flag has been added to the SAML SSO configuration to allow a user's group membership to be included in the profile information included when FlowFuse Authentication is used with the Node-RED Dashboard v2.",[13,3310,3311,3312,3315],{},"Shown here is the content of the ",[86,3313,3314],{},"_client"," object attached to messages generated by the Dashboard nodes.",[765,3317,3321],{"className":3318,"code":3319,"language":3320,"meta":39,"style":39},"language-json shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","{\n    \"user\": {\n        \"username\": \"ben-example_com\",\n        \"email\": \"ben@example.com\",\n        \"image\": \"https:\u002F\u002Fforge.example.com\u002Favatar\u002FYmVu\",\n        \"name\": \"Ben\",\n        \"userId\": \"r3VG59G85J\",\n        \"role\": \"owner\",\n        \"SSOGroups\": [\n            \"FlowFuse\",\n            \"ff-development-owner\",\n            \"test_ff-development-owner_test\"\n        ]\n    },\n    \"socketId\": \"NA7eDLuWbR6wmCpSAAAF\",\n    \"socketIp\": \"192.168.1.56\"\n}\n","json",[86,3322,3323,3328,3345,3367,3387,3407,3427,3447,3467,3482,3495,3507,3518,3524,3530,3551,3570],{"__ignoreMap":39},[1845,3324,3325],{"class":1847,"line":1848},[1845,3326,3327],{"class":1871},"{\n",[1845,3329,3330,3333,3337,3340,3342],{"class":1847,"line":194},[1845,3331,3332],{"class":1871},"    \"",[1845,3334,3336],{"class":3335},"spNyl","user",[1845,3338,3339],{"class":1871},"\"",[1845,3341,1920],{"class":1871},[1845,3343,3344],{"class":1871}," {\n",[1845,3346,3347,3350,3352,3354,3356,3359,3362,3364],{"class":1847,"line":598},[1845,3348,3349],{"class":1871},"        \"",[1845,3351,908],{"class":1851},[1845,3353,3339],{"class":1871},[1845,3355,1920],{"class":1871},[1845,3357,3358],{"class":1871}," \"",[1845,3360,3361],{"class":1855},"ben-example_com",[1845,3363,3339],{"class":1871},[1845,3365,3366],{"class":1871},",\n",[1845,3368,3369,3371,3374,3376,3378,3380,3383,3385],{"class":1847,"line":55},[1845,3370,3349],{"class":1871},[1845,3372,3373],{"class":1851},"email",[1845,3375,3339],{"class":1871},[1845,3377,1920],{"class":1871},[1845,3379,3358],{"class":1871},[1845,3381,3382],{"class":1855},"ben@example.com",[1845,3384,3339],{"class":1871},[1845,3386,3366],{"class":1871},[1845,3388,3389,3391,3394,3396,3398,3400,3403,3405],{"class":1847,"line":1956},[1845,3390,3349],{"class":1871},[1845,3392,3393],{"class":1851},"image",[1845,3395,3339],{"class":1871},[1845,3397,1920],{"class":1871},[1845,3399,3358],{"class":1871},[1845,3401,3402],{"class":1855},"https:\u002F\u002Fforge.example.com\u002Favatar\u002FYmVu",[1845,3404,3339],{"class":1871},[1845,3406,3366],{"class":1871},[1845,3408,3409,3411,3414,3416,3418,3420,3423,3425],{"class":1847,"line":1964},[1845,3410,3349],{"class":1871},[1845,3412,3413],{"class":1851},"name",[1845,3415,3339],{"class":1871},[1845,3417,1920],{"class":1871},[1845,3419,3358],{"class":1871},[1845,3421,3422],{"class":1855},"Ben",[1845,3424,3339],{"class":1871},[1845,3426,3366],{"class":1871},[1845,3428,3429,3431,3434,3436,3438,3440,3443,3445],{"class":1847,"line":1977},[1845,3430,3349],{"class":1871},[1845,3432,3433],{"class":1851},"userId",[1845,3435,3339],{"class":1871},[1845,3437,1920],{"class":1871},[1845,3439,3358],{"class":1871},[1845,3441,3442],{"class":1855},"r3VG59G85J",[1845,3444,3339],{"class":1871},[1845,3446,3366],{"class":1871},[1845,3448,3450,3452,3455,3457,3459,3461,3463,3465],{"class":1847,"line":3449},8,[1845,3451,3349],{"class":1871},[1845,3453,3454],{"class":1851},"role",[1845,3456,3339],{"class":1871},[1845,3458,1920],{"class":1871},[1845,3460,3358],{"class":1871},[1845,3462,245],{"class":1855},[1845,3464,3339],{"class":1871},[1845,3466,3366],{"class":1871},[1845,3468,3470,3472,3475,3477,3479],{"class":1847,"line":3469},9,[1845,3471,3349],{"class":1871},[1845,3473,3474],{"class":1851},"SSOGroups",[1845,3476,3339],{"class":1871},[1845,3478,1920],{"class":1871},[1845,3480,3481],{"class":1871}," [\n",[1845,3483,3485,3488,3491,3493],{"class":1847,"line":3484},10,[1845,3486,3487],{"class":1871},"            \"",[1845,3489,3490],{"class":1855},"FlowFuse",[1845,3492,3339],{"class":1871},[1845,3494,3366],{"class":1871},[1845,3496,3498,3500,3503,3505],{"class":1847,"line":3497},11,[1845,3499,3487],{"class":1871},[1845,3501,3502],{"class":1855},"ff-development-owner",[1845,3504,3339],{"class":1871},[1845,3506,3366],{"class":1871},[1845,3508,3510,3512,3515],{"class":1847,"line":3509},12,[1845,3511,3487],{"class":1871},[1845,3513,3514],{"class":1855},"test_ff-development-owner_test",[1845,3516,3517],{"class":1871},"\"\n",[1845,3519,3521],{"class":1847,"line":3520},13,[1845,3522,3523],{"class":1871},"        ]\n",[1845,3525,3527],{"class":1847,"line":3526},14,[1845,3528,3529],{"class":1871},"    },\n",[1845,3531,3533,3535,3538,3540,3542,3544,3547,3549],{"class":1847,"line":3532},15,[1845,3534,3332],{"class":1871},[1845,3536,3537],{"class":3335},"socketId",[1845,3539,3339],{"class":1871},[1845,3541,1920],{"class":1871},[1845,3543,3358],{"class":1871},[1845,3545,3546],{"class":1855},"NA7eDLuWbR6wmCpSAAAF",[1845,3548,3339],{"class":1871},[1845,3550,3366],{"class":1871},[1845,3552,3554,3556,3559,3561,3563,3565,3568],{"class":1847,"line":3553},16,[1845,3555,3332],{"class":1871},[1845,3557,3558],{"class":3335},"socketIp",[1845,3560,3339],{"class":1871},[1845,3562,1920],{"class":1871},[1845,3564,3358],{"class":1871},[1845,3566,3567],{"class":1855},"192.168.1.56",[1845,3569,3517],{"class":1871},[1845,3571,3573],{"class":1847,"line":3572},17,[1845,3574,3575],{"class":1871},"}\n",[13,3577,3578,3579,3581],{},"The new key ",[86,3580,3474],{}," includes the list of Groups passed to the SSO configuration by the SAML backend and can be used by the Dashboard to control what information is shown to the user.",[13,3583,3584,3585],{},"More details about how to create mutli-user Node-RED Dashboards can be found ",[26,3586,226],{"href":3587,"rel":3588},"https:\u002F\u002Fdashboard.flowfuse.com\u002Fuser\u002Fmulti-tenancy",[30],[13,3590,3591],{},"SSO is available to Enterprise teams on FlowFuse Cloud. Contact support if you would like this feature to be enable for your team.",[1993,3593,3594],{},"html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html pre.shiki code .spNyl, html code.shiki .spNyl{--shiki-light:#9C3EDA;--shiki-default:#C792EA;--shiki-dark:#C792EA}html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":39,"searchDepth":55,"depth":55,"links":3596},[],"2025-09-25","SAML Group information included in the FlowFuse Authentication information passed to the Node-RED Dashboard",[3600],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5902",{"tags":3602},[64],"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard",{"title":3302,"description":3598},{"loc":3603},"changelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","y2Fqv_bBVzaAnoeq5U9OfETfEx5_VYG9zLyx2tzmuuA",{"id":3609,"title":3610,"authors":3611,"body":3612,"date":3678,"description":3679,"extension":59,"issues":70,"meta":3680,"navigation":65,"path":3682,"seo":3683,"sitemap":3684,"stem":3685,"subtitle":70,"__hash__":3686},"changelog\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent.md","No more @flowforge\u002Fflowforge-device-agent releases",[210],{"type":10,"value":3613,"toc":3676},[3614,3624,3627,3634,3640,3646,3653,3658,3664,3669],[13,3615,3616,3617,3620,3621,227],{},"When we changed company name from FlowForge to FlowFuse we continued to publish the Device Agent under the old package name ",[86,3618,3619],{},"@flowforge\u002Fflowforge-device-agent"," as well as the new package name ",[86,3622,3623],{},"@flowfuse\u002Fdevice-agent",[13,3625,3626],{},"The current version 3.6.1 will be last release under the old package name.",[13,3628,3629,3630,227],{},"The latest version can be found on npmjs.org ",[26,3631,226],{"href":3632,"rel":3633},"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@flowfuse\u002Fdevice-agent",[30],[13,3635,3636,3637,3639],{},"To upgrade please uninstall ",[86,3638,3619],{}," using",[765,3641,3644],{"className":3642,"code":3643,"language":770},[768],"npm uninstall -g @flowforge\u002Fflowforge-device-agent\n",[86,3645,3643],{"__ignoreMap":39},[13,3647,3648,3649,3652],{},"(You may need to prefix this command with ",[86,3650,3651],{},"sudo"," on Unix platforms)",[13,3654,3655,3656,227],{},"and install ",[86,3657,3623],{},[765,3659,3662],{"className":3660,"code":3661,"language":770},[768],"npm install -g @flowfuse\u002Fdevice-agent\n",[86,3663,3661],{"__ignoreMap":39},[13,3665,3666,3667,3652],{},"(again you may need to prefix this with ",[86,3668,3651],{},[13,3670,3671,3672,3675],{},"The replacement package includes a migration binary called ",[86,3673,3674],{},"flowforge-device-agent"," which can still be used to start the new package.",{"title":39,"searchDepth":55,"depth":55,"links":3677},[],"2025-09-22","The FlowFuse Device agent will no longer update the old package name",{"tags":3681},[64],"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent",{"title":3610,"description":3679},{"loc":3682},"changelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","IsPIT-MpeZMQgecT75dg_2TPnFoAVDyq4d5jfY-1NAE",{"id":3688,"title":3689,"authors":3690,"body":3691,"date":3678,"description":3718,"extension":59,"issues":3719,"meta":3721,"navigation":65,"path":3723,"seo":3724,"sitemap":3725,"stem":3726,"subtitle":70,"__hash__":3727},"changelog\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api.md","Capture Async API data from FlowFuse Team Broker",[210],{"type":10,"value":3692,"toc":3716},[3693,3696,3699,3707,3710,3713],[13,3694,3695],{},"The FlowFuse Team Broker now includes automatically curated smart suggestions for the published payloads in each topic.",[13,3697,3698],{},"You can run this by simply toggling on the toggle found in the Topic Hierarchy view. This will run for 24 hours.",[13,3700,3701,3704],{},[36,3702],{"alt":39,"dataZoomable":39,"src":3703},"\u002Fchangelog\u002F2025\u002F09\u002Fimages\u002Fteam-broker-schema.png",[43,3705,3706],{},"Team Broker Schema Capture",[13,3708,3709],{},"Our agent will monitor for any payloads published on your broker in that time, and offer smart suggestions on data structure found. You can review these suggestions with the FlowFuse user interface, and confirm them where appropriate.",[13,3711,3712],{},"Once confirmed, the Async API documentation can be viewed by clicking on the \"Open Schema\" button. This means that your whole team can be aligned when building with your UNS.",[13,3714,3715],{},"This functionality was previously only available to 3rd party MQTT brokers using the MQTT Schema Agent, it is enabled on FlowFuse Cloud and will be available to Enterprise Licensed Self Hosted customers from v2.22.0.",{"title":39,"searchDepth":55,"depth":55,"links":3717},[],"Adding the ability to capture message payload schema from topics published on the FlowFuse Team Broker",[3720],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5951",{"tags":3722},[64],"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api",{"title":3689,"description":3718},{"loc":3723},"changelog\u002F2025\u002F09\u002Fteam-broker-async-api","ifuwnUekPrB16UcGSWO62eU00wHp_bSyUiBu2MLL6wI",{"id":3729,"title":3730,"authors":3731,"body":3732,"date":3760,"description":3761,"extension":59,"issues":3762,"meta":3764,"navigation":65,"path":3766,"seo":3767,"sitemap":3768,"stem":3769,"subtitle":70,"__hash__":3770},"changelog\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui.md","Streamlined Snapshot Management",[285],{"type":10,"value":3733,"toc":3758},[3734,3744,3747],[13,3735,3736,3737,3740,3741,3743],{},"We’ve redesigned how you interact with Hosted Instance ",[150,3738,3739],{},"snapshots"," by bringing all related actions into one place.",[1107,3742],{},"\nInstead of jumping between different menus, you can now manage everything directly from a single consolidated view.",[13,3745,3746],{},"This update keeps all existing functionality, but makes it easier and faster to find and use.",[13,3748,3749,3753,3755],{},[36,3750],{"alt":3751,"dataZoomable":39,"src":3752},"Snapshot interaction redesign","\u002Fchangelog\u002F2025\u002F09\u002Fimages\u002Frevised-instance-snapshots.gif",[1107,3754],{},[43,3756,3757],{},"Streamlined snapshot management",{"title":39,"searchDepth":55,"depth":55,"links":3759},[],"2025-09-19","All snapshot actions are now consolidated in a single, unified view",[3763],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F6001",{"tags":3765},[64],"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui",{"title":3730,"description":3761},{"loc":3766},"changelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","4Svi9Zoo-AFuvhTUpUxMO3Ya6N9b6u-i1KXkVS-i9vw",{"id":3772,"title":3773,"authors":3774,"body":3775,"date":3824,"description":3825,"extension":59,"issues":3826,"meta":3828,"navigation":65,"path":3830,"seo":3831,"sitemap":3832,"stem":3833,"subtitle":70,"__hash__":3834},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote.md","AI Snapshot Descriptions Now Work with Remote Instances",[285],{"type":10,"value":3776,"toc":3821},[3777,3787,3790,3794,3797,3807,3818],[13,3778,3779,3780,3783,3784,227],{},"We've extended ",[150,3781,3782],{},"AI-generated snapshot descriptions"," to ",[150,3785,3786],{},"remote instances",[13,3788,3789],{},"Whether your remote instance is linked to an application or a hosted instance, you can now generate a smart, clear description of the snapshot with a single click.",[385,3791,3793],{"id":3792},"two-flows-same-outcome","Two Flows, Same Outcome",[13,3795,3796],{},"Depending on how your remote instance is owned, the flow is slightly different:",[13,3798,3799,3803,3805],{},[36,3800],{"alt":3801,"dataZoomable":39,"src":3802},"AI for application-owned remote instances","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fdevice-llm-snapshot-description_application-owned.gif",[1107,3804],{},[43,3806,3801],{},[13,3808,3809,3813,3815],{},[36,3810],{"alt":3811,"dataZoomable":39,"src":3812},"AI for hosted-instance-owned remote","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fdevice-llm-snapshot-description_instance-owned.gif",[1107,3814],{},[43,3816,3817],{},"AI for hosted-instance-owned remote instances",[13,3819,3820],{},"This rounds out our support for AI-generated snapshot descriptions.",{"title":39,"searchDepth":55,"depth":55,"links":3822},[3823],{"id":3792,"depth":598,"text":3793},"2025-09-11","AI-powered snapshot descriptions now available for remote instances",[3827],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5758",{"tags":3829},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote",{"title":3773,"description":3825},{"loc":3830},"changelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","Gr2Q2iRnlvYaDYeRc3AF1vg0Db77x9ws5A3O9uGDMwY",{"id":3836,"title":3837,"authors":3838,"body":3839,"date":3875,"description":3876,"extension":59,"issues":70,"meta":3877,"navigation":65,"path":3879,"seo":3880,"sitemap":3881,"stem":3882,"subtitle":70,"__hash__":3883},"changelog\u002Fchangelog\u002F2025\u002F09\u002Finline-assist.md","FlowFuse Expert can help you write code",[284],{"type":10,"value":3840,"toc":3872},[3841,3844,3848,3855,3862,3869],[13,3842,3843],{},"More goodness has been added to the FlowFuse Expert by way of inline suggestions as you type.\nInitially, we have added support for the Function Node, Tables Query Node and the Dashboard Template Node.\nIt is contextually aware so will offer suggestions applicable to what it sees and what is already written.",[385,3845,3847],{"id":3846},"lets-see-it-in-action","Let's see it in action",[13,3849,3850,3854],{},[36,3851],{"alt":3852,"dataZoomable":39,"src":3853},"Demo of function node with inline completions","\u002Fchangelog\u002F2025\u002F09\u002Fimages\u002Finline-assist-function-node.gif","\n_Demo of function node with inline completions",[13,3856,3857,3861],{},[36,3858],{"alt":3859,"dataZoomable":39,"src":3860},"Demo of tables query node with inline completions","\u002Fchangelog\u002F2025\u002F09\u002Fimages\u002Finline-assist-query-node.gif","\n_Demo of tables query node with inline completions",[13,3863,3864,3868],{},[36,3865],{"alt":3866,"dataZoomable":39,"src":3867},"Demo of dashboard template node with inline completions","\u002Fchangelog\u002F2025\u002F09\u002Fimages\u002Finline-assist-template-node.gif","\n_Demo of dashboard template node with inline completions",[13,3870,3871],{},"This will be made availabe to our Pro and Enterprise users in remote and hosted instances in the next update however\nif you want to give it a go right away, you can update the FlowFuse Expert in the Node-RED Palette Manager today.",{"title":39,"searchDepth":55,"depth":55,"links":3873},[3874],{"id":3846,"depth":598,"text":3847},"2025-09-05","The FlowFuse Expert will now offer inline completions when writing functions, SQL and Dashboard templates",{"tags":3878},[64],"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist",{"title":3837,"description":3876},{"loc":3879},"changelog\u002F2025\u002F09\u002Finline-assist","mw4BYJtjTMqw29xBu7mTjGcWOFJfAUvLeV2UAdPBK8Q",{"id":3885,"title":3886,"authors":3887,"body":3888,"date":3932,"description":3933,"extension":59,"issues":3934,"meta":3935,"navigation":65,"path":3937,"seo":3938,"sitemap":3939,"stem":3940,"subtitle":70,"__hash__":3941},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted.md","Generate snapshot descriptions with AI",[285],{"type":10,"value":3889,"toc":3929},[3890,3899,3902,3906,3912,3922],[13,3891,3892,3893,227,3896,3898],{},"We’ve introduced a new feature: ",[150,3894,3895],{},"AI-generated Snapshot Descriptions",[1107,3897],{},"\nWhen creating a snapshot, you can now generate a concise description of what it contains and why it was created.",[13,3900,3901],{},"This makes it easier to understand the purpose of a snapshot at a glance, especially when working in a team or looking back weeks later.",[385,3903,3905],{"id":3904},"how-it-works","How it works",[13,3907,3908,3909,3911],{},"When creating a snapshot, you’ll see a new “Generate with AI” option.",[1107,3910],{},"\nWith one click, a suggested description is created for you, which you can accept as-is or edit before saving.",[13,3913,3914,3918,3920],{},[36,3915],{"alt":3916,"dataZoomable":39,"src":3917},"Demo of generating snapshot descriptions","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fsnapshot-description-generation-hosted.gif",[1107,3919],{},[43,3921,3916],{},[13,3923,3924,3925,3928],{},"This feature is currently available for ",[150,3926,3927],{},"hosted instances only",". Support for remote instances will follow shortly.",{"title":39,"searchDepth":55,"depth":55,"links":3930},[3931],{"id":3904,"depth":598,"text":3905},"2025-08-28","AI-powered descriptions to make your snapshots easier to understand",[3827],{"tags":3936},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted",{"title":3886,"description":3933},{"loc":3937},"changelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","4U7Nb8BVuJgQCshj7CcPOmSp5mwlsbwF1jRx6x16BHg",{"id":3943,"title":3944,"authors":3945,"body":3946,"date":3932,"description":3967,"extension":59,"issues":3968,"meta":3970,"navigation":65,"path":3972,"seo":3973,"sitemap":3974,"stem":3975,"subtitle":70,"__hash__":3976},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance.md","FlowFuse Remote Instance Performance Data",[210],{"type":10,"value":3947,"toc":3965},[3948,3951,3959,3962],[13,3949,3950],{},"FlowFuse Device Agent version v3.6.0 combined with FlowFuse v2.21.0 allows you to monitor the CPU and Memory usage of Remote Instances",[13,3952,3953,3957],{},[36,3954],{"alt":3955,"dataZoomable":39,"src":3956},"Screenshot of Device Performance data","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fdevice-performance.png",[43,3958,3955],{},[13,3960,3961],{},"The view is available from the \"Performance\" tab on the Remote Instance page.",[13,3963,3964],{},"This feature is available to Enterprise customers on FlowFuse Cloud and to Enterprise licensed self hosting customers.",{"title":39,"searchDepth":55,"depth":55,"links":3966},[],"View CPU and Memory usage of Remote Instances",[3969],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5847",{"tags":3971},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance",{"title":3944,"description":3967},{"loc":3972},"changelog\u002F2025\u002F08\u002Fdevice-performance","fotR2X56k7bmFjhjuzTL0eaLRK5hos2wWYWc-P4DwxA",{"id":3978,"title":3979,"authors":3980,"body":3981,"date":3932,"description":4007,"extension":59,"issues":70,"meta":4008,"navigation":65,"path":4010,"seo":4011,"sitemap":4012,"stem":4013,"subtitle":70,"__hash__":4014},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso.md","Direct SSO Login",[210],{"type":10,"value":3982,"toc":4005},[3983,3986,3994,3997],[13,3984,3985],{},"As part of FlowFuse release v2.21.0, self hosted Enterprise users will be able to enable direct SSO login from the FlowFuse login page.",[13,3987,3988,3992],{},[36,3989],{"alt":3990,"dataZoomable":39,"src":3991},"Screenshot of FlowFuse Login Page with SSO Direct Button","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fdirect-sso.png",[43,3993,3990],{},[13,3995,3996],{},"This can be enabled from the Admin Settings page. When enabled it will add a button for all SAML SSO configurations to the login page. These buttons bypass the email domain matching that would normally be used to select which SSO provider to use. This can be used when users use the same email domain but need to authenticate with different SSO providers.",[13,3998,3999,4003],{},[36,4000],{"alt":4001,"dataZoomable":39,"src":4002},"Screenshot of FlowFuse Admin Settings for Direct SSO","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fdirect-sso-config.png",[43,4004,4001],{},{"title":39,"searchDepth":55,"depth":55,"links":4006},[],"Allows direct redirects to SAML SSO providers",{"tags":4009},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso",{"title":3979,"description":4007},{"loc":4010},"changelog\u002F2025\u002F08\u002Fdirect-sso","LwXZ5NfMz4zT9Ki-AVEOXU-2FeanEDCCIq0FKpARxHc",{"id":4016,"title":4017,"authors":4018,"body":4019,"date":3932,"description":4040,"extension":59,"issues":70,"meta":4041,"navigation":65,"path":4043,"seo":4044,"sitemap":4045,"stem":4046,"subtitle":70,"__hash__":4047},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors.md","Configure HTTP CORS",[210],{"type":10,"value":4020,"toc":4038},[4021,4024,4027,4035],[13,4022,4023],{},"Included in FlowFuse v2.21.0 is the ability to configure the HTTP CORS response for HTTP routes served by the Node-RED instances.",[13,4025,4026],{},"This includes routes from HTTP-in\u002FHTTP-response nodes and the Node-RED Dashboard.",[13,4028,4029,4033],{},[36,4030],{"alt":4031,"dataZoomable":39,"src":4032},"Screenshot of Hosted Instance Security Settings","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fhttp-cors.png",[43,4034,4031],{},[13,4036,4037],{},"This feature will require the latest Stack version and uses will be prompted to upgrade if required.",{"title":39,"searchDepth":55,"depth":55,"links":4039},[],"Allows setting HTTP CORS values for Hosted Instances",{"tags":4042},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors",{"title":4017,"description":4040},{"loc":4043},"changelog\u002F2025\u002F08\u002Fhttp-cors","IwPrY3ru0Q9TQ_H-_yDuJUmSUV2uI1F4-DhOTvCPvNA",{"id":4049,"title":4050,"authors":4051,"body":4052,"date":3932,"description":4084,"extension":59,"issues":4085,"meta":4087,"navigation":65,"path":4089,"seo":4090,"sitemap":4091,"stem":4092,"subtitle":70,"__hash__":4093},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export.md","Export SubFlow as Node-RED module",[210],{"type":10,"value":4053,"toc":4082},[4054,4057,4060,4068,4071,4079],[13,4055,4056],{},"Instances running the latest Node-RED version on FlowFuse v2.21.0 will now be able to export Node-RED SubFlows as Node-RED nodes.",[13,4058,4059],{},"This is done from the Node-RED editor using a custom sidebar.",[13,4061,4062,4066],{},[36,4063],{"alt":4064,"dataZoomable":39,"src":4065},"Screenshot of Node-RED with the SubFlow export sidebar","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fsubflow-export.png",[43,4067,4064],{},[13,4069,4070],{},"The nodes are added to the Team's Library of Custom Nodes and can be installed into any of the Team's Node-RED instances from the Catalogue generated by the Team Library.",[13,4072,4073,4077],{},[36,4074],{"alt":4075,"dataZoomable":39,"src":4076},"Screenshot of Node-RED Manage Palette showing new SubFlow modules","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fsubflow-catalogue.png",[43,4078,4075],{},[13,4080,4081],{},"This feature is available to FlowFuse Cloud Pro and Enterprise teams and to Enterprise Self hosting users.",{"title":39,"searchDepth":55,"depth":55,"links":4083},[],"Allow SubFlows to be packaged as nodes and published to Team Library",[4086],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F3666",{"tags":4088},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export",{"title":4050,"description":4084},{"loc":4089},"changelog\u002F2025\u002F08\u002Fsubflow-export","9ApjrGAAZxFmo_rYhyHbSIbVsDcZ02EJO4UGEgLfqqM",{"id":4095,"title":4096,"authors":4097,"body":4098,"date":3932,"description":4125,"extension":59,"issues":70,"meta":4126,"navigation":65,"path":4128,"seo":4129,"sitemap":4130,"stem":4131,"subtitle":70,"__hash__":4132},"changelog\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant.md","FlowFuse Tables with a little help from the Assistant",[284],{"type":10,"value":4099,"toc":4122},[4100,4109,4112,4114],[13,4101,4102,4103,4108],{},"The new ",[26,4104,4107],{"href":4105,"rel":4106},"https:\u002F\u002Fflowfuse.com\u002Fblog\u002F2025\u002F07\u002Fflowfuse-release-2-20\u002F#introducing%3A-flowfuse-tables",[30],"Tables"," we introduced in FlowFuse 2.20.0 feature may be still in Beta but to help you make the most of it we have added a codelens to the query editor to help you get your queries written faster.",[13,4110,4111],{},"Behind the scenes, when you ask for assistance, we gather schema info and include this in the process of making a prediction as to the best tables and fields to use for in the query.",[385,4113,3847],{"id":3846},[13,4115,4116,4120],{},[36,4117],{"alt":4118,"dataZoomable":39,"src":4119},"Demo of table node with assistance","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fquery-assist.gif",[43,4121,4118],{},{"title":39,"searchDepth":55,"depth":55,"links":4123},[4124],{"id":3846,"depth":598,"text":3847},"Build FlowFuse Tables Queries with a bit of AI Assistance.",{"tags":4127},[64],"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant",{"title":4096,"description":4125},{"loc":4128},"changelog\u002F2025\u002F08\u002Ftables-assistant","XRlouY2mBEWKEJjjGMVqOiW1GOuEBE_HKMc5Ei9kl1Y",{"id":4134,"title":4135,"authors":4136,"body":4137,"date":4175,"description":4176,"extension":59,"issues":70,"meta":4177,"navigation":65,"path":4179,"seo":4180,"sitemap":4181,"stem":4182,"subtitle":70,"__hash__":4183},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt.md","FlowFuse MQTT",[284],{"type":10,"value":4138,"toc":4173},[4139,4147,4150,4153,4162,4170],[13,4140,4141,4142,4146],{},"FlowFuse has offered a built in MQTT ",[26,4143,4145],{"href":4144},"\u002Fdocs\u002Fuser\u002Fteambroker","Team Broker"," since FlowFuse v2.10.0, but connecting to it still required manual configuration in your Node-RED instances through the core MQTT nodes.",[13,4148,4149],{},"Today, we are adding dedicated MQTT nodes that require no setup to use. Just add a FlowFuse MQTT Node to your Node-RED instance, deploy it & go.",[13,4151,4152],{},"Pretty much all of the capabilities of the Node-RED MQTT Nodes are present making it very straightforward and to get up and running in no time.",[13,4154,4155,4159],{},[36,4156],{"alt":4157,"dataZoomable":39,"src":4158},"Screenshot of Node-RED with FlowFuse MQTT nodes","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fmqtt-nodes-1.png",[43,4160,4161],{},"Screenshot of Node-RED with FlowFuse MQTT Nodes",[13,4163,4164,4168],{},[36,4165],{"alt":4166,"dataZoomable":39,"src":4167},"Screenshot of Node-RED with FlowFuse MQTT-in node edit panel","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fmqtt-nodes-2.png",[43,4169,4166],{},[13,4171,4172],{},"To get the new FlowFuse MQTT Nodes in your Node-RED instance, you will need to be running the latest version of the FlowFuse Device Agent (V3.6.0 or greater) or a stack running with the FlowFuse launcher (V2.20.1 or greater) which will be released in the coming days.",{"title":39,"searchDepth":55,"depth":55,"links":4174},[],"2025-08-18","MQTT Simplified",{"tags":4178},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt",{"title":4135,"description":4176},{"loc":4179},"changelog\u002F2025\u002F08\u002Fflowfuse-mqtt","satQ-Ozdohfb73LzU_lTQ9nHYh9MKaYiJB3b2ae2A0Q",{"id":4185,"title":4186,"authors":4187,"body":4188,"date":4213,"description":4214,"extension":59,"issues":70,"meta":4215,"navigation":65,"path":4217,"seo":4218,"sitemap":4219,"stem":4220,"subtitle":70,"__hash__":4221},"changelog\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant.md","FlowFuse Expert documents your flows",[284],{"type":10,"value":4189,"toc":4210},[4190,4193,4195,4203],[13,4191,4192],{},"Recently, we introduced \"Flows Explainer\" to the FlowFuse Expert. It provides a concise description of the selected flows.\nThis turned out so well we thought \"wouldn't it be good if the generated explanation could be persisted as built in documentation\" so we added a single click option to add the documentation as a comment node to your flows.\nWe also provided a Copy to Clipboard button so you can grab it and add it to the Documentation section of a flow tab, node group or external documentation.",[385,4194,3847],{"id":3846},[13,4196,4197,4201],{},[36,4198],{"alt":4199,"dataZoomable":39,"src":4200},"Demo of documenting flows with the Flows Explainer","\u002Fchangelog\u002F2025\u002F08\u002Fimages\u002Fexplainer-to-comment-node.gif",[43,4202,4199],{},[13,4204,4205,4206,4209],{},"While this feature is just a simple ",[43,4207,4208],{},"quality of life"," addition, we are hopeful it is small touches like these that improve your daily workflow.",{"title":39,"searchDepth":55,"depth":55,"links":4211},[4212],{"id":3846,"depth":598,"text":3847},"2025-08-06","Document your flows at the click of a button with the power of AI",{"tags":4216},[64],"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant",{"title":4186,"description":4214},{"loc":4217},"changelog\u002F2025\u002F08\u002Fflowfuse-assistant","7VYNCQt_GNRVNTYzVVIJer65gWxutOcvgYOZc4xCGe0",{"id":4223,"title":4224,"authors":4225,"body":4226,"date":4258,"description":4259,"extension":59,"issues":70,"meta":4260,"navigation":65,"path":4262,"seo":4263,"sitemap":4264,"stem":4265,"subtitle":70,"__hash__":4266},"changelog\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename.md","Team Plan Renamed to Pro Plan",[2729],{"type":10,"value":4227,"toc":4256},[4228,4231,4234,4237,4240,4248],[13,4229,4230],{},"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.",[13,4232,4233],{},"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.",[13,4235,4236],{},"All existing Team plan subscribers will automatically transition to Pro. Your applications, instances, and team configurations remain exactly the same.",[13,4238,4239],{},"What's new:",[251,4241,4242,4245],{},[254,4243,4244],{},"A name that better represents professional Node-RED application development",[254,4246,4247],{},"Clearer positioning for organizations ready to scale their Node-RED implementations",[13,4249,4250,4251,4255],{},"Ready to build professional Node-RED applications? [Get started with Pro]({% include \"sign-up-url.njk\" %}) or ",[26,4252,4254],{"href":4253},"\u002Fcontact-us","contact us"," to learn more.",{"title":39,"searchDepth":55,"depth":55,"links":4257},[],"2025-08-04","The Team tier has been renamed to Pro tier to better reflect the plan's capabilities and target audience",{"tags":4261},[64],"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename",{"title":4224,"description":4259},{"loc":4262},"changelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","nT0FS0FiO6lkt5xxlAFZIBkZYtEw-zbKjgwqxpFT2vs",{"id":4268,"title":4269,"authors":4270,"body":4271,"date":4324,"description":4325,"extension":59,"issues":4326,"meta":4328,"navigation":65,"path":4330,"seo":4331,"sitemap":4332,"stem":4333,"subtitle":70,"__hash__":4334},"changelog\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables.md","FlowFuse Tables",[210],{"type":10,"value":4272,"toc":4322},[4273,4276,4284,4287,4295,4298,4307,4310,4313],[13,4274,4275],{},"As part of the FlowFuse v2.20.0 release we are adding an option for a Team level hosted relational database.",[13,4277,4278,4282],{},[36,4279],{"alt":4280,"dataZoomable":39,"src":4281},"Screenshot of the FlowFuse Tables onboarding wizard","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Fcreate-database.png",[43,4283,4280],{},[13,4285,4286],{},"Tools to create tables and to show sample data are included, but we will be iterating on these moving forward.",[13,4288,4289,4293],{},[36,4290],{"alt":4291,"dataZoomable":39,"src":4292},"Screenshot of Table Explorer","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Ftable-data-sample.png",[43,4294,4291],{},[13,4296,4297],{},"Paired with the Database is a new FlowFuse Tables node which will automatically pick up the credentials when deployed in FlowFuse Hosted Instance running on a v2.20.0+ Stack, or when running with the latest version of the FlowFuse Device Agent.",[13,4299,4300,4304],{},[36,4301],{"alt":4302,"dataZoomable":39,"src":4303},"Screenshot of Node-RED with FlowFuse Tables node","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Ftables-node.png",[43,4305,4306],{},"Screenshot of Node-RED with FlowFuse Tables Node",[13,4308,4309],{},"The database is a Postgres instance and you will be able to connect 3rd party clients using the credentials provided.",[13,4311,4312],{},"This feature will be available to FlowFuse Cloud Enterprise Tier customers and to Enterprise Licensed Self Hosted customers on Kubernetes to start with, we hope to make it available to Docker Compose users in a future release.",[13,4314,4315,4316,4321],{},"It is currently marked as a ",[26,4317,4320],{"href":4318,"rel":4319},"https:\u002F\u002Fflowfuse.com\u002Fhandbook\u002Fengineering\u002Freleases\u002F#beta-release",[30],"Beta Feature"," while we continue to iterate on adding new features and observe how it is used.",{"title":39,"searchDepth":55,"depth":55,"links":4323},[],"2025-07-31","Adding a Team level Relational Database to FlowFuse",[4327],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F4911",{"tags":4329},[64],"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"title":4269,"description":4325},{"loc":4330},"changelog\u002F2025\u002F07\u002Fflowfuse-tables","jOh-BYxoV3e8sDBAKy56qr93w1CwpEk666dcRd8tU8o",{"id":4336,"title":4337,"authors":4338,"body":4339,"date":4324,"description":4378,"extension":59,"issues":70,"meta":4379,"navigation":65,"path":4381,"seo":4382,"sitemap":4383,"stem":4384,"subtitle":70,"__hash__":4385},"changelog\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions.md","Smart Suggestions",[284],{"type":10,"value":4340,"toc":4375},[4341,4344,4359,4362,4364,4372],[13,4342,4343],{},"In conjunction with the release of Node-RED 4.1.0 and FlowFuse 2.20.0, we have added smart suggestions to the Editor.",[13,4345,4346,4347,4350,4351,4354,4355,4358],{},"When you drop a node onto the editor workspace, the upstream connected nodes in your flow are analysed and a next node suggestion is presented for quick insertion via the keyboard ",[86,4348,4349],{},"TAB"," key or the click of your mouse.\nIt presents up to 5 of the most common following nodes which can be cycled through using your keyboards ",[86,4352,4353],{},"UP"," and ",[86,4356,4357],{},"DOWN"," arrows, so even if the first suggestion isn't correct, it's very likely that the correct choice is only a key press away.",[13,4360,4361],{},"To achieve this, we processed thousands of real working flows and built a decision tree model for the greatest accuracy possible.",[385,4363,3847],{"id":3846},[13,4365,4366,4370],{},[36,4367],{"alt":4368,"dataZoomable":39,"src":4369},"Demo of smart suggestions","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Fsmart-suggestion.gif",[43,4371,4368],{},[13,4373,4374],{},"We hope this new feature makes the process of writing flows for Node-RED flows in FlowFuse even easier.",{"title":39,"searchDepth":55,"depth":55,"links":4376},[4377],{"id":3846,"depth":598,"text":3847},"Next Node Smart Suggestions to speed up flow development",{"tags":4380},[64],"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions",{"title":4337,"description":4378},{"loc":4381},"changelog\u002F2025\u002F07\u002Fsmart-suggestions","lIlHYQGf2NekPgPhSwKhr2FceJendO0S7XYGIGmT0ko",{"id":4387,"title":4388,"authors":4389,"body":4390,"date":4484,"description":4485,"extension":59,"issues":4486,"meta":4488,"navigation":65,"path":4490,"seo":4491,"sitemap":4492,"stem":4493,"subtitle":70,"__hash__":4494},"changelog\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview.md","Simplified Applications Page with Summary Tiles",[285],{"type":10,"value":4391,"toc":4480},[4392,4399,4403,4454,4458,4472],[13,4393,4394,4395,4398],{},"We’ve rolled out a redesigned ",[150,4396,4397],{},"Applications Page"," interface to give you sharper insight into instance status across hosted and remote deployments.",[385,4400,4402],{"id":4401},"key-updates","Key Updates",[251,4404,4405,4426,4442,4448],{},[254,4406,4407,4410,4411,549,4414,549,4417,549,4420,553,4422,4425],{},[150,4408,4409],{},"Application Shortcuts Maintained","\nThe existing shortcuts to ",[150,4412,4413],{},"instances",[150,4415,4416],{},"devices",[150,4418,4419],{},"device groups",[150,4421,3739],{},[150,4423,4424],{},"pipelines"," have been retained in the new layout for easy access.",[254,4427,4428,4431,4432,549,4435,553,4438,4441],{},[150,4429,4430],{},"Summary Tiles for Each App","\nInstead of listing every instance individually, you now get compact summary tiles with counts of ",[150,4433,4434],{},"Running",[150,4436,4437],{},"Error",[150,4439,4440],{},"Not Running"," instances for both hosted and remote groups. Visual layout is clean and instant to scan.",[254,4443,4444,4447],{},[150,4445,4446],{},"Grouped Instances by Status","\nEach application shows two separate tiles: one for hosted instances and one for remote. That way you see app health at a glance, without needing to drill into details.",[254,4449,4450,4453],{},[150,4451,4452],{},"Aggregate Status Tiles","\nEach status tile represents an aggregate count of instances in a given state (e.g. Running, Error). Clicking on a tile takes you to a filtered view of the underlying instances.",[385,4455,4457],{"id":4456},"why-this-matters","Why This Matters",[251,4459,4460,4463,4466,4469],{},[254,4461,4462],{},"Page load times have been significantly improved by reducing the number of rendered elements and simplifying data fetching.",[254,4464,4465],{},"Cuts out clutter, no more scrolling through long lists.",[254,4467,4468],{},"Quick status view helps you spot issues fast.",[254,4470,4471],{},"Cleaner separation between hosted vs remote gives context instantly.",[13,4473,4474,4478],{},[36,4475],{"alt":4476,"dataZoomable":39,"src":4477},"Screenshot of the Simplified Applications page","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Fsimplified-applications.png",[43,4479,4476],{},{"title":39,"searchDepth":55,"depth":55,"links":4481},[4482,4483],{"id":4401,"depth":598,"text":4402},{"id":4456,"depth":598,"text":4457},"2025-07-29","Simplified Applications overview with clearer status summaries for hosted and remote instances",[4487],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F4737",{"tags":4489},[64],"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview",{"title":4388,"description":4485},{"loc":4490},"changelog\u002F2025\u002F07\u002Fsimplified-applications-overview","9cCSpgZ4UEPEV7nR03PxI-QW0ThjHy14cDOAhTuUcRg",{"id":4496,"title":4497,"authors":4498,"body":4499,"date":4554,"description":4555,"extension":59,"issues":4556,"meta":4558,"navigation":65,"path":4560,"seo":4561,"sitemap":4562,"stem":4563,"subtitle":70,"__hash__":4564},"changelog\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows.md","Browse for Node-RED Flows During Remote Instance Setup",[284],{"type":10,"value":4500,"toc":4551},[4501,4504,4515,4518,4527,4535,4540,4548],[13,4502,4503],{},"Last month we introduced a way for the FlowFuse Device Agent to import Node-RED flows during the setup process. Today, we have built on that and added some new features:",[251,4505,4506,4509,4512],{},[254,4507,4508],{},"Automatically scan common file locations and offer any flows found for immediate selection",[254,4510,4511],{},"Scan common directories and present any that contain multiple flows as a quick browse selection",[254,4513,4514],{},"Offer a \"Browse filesystem\" option to let you navigate and select any flows on your device",[385,4516,4517],{"id":3846},"Lets see it in action",[13,4519,4520],{},[150,4521,4522,4523,4526],{},"Import automatically located ",[86,4524,4525],{},"~\u002F.node-red\u002Fflows.json"," flows file",[13,4528,4529,4533],{},[36,4530],{"alt":4531,"dataZoomable":39,"src":4532},"Screenshot of the Importing an Automatically located flows file during Device Agent Setup","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Fimport-flows-quick-select.gif",[43,4534,4531],{},[13,4536,4537],{},[150,4538,4539],{},"Using the \"Browse filesystem\" option to navigate the filesystem to chose a different flows file",[13,4541,4542,4546],{},[36,4543],{"alt":4544,"dataZoomable":39,"src":4545},"Screenshot of Browsing the filesystem for flows file during Device Agent Setup","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Fimport-flows-browsed.gif",[43,4547,4544],{},[13,4549,4550],{},"We hope these new enhancements make the process of migrating existing Node-RED flows to FlowFuse even easier.",{"title":39,"searchDepth":55,"depth":55,"links":4552},[4553],{"id":3846,"depth":598,"text":4517},"2025-07-03","Remote Instance setup improvements to help you get up and running faster with the FlowFuse Device Agent.",[4557],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Fissues\u002F415",{"tags":4559},[64],"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows",{"title":4497,"description":4555},{"loc":4560},"changelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","R_ChR3mSMjQNw-FcZopxarAQB3IYbJwU5fVVvZBTqyo",{"id":4566,"title":4567,"authors":4568,"body":4569,"date":4554,"description":4615,"extension":59,"issues":4616,"meta":4618,"navigation":65,"path":4620,"seo":4621,"sitemap":4622,"stem":4623,"subtitle":70,"__hash__":4624},"changelog\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints.md","Import blueprints directly into your existing instances",[8],{"type":10,"value":4570,"toc":4613},[4571,4580,4583,4594,4602,4610],[13,4572,4573,4574,4579],{},"FlowFuse provides a growing ",[26,4575,4578],{"href":4576,"rel":4577},"https:\u002F\u002Fflowfuse.com\u002Fblueprints\u002F",[30],"library of blueprints"," that provide a great way to get started quickly with a pre-built solution across a range of scenarios.",[13,4581,4582],{},"With the 2.19 release of FlowFuse, instances that have been updated to the latest version can now import blueprints directly into their editor.",[13,4584,4585,4586,4589,4590,4593],{},"The Node-RED import dialog (",[86,4587,4588],{},"Ctrl-i"," or the ",[86,4591,4592],{},"import"," menu option) now has a blueprints section. Under that you can browse the available blueprints by category and select one to import.",[13,4595,4596,4600],{},[36,4597],{"alt":4598,"dataZoomable":39,"src":4599},"Screenshot of the Node-RED import dialog","\u002Fchangelog\u002F2025\u002F07\u002Fimages\u002Fimport-blueprint.png",[43,4601,4598],{},[13,4603,4604,4605,4609],{},"When you import a blueprint, you may get an error about 'unknown' nodes. This will be because the blueprint depends on Node-RED nodes you haven't currently got installed. You can check the ",[26,4606,4608],{"href":4576,"rel":4607},[30],"blueprint library"," for details on what the blueprints require and then install them via the Palette Manager within Node-RED.",[13,4611,4612],{},"We recognise that isn't as smooth an experience as we'd like - but the good news is it's about to get much better. With the imminent Node-RED 4.1 release, the editor will be able to automatically install any missing modules for you. Keep an eye out for the 4.1 release announcement and update your instances to take full advantage.",{"title":39,"searchDepth":55,"depth":55,"links":4614},[],"Making it easier to try out the FlowFuse Blueprints within your existing Node-RED instances",[4617],"5320",{"tags":4619},[64],"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints",{"title":4567,"description":4615},{"loc":4620},"changelog\u002F2025\u002F07\u002Fimport-blueprints","XQiF8vpOKig8-6E2uJk0D9pXDYFPXeMbLbOeK7F23y0",{"id":4626,"title":4627,"authors":4628,"body":4629,"date":4734,"description":4735,"extension":59,"issues":4736,"meta":4738,"navigation":65,"path":4740,"seo":4741,"sitemap":4742,"stem":4743,"subtitle":70,"__hash__":4744},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2.md","FlowFuse Expert just got smarter",[284],{"type":10,"value":4630,"toc":4728},[4631,4634,4637,4648,4651,4656,4664,4668,4676,4680,4688,4696,4700,4703,4712,4719],[13,4632,4633],{},"Following on from the recent improvements we made earlier this month, we have added even more goodness to the FlowFuse Expert:",[13,4635,4636],{},"We have:",[251,4638,4639,4642,4645],{},[254,4640,4641],{},"Added a menu for quick access to the new features",[254,4643,4644],{},"Improved the look and feel of the Flow Explainer",[254,4646,4647],{},"Added a codelens to assist you creating HTML, VUE, Vuetify & CSS in FlowFuse Node-RED Dashboard templates",[13,4649,4650],{},"And there more to come in the next week - stay tuned!",[4652,4653,4655],"h4",{"id":4654},"new-menu","New Menu",[13,4657,4658,4662],{},[36,4659],{"alt":4660,"dataZoomable":39,"src":4661},"Screenshot of the new Assistant Menu","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-new-menu.png",[43,4663,4660],{},[4652,4665,4667],{"id":4666},"flow-explainer-updated-look-feel","Flow Explainer updated look & feel",[13,4669,4670,4674],{},[36,4671],{"alt":4672,"dataZoomable":39,"src":4673},"Animated GIF showing the Flow Explainer Updated Layout","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-0-3-0-flow-explainer.gif",[43,4675,4672],{},[4652,4677,4679],{"id":4678},"new-codelens-for-building-ui-templates","New Codelens for building ui-templates",[13,4681,4682,4686],{},[36,4683],{"alt":4684,"dataZoomable":39,"src":4685},"Animated GIF showing the Assistant building HTML & VUE template code","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-0-3-0-ui-template-vue.gif",[43,4687,4684],{},[13,4689,4690,4694],{},[36,4691],{"alt":4692,"dataZoomable":39,"src":4693},"Animated GIF showing the Assistant building CSS styles","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-0-3-0-ui-template-css.gif",[43,4695,4692],{},[4652,4697,4699],{"id":4698},"updating-the-assistant","Updating the Assistant",[13,4701,4702],{},"If you are running Node-RED v4.x, head over to the Palette Manager, update the plugin and restart your instance.",[13,4704,4705,4709],{},[36,4706],{"alt":4707,"dataZoomable":39,"src":4708},"Updating assistant on Node-RED 4","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-0-3-0-update-nr4.png",[43,4710,4711],{},"Screenshot of Updating the Assistant for a Node-RED 4 instance",[13,4713,4714,4715,4718],{},"If you are still running Node-RED v3.x we strogly recommend you update your stack to use Node-RED v4.x but you can\nstill manually update the plugin by adding ",[86,4716,4717],{},"@flowfuse\u002Fnr-assistant"," to the instance settings then restart it.",[13,4720,4721,4725],{},[36,4722],{"alt":4723,"dataZoomable":39,"src":4724},"Updating assistant on Node-RED 3","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-update-nr3.png",[43,4726,4727],{},"Screenshot of Updating Assistant for a Node-RED 3 instance",{"title":39,"searchDepth":55,"depth":55,"links":4729},[4730,4731,4732,4733],{"id":4654,"depth":55,"text":4655},{"id":4666,"depth":55,"text":4667},{"id":4678,"depth":55,"text":4679},{"id":4698,"depth":55,"text":4699},"2025-06-30","Understand what your teams flows are doing with the power of AI",[4737],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fnr-assistant\u002Fpull\u002F44",{"tags":4739},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"title":4627,"description":4735},{"loc":4740},"changelog\u002F2025\u002F06\u002Fflowfuse-assistant-2","xNWLAnkdH3lGDns57kECSYLp5twGNC8NJBmwWOBI5qI",{"id":4746,"title":4747,"authors":4748,"body":4749,"date":4827,"description":4828,"extension":59,"issues":4829,"meta":4831,"navigation":65,"path":4833,"seo":4834,"sitemap":4835,"stem":4836,"subtitle":70,"__hash__":4837},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page.md","Introducing the New Home Page Experience",[285],{"type":10,"value":4750,"toc":4824},[4751,4758,4762,4809,4812,4821],[13,4752,4753,4754,4757],{},"We’re excited to announce the release of the all-new ",[150,4755,4756],{},"Home Page",", designed to simplify navigation and provide relevant information at a glance.",[385,4759,4761],{"id":4760},"key-features","Key Features",[251,4763,4764,4771,4803],{},[254,4765,4766,4767,4770],{},"A more intuitive and ",[150,4768,4769],{},"dedicated landing page",", replacing the dual-purpose \"Applications\" view.",[254,4772,4773,4776,4777,4780,4781],{},[150,4774,4775],{},"Recently Modified Instances",": The Home page highlights ",[150,4778,4779],{},"recently modified hosted and remote instances",", providing key statistics at a glance:\n",[251,4782,4783,4796],{},[254,4784,4785,4786,549,4789,553,4792,4795],{},"Number of ",[150,4787,4788],{},"running",[150,4790,4791],{},"error",[150,4793,4794],{},"not running"," instances.",[254,4797,4798,4799,4802],{},"Each tile is ",[150,4800,4801],{},"clickable"," for direct access.",[254,4804,4805,4808],{},[150,4806,4807],{},"Recent Activity Section",": A comprehensive view of the latest 50 changes made within the current team is now integrated, enabling better tracking of team activities and updates.",[13,4810,4811],{},"These enhancements are intended to make managing your instances and reviewing activity smoother and more effective.",[13,4813,4814,4818],{},[36,4815],{"alt":4816,"dataZoomable":39,"src":4817},"Screenshot of the New Home Page","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fnew-home-page.png",[43,4819,4820],{},"Screenshot of the new home\u002Flanding page in FlowFuse",[13,4822,4823],{},"This improvement aligns with the feedback we received from the community, aimed at delivering a more user-friendly and focused experience.",{"title":39,"searchDepth":55,"depth":55,"links":4825},[4826],{"id":4760,"depth":598,"text":4761},"2025-06-24","A modernized Home page with enhanced usability for FlowFuse users",[4830],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5600",{"tags":4832},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page",{"title":4747,"description":4828},{"loc":4833},"changelog\u002F2025\u002F06\u002Fnew-home-page","MTL9wPFFJ2cBmON5C4FpCiaadaIa_bSrwDs3HNtU6K4",{"id":4839,"title":4840,"authors":4841,"body":4842,"date":4861,"description":4862,"extension":59,"issues":4863,"meta":4865,"navigation":65,"path":4867,"seo":4868,"sitemap":4869,"stem":4870,"subtitle":70,"__hash__":4871},"changelog\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory.md","Memory Metrics in Instance Performance View",[285],{"type":10,"value":4843,"toc":4859},[4844,4847,4856],[13,4845,4846],{},"We're excited to announce an enhancement to the existing Performance view for Hosted Instances in FlowFuse. We've expanded the view to include a new Memory Utilization chart.",[13,4848,4849,4853],{},[36,4850],{"alt":4851,"dataZoomable":39,"src":4852},"Screenshot of the expanded Performance view with Memory Utilization","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Finstance-performance-memory.png",[43,4854,4855],{},"Screenshot of the Performance view with Memory Utilization",[13,4857,4858],{},"This update provides additional insight, allowing you to monitor not only CPU usage but also memory consumption over time. The inclusion of memory metrics makes it easier than ever to detect performance issues and optimize your Node-RED Flows.",{"title":39,"searchDepth":55,"depth":55,"links":4860},[],"2025-06-20","The Performance view for hosted Node-RED instances now includes a memory usage chart",[4864],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5590",{"tags":4866},[64],"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory",{"title":4840,"description":4862},{"loc":4867},"changelog\u002F2025\u002F06\u002Finstance-performance-memory","SLdEdGOQjxV1P_qix4Fp8SFQ7ynD0GTnWM0YEioJvqM",{"id":4873,"title":4627,"authors":4874,"body":4875,"date":4924,"description":4735,"extension":59,"issues":4925,"meta":4926,"navigation":65,"path":4928,"seo":4929,"sitemap":4930,"stem":4931,"subtitle":70,"__hash__":4932},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant.md",[284],{"type":10,"value":4876,"toc":4920},[4877,4880,4883,4887,4896,4898,4900,4908,4913],[13,4878,4879],{},"Last year, we introduced the FlowFuse Expert, a Node-RED plugin designed to assist FlowFuse users with tools for developing their Node-RED instances. Today, we are excited to announce that the Assistant has been updated with a new feature powered by AI: the Flows Explainer. This feature uses AI to analyze your Node-RED flows and provide a detailed explanation of what they do, making it easier for you to understand and manage your flows.",[13,4881,4882],{},"Stay tuned; this is just a taste of what is to come.",[4652,4884,4886],{"id":4885},"flows-explainer","Flows Explainer",[13,4888,4889,4893],{},[36,4890],{"alt":4891,"dataZoomable":39,"src":4892},"flowfuse-assistant-flow-explainer","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fflowfuse-assistant-flow-explainer.gif",[43,4894,4895],{},"Screenshot of the FlowFuse Expert Flow Explainer",[4652,4897,4699],{"id":4698},[13,4899,4702],{},[13,4901,4902,4905],{},[36,4903],{"alt":4707,"dataZoomable":39,"src":4904},"\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fassistant-update-nr4.png",[43,4906,4907],{},"Screenshot of Updating assistant on Node-RED 4",[13,4909,4910,4911,4718],{},"If you are still running Node-RED v3.x we strogly recommend you update your stack to use Node-RED v4.x but you can still manually update the plugin by adding ",[86,4912,4717],{},[13,4914,4915,4917],{},[36,4916],{"alt":4723,"dataZoomable":39,"src":4724},[43,4918,4919],{},"Screenshot of Updating assistant on Node-RED 3",{"title":39,"searchDepth":55,"depth":55,"links":4921},[4922,4923],{"id":4885,"depth":55,"text":4886},{"id":4698,"depth":55,"text":4699},"2025-06-12",[4737],{"tags":4927},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant",{"title":4627,"description":4735},{"loc":4928},"changelog\u002F2025\u002F06\u002Fflowfuse-assistant","c0z7ePvFMOGQk8ZXh_J7Vl6bkWJ6XLUvg-RwomRt99Q",{"id":4934,"title":4935,"authors":4936,"body":4937,"date":4958,"description":4959,"extension":59,"issues":70,"meta":4960,"navigation":65,"path":4962,"seo":4963,"sitemap":4964,"stem":4965,"subtitle":70,"__hash__":4966},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh.md","Navigation UI Refresh",[285],{"type":10,"value":4938,"toc":4956},[4939,4942,4945,4948],[13,4940,4941],{},"We’ve given the top navigation in FlowFuse a visual refresh as part of our effort to constantly improve and modernise the user experience of FlowFuse.",[13,4943,4944],{},"Menus now use a clean white background, with updated colors, spacing, and transitions across the user menu, team switcher, and notification buttons. Mobile menus have also been cleaned up for better usability.",[13,4946,4947],{},"This is the first step in a broader UI modernization effort based on community feedback.",[13,4949,4950,4954],{},[36,4951],{"alt":4952,"dataZoomable":39,"src":4953},"Screenshot of the re-designed top navigation","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fui-refresh-1.png",[43,4955,4952],{},{"title":39,"searchDepth":55,"depth":55,"links":4957},[],"2025-06-11","Redesigned top navigation with improved layout, colors, and menu styling for a cleaner user experience.",{"tags":4961},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh",{"title":4935,"description":4959},{"loc":4962},"changelog\u002F2025\u002F06\u002Fui-refresh","92DMmM77di-2Dc-zrxqZ1KMJ7_4zpPd2ymDmhAq5Eu4",{"id":4968,"title":4969,"authors":4970,"body":4971,"date":5000,"description":5001,"extension":59,"issues":5002,"meta":5004,"navigation":65,"path":5006,"seo":5007,"sitemap":5008,"stem":5009,"subtitle":70,"__hash__":5010},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance.md","Team Performance Feature",[285],{"type":10,"value":4972,"toc":4998},[4973,4980,4986,4989],[13,4974,4975,4976,4979],{},"We've expanded the ",[150,4977,4978],{},"Performance"," feature with an exciting new addition: Team Performance metrics.",[13,4981,4982,4985],{},[150,4983,4984],{},"Team-Wide CPU Monitoring",": Get a complete overview of CPU usage across all hosted instances in your team,\nhelping you track and analyze resource allocation efficiently.",[13,4987,4988],{},"These enhancements are designed to improve operational visibility and resource management based on user feedback from\nour community.",[13,4990,4991,4995],{},[36,4992],{"alt":4993,"dataZoomable":39,"src":4994},"Illustration of the New Feature","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Fteam-performance.png",[43,4996,4997],{},"Overview of CPU Usage in the Team Performance Feature",{"title":39,"searchDepth":55,"depth":55,"links":4999},[],"2025-06-05","A new feature providing comprehensive visualization of instance CPU usage",[5003],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F5525",{"tags":5005},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance",{"title":4969,"description":5001},{"loc":5006},"changelog\u002F2025\u002F06\u002Fteam-performance","5MhNt8jDHvpKJdrPM-rzdFWUiwkdouKy2o0Dil1xpQs",{"id":5012,"title":5013,"authors":5014,"body":5015,"date":5060,"description":5061,"extension":59,"issues":70,"meta":5062,"navigation":65,"path":5064,"seo":5065,"sitemap":5066,"stem":5067,"subtitle":70,"__hash__":5068},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration.md","Pulling snapshots from Git with Pipelines",[8],{"type":10,"value":5016,"toc":5058},[5017,5025,5028,5033,5036,5041,5044,5047,5050],[13,5018,5019,5020,5024],{},"We released support for ",[26,5021,5023],{"href":5022},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration\u002F","pushing snapshots to a Git repository"," as part of the DevOps Pipelines feature last month. As promised, we've now added the ability to pull snapshots back from the repository.",[13,5026,5027],{},"This unlocks a number of powerful workflows with the Pipelines.",[13,5029,5030],{},[150,5031,5032],{},"Review-based Pipelines",[13,5034,5035],{},"The Git Pipeline stage can be configured to push and pull from different branches of the Git Repostory. By making use of a GitHub Pull Request, you can create a workflow where the snapshot is reviewed and merged before the pipeline can deploy the snapshot to the later stages.",[13,5037,5038],{},[150,5039,5040],{},"Deploying snapshots across Teams",[13,5042,5043],{},"By using an external Git Repository, it is simple to create a workflow that enables moving snapshots between two different Teams on the platform whilst maintaining the security and auditability of the individual Teams.",[13,5045,5046],{},"This feature is available today for Enterprise tier teams on FlowFuse Cloud and will be available for self-hosted Enterprise customers as part of the 2.18 release later this week.",[13,5048,5049],{},"We still only support GitHub.com hosted repositories, but we're looking at support for Azure hosted repos in the near future.",[13,5051,5052,5056],{},[36,5053],{"alt":5054,"dataZoomable":39,"src":5055},"Screenshot of a Git Pipeline Stage","\u002Fchangelog\u002F2025\u002F04\u002Fimages\u002Fgit-pipeline-stage.png",[43,5057,5054],{},{"title":39,"searchDepth":55,"depth":55,"links":5059},[],"2025-06-02","Adding git pull support to DevOps Pipelines",{"tags":5063},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration",{"title":5013,"description":5061},{"loc":5064},"changelog\u002F2025\u002F06\u002Fgit-integration","i3goG_F8c3WChbCL3Amx7tMGORAN9WpJfRwEtTP8NwI",{"id":5070,"title":5071,"authors":5072,"body":5074,"date":5060,"description":5094,"extension":59,"issues":70,"meta":5095,"navigation":65,"path":5097,"seo":5098,"sitemap":5099,"stem":5100,"subtitle":70,"__hash__":5101},"changelog\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view.md","Instance Performance View",[5073],"joe-pavitt",{"type":10,"value":5075,"toc":5092},[5076,5079,5087,5090],[13,5077,5078],{},"We've added a new view for every Hosted Instance in FlowFuse, Performance.",[13,5080,5081,5085],{},[36,5082],{"alt":5083,"dataZoomable":39,"src":5084},"Screenshot of the Performance view for a Hosted Instance","\u002Fchangelog\u002F2025\u002F06\u002Fimages\u002Finstance-performance.png",[43,5086,5083],{},[13,5088,5089],{},"This view provides a comprehensive insight into the performance of your hosted Node-RED instances, focussing on CPU usage over time, better enabling you to detect performance issues within your Node-RED Flows.",[13,5091,5046],{},{"title":39,"searchDepth":55,"depth":55,"links":5093},[],"A new view for monitoring the performance of your hosted Node-RED instances",{"tags":5096},[64],"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view",{"title":5071,"description":5094},{"loc":5097},"changelog\u002F2025\u002F06\u002Fteam-performance-view","Jd8QtPC21hhhkt9MrUMhk6xeq8-CQrRm6JTJxApzIRE",{"id":5103,"title":5104,"authors":5105,"body":5106,"date":5210,"description":5211,"extension":59,"issues":70,"meta":5212,"navigation":65,"path":5214,"seo":5215,"sitemap":5216,"stem":5217,"subtitle":70,"__hash__":5218},"changelog\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows.md","Import Node-RED Flows During Remote Instance Setup",[284],{"type":10,"value":5107,"toc":5205},[5108,5111,5122,5124,5164,5168,5184,5186,5194,5202],[13,5109,5110],{},"FlowFuse Device Agent now supports importing Node-RED flows during the setup process. This feature streamlines the configuration of your Remote Instance by allowing you to:",[251,5112,5113,5116,5119],{},[254,5114,5115],{},"Select an existing Node-RED flows directory from your device.",[254,5117,5118],{},"Choose a specific flows file to import.",[254,5120,5121],{},"Automatically import associated credentials and package files.",[385,5123,3905],{"id":3904},[891,5125,5126,5132,5152,5158],{},[254,5127,5128,5131],{},[150,5129,5130],{},"Setup Command",": Run the setup command provided in the FlowFuse interface.",[254,5133,5134,5137,5138],{},[150,5135,5136],{},"Flow Selection",": During setup, you will be prompted to import existing Node-RED flows. Options include:\n",[251,5139,5140,5143,5149],{},[254,5141,5142],{},"Skipping the import.",[254,5144,5145,5146,2327],{},"Selecting a default Node-RED directory (e.g., ",[86,5147,5148],{},".node-red",[254,5150,5151],{},"Specifying a custom path.",[254,5153,5154,5157],{},[150,5155,5156],{},"File Selection",": If a directory is selected, you can choose a specific flows file to import.",[254,5159,5160,5163],{},[150,5161,5162],{},"Automatic Import",": The Device Agent will handle importing credentials, package files, and generate a snapshot to the FlowFuse Platform, setting it as the \"Target Snapshot\" for the device.",[385,5165,5167],{"id":5166},"notes","Notes",[251,5169,5170,5173,5178,5181],{},[254,5171,5172],{},"When your Remote Instance is started, it will install all the necessary pieces and run your new Snapshot.",[254,5174,5175,5176],{},"The Remote Instance must be assigned to an application before running the ",[150,5177,5130],{},[254,5179,5180],{},"Requires Device Agent v3.3.1",[254,5182,5183],{},"Available on FlowFuse Cloud today. For self-hosted customers, you'll need FlowFuse version 2.17",[385,5185,3108],{"id":3107},[13,5187,5188,5192],{},[36,5189],{"alt":5190,"dataZoomable":39,"src":5191},"Screenshot of the FlowFuse interface for configuring a Remote Instance","\u002Fchangelog\u002F2025\u002F05\u002Fimages\u002Fdevice-setup-dialog.png",[43,5193,5190],{},[13,5195,5196,5200],{},[36,5197],{"alt":5198,"dataZoomable":39,"src":5199},"Screenshot of the new import options in the Device Agent during setup","\u002Fchangelog\u002F2025\u002F05\u002Fimages\u002Fdevice-agent-import.png",[43,5201,5198],{},[13,5203,5204],{},"We hope this enhancement simplifies the process of migrating existing Node-RED flows to FlowFuse.",{"title":39,"searchDepth":55,"depth":55,"links":5206},[5207,5208,5209],{"id":3904,"depth":598,"text":3905},{"id":5166,"depth":598,"text":5167},{"id":3107,"depth":598,"text":3108},"2025-05-08","Streamline your Remote Instance setup by importing Node-RED flows with the FlowFuse Device Agent.",{"tags":5213},[64],"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows",{"title":5104,"description":5211},{"loc":5214},"changelog\u002F2025\u002F05\u002Fimport-node-red-flows","twFQkdS6dbW1Z-mnoPAjzK6OE9eiAopvgPI7QPL0Mpc",{"id":5220,"title":5221,"authors":5222,"body":5223,"date":5300,"description":5301,"extension":59,"issues":70,"meta":5302,"navigation":65,"path":5304,"seo":5305,"sitemap":5306,"stem":5307,"subtitle":70,"__hash__":5308},"changelog\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags.md","Changes to tags for flowfuse\u002Fnode-red",[210],{"type":10,"value":5224,"toc":5298},[5225,5235,5238,5243,5246,5249,5252,5287],[13,5226,5227,5228,5230,5231,5234],{},"As part of the upcoming FlowFuse 2.16.0 release we will be updating which\nversion the ",[86,5229,715],{}," tag points to for the ",[86,5232,5233],{},"flowfuse\u002Fnode-red"," containers.",[13,5236,5237],{},"This change will impact self-hosted Docker and Kubernetes installs that have not changed the default stack.",[13,5239,2255,5240,5242],{},[86,5241,715],{}," tag currently points to the latest version of the FlowFuse Stack container but contains Node-RED version 3.0.2 and NodeJS 16. After the update it will contain Node-RED version 4.0.9 and NodeJS 20.",[13,5244,5245],{},"It will then continue to track the latest stable Node-RED version as they are released.",[13,5247,5248],{},"You can update the tag by creating a new version of the Stack under the Admin Settings -> Stacks page as a FlowFuse Admin user.",[13,5250,5251],{},"We make the following tags available which track the latest version of FlowFuse:",[251,5253,5254,5260,5266,5272,5278],{},[254,5255,5256,5259],{},[86,5257,5258],{},"flowfuse\u002Fnode-red:latest"," as described above",[254,5261,5262,5265],{},[86,5263,5264],{},"flowfuse\u002Fnode-red:latest-2.2.x"," which contains Node-RED 2.2.2 NodeJS 16",[254,5267,5268,5271],{},[86,5269,5270],{},"flowfuse\u002Fnode-red:latest-3.0.x"," which contains Node-RED 3.0.2 NodeJS 16",[254,5273,5274,5277],{},[86,5275,5276],{},"flowfuse\u002Fnode-red:latest-3.1.x"," which contains Node-RED 3.1.15 NodeJS 18",[254,5279,5280,5283,5284,5286],{},[86,5281,5282],{},"flowfuse\u002Fnode-red:latest-4.0.x"," which contains Node-RED 4.0.9 NodeJS 20 (same as ",[86,5285,5258],{},")",[13,5288,5289,5290,5293,5294,5297],{},"We also publish tags explicitly pinned to a FlowFuse version with the following format ",[86,5291,5292],{},"\u003Cversion>-\u003Cnode-red-version>"," e.g. ",[86,5295,5296],{},"flowfuse\u002Fnode-red:2.15.0-4.0.x"," which would be FlowFuse 2.15.0 and Node-RED 4.0.x.",{"title":39,"searchDepth":55,"depth":55,"links":5299},[],"2025-04-09","Updating what Node-RED version the latest tag points to",{"tags":5303},[64],"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags",{"title":5221,"description":5301},{"loc":5304},"changelog\u002F2025\u002F03\u002Fcontainer-tags","7L-JK3vbDbXCXlczHMVVyV8ucYJ_zly6YGKEp5BZYA8",{"id":5310,"title":5311,"authors":5312,"body":5313,"date":5300,"description":39,"extension":59,"issues":70,"meta":5352,"navigation":65,"path":5354,"seo":5355,"sitemap":5356,"stem":5357,"subtitle":70,"__hash__":5358},"changelog\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration.md","Git Integration with Pipelines",[8],{"type":10,"value":5314,"toc":5350},[5315,5318,5321,5324,5327,5338,5341,5344],[13,5316,5317],{},"From today, Enterprise tier teams on FlowFuse Cloud are able to add a Git Repository stage to their deployment pipelines. When the pipeline is triggered, the latest snapshot will get pushed to the configured repository.",[13,5319,5320],{},"This has been one of those features that has come up a number of times with our users; we knew we wanted to have Git integration in the platform, but we also wanted it to fit in a natural way with the developer workflows we provide.",[13,5322,5323],{},"This is very much a \"first-iteration\" of the feature that will allow us to get feedback early and continue to iterate.",[13,5325,5326],{},"With this release, the following restrictions apply:",[251,5328,5329,5332,5335],{},[254,5330,5331],{},"Only GitHub.com hosted repostories are supported",[254,5333,5334],{},"Users must create a GitHub Personal Access Token and add to their Team Settings",[254,5336,5337],{},"We currently only support pushing snapshots to a Git repository",[13,5339,5340],{},"This last point is important; this release lets you backup your flows to git, but we haven't yet enabled the return journey of pulling a snapshot from a Git repository back to your Node-RED instance. That'll come in the near future and will unlock a full git-based review workflow within the pipelines.",[13,5342,5343],{},"We'll also look at enabling other Git hosting providers - let us know which you'd like to see on the list.",[13,5345,5346,5348],{},[36,5347],{"alt":5054,"dataZoomable":39,"src":5055},[43,5349,5054],{},{"title":39,"searchDepth":55,"depth":55,"links":5351},[],{"tags":5353},[64],"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration",{"title":5311,"description":39},{"loc":5354},"changelog\u002F2025\u002F04\u002Fgit-integration","g43PxQSdzsiWHN6mw08Qz2YhKlAqE3FjQg2wQdR7k-4",{"id":5360,"title":5361,"authors":5362,"body":5363,"date":5300,"description":5387,"extension":59,"issues":70,"meta":5388,"navigation":65,"path":5390,"seo":5391,"sitemap":5392,"stem":5393,"subtitle":70,"__hash__":5394},"changelog\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing.md","Better Node-RED log handling",[8],{"type":10,"value":5364,"toc":5385},[5365,5368,5371,5374,5377],[13,5366,5367],{},"We've improved the log handling within our Hosted Node-RED instances. Previously we were using a fix sized buffer in memory; meaning the noiser your Node-RED instance was, the less history you'd have. The UI for browsing the logs was also awkward when you wanted to jump back to an earlier section of the logs.",[13,5369,5370],{},"With this release, once you update your instances to the latest version, we will\nnow store the last 7 days worth of logs for each hosted Node-RED instance.",[13,5372,5373],{},"To go along side this, we've added the ability to jump to a specific time\u002Fdate in the logs without having to endlessly scroll.",[13,5375,5376],{},"To start benefiting from the extended logs, make sure you update the latest version via your Instance Settings page.",[13,5378,5379,5383],{},[36,5380],{"alt":5381,"dataZoomable":39,"src":5382},"Screenshot of browsing Node-RED logs by timestamp","\u002Fchangelog\u002F2025\u002F04\u002Fimages\u002Fbrowse-logs.png",[43,5384,5381],{},{"title":39,"searchDepth":55,"depth":55,"links":5386},[],"Keeping the last 7 days of log history and making it easier to access",{"tags":5389},[64],"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing",{"title":5361,"description":5387},{"loc":5390},"changelog\u002F2025\u002F04\u002Finstance-log-browsing","hY36oIiFLctBsu-qWf_inguzkk_mgv8pt-rQXTajGzE",{"id":5396,"title":5397,"authors":5398,"body":5399,"date":5429,"description":5430,"extension":59,"issues":70,"meta":5431,"navigation":65,"path":5433,"seo":5434,"sitemap":5435,"stem":5436,"subtitle":70,"__hash__":5437},"changelog\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning.md","Remote Instance Provisioning",[284],{"type":10,"value":5400,"toc":5427},[5401,5404,5407,5410,5418],[13,5402,5403],{},"FlowFuse has had the ability to provision remote instances at scale for some time now, but assigning remote instances to an application has, until now, been a manual process.",[13,5405,5406],{},"In this update, we have added the ability to have your bulk provisioned remote instances automatically assign themselves to an application upon creation.",[13,5408,5409],{},"This will save you a lot of time if you have a large number of remote instances to provision.",[13,5411,5412,5416],{},[36,5413],{"alt":5414,"dataZoomable":39,"src":5415},"Screenshot of creating a provisioning token","\u002Fchangelog\u002F2025\u002F04\u002Fimages\u002Fcreate-provisioning-token.png",[43,5417,5414],{},[13,5419,5420,5421,5426],{},"Checkout the Bulk Registration section in the ",[26,5422,5425],{"href":5423,"rel":5424},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Fregister",[30],"Device Agent Registration"," documentation for more information on how to use this feature.",{"title":39,"searchDepth":55,"depth":55,"links":5428},[],"2025-04-04","Bulk Registration now supports auto assigning your Remote Instances to an Application.",{"tags":5432},[64],"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning",{"title":5397,"description":5430},{"loc":5433},"changelog\u002F2025\u002F04\u002Fdevice-provisioning","KdzPcSf7qk1IJoZXjInvJfHFChntlFGAANUtAy6ajLE",{"id":5439,"title":5440,"authors":5441,"body":5442,"date":5476,"description":5477,"extension":59,"issues":70,"meta":5478,"navigation":65,"path":5480,"seo":5481,"sitemap":5482,"stem":5483,"subtitle":70,"__hash__":5484},"changelog\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login.md","Local Login for Remote Instances",[284],{"type":10,"value":5443,"toc":5474},[5444,5447,5450,5453,5456,5465],[13,5445,5446],{},"With the new 3.2.0 release of the FlowFuse Device Agent, we have introduced a new Local Login option for Remote Instances.",[13,5448,5449],{},"This feature allows you to enable a local login for your Remote Instance, which is particularly useful in air-gapped environments or times when the instance cannot reach the FlowFuse platform.",[13,5451,5452],{},"When local login is enabled, users can log in to Node-RED directly using the specified credentials.",[13,5454,5455],{},"For day-to-day activity, we still recommending accessing the editor through the FlowFuse Platform for the best user experience. However, for those times when that isn't possible, this option provides a fall-back to allow continued access to the device.",[13,5457,5458,5459,5463],{},"You can configure this option in your Remote Instance Settings tab under the Security section.\n",[36,5460],{"alt":5461,"dataZoomable":39,"src":5462},"Screenshot of local login options","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Fdevice-agent-local-login-settings.png",[43,5464,5461],{},[13,5466,5467,5468,5473],{},"Additionally, you can enable or disable local login for in the Device Agents YAML configuration file. For more information, refer to the ",[26,5469,5472],{"href":5470,"rel":5471},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Fregister\u002F#node-red-settings",[30],"Node-RED Settings"," in our documentation.",{"title":39,"searchDepth":55,"depth":55,"links":5475},[],"2025-03-27","Local Login option for Remote Instances, powered by Device Agent",{"tags":5479},[64],"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login",{"title":5440,"description":5477},{"loc":5480},"changelog\u002F2025\u002F03\u002Fdevice-local-login","ecQpRAQ42luGqRK5_B8P7RP2KhaLS6NbidW52VoNZRw",{"id":5486,"title":5487,"authors":5488,"body":5489,"date":5534,"description":5535,"extension":59,"issues":70,"meta":5536,"navigation":65,"path":5538,"seo":5539,"sitemap":5540,"stem":5541,"subtitle":70,"__hash__":5542},"changelog\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications.md","Resource Alerts",[284],{"type":10,"value":5490,"toc":5531},[5491,5494,5497,5500,5508,5512,5523],[13,5492,5493],{},"To help you manage resource utilization more effectively, we’ve introduced notifications to alert you when you’re nearing critical thresholds.",[13,5495,5496],{},"The new CPU and Memory notifications will notify you when usage exceeds 75% of capacity. This proactive alerting gives you the opportunity to take action before experiencing downtime or performance issues.",[13,5498,5499],{},"We hope this feature helps you avoid unexpected resource-related challenges with your applications.",[13,5501,5502,5506],{},[36,5503],{"alt":5504,"dataZoomable":39,"src":5505},"Screenshot of the new resource notifications","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Fresource-notifications.png",[43,5507,5504],{},[385,5509,5511],{"id":5510},"how-to-enable-or-disable-notifications","How to Enable or Disable Notifications",[13,5513,5514,5515,5518,5519,5522],{},"You can manage these notifications in your Hosted Instance ",[150,5516,5517],{},"Settings"," tab under the ",[150,5520,5521],{},"Alerts"," section.",[13,5524,5525,5529],{},[36,5526],{"alt":5527,"dataZoomable":39,"src":5528},"Screenshot of the new resource notifications settings","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Fresource-notifications-settings.png",[43,5530,5527],{},{"title":39,"searchDepth":55,"depth":55,"links":5532},[5533],{"id":5510,"depth":598,"text":5511},"2025-03-25","Notifications and email alerts to help you stay ahead of resource limits",{"tags":5537},[64],"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications",{"title":5487,"description":5535},{"loc":5538},"changelog\u002F2025\u002F03\u002Fresource-notifications","2EJHLQIRObkCO0DXVTPYAzwQmStsN10i3UakbL8arRo",{"id":5544,"title":5545,"authors":5546,"body":5547,"date":5583,"description":5584,"extension":59,"issues":70,"meta":5585,"navigation":65,"path":5587,"seo":5588,"sitemap":5589,"stem":5590,"subtitle":70,"__hash__":5591},"changelog\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry.md","NPM Package Hosting",[210],{"type":10,"value":5548,"toc":5581},[5549,5552,5559,5567,5570,5578],[13,5550,5551],{},"For Team and Enterprise tier Teams on FlowFuse Cloud we are introducing a NPM package repository giving you a place to host custom Node-RED nodes.",[13,5553,5554,5555,5558],{},"These Node-RED nodes can be used in both Hosted and Remote Instances and will show up in a custom catalogue with the name \"FlowFuse Team ",[1845,5556,5557],{},"team name"," Catalogue\" in the Node-RED editor.",[13,5560,5561,5565],{},[36,5562],{"alt":5563,"dataZoomable":39,"src":5564},"Custom Catalogue","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Fcustom-catalogue.png",[43,5566,5563],{},[13,5568,5569],{},"A list of NPM Packages published to the Team's repository can be seen under the Team's Library section in the \"Custom Nodes\" tab",[13,5571,5572,5576],{},[36,5573],{"alt":5574,"dataZoomable":39,"src":5575},"Custom Nodes list","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Fcustom-node-library.png",[43,5577,5574],{},[13,5579,5580],{},"This feature is also available to self hosting Enterprise customers on Kubernetes with Docker following shortly.",{"title":39,"searchDepth":55,"depth":55,"links":5582},[],"2025-03-13","Make private NPM packages available to Instances",{"tags":5586},[64],"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry",{"title":5545,"description":5584},{"loc":5587},"changelog\u002F2025\u002F03\u002Fteam-npm-registry","_BhHNe65zBRn43ooENxKXXy4un08qOhjchsUE4vTYgQ",{"id":5593,"title":5594,"authors":5595,"body":5596,"date":5614,"description":5615,"extension":59,"issues":70,"meta":5616,"navigation":65,"path":5618,"seo":5619,"sitemap":5620,"stem":5621,"subtitle":70,"__hash__":5622},"changelog\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion.md","MQTT Topic Management",[284],{"type":10,"value":5597,"toc":5612},[5598,5601,5604],[13,5599,5600],{},"We are always looking for ways to improve FlowFuse and today, we have made a small but notable addition: the ability to delete old topics from your hierarchy.",[13,5602,5603],{},"This helps you keep things tidy and not clutter your hierarchy with old topics. Note that if the topic is published to again and detected by the platform, it will get added back.",[13,5605,5606,5610],{},[36,5607],{"alt":5608,"dataZoomable":39,"src":5609},"Screenshot of the new Topic Delete feature","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Ftopic-deletion.png",[43,5611,5608],{},{"title":39,"searchDepth":55,"depth":55,"links":5613},[],"2025-03-12","MQTT Topics can now be removed from the Topic Hierarchy",{"tags":5617},[64],"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion",{"title":5594,"description":5615},{"loc":5618},"changelog\u002F2025\u002F03\u002Ftopic-deletion","YAB3VjNi3UF09fQRqjSphy0p8MPF54ZIO63BzD-NIhw",{"id":5624,"title":5625,"authors":5626,"body":5627,"date":5642,"description":5643,"extension":59,"issues":70,"meta":5644,"navigation":65,"path":5646,"seo":5647,"sitemap":5648,"stem":5649,"subtitle":70,"__hash__":5650},"changelog\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter.md","Filtering Snapshots",[284],{"type":10,"value":5628,"toc":5640},[5629,5632],[13,5630,5631],{},"To simplify management of Snapshots, they can now be filtered to \"All Snapshots\", \"User Snapshots\" or \"Auto Snapshots\"",[13,5633,5634,5638],{},[36,5635],{"alt":5636,"dataZoomable":39,"src":5637},"Screenshot of the new Snapshot filter","\u002Fchangelog\u002F2025\u002F03\u002Fimages\u002Fsnapshot-filter.png",[43,5639,5636],{},{"title":39,"searchDepth":55,"depth":55,"links":5641},[],"2025-03-11","Filter Snapshots to show all, user or auto snapshots",{"tags":5645},[64],"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter",{"title":5625,"description":5643},{"loc":5646},"changelog\u002F2025\u002F03\u002Fsnapshot-filter","JtY2J-tGZGzVzms03vFMEd-I99DzepHDTXYc-cfGp78",{"id":5652,"title":5653,"authors":5654,"body":5655,"date":5668,"description":5669,"extension":59,"issues":70,"meta":5670,"navigation":65,"path":5672,"seo":5673,"sitemap":5674,"stem":5675,"subtitle":70,"__hash__":5676},"changelog\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups.md","Multiple Device Groups in a pipeline",[284],{"type":10,"value":5656,"toc":5666},[5657,5660,5663],[13,5658,5659],{},"Last year, we announced the introduction of Device Groups. For those that are not familiar with Device Groups, this feature enables users to logically group their Remote Instances so that they can be targeted in a DevOps Pipeline facilitating streamlined and efficient deployments across your fleet of devices.",[13,5661,5662],{},"Previously, you could only use a Group as the last stage in a pipeline. With this update, you can now have Groups at other stages in a pipeline. For example, you may have a group of test devices that you want to push updates to before pushing them out to your larger group of production devices.",[13,5664,5665],{},"This improvement not only saves time but also enhances the consistency and reliability of remote instance management across your fleet.",{"title":39,"searchDepth":55,"depth":55,"links":5667},[],"2025-03-10","Device Groups can now be chained in a Pipeline, further simplifying device management across your fleet",{"tags":5671},[64],"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups",{"title":5653,"description":5669},{"loc":5672},"changelog\u002F2025\u002F03\u002Fdevice-groups","hdeR3da6l4tjOHh4WLAiM1RLtbBAWTG4tAQRFcHlT8M",{"id":5678,"title":5679,"authors":5680,"body":5681,"date":5706,"description":5707,"extension":59,"issues":70,"meta":5708,"navigation":65,"path":5710,"seo":5711,"sitemap":5712,"stem":5713,"subtitle":70,"__hash__":5714},"changelog\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier.md","Free Tier now more accessible to all",[8],{"type":10,"value":5682,"toc":5704},[5683,5691,5694,5697],[13,5684,5685,5686,5690],{},"We introduced the Free tier on FlowFuse Cloud ",[26,5687,5689],{"href":5688},"\u002Fblog\u002F2024\u002F12\u002Fflowfuse-release-2-12\u002F","back in December",". This allows you to manage two remote instances using the FlowFuse Device Agent completely free of charge.",[13,5692,5693],{},"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.",[13,5695,5696],{},"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.",[13,5698,5699,5700,5703],{},"Check out the ",[26,5701,5702],{"href":5688},"original announcement blog post"," on how to get started with the Free tier.",{"title":39,"searchDepth":55,"depth":55,"links":5705},[],"2025-03-06","Signing up to our Free Tier no longer requires a credit card",{"tags":5709},[64],"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier",{"title":5679,"description":5707},{"loc":5710},"changelog\u002F2025\u002F03\u002Ffree-tier","KM-gu6Dis-r3nLe8KZmxXo8sMTV53j_WpUkkEtz8BYQ",{"id":5716,"title":5717,"authors":5718,"body":5719,"date":5732,"description":5733,"extension":59,"issues":70,"meta":5734,"navigation":65,"path":5736,"seo":5737,"sitemap":5738,"stem":5739,"subtitle":70,"__hash__":5740},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions.md","MQTT Smart Schema Suggestions",[285],{"type":10,"value":5720,"toc":5730},[5721,5724,5727],[13,5722,5723],{},"FlowFuse's new \"Smart Suggestions\" feature will help you get your full UNS and MQTT Broker documented with ease.",[13,5725,5726],{},"Our agent will monitor traffic through the Broker, and make calculate the schema of any payloads passed through. This assessment is turned into a \"Suggestion\" within the FlowFuse Platform, and can quickly be added to the formal schema for your Broker.",[1500,5728],{"videoid":5729,"params":1503,"style":1504},"bNeTDJUZ1So",{"title":39,"searchDepth":55,"depth":55,"links":5731},[],"2025-03-04","MQTT topics suggestions",{"tags":5735},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions",{"title":5717,"description":5733},{"loc":5736},"changelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","zjYHkRaszCIrhBM_ASTmKRjTdqKUi2l2LZB56U3Dj7o",{"id":5742,"title":5743,"authors":5744,"body":5745,"date":5760,"description":70,"extension":59,"issues":70,"meta":5761,"navigation":65,"path":5763,"seo":5764,"sitemap":5765,"stem":5766,"subtitle":70,"__hash__":5767},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback.md","Improved Broker Connection Feedback",[5073],{"type":10,"value":5746,"toc":5758},[5747,5755],[13,5748,5749,5753],{},[36,5750],{"alt":5751,"dataZoomable":39,"src":5752},"Improved feedback displayed to a user when a third-party broker does nto connect as expected","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Fbroker-error-feedback.png",[43,5754,5751],{},[13,5756,5757],{},"We've improved the feedback displayed to a user when a third-party broker does not connect as expected. This will help users to diagnose and resolve issues with their broker connections more easily, extending on the \"error\" status pill that was initially implemented alongside the broker's name.",{"title":39,"searchDepth":55,"depth":55,"links":5759},[],"2025-02-28",{"tags":5762},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback",{"title":5743,"description":70},{"loc":5763},"changelog\u002F2025\u002F02\u002Fbroker-error-feedback","-3_hMshAU9dKwAQsdKWzuvTaQ6uKvkX90LIjIl1YVow",{"id":5769,"title":5770,"authors":5771,"body":5772,"date":5809,"description":70,"extension":59,"issues":70,"meta":5810,"navigation":65,"path":5812,"seo":5813,"sitemap":5814,"stem":5815,"subtitle":70,"__hash__":5816},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events.md","New Remote Instances Version History Events",[285],{"type":10,"value":5773,"toc":5806},[5774,5777,5781,5803],[13,5775,5776],{},"Users can now get better visibility of the state of their Remote Instances with additional events in the Version History timeline. This enhancement improves traceability and provides deeper insights into remote instance state changes over time.",[170,5778,5780],{"id":5779},"new-trackable-events","New Trackable Events",[251,5782,5783,5788,5793,5798],{},[254,5784,5785],{},[150,5786,5787],{},"Deploying Snapshots to Remote Instance via a Pipeline",[254,5789,5790],{},[150,5791,5792],{},"Deploying Snapshots through a Hosted Instance",[254,5794,5795],{},[150,5796,5797],{},"Snapshot Rollback",[254,5799,5800],{},[150,5801,5802],{},"Snapshot Create",[13,5804,5805],{},"These events will be automatically recorded in the version history, allowing users to review and audit changes more effectively.",{"title":39,"searchDepth":55,"depth":55,"links":5807},[5808],{"id":5779,"depth":194,"text":5780},"2025-02-25",{"tags":5811},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events",{"title":5770,"description":70},{"loc":5812},"changelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","ldB-btu4ok5sky-dmepq67Z5yN6gFapQvK91d_jfm8M",{"id":5818,"title":5819,"authors":5820,"body":5821,"date":5843,"description":70,"extension":59,"issues":70,"meta":5844,"navigation":65,"path":5846,"seo":5847,"sitemap":5848,"stem":5849,"subtitle":70,"__hash__":5850},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration.md","Re-send Team Invitations",[285],{"type":10,"value":5822,"toc":5841},[5823,5830,5833],[13,5824,5825,5826,5829],{},"We have added the ability to ",[150,5827,5828],{},"re-send team invitations",", which also extends the expiration date of the invitation. This improvement ensures that invitations remain valid for a longer period and allows team administrators to easily re-invite users who may have missed their initial invitation.",[13,5831,5832],{},"This update enhances user management and simplifies the process of maintaining team memberships within FlowFuse.",[13,5834,5835,5839],{},[36,5836],{"alt":5837,"dataZoomable":39,"src":5838},"Screenshot of the member invitation page","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Fresend-invitation.png",[43,5840,5837],{},{"title":39,"searchDepth":55,"depth":55,"links":5842},[],"2025-02-21",{"tags":5845},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration",{"title":5819,"description":70},{"loc":5846},"changelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Hme0zyuTzxzoyBnrzpF5a1fGBpy7VE6mrnkWj8wDAo4",{"id":5852,"title":5853,"authors":5854,"body":5855,"date":5872,"description":5873,"extension":59,"issues":70,"meta":5874,"navigation":65,"path":5876,"seo":5877,"sitemap":5878,"stem":5879,"subtitle":70,"__hash__":5880},"changelog\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search.md","Search & Filter for Topic Hierarchy List",[285],{"type":10,"value":5856,"toc":5870},[5857,5867],[13,5858,5859,5863,5865],{},[36,5860],{"alt":5861,"dataZoomable":39,"src":5862},"Search and filter functionality in the topic hierarchy list","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Ftopic-hierarchy-search.png",[1107,5864],{},[43,5866,5861],{},[13,5868,5869],{},"We've introduced search and filter capabilities to the topic hierarchy list. This allows users to quickly find specific topics, making navigation more efficient and improving usability when working with large topic trees.",{"title":39,"searchDepth":55,"depth":55,"links":5871},[],"2025-02-18","Users can now search and filter the topic hierarchy list for easier navigation.",{"tags":5875},[64],"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search",{"title":5853,"description":5873},{"loc":5876},"changelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","boiGGT18Z_ktQUU91xHlpKCVauIUay5kX41CxwR_LCQ",{"id":5882,"title":5883,"authors":5884,"body":5885,"date":5919,"description":70,"extension":59,"issues":70,"meta":5920,"navigation":65,"path":5922,"seo":5923,"sitemap":5924,"stem":5925,"subtitle":70,"__hash__":5926},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates.md","FlowFuse User Authentication on Remote Instances",[8],{"type":10,"value":5886,"toc":5915},[5887,5890,5893,5896,5899,5903,5906,5909,5912],[13,5888,5889],{},"With the 3.1.1 release of the FlowFuse Device Agent, we've added two important pieces of new functionality.",[385,5891,792],{"id":5892},"flowfuse-user-authentication",[13,5894,5895],{},"It is now possible to enable end-point security on the instance. In the same way you can for Hosted Instances,\nyou can now configure Basic Username\u002FPassword authentication or the more powerful FlowFuse User Authentication.",[13,5897,5898],{},"This means you can serve up your dashboards on remote Instances confident that only users in your FlowFuse team can access them.",[385,5900,5902],{"id":5901},"modifying-settings-in-developer-mode","Modifying settings in Developer Mode",[13,5904,5905],{},"Whilst a remote instance is in developer mode, you can access the Node-RED editor through the FlowFuse platform. This\nis a great way to develop your flows on real hardware through the platform.",[13,5907,5908],{},"A common developer task is to want to modify environment variables, or change device settings (such as enabling the new\nFlowFuse User authentication option).",[13,5910,5911],{},"Previously this would require taking the device out of developer mode in order to apply the changes. From a workflow, this required lots of additional steps for not a lot of benefit.",[13,5913,5914],{},"With the new release of the Device Agent, the agent will pick up any settings changes when it is restarted via the action menu in the FlowFuse UI. A small change, but a big improvement to the developer workflow.",{"title":39,"searchDepth":55,"depth":55,"links":5916},[5917,5918],{"id":5892,"depth":598,"text":792},{"id":5901,"depth":598,"text":5902},"2025-02-13",{"tags":5921},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates",{"title":5883,"description":70},{"loc":5922},"changelog\u002F2025\u002F02\u002Fdevice-agent-updates","c6H9kYrBh9_sJPBC05_CeW7DLkbqy3FqBIdQe0d414M",{"id":5928,"title":5929,"authors":5930,"body":5931,"date":5969,"description":5970,"extension":59,"issues":70,"meta":5971,"navigation":65,"path":5973,"seo":5974,"sitemap":5975,"stem":5976,"subtitle":70,"__hash__":5977},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline.md","Version History Timeline",[285],{"type":10,"value":5932,"toc":5967},[5933,5939,5942,5945,5956],[13,5934,5935,5938],{},[150,5936,5937],{},"Remote instances"," can now make use of the new Timeline feature, providing a concise, chronological view of key activities within your Node-RED remote setup.",[13,5940,5941],{},"The Timeline and Snapshots are now grouped together under the Version History tab, simplifying the navigation of your remote instance's history.",[13,5943,5944],{},"This feature is only available to Enterprise license and Cloud Team users. Note that the Timeline can only be accessed at the remote instance level.",[13,5946,5947,5951,5953],{},[36,5948],{"alt":5949,"dataZoomable":39,"src":5950},"Screenshot showing the version history Timeline","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Fdevice-version-history-timeline.png",[1107,5952],{},[43,5954,5955],{},"Screenshot showing the new version history timeline",[13,5957,5958,5962,5964],{},[36,5959],{"alt":5960,"dataZoomable":39,"src":5961},"version-history-snapshots.png","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Fdevice-version-history-snapshots.png",[1107,5963],{},[43,5965,5966],{},"Screenshot showing the relocated snapshot page under the version history tab",{"title":39,"searchDepth":55,"depth":55,"links":5968},[],"2025-02-12","Components of what to include in a snapshot can now be selected.",{"tags":5972},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"title":5929,"description":5970},{"loc":5973},"changelog\u002F2025\u002F02\u002Fdevice-version-history-timeline","b-TK5ZCpuoOhqi7o7W5bKjTfktU-FGGKht4C4wfMQB8",{"id":5979,"title":5980,"authors":5981,"body":5982,"date":5969,"description":70,"extension":59,"issues":70,"meta":6018,"navigation":65,"path":6020,"seo":6021,"sitemap":6022,"stem":6023,"subtitle":70,"__hash__":6024},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers.md","External MQTT Brokers",[210],{"type":10,"value":5983,"toc":6016},[5984,5987,5990,5999,6002,6010,6013],[13,5985,5986],{},"In a previous release, we introduced the FlowFuse Team Broker; an MQTT broker available to all instances running in your team. Whilst the Team Broker is a great addition, we are aware that many of our customers already have their own existing MQTT brokers and infrastructure.",[13,5988,5989],{},"We have now made it possible to connect the FlowFuse platform to your existing external MQTT broker. With that you'll get access to the same great features to help you gain a clear understanding of the activity on your broker, and the structure of the data and topics that are being used.",[13,5991,5992,5996],{},[36,5993],{"alt":5994,"dataZoomable":39,"src":5995},"Screenshot from creating new external broker","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Fnew-external-broker.png",[43,5997,5998],{},"Screenhot from creating new external broker",[13,6000,6001],{},"As well as building a topic schema, the message payloads will also be\ninspected to infer their format to help you understand your data.",[13,6003,6004,6008],{},[36,6005],{"alt":6006,"dataZoomable":39,"src":6007},"Screenshot of topic and inferred payload schema","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Ftopic-and-payload-schema.png",[43,6009,6006],{},[13,6011,6012],{},"Whilst connected, the FlowFuse platform will monitor the messages being published on the broker and update the information every few minutes. This means there will be a short delay between a message being published to a topic and that topic being shown in the hierarchy.",[13,6014,6015],{},"This is available on FlowFuse Cloud and for Self Hosting users with an Enterprise License on Kubernetes and LocalFS. Docker support will follow shortly.",{"title":39,"searchDepth":55,"depth":55,"links":6017},[],{"tags":6019},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers",{"title":5980,"description":70},{"loc":6020},"changelog\u002F2025\u002F02\u002Fexternal-brokers","rZQIzXNT_wmQpNJPPCPQu1tu_oXRf1zQ8jQHqw8tDIc",{"id":6026,"title":6027,"authors":6028,"body":6029,"date":5969,"description":6056,"extension":59,"issues":70,"meta":6057,"navigation":65,"path":6059,"seo":6060,"sitemap":6061,"stem":6062,"subtitle":70,"__hash__":6063},"changelog\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs.md","Personalized Schema Documentation",[5073],{"type":10,"value":6030,"toc":6054},[6031,6039,6042,6051],[13,6032,6033,6037],{},[36,6034],{"alt":6035,"dataZoomable":39,"src":6036},"Screenshot of the new MQTT Broker schema documentation view available in FlowFuse","\u002Fchangelog\u002F2025\u002F02\u002Fimages\u002Fschema-documentation.png",[43,6038,6035],{},[13,6040,6041],{},"This new view for your MQTT Broker focusses on clarity, and collaboration. It provides a single, easy to read window that provides the relevant information any member of your team or organization would need in order to understand what your MQTT broker is used for.",[13,6043,6044,6045,6050],{},"The underlying schema is generated automatically by FlowFuse, using the industry-standard, open-sourced, ",[26,6046,6049],{"href":6047,"rel":6048},"https:\u002F\u002Fwww.asyncapi.com\u002F",[30],"AsyncAPI",", saving your months of resource in manually documenting payload and topic structures yourself.",[13,6052,6053],{},"The documentation provides a comprehensive view of the topics published to on your Broker, as well as crafted descriptions to help users understand each topic's purpose. This feature is available for both the in-built FlowFuse Broker, and any third-party broker that you choose to connect to.",{"title":39,"searchDepth":55,"depth":55,"links":6055},[],"View personalized schema documentation for your MQTT brokers in this new, automatically generated view.",{"tags":6058},[64],"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs",{"title":6027,"description":6056},{"loc":6059},"changelog\u002F2025\u002F02\u002Fschema-docs","ARhyUviPAvn-mYDD2vxIt6COs4UQNaPVEVLi3wqADqY",{"id":6065,"title":6066,"authors":6067,"body":6068,"date":6126,"description":6072,"extension":59,"issues":70,"meta":6127,"navigation":65,"path":6130,"seo":6131,"sitemap":6132,"stem":6133,"subtitle":70,"__hash__":6134},"changelog\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars.md","Hidden Environment Variables",[285],{"type":10,"value":6069,"toc":6123},[6070,6073,6076,6079,6104,6107,6115],[13,6071,6072],{},"We’ve expanded the functionality of managing Node-RED environment variables by introducing the ability to hide their values in the UI.",[385,6074,6075],{"id":2394},"What’s new?",[13,6077,6078],{},"This feature is supported by both hosted and remote Node-RED instances.",[251,6080,6081,6084,6087,6101],{},[254,6082,6083],{},"Users can now designate values as 'hidden' when creating or editing them.",[254,6085,6086],{},"Hidden values are concealed in the UI for enhanced privacy and security.",[254,6088,6089,6090],{},"Once marked as hidden and saved:\n",[251,6091,6092,6098],{},[254,6093,6094,6095,6097],{},"the ",[150,6096,3413],{}," cannot be changed.",[254,6099,6100],{},"the value can only be updated - its existing value cannot be seen.",[254,6102,6103],{},"To make a value visible again, users must delete the entry and recreate it as a visible one.",[13,6105,6106],{},"This feature enhances security and allows for more control over sensitive configuration data, ensuring better management in your Node-RED workflows.",[13,6108,6109,6113],{},[36,6110],{"alt":6111,"dataZoomable":39,"src":6112},"Screenshot of the new hidden environment variables feature - Hosted Instances","\u002Fchangelog\u002F2025\u002F01\u002Fimages\u002Fhidden-env-var-instances.png",[43,6114,6111],{},[13,6116,6117,6121],{},[36,6118],{"alt":6119,"dataZoomable":39,"src":6120},"Screenshot of the new hidden environment variables feature - Remote Instances","\u002Fchangelog\u002F2025\u002F01\u002Fimages\u002Fhidden-env-var-devices.png",[43,6122,6119],{},{"title":39,"searchDepth":55,"depth":55,"links":6124},[6125],{"id":2394,"depth":598,"text":6075},"2025-01-21",{"summary":6128,"tags":6129},"Users can now hide environment variable values in the UI when creating or editing them.",[64],"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars",{"title":6066,"description":6072},{"loc":6130},"changelog\u002F2025\u002F01\u002Fhidden-env-vars","2EbsZh79ie28FdWTspen-DiSp9bfqW2dh6qiYqUmTb0",{"id":6136,"title":6137,"authors":6138,"body":6139,"date":6160,"description":6161,"extension":59,"issues":70,"meta":6162,"navigation":65,"path":6164,"seo":6165,"sitemap":6166,"stem":6167,"subtitle":70,"__hash__":6168},"changelog\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups.md","Team level view of Groups",[285],{"type":10,"value":6140,"toc":6158},[6141,6149,6152,6155],[13,6142,6143,6147],{},[36,6144],{"alt":6145,"dataZoomable":39,"src":6146},"Screenshot from the new team level groups","\u002Fchangelog\u002F2025\u002F01\u002Fimages\u002Fteam-level-groups.png",[43,6148,6145],{},[13,6150,6151],{},"Managing remote instances is easier with the new Team-level view of Groups.",[13,6153,6154],{},"Groups let you organize your Remote Instances by application. They can then be used as a Target in DevOps pipelines for seamless updates across\nmultiple instances in one operation.",[13,6156,6157],{},"This simplifies deployments, enhances collaboration, and streamlines infrastructure management for faster, more\nefficient workflows.",{"title":39,"searchDepth":55,"depth":55,"links":6159},[],"2025-01-16","We've introduced a new feature that provides teams with a comprehensive view of Groups, helping to streamline collaboration and organization.",{"tags":6163},[64],"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups",{"title":6137,"description":6161},{"loc":6164},"changelog\u002F2025\u002F01\u002Fteam-level-groups","_mf7UtnrpHk2pktszKj6F0SRvwUp1z6zkXpFg-BG9HM",{"id":6170,"title":6171,"authors":6172,"body":6173,"date":6189,"description":6190,"extension":59,"issues":70,"meta":6191,"navigation":65,"path":6193,"seo":6194,"sitemap":6195,"stem":6196,"subtitle":70,"__hash__":6197},"changelog\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics.md","Improved Diagnostics",[284],{"type":10,"value":6174,"toc":6187},[6175,6178,6181,6184],[13,6176,6177],{},"It happens! Sometimes things go wrong, but don't worry, we have you covered.",[13,6179,6180],{},"For Team and Enterprise customers on FlowFuse Cloud, we've improved the emails we send notifying you that something has gone wrong with one of your instances.",[13,6182,6183],{},"The emails now include more information about what has happened, including the most recent logs from Node-RED. We also include some tips as to what to do next, whether it was a code bug or a memory issue that triggered the problem.",[13,6185,6186],{},"We hope you never need to see these emails, but if you do, we hope they help you get back on track quickly.",{"title":39,"searchDepth":55,"depth":55,"links":6188},[],"2025-01-14","Improved diagnostic info directly to your inbox",{"tags":6192},[64],"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics",{"title":6171,"description":6190},{"loc":6193},"changelog\u002F2025\u002F01\u002Fimproved-diagnostics","7XmjLWiMhBdOAAZ_hLM4BcnTdIn-q90esZ-gTKZ7InI",{"id":6199,"title":6200,"authors":6201,"body":6202,"date":6220,"description":6221,"extension":59,"issues":70,"meta":6222,"navigation":65,"path":6224,"seo":6225,"sitemap":6226,"stem":6227,"subtitle":70,"__hash__":6228},"changelog\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding.md","New Onboarding Tour for Free Tier Users",[5073],{"type":10,"value":6203,"toc":6218},[6204,6212,6215],[13,6205,6206,6210],{},[36,6207],{"alt":6208,"dataZoomable":39,"src":6209},"Screenshot from the new onboarding tour for \"Free\" tier FlowFuse Cloud users","\u002Fchangelog\u002F2025\u002F01\u002Fimages\u002Ffree-tier-onboarding.png",[43,6211,6208],{},[13,6213,6214],{},"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.",[13,6216,6217],{},"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.",{"title":39,"searchDepth":55,"depth":55,"links":6219},[],"2025-01-07","For new, free-tier users on FlowFuse Cloud, we have a new onboarding tour to help you get started",{"tags":6223},[64],"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding",{"title":6200,"description":6221},{"loc":6224},"changelog\u002F2025\u002F01\u002Ffree-tier-onboarding","OZsQGHTjnZ3BD7sPiNaGqlFKYVAr68n3dZc919qn_G4",{"id":6230,"title":6231,"authors":6232,"body":6233,"date":6263,"description":70,"extension":59,"issues":70,"meta":6264,"navigation":65,"path":6266,"seo":6267,"sitemap":6268,"stem":6269,"subtitle":70,"__hash__":6270},"changelog\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe.md","Allow Dashboards to be embedded in iFrames",[210],{"type":10,"value":6234,"toc":6261},[6235,6238,6241,6250,6253],[13,6236,6237],{},"With the 2.12.0 release the correct HTTP Headers can now be set to allow Dashboards hosted in Node-RED Instances on FlowFuse to be embedded into other pages as iFrames.",[13,6239,6240],{},"This option is under the Instance Settings on the Editor section.",[13,6242,6243,6247],{},[36,6244],{"alt":6245,"dataZoomable":39,"src":6246},"Enable iFrame Support","\u002Fchangelog\u002F2024\u002F12\u002Fimages\u002Fenable-iframe.png",[43,6248,6249],{},"Enabled iFrame Support",[13,6251,6252],{},"This feature will require the latest Stack version, you will be prompted to upgrade if required.",[13,6254,6255,6259],{},[36,6256],{"alt":6257,"dataZoomable":39,"src":6258},"Upgrade Stack to Enable","\u002Fchangelog\u002F2024\u002F12\u002Fimages\u002Fupgrade-iframe-dashboard.png",[43,6260,6257],{},{"title":39,"searchDepth":55,"depth":55,"links":6262},[],"2024-12-19",{"tags":6265},[64],"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe",{"title":6231,"description":70},{"loc":6266},"changelog\u002F2024\u002F12\u002Fdashboad-iframe","MqznP_Y_VwF_SB0loYP5Jlo5XDx-r_QPa7QLBaLr5Es",{"id":6272,"title":6273,"authors":6274,"body":6275,"date":6263,"description":70,"extension":59,"issues":70,"meta":6285,"navigation":65,"path":6287,"seo":6288,"sitemap":6289,"stem":6290,"subtitle":70,"__hash__":6291},"changelog\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache.md","Device Editor Access Speed Up",[210],{"type":10,"value":6276,"toc":6283},[6277,6280],[13,6278,6279],{},"With the 2.12 release we have included some improvements to the Device Editor experience.",[13,6281,6282],{},"For Devices running with Node-RED 4.0.x and newer, there should be significant performance improvements when loading the editor, especially when the device is on a slow network link.",{"title":39,"searchDepth":55,"depth":55,"links":6284},[],{"tags":6286},[64],"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache",{"title":6273,"description":70},{"loc":6287},"changelog\u002F2024\u002F12\u002Fdevice-editor-cache","Xa7KREhP51D30demmr0HfdBLVEwAWIuH3POyLiY27c0",{"id":6293,"title":6294,"authors":6295,"body":6296,"date":6325,"description":70,"extension":59,"issues":70,"meta":6326,"navigation":65,"path":6328,"seo":6329,"sitemap":6330,"stem":6331,"subtitle":70,"__hash__":6332},"changelog\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline.md","Team BOM and Pipeline Views",[210],{"type":10,"value":6297,"toc":6323},[6298,6301,6304,6312,6315],[13,6299,6300],{},"Team-level views of all Pipelines and Bill of Materials have been added to provide a complete overview.",[13,6302,6303],{},"The Bill of Materials view shows which components and their versions across all Node-RED Devices &  Instances in the whole Team rather than at an Application level.",[13,6305,6306,6310],{},[36,6307],{"alt":6308,"dataZoomable":39,"src":6309},"Team BOM view","\u002Fchangelog\u002F2024\u002F12\u002Fimages\u002Fteam-bom.png",[43,6311,6308],{},[13,6313,6314],{},"Similarly the Team Pipeline view shows all CI delivery pipelines in all the Applications in the Team, giving team members a quicker way to jump to a specific Pipeline.",[13,6316,6317,6321],{},[36,6318],{"alt":6319,"dataZoomable":39,"src":6320},"Team Pipelines","\u002Fchangelog\u002F2024\u002F12\u002Fimages\u002Fteam-pipeline.png",[43,6322,6319],{},{"title":39,"searchDepth":55,"depth":55,"links":6324},[],"2024-12-16",{"tags":6327},[64],"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline",{"title":6294,"description":70},{"loc":6328},"changelog\u002F2024\u002F12\u002Fteam-bom-timeline","9-B6EMREWrUh_tj8uv7D6UqS0skaoYi0bfFmbia4qjQ",{"id":6334,"title":6335,"authors":6336,"body":6337,"date":6363,"description":6364,"extension":59,"issues":70,"meta":6365,"navigation":65,"path":6367,"seo":6368,"sitemap":6369,"stem":6370,"subtitle":70,"__hash__":6371},"changelog\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy.md","MQTT Topic Hierarchy view",[8],{"type":10,"value":6338,"toc":6361},[6339,6347,6350,6353],[13,6340,6341,6342,6346],{},"Having recently added ",[26,6343,6345],{"href":6344},"\u002Fblog\u002F2024\u002F10\u002Fannouncement-mqtt-broker","our very own MQTT Service"," to the platform, we're continuing to expand on the features and tools we provide to help teams build their solutions.",[13,6348,6349],{},"We have added a view that shows you what MQTT topics are being used on the Team Broker. This helps give you clarity on the structure of your topic-space, whether you're using the MQTT Broker for a unified namespace (UNS) or any other use case.",[13,6351,6352],{},"This is a small iteration of the feature but we'll have lots more to come.",[13,6354,6355,6359],{},[36,6356],{"alt":6357,"dataZoomable":39,"src":6358},"Screenshot of the UI to explore your MQTT topic hierarchy","\u002Fchangelog\u002F2024\u002F11\u002Fimages\u002Fscreenshot-mqtt-hierarchy.png",[43,6360,6357],{},{"title":39,"searchDepth":55,"depth":55,"links":6362},[],"2024-11-21","View your in-use MQTT topics",{"tags":6366},[64],"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy",{"title":6335,"description":6364},{"loc":6367},"changelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","ZM0aPnvfcJUYamADJO6J4zvWJFgpxgGxuNS0131HDoA",{"id":6373,"title":6374,"authors":6375,"body":6376,"date":6363,"description":70,"extension":59,"issues":70,"meta":6397,"navigation":65,"path":6399,"seo":6400,"sitemap":6401,"stem":6402,"subtitle":70,"__hash__":6403},"changelog\u002Fchangelog\u002F2024\u002F11\u002Fteam-search.md","Team-wide search",[8],{"type":10,"value":6377,"toc":6395},[6378,6381,6384,6387],[13,6379,6380],{},"A new search bar has been added that makes it quick and easy to find resources within your team.",[13,6382,6383],{},"This expands on the search available on the Applications summary view - but by moving to the top header, it's now available on all pages.",[13,6385,6386],{},"For this release, it searches your Applications, Instances and Devices. We'll be expanding its coverage in future iterations to include other resources in the team.",[13,6388,6389,6393],{},[36,6390],{"alt":6391,"dataZoomable":39,"src":6392},"Screenshot of the team-wide search","\u002Fchangelog\u002F2024\u002F11\u002Fimages\u002Fscreenshot-search.png",[43,6394,6391],{},{"title":39,"searchDepth":55,"depth":55,"links":6396},[],{"tags":6398},[64],"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search",{"title":6374,"description":70},{"loc":6399},"changelog\u002F2024\u002F11\u002Fteam-search","CX64U2U0pSJfasPXqhEbwBQzDevFbA84mDTvHbbgPN8",{"id":6405,"title":6406,"authors":6407,"body":6408,"date":6426,"description":6427,"extension":59,"issues":70,"meta":6428,"navigation":65,"path":6430,"seo":6431,"sitemap":6432,"stem":6433,"subtitle":70,"__hash__":6434},"changelog\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy.md","Audit logs show hierarchical events",[284],{"type":10,"value":6409,"toc":6424},[6410,6413,6421],[13,6411,6412],{},"In FlowFuse V2.11, we have updated the Audit Log views to let you see more of the events happening within your team. Previously, the Audit Log view would only show you top-level events happening to the application or team. With this release, it now provides an aggregated view of all of your resources.\nAdditionally, each row contains an icon and name of the item raised the event that you can click to navigate straight to it making your workflow more streamlined.",[13,6414,6415,6419],{},[36,6416],{"alt":6417,"src":6418},"Screenshot showing Audit Log with hierarchical events","\u002Fchangelog\u002F2024\u002F11\u002Fimages\u002Faudit-log-child-events.png",[43,6420,6417],{},[13,6422,6423],{},"We hope this feature will help you better understand and navigate your FlowFuse applications.",{"title":39,"searchDepth":55,"depth":55,"links":6425},[],"2024-11-20","Audit logs for Team, Application and Instance will now include child events",{"tags":6429},[64],"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy",{"title":6406,"description":6427},{"loc":6430},"changelog\u002F2024\u002F11\u002Faudit-log-hierarchy","uVInpslHKdQUVEz509AZ-2Q6Ulj6XF8YmSjLAz-VZYM",{"id":6436,"title":6437,"authors":6438,"body":6439,"date":6463,"description":6464,"extension":59,"issues":70,"meta":6465,"navigation":65,"path":6467,"seo":6468,"sitemap":6469,"stem":6470,"subtitle":70,"__hash__":6471},"changelog\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release.md","Device Agent 3.0 released",[8],{"type":10,"value":6440,"toc":6461},[6441,6444,6447,6450,6453],[13,6442,6443],{},"The FlowFuse Device Agent is the piece of software we provide to manage Node-RED instances running anywhere outside of the FlowFuse platform.",[13,6445,6446],{},"Today we have released the latest version of the agent that now requires at least Node.js 18 to run. To reflect this change, we are releasing this as a new major version - 3.0.",[13,6448,6449],{},"We recognize that software update lifecycles can be a challenge in some environments. This is why we've held off dropping support for older Node.js versions for as long as we could. However, we have to balance that against ensuring we continue to keep the Device Agent up to date with the latest security fixes.",[13,6451,6452],{},"If your devices cannot be updated to the latest Node.js versions, then please ensure you stay on the 2.x release of the Device Agent until a time that you are able to update Node.js.",[13,6454,6455,6456,227],{},"Details for upgrading to this release are available ",[26,6457,6460],{"href":6458,"rel":6459},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Finstall\u002F#upgrading-the-agent",[30],"in the documentation",{"title":39,"searchDepth":55,"depth":55,"links":6462},[],"2024-11-08","New version of the Device Agent drops support for old Node.js versions",{"tags":6466},[64],"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release",{"title":6437,"description":6464},{"loc":6467},"changelog\u002F2024\u002F11\u002Fdevice-agent-release","i9bxDRN6qSYGRKY8Czuyf7PuABrYHVG1C-Qx0AqTvIc",{"id":6473,"title":6474,"authors":6475,"body":6476,"date":6498,"description":6499,"extension":59,"issues":70,"meta":6500,"navigation":65,"path":6503,"seo":6504,"sitemap":6505,"stem":6506,"subtitle":70,"__hash__":6507},"changelog\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service.md","MQTT Broker Service",[210],{"type":10,"value":6477,"toc":6496},[6478,6481,6484,6487],[13,6479,6480],{},"To celebrate 25 years since the first release of the MQTT Specification we are happy announce a new MQTT Broker Service as part of FlowFuse Cloud.",[13,6482,6483],{},"The initial deployment is available to Enterprise Teams and allows up to 20 clients to connect to the broker. Each team has their own independent topic space and can set their own topic ACLs to control what clients can access.",[13,6485,6486],{},"From today, this feature is available to FlowFuse Cloud Enterprise Teams. We'll be bringing it to Self-Hosted customers in the near future, as well as adding the ability to purchase additional packs of clients.",[13,6488,6489,6490,6495],{},"See the ",[26,6491,6494],{"href":6492,"rel":6493},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fcloud\u002Fintroduction\u002F#enterprise-team-broker",[30],"broker documentation"," for more details.",{"title":39,"searchDepth":55,"depth":55,"links":6497},[],"2024-10-24","Generic MQTT Broker Service",{"tags":6501},[64,6502],"mqtt","\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service",{"title":6474,"description":6499},{"loc":6503},"changelog\u002F2024\u002F10\u002Fmqtt-service","LPWr1odzWBfyIxyxLSHloMfdAeA69MDezQ9IoqQxOws",{"id":6509,"title":5929,"authors":6510,"body":6511,"date":6498,"description":6541,"extension":59,"issues":70,"meta":6542,"navigation":65,"path":6544,"seo":6545,"sitemap":6546,"stem":6547,"subtitle":70,"__hash__":6548},"changelog\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline.md",[285],{"type":10,"value":6512,"toc":6539},[6513,6516,6519,6522,6525,6532],[13,6514,6515],{},"Instances can now make use of the new Timeline feature, providing a concise, chronological view of key activities within your Node-RED instance.",[13,6517,6518],{},"The Timeline tracks important events such as pipeline stage deployments, snapshot restorations, flow deployments, snapshot creations, and updates to instance settings, offering clear insight into when and what changes have been made.",[13,6520,6521],{},"The Timeline and Snapshots are now grouped together under the Version History tab, simplifying the navigation of your instance's history.",[13,6523,6524],{},"This feature is only available to Enterprise license and Cloud Team users. Note that the Timeline can only be accessed at the instance level.",[13,6526,6527,6530],{},[36,6528],{"alt":5949,"dataZoomable":39,"src":6529},"\u002Fchangelog\u002F2024\u002F10\u002Fimages\u002Fversion-history-timeline.png",[43,6531,5955],{},[13,6533,6534,6537],{},[36,6535],{"alt":5960,"dataZoomable":39,"src":6536},"\u002Fchangelog\u002F2024\u002F10\u002Fimages\u002Fversion-history-snapshots.png",[43,6538,5966],{},{"title":39,"searchDepth":55,"depth":55,"links":6540},[],"Components of a what to include in a snapshot can now be selected.",{"tags":6543},[64],"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"title":5929,"description":6541},{"loc":6544},"changelog\u002F2024\u002F10\u002Fversion-history-timeline","ZAHwPWfCr9Z3TRcNMr4MMqdwb2uC9hyct7ut_M9ErLw",{"id":6550,"title":6551,"authors":6552,"body":6553,"date":6579,"description":6580,"extension":59,"issues":70,"meta":6581,"navigation":65,"path":6583,"seo":6584,"sitemap":6585,"stem":6586,"subtitle":70,"__hash__":6587},"changelog\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars.md","Environment Variables for your Device Groups",[284],{"type":10,"value":6554,"toc":6577},[6555,6558,6566,6569],[13,6556,6557],{},"We have added the ability to set Environment Variables on a Device Group.\nThis allows you to set common values that all member devices can make use of.",[13,6559,6560,6564],{},[36,6561],{"alt":6562,"dataZoomable":39,"src":6563},"Screenshot showing Device Group Environment Variables","\u002Fchangelog\u002F2024\u002F10\u002Fimages\u002Fdevice-group--with-env-vars.png",[43,6565,6562],{},[13,6567,6568],{},"We hope this feature will make it easier to manage your devices and keep your configuration in one place.",[13,6570,6489,6571,6576],{},[26,6572,6575],{"href":6573,"rel":6574},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fdevice-groups",[30],"Device Group"," documentation for more information on how to set environment variables for your device groups.",{"title":39,"searchDepth":55,"depth":55,"links":6578},[],"2024-10-21","Set Environment Variables in your Device Groups for its member devices to utilize",{"tags":6582},[64],"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars",{"title":6551,"description":6580},{"loc":6583},"changelog\u002F2024\u002F10\u002Fdevice-group-env-vars","EnxS3ASwiSGW_rKEztOO1SbSJ1AYFIeEpNiOwo92zAM",{"id":6589,"title":6590,"authors":6591,"body":6592,"date":6648,"description":6541,"extension":59,"issues":70,"meta":6649,"navigation":65,"path":6651,"seo":6652,"sitemap":6653,"stem":6654,"subtitle":70,"__hash__":6655},"changelog\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options.md","Snapshot Upload and Download Improvements",[284],{"type":10,"value":6593,"toc":6646},[6594,6597,6600,6619,6627,6635,6638],[13,6595,6596],{},"We have added the ability to select which components of a snapshot you want to keep when downloading or uploading a snapshot.",[13,6598,6599],{},"The options available are:",[251,6601,6602,6605,6608],{},[254,6603,6604],{},"Flows: Include the flows of the snapshot",[254,6606,6607],{},"Credentials: Include the credentials of the snapshots flows",[254,6609,6610,6611],{},"Environment Variables\n",[251,6612,6613,6616],{},[254,6614,6615],{},"Keys and Values: Include the keys and values of the environment variables",[254,6617,6618],{},"Keys Only: Include only the keys of the environment variables",[13,6620,6621,6625],{},[36,6622],{"alt":6623,"dataZoomable":39,"src":6624},"Screenshot showing snapshot download component options","\u002Fchangelog\u002F2024\u002F10\u002Fimages\u002Fsnapshot-download--with-options.png",[43,6626,6623],{},[13,6628,6629,6633],{},[36,6630],{"alt":6631,"dataZoomable":39,"src":6632},"Screenshot showing snapshot upload component options","\u002Fchangelog\u002F2024\u002F10\u002Fimages\u002Fsnapshot-upload--with-options.png",[43,6634,6631],{},[13,6636,6637],{},"This feature can help you be specific about what you want to include in a downloaded snapshot. This is especially useful when\nyou want to share a snapshot with others, but don't want to include sensitive information like credentials. Also,\nwhen you receive a snapshot that needs importing into a different FlowFuse platform or team, you can can now be selective\nabout what to keep and what to exclude.",[13,6639,6489,6640,6645],{},[26,6641,6644],{"href":6642,"rel":6643},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fsnapshots",[30],"Snapshots"," documentation for more information.",{"title":39,"searchDepth":55,"depth":55,"links":6647},[],"2024-10-14",{"tags":6650},[64],"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options",{"title":6590,"description":6541},{"loc":6651},"changelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","xWi2FR_AluXY9jv9zpF9mWSTbhY8K0cHxuyrYwy1d20",{"id":6657,"title":6658,"authors":6659,"body":6660,"date":6676,"description":6677,"extension":59,"issues":70,"meta":6678,"navigation":65,"path":6680,"seo":6681,"sitemap":6682,"stem":6683,"subtitle":70,"__hash__":6684},"changelog\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions.md","Managing Notifications",[285],{"type":10,"value":6661,"toc":6674},[6662,6665,6668],[13,6663,6664],{},"We have now added the ability to manage notifications in bulk. This allows users to select more than one notification so that they can be marked as read, or marked as unread, all in one go.",[13,6666,6667],{},"We hope this small improvement saves you bundle of clicks and streamlines your operations.",[13,6669,6670],{},[36,6671],{"alt":6672,"src":6673},"bulk-notifications.png","\u002Fchangelog\u002F2024\u002F10\u002Fimages\u002Fbulk-notifications.png",{"title":39,"searchDepth":55,"depth":55,"links":6675},[],"2024-10-04","Interact with notifications",{"tags":6679},[64],"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions",{"title":6658,"description":6677},{"loc":6680},"changelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","t1x-RU2K0Dv5bVJzAYkQQUR4YEXBClR1JS5l03eDZvc",{"id":6686,"title":6687,"authors":6688,"body":6689,"date":6708,"description":6709,"extension":59,"issues":70,"meta":6710,"navigation":65,"path":6714,"seo":6715,"sitemap":6716,"stem":6717,"subtitle":70,"__hash__":6718},"changelog\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials.md","Bill of Materials",[285],{"type":10,"value":6690,"toc":6706},[6691,6694,6700,6703],[13,6692,6693],{},"Starting with the v2.9.0 release FlowFuse a new Application Dependencies tab will be available for Enterprise self-hosted\nand Enterprise Tier FlowFuse Cloud users where a complete list of dependencies belonging to every Instance associated to the application can be found.",[13,6695,6696],{},[36,6697],{"alt":6698,"src":6699},"bom.png","\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fbom.png",[13,6701,6702],{},"The intent is to give users a birds eye view of an application's dependencies and track dependency changes.",[13,6704,6705],{},"Users can search by package name, version, instance or device name.",{"title":39,"searchDepth":55,"depth":55,"links":6707},[],"2024-09-25","Get a single view of all dependencies used by your applications",{"tags":6711},[6712,6713],"license","enterprise","\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials",{"title":6687,"description":6709},{"loc":6714},"changelog\u002F2024\u002F08\u002Fbill-of-materials","rzZkUSWRyXFQhxqWb3POTaajrgfxBB27Gpojp4fGC-4",{"id":6720,"title":6721,"authors":6722,"body":6723,"date":6756,"description":6757,"extension":59,"issues":70,"meta":6758,"navigation":65,"path":6760,"seo":6761,"sitemap":6762,"stem":6763,"subtitle":70,"__hash__":6764},"changelog\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility.md","Static File Service Navigation and Visibility",[285],{"type":10,"value":6724,"toc":6754},[6725,6733,6736,6739,6742],[13,6726,6727,6728,227],{},"Users of FlowFuse Cloud can now make use of an enhanced navigation tool and visibility selector when using the ",[26,6729,6732],{"href":6730,"rel":6731},"https:\u002F\u002Fflowfuse.com\u002Fblog\u002F2024\u002F08\u002Fflowfuse-2-8-release\u002F#static-assets-service",[30],"static file service feature",[13,6734,6735],{},"By settings the visibility of a folder to 'public', their Node-RED instance will automatically make any files in that folder publicly available - on a path of the user's choosing.",[13,6737,6738],{},"This makes it very simple to serve up additional assets such as images or libraries that can be used in your Node-RED Dashboards.",[13,6740,6741],{},"The visibility settings apply to the folder; you cannot make individual files public. Any changes to the visibility settings will require the instance to be restarted for the changes to take effect.",[13,6743,6744,6748,6751],{},[36,6745],{"alt":6746,"src":6747},"static-file-service-navigation-visibility","\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fstatic-file-service-navigation-visibility\u002F1-selector.png",[36,6749],{"alt":6746,"src":6750},"\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fstatic-file-service-navigation-visibility\u002F2-select-static-path.png",[36,6752],{"alt":6746,"src":6753},"\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fstatic-file-service-navigation-visibility\u002F3-public-visibility.png",{"title":39,"searchDepth":55,"depth":55,"links":6755},[],"2024-09-19","Navigate static files with better navigation and visibility selector",{"tags":6759},[64],"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility",{"title":6721,"description":6757},{"loc":6760},"changelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","CXZ6ORy-wKy_l2oedT5WhniwRZUmV8LnYnW0gkwav4Q",{"id":6766,"title":6767,"authors":6768,"body":6769,"date":6875,"description":6876,"extension":59,"issues":70,"meta":6877,"navigation":65,"path":6880,"seo":6881,"sitemap":6882,"stem":6883,"subtitle":70,"__hash__":6884},"changelog\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups.md","LDAP Single Sign On Updates",[210],{"type":10,"value":6770,"toc":6869},[6771,6774,6778,6785,6791,6808,6812,6818,6821,6841,6847,6854,6858,6861,6866],[13,6772,6773],{},"In the v2.8.0 release we have updated the LDAP SSO feature to allow group\nmembership to be managed by LDAP groups.",[170,6775,6777],{"id":6776},"configuring","Configuring",[13,6779,6780,6781,6784],{},"Building on the SAML based SSO configuration there is now a ",[86,6782,6783],{},"Manage roles using group assertions"," check box on the LDAP SSO configuration page. This allows a base LDAP DN for groups to be set. This will used to look up which groups a user is a member of when they login to the platform.",[13,6786,6787],{},[36,6788],{"alt":6789,"src":6790},"screen shot showing new LDAP group management settings","\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fldap-group.png",[13,6792,6793,6794,463,6797,6800,6801,463,6804,6807],{},"Groups can be ",[86,6795,6796],{},"groupOfNames",[86,6798,6799],{},"groupOfUniqueNames"," and membership will be checked against ",[86,6802,6803],{},"memberOf",[86,6805,6806],{},"uniqueMemberOf"," fields respectively.",[385,6809,6811],{"id":6810},"group-naming","Group Naming",[13,6813,6814,6815],{},"Group names must follow the this pattern ",[86,6816,6817],{},"ff-\u003Cteam slug>-role",[13,6819,6820],{},"The valid roles for a user in a team are:",[251,6822,6823,6827,6831,6836],{},[254,6824,6825],{},[86,6826,245],{},[254,6828,6829],{},[86,6830,241],{},[254,6832,6833],{},[86,6834,6835],{},"viewer",[254,6837,6838],{},[86,6839,6840],{},"dashboard",[13,6842,6843,6846],{},[43,6844,6845],{},"Note",": this uses the team slug property to identify the team. This has been chosen to simplify managing\nthe groups in the LDAP Provider - rather than using the team's id. However, a team's slug can be changed\nby a team owner. Doing so will break the link between the group and the team membership - so should only\nbe done with care.",[13,6848,6849,6850,227],{},"More details can be found in the ",[26,6851,6853],{"href":6852},"\u002Fdocs\u002Fadmin\u002Fsso\u002Fldap","SSO LDAP documentation",[170,6855,6857],{"id":6856},"managing-flowfuse-admins","Managing FlowFuse Admins",[13,6859,6860],{},"In the previous release we added support for managing FlowFuse Admin users by group membership to SAML SSO, this is now available to LDAP as well.",[13,6862,6863,6865],{},[43,6864,6845],{},": It is advised to maintain a backup admin user that does not\nauthenticate via SSO so ensure access can be maintained if the SSO\nprovider is unavailable. Also the system will not remove the admin flag\nfrom a user if that would leave the platform with no admins even if they\nremoved from the group.",[13,6867,6868],{},"This feature is only available to FlowFuse self-hosted customers.",{"title":39,"searchDepth":55,"depth":55,"links":6870},[6871,6874],{"id":6776,"depth":194,"text":6777,"children":6872},[6873],{"id":6810,"depth":598,"text":6811},{"id":6856,"depth":194,"text":6857},"2024-08-28","Team membership controlled by LDAP groups",{"tags":6878},[6879],"sso","\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups",{"title":6767,"description":6876},{"loc":6880},"changelog\u002F2024\u002F08\u002Fldap-sso-groups","JKia6MeN4iqbvFCV2dGIz4vbIB1WIPqEoPHAe_m72oU",{"id":6886,"title":6887,"authors":6888,"body":6889,"date":6915,"description":6916,"extension":59,"issues":70,"meta":6917,"navigation":65,"path":6919,"seo":6920,"sitemap":6921,"stem":6922,"subtitle":70,"__hash__":6923},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update.md","Notifications Inbox",[284],{"type":10,"value":6890,"toc":6913},[6891,6894,6897,6905],[13,6892,6893],{},"To keep you focused, we have added a \"Hide Read\" checkbox that is checked by default so that you only see active notifications.",[13,6895,6896],{},"Not only that, we've added some new notifications so that members and owners get fast feedback for important events in your system.",[13,6898,6899,6903],{},[36,6900],{"alt":6901,"dataZoomable":39,"src":6902},"Screenshot showing unread Notifications Inbox in FlowFuse","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fnotifications-inbox-unread.png",[43,6904,6901],{},[13,6906,6907,6911],{},[36,6908],{"alt":6909,"dataZoomable":39,"src":6910},"Screenshot showing read Notifications Inbox in FlowFuse","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fnotifications-inbox-read.png",[43,6912,6909],{},{"title":39,"searchDepth":55,"depth":55,"links":6914},[],"2024-08-27","More notifications and alerts in FlowFuse",{"tags":6918},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"title":6887,"description":6916},{"loc":6919},"changelog\u002F2024\u002F07\u002Fnotifications-update","HqnjODHjQ0fgBongaqkTqazdEtXznx4ynX3E9p4_hZM",{"id":6925,"title":6926,"authors":6927,"body":6928,"date":6961,"description":6962,"extension":59,"issues":70,"meta":6963,"navigation":65,"path":6965,"seo":6966,"sitemap":6967,"stem":6968,"subtitle":70,"__hash__":6969},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move.md","Managing devices",[284],{"type":10,"value":6929,"toc":6959},[6930,6933,6936,6939,6945,6951],[13,6931,6932],{},"Having recently added the ability to delete multiple devices at once, we have now added the ability to move multiple devices at once.",[13,6934,6935],{},"To use this feature, navigate to the devices page, application devices or instance devices and place a check in the box next to the devices you wish to move.\nOnce you have selected the devices you wish to move, click the new menu button above the table & select the new location for the devices.",[13,6937,6938],{},"We are are sure this will make managing your devices a good deal easier.",[13,6940,6941],{},[36,6942],{"alt":6943,"src":6944},"New menu for managing multiple devices","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fbulk-menu.png",[13,6946,6947],{},[36,6948],{"alt":6949,"src":6950},"Moving multiple devices","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fbulk-move.png",[13,6952,6953,6954,227],{},"You can read up on the new feature in our ",[26,6955,6958],{"href":6956,"rel":6957},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Fregister\u002F#assign-the-device",[30],"documentation",{"title":39,"searchDepth":55,"depth":55,"links":6960},[],"2024-08-12","Making device management that little bit easier.",{"tags":6964},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"title":6926,"description":6962},{"loc":6965},"changelog\u002F2024\u002F07\u002Fdevice-management-bulk-move","GQT0319GZyTL8_KIPL35TIICoNiQdbgYbW2Z-qiGgQE",{"id":6971,"title":6972,"authors":6973,"body":6974,"date":6992,"description":6993,"extension":59,"issues":70,"meta":6994,"navigation":65,"path":6996,"seo":6997,"sitemap":6998,"stem":6999,"subtitle":70,"__hash__":7000},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots.md","Edit Snapshots",[284],{"type":10,"value":6975,"toc":6990},[6976,6979,6987],[13,6977,6978],{},"Snapshots can now be renamed and their descriptions updated, even after they're created.",[13,6980,6981,6985],{},[36,6982],{"alt":6983,"dataZoomable":39,"src":6984},"Screenshot showing the new Edit Snapshots feature in FlowFuse","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fedit-snapshots.png",[43,6986,6983],{},[13,6988,6989],{},"This is particularly useful for the snapshots that are automatically generated each time your deploy your flows, making it easier to track back your changes and revert to a previous state if needed.",{"title":39,"searchDepth":55,"depth":55,"links":6991},[],"2024-08-01","We've now enabled the ability to edit the names and descriptions of Snapshots after they've been created.",{"tags":6995},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots",{"title":6972,"description":6993},{"loc":6996},"changelog\u002F2024\u002F07\u002Fedit-snapshots","-QhYT16ukeR5zOctVx20c8iX94XZQe4kKgZ_l_Zj2nE",{"id":7002,"title":7003,"authors":7004,"body":7005,"date":7022,"description":7023,"extension":59,"issues":70,"meta":7024,"navigation":65,"path":7026,"seo":7027,"sitemap":7028,"stem":7029,"subtitle":70,"__hash__":7030},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot.md","Device Groups Snapshots",[284],{"type":10,"value":7006,"toc":7020},[7007,7010,7013],[13,7008,7009],{},"An update to let you know you can now clear the target snapshot of a device group. This is small but useful feature that can help you manage your device groups more effectively.",[13,7011,7012],{},"For those unfamiliar with FlowFuse device groups, essentially, they permit you to deploy a snapshot to one or many devices via a pipeline in a single action. This is great for managing changes across a fleet of devices.",[13,7014,6489,7015,7019],{},[26,7016,7018],{"href":6573,"rel":7017},[30],"device groups documentation"," for more information on how to make use of device groups.",{"title":39,"searchDepth":55,"depth":55,"links":7021},[],"2024-07-30","It is now possible clear a the target snapshot of a device group.",{"tags":7025},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot",{"title":7003,"description":7023},{"loc":7026},"changelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","D_lbwZI4yN6gcsRAiypoDm9JuJJi1D5JUifBGW3iGfI",{"id":7032,"title":7033,"authors":7034,"body":7035,"date":7067,"description":7068,"extension":59,"issues":70,"meta":7069,"navigation":65,"path":7071,"seo":7072,"sitemap":7073,"stem":7074,"subtitle":70,"__hash__":7075},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fsso.md","Single Sign On Updates",[210],{"type":10,"value":7036,"toc":7063},[7037,7040,7044,7047,7050,7054,7057,7060],[13,7038,7039],{},"In the v2.7.0 release we have included some new SSO features",[170,7041,7043],{"id":7042},"user-creation-on-first-log-in","User creation on first log in",[13,7045,7046],{},"Before v2.7.0 users needed to be created before they could use SSO to\nlog in to FlowFuse. Now if enabled in the SSO configuration users will\nbe created when they first sign in. If team membership is controlled by\nSSO Groups (SAML only) then they will be added to the relevant teams, otherwise if the system is configured to create a Team for a new user it will do so.",[13,7048,7049],{},"FlowFuse Cloud customers should contact support to discuss enabling this\nfeature for their teams.",[170,7051,7053],{"id":7052},"managing-flowfuse-admins-with-sso-groups","Managing FlowFuse Admins with SSO Groups",[13,7055,7056],{},"It is now possible to configure a group to manage which users are granted\nadministration privileges. The name of the group can be added to the SSO\nconfiguration (SAML only).",[13,7058,7059],{},"NOTE: It is advised to maintain a backup admin user that does not\nauthenticate via SSO so ensure access can be maintained if the SSO\nprovider is unavailable. Also the system will not remove the admin flag\nfrom a user if that would leave the platform with no admins even if they\nremoved from the group.",[13,7061,7062],{},"This feature is not available to FlowFuse Cloud customers.",{"title":39,"searchDepth":55,"depth":55,"links":7064},[7065,7066],{"id":7042,"depth":194,"text":7043},{"id":7052,"depth":194,"text":7053},"2024-07-24","Direct User Provisioning and Admin Group management",{"tags":7070},[6879],"\u002Fchangelog\u002F2024\u002F07\u002Fsso",{"title":7033,"description":7068},{"loc":7071},"changelog\u002F2024\u002F07\u002Fsso","cEHHD0ZOImRSDW3Dz5_2T7ZEmbkk8dWEBPfFqQZR9NM",{"id":7077,"title":7078,"authors":7079,"body":7080,"date":7067,"description":7162,"extension":59,"issues":70,"meta":7163,"navigation":65,"path":7165,"seo":7166,"sitemap":7167,"stem":7168,"subtitle":70,"__hash__":7169},"changelog\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update.md","Enforcing Enterprise Restrictions",[210],{"type":10,"value":7081,"toc":7157},[7082,7085,7093,7097,7100,7114,7117,7121,7147,7151,7154],[13,7083,7084],{},"Starting with the v2.8.0 release FlowFuse will be taking a slightly stricter\napproach to License enforcement outside of FlowFuse Cloud. Previously\nwhen a license expired the platform would continue to run with the same\ncapabilities as when the license was valid.",[13,7086,7087,7088,7092],{},"If you are currently running with older version with an expired license\nplease ",[26,7089,7091],{"href":7090},"\u002Fcontact-us\u002F","contact the Sales team"," to discuss renewing your\nlicense before upgrading. You can check your current license on the\nAdmin Settings -> Overview page.",[170,7094,7096],{"id":7095},"notifications","Notifications",[13,7098,7099],{},"Starting 30 days before the license expires:",[251,7101,7102,7111],{},[254,7103,7104,7105,7107],{},"Admin users will see a banner showing the number of days left.",[1107,7106],{},[36,7108],{"alt":7109,"src":7110},"expiring banner","\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fexpiring-banner.png",[254,7112,7113],{},"A email will be sent to all Admin users.",[13,7115,7116],{},"The email will be sent again every Sunday evening in the 30 days.",[170,7118,7120],{"id":7119},"after-expiry","After Expiry",[251,7122,7123,7126,7129,7132,7135,7144],{},[254,7124,7125],{},"All running instances will be suspended.",[254,7127,7128],{},"Instances will not be started.",[254,7130,7131],{},"No new Instances or Devices can be created.",[254,7133,7134],{},"A email will be sent to all Admin users saying the license has expired.",[254,7136,7137,7138,7140],{},"A banner showing the license as expired will be shown to all users.",[1107,7139],{},[36,7141],{"alt":7142,"src":7143},"expired banner","\u002Fchangelog\u002F2024\u002F08\u002Fimages\u002Fexpired-banner.png",[254,7145,7146],{},"All connections to the MQTT broker will be refused (This will impact\nProject Nodes and Device control).",[170,7148,7150],{"id":7149},"applying-a-new-license","Applying a New License",[13,7152,7153],{},"A new license can be applied in the Admin Settings -> Settings section.",[13,7155,7156],{},"Once applied you will be able to restart all existing Instances and\ncreate new Instances and Devices. The MQTT will accept new connections.",{"title":39,"searchDepth":55,"depth":55,"links":7158},[7159,7160,7161],{"id":7095,"depth":194,"text":7096},{"id":7119,"depth":194,"text":7120},{"id":7149,"depth":194,"text":7150},"A stricter approach to expired licenses",{"tags":7164},[6712,6713],"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update",{"title":7078,"description":7162},{"loc":7165},"changelog\u002F2024\u002F08\u002Fenterprise-license-update","RwGH1Jh27Ho8kS87hWf6heRSiw0g-mXZaSyGDcgi7Rs",{"id":7171,"title":6887,"authors":7172,"body":7174,"date":7192,"description":7193,"extension":59,"issues":70,"meta":7194,"navigation":65,"path":7196,"seo":7197,"sitemap":7198,"stem":7199,"subtitle":70,"__hash__":7200},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox.md",[7173],"serban-costan",{"type":10,"value":7175,"toc":7190},[7176,7179,7187],[13,7177,7178],{},"We've made some changes to the way notifications are displayed and handled in FlowFuse to make it easier to see what's going on in your system, with a new, dedicated, \"Notifications Inbox\".",[13,7180,7181,7185],{},[36,7182],{"alt":7183,"dataZoomable":39,"src":7184},"Screenshot showing the new Notifications Inbox in FlowFuse","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fnotifications-inbox.png",[43,7186,7183],{},[13,7188,7189],{},"Whilst the only notifications we're supporting right now are team invites, this groundwork will allow us to expand the types of notifications we can send in the future to give better visibility of what's happening in your FlowFuse environment.",{"title":39,"searchDepth":55,"depth":55,"links":7191},[],"2024-07-21","Clearer notifications and alerts in FlowFuse",{"tags":7195},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox",{"title":6887,"description":7193},{"loc":7196},"changelog\u002F2024\u002F07\u002Fnotifications-inbox","bQjCb0UVtuOfdh0piBKekQxHjH1BnKLeoMuYJ6ZyQek",{"id":7202,"title":6926,"authors":7203,"body":7204,"date":7226,"description":6962,"extension":59,"issues":70,"meta":7227,"navigation":65,"path":7229,"seo":7230,"sitemap":7231,"stem":7232,"subtitle":70,"__hash__":7233},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete.md",[284],{"type":10,"value":7205,"toc":7224},[7206,7209,7212,7215,7218],[13,7207,7208],{},"We have added bulk operations for managing devices.",[13,7210,7211],{},"In this first iteration we have added the ability to delete multiple devices at once.",[13,7213,7214],{},"To use this feature, navigate to the devices page, application devices or instance devices and place a check in the box next to the devices you wish to delete.\nOnce you have selected the devices you wish to delete, click the trash can button above the table & confirm the deletion.",[13,7216,7217],{},"We will be adding more bulk operations in the future, so keep an eye out for more updates.",[13,7219,7220],{},[36,7221],{"alt":7222,"src":7223},"Deleting multiple devices","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fbulk-delete-1.png",{"title":39,"searchDepth":55,"depth":55,"links":7225},[],"2024-07-19",{"tags":7228},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete",{"title":6926,"description":6962},{"loc":7229},"changelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","KfZWcxUgBSt5tTAKYoj9O2Bci2cDS5OoJHmqiZP5gT0",{"id":7235,"title":7236,"authors":7237,"body":7238,"date":7255,"description":7256,"extension":59,"issues":70,"meta":7257,"navigation":65,"path":7259,"seo":7260,"sitemap":7261,"stem":7262,"subtitle":70,"__hash__":7263},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search.md","Applications Search",[7173],{"type":10,"value":7239,"toc":7253},[7240,7243,7250],[13,7241,7242],{},"With hundreds of devices and instances running in FlowFuse, it can be very difficult to find the resource you're looking for. That's why we've introduced a new search feature that allows you to search across all of your FlowFuse instances, devices and applications from a single place.",[13,7244,7245,7248],{},[36,7246],{"alt":7183,"dataZoomable":39,"src":7247},"\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fapplications-search.png",[43,7249,7183],{},[13,7251,7252],{},"The view will automatically filter as you type making it easy to find the resource you're looking for, it will keep reference to any applications and or child instances\u002Fdevices where appropriate.",{"title":39,"searchDepth":55,"depth":55,"links":7254},[],"2024-07-16","Centralized search across all of your FlowFuse instances, devices and applications.",{"tags":7258},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search",{"title":7236,"description":7256},{"loc":7259},"changelog\u002F2024\u002F07\u002Fapplications-search","J5bu-UNvmRfxime4hAMgwyi2k-cf2Ue1Q-tlMbzKBbM",{"id":7265,"title":7266,"authors":7267,"body":7268,"date":7255,"description":7355,"extension":59,"issues":70,"meta":7356,"navigation":65,"path":7358,"seo":7359,"sitemap":7360,"stem":7361,"subtitle":70,"__hash__":7362},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json.md","FlowFuse Expert Writes JSON",[284],{"type":10,"value":7269,"toc":7347},[7270,7273,7276,7279,7282,7285,7293,7303,7314,7323,7326,7330,7332,7337,7342],[13,7271,7272],{},"The FlowFuse Expert can now assist you by generating JSON.",[13,7274,7275],{},"Wherever you edit JSON in the Rich Monaco Editor you will see the \"Ask the FlowFuse Expert 🪄\" code lens.\nThat includes the Inject Node, the Template Node and any contrib node that uses the built-in editor for writing JSON.",[13,7277,7278],{},"We think you will find this to be a great time saver and a good helper when you are unsure of the syntax.",[13,7280,7281],{},"Just ask for what you want and it does a decent job of figuring it out.",[13,7283,7284],{},"Here are some examples:",[385,7286,7288,7289,7292],{"id":7287},"asking-the-assistant-to-generate-json-from-within-the-template-node","Asking the Assistant to generate JSON from within the ",[86,7290,7291],{},"template"," node",[13,7294,7295,7299],{},[36,7296],{"alt":7297,"src":7298},"Prompting from within the Template Node","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fask-assistant-json-1a.png",[36,7300],{"alt":7301,"src":7302},"Resulting JSON","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fask-assistant-json-1b.png",[385,7304,7288,7306,7309,7310,7313],{"id":7305},"asking-the-assistant-to-generate-json-from-within-the-inject-node-for-the-payload-value",[86,7307,7308],{},"inject"," node for the ",[86,7311,7312],{},"payload"," value",[13,7315,7316,7320],{},[36,7317],{"alt":7318,"src":7319},"Prompting from within the Inject Nodes Typed Input","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fask-assistant-json-2a.png",[36,7321],{"alt":7301,"src":7322},"\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fask-assistant-json-2b.png",[13,7324,7325],{},"This is just the beginning of the FlowFuse Expert's capabilities. Stay tuned!",[4652,7327,7329],{"id":7328},"updating-the-assistant-to-get-these-new-features","Updating the Assistant to get these new features",[13,7331,4702],{},[13,7333,7334],{},[36,7335],{"alt":4707,"src":7336},"\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fassistant-update-nr4.png",[13,7338,7339,7340,4718],{},"If you are still running Node-RED v3.x, you can update the plugin by adding ",[86,7341,4717],{},[13,7343,7344],{},[36,7345],{"alt":4723,"src":7346},"\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fassistant-update-nr3.png",{"title":39,"searchDepth":55,"depth":55,"links":7348},[7349,7351],{"id":7287,"depth":598,"text":7350},"Asking the Assistant to generate JSON from within the template node",{"id":7305,"depth":598,"text":7352,"children":7353},"Asking the Assistant to generate JSON from within the inject node for the payload value",[7354],{"id":7328,"depth":55,"text":7329},"The FlowFuse Expert gets more helpful.",{"tags":7357},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json",{"title":7266,"description":7355},{"loc":7358},"changelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","H65nEUOIAmx7QPKUobeS4egiSoCSZDMP_fAF7orWBzw",{"id":7364,"title":7365,"authors":7366,"body":7367,"date":7401,"description":7402,"extension":59,"issues":70,"meta":7403,"navigation":65,"path":7405,"seo":7406,"sitemap":7407,"stem":7408,"subtitle":70,"__hash__":7409},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant.md","The FlowFuse Expert",[284],{"type":10,"value":7368,"toc":7399},[7369,7372,7375,7378,7381,7387,7393],[13,7370,7371],{},"We are excited to announce the first release of The FlowFuse Expert, a new plugin for your Node-RED instances designed to enhance your development experience.",[13,7373,7374],{},"In this initial release, The FlowFuse Expert can help you create function nodes for those times when a no-code solution is either not feasible or not possible.\nAdditionally, it works directly inside the Function Node editor right where you need it.",[13,7376,7377],{},"This is just the beginning. The FlowFuse Expert will continue to evolve, with future updates bringing even more powerful features and enhancements.",[13,7379,7380],{},"Starting from today, FlowFuse Expert is available on FlowFuse Cloud. Users will need to update their instances to the latest stack to enable it.",[13,7382,7383],{},[36,7384],{"alt":7385,"src":7386},"Node-RED Editor toolbar button for the assistant","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fassistant-toolbar.png",[13,7388,7389],{},[36,7390],{"alt":7391,"src":7392},"FlowFuse Expert Input Dialog","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fassistant-dialog-function-node-builder.png",[13,7394,7395],{},[36,7396],{"alt":7397,"src":7398},"FlowFuse Expert Code Lens","\u002Fchangelog\u002F2024\u002F07\u002Fimages\u002Fassistant-function-node-inline-code-lens.png",{"title":39,"searchDepth":55,"depth":55,"links":7400},[],"2024-07-04","Introducing the FlowFuse Expert: making low-code even more accessible.",{"tags":7404},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant",{"title":7365,"description":7402},{"loc":7405},"changelog\u002F2024\u002F07\u002Fflowfuse-assistant","QRlgSdirZV6D0U1_CIAAbUNUqB5e0v4B7of84kLxz7o",{"id":7411,"title":7412,"authors":7413,"body":7414,"date":7401,"description":7452,"extension":59,"issues":70,"meta":7453,"navigation":65,"path":7455,"seo":7456,"sitemap":7457,"stem":7458,"subtitle":70,"__hash__":7459},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage.md","Persistent Storage on FlowFuse Cloud",[210],{"type":10,"value":7415,"toc":7450},[7416,7419,7426,7435,7438,7447],[13,7417,7418],{},"Users of FlowFuse Cloud and self-hosted users on Kubernetes can now make use of a\nnew persistent storage solution.",[13,7420,7421,7422,7425],{},"Starting with the v2.6.0 release the Pods running the Node-RED Instances will have\na Persistent Volume mounted on ",[86,7423,7424],{},"\u002Fdata\u002Fstorage"," in which files can be written. These\nfiles will persist for the lifetime of the Instance including across Susspend\u002FResume\nand Stack upgrades.",[13,7427,7428,7429,7434],{},"This update means nodes like ",[26,7430,7433],{"href":7431,"rel":7432},"https:\u002F\u002Fflows.nodered.org\u002Fnode\u002Fnode-red-node-sqlite",[30],"node-red-node-sqlite"," can be used to store data safely.",[13,7436,7437],{},"This capability replaces the current FlowFuse FileServer which made use of custom\nversions of the Node-RED code File nodes to store and read files from a remote network\nstore. However this didn't allow 3rd party nodes to also benefit from the storage provided.",[13,7439,7440,7441,7446],{},"New instances created will default to use the new Persistent Storage volumes. If you want to upgrade an existing instance that uses the FileServer storage, get in touch with ",[26,7442,7445],{"href":7443,"rel":7444},"https:\u002F\u002Fflowfuse.com\u002Fcontact-us\u002F",[30],"Support"," and we can help migrate your data over.",[13,7448,7449],{},"Similar support for Docker will be available in later releases.",{"title":39,"searchDepth":55,"depth":55,"links":7451},[],"Bring persistent storage to FlowFuse Cloud and self-hosted Kubernetes platforms",{"tags":7454},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage",{"title":7412,"description":7452},{"loc":7455},"changelog\u002F2024\u002F07\u002Fpersistent-storage","6Zld8ZyadxOrc21h1XDx81YMJSqCE2xGIqqJFO3hAmA",{"id":7461,"title":7462,"authors":7463,"body":7464,"date":7485,"description":7486,"extension":59,"issues":70,"meta":7487,"navigation":65,"path":7489,"seo":7490,"sitemap":7491,"stem":7492,"subtitle":70,"__hash__":7493},"changelog\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor.md","Immersive Editor Experience",[5073],{"type":10,"value":7465,"toc":7483},[7466,7469,7472,7477,7480],[13,7467,7468],{},"We found out that many users have to frequently switch between the Node-RED Editor and FlowFuse UI. This back-and-forth movement was often necessary to view logs, save snapshots, restart the Editor after updates, and perform other tasks.",[13,7470,7471],{},"We're always seeking to reduce friction in the FlowFuse user experience, and as such, we've introduced a large overhaul of the developer experience for Node-RED when running in FlowFuse, in what we're calling the \"Immersive Editor\".",[13,7473,7474],{},[36,7475],{"alt":7385,"dataZoomable":39,"src":7476},"\u002Fblog\u002F2024\u002F07\u002Fimages\u002Fimmersive-editor.png",[13,7478,7479],{},"Now, the instances tabs are all available in the same view as the Editor, and you can manage your instance, watch logs, capture snapshots and event restart it, all without leaving the Node-RED Editor.",[13,7481,7482],{},"The new Immersive Editor is available for instances running Node-RED 4.0.2 or later - older versions of Node-RED will still use the separate views.",{"title":39,"searchDepth":55,"depth":55,"links":7484},[],"2024-07-02","Closer integration between the FlowFuse and Node-RED experiences",{"tags":7488},[64],"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor",{"title":7462,"description":7486},{"loc":7489},"changelog\u002F2024\u002F07\u002Fimmersive-editor","jhBbiqiuyVSo55GXZsr_OY4j4eMDNMpeAgykvciaQ3E",{"id":7495,"title":7496,"authors":7497,"body":7498,"date":7521,"description":7522,"extension":59,"issues":70,"meta":7523,"navigation":65,"path":7525,"seo":7526,"sitemap":7527,"stem":7528,"subtitle":70,"__hash__":7529},"changelog\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars.md","Multi-line Environment Variables",[284],{"type":10,"value":7499,"toc":7519},[7500,7503,7506,7513],[13,7501,7502],{},"FlowFuse now supports the input of multi-line environment variables for your Node-RED instances running on FlowFuse.",[13,7504,7505],{},"This unlocks the ability to store certs or multi-line values like JSON as environment variables.",[13,7507,7508,7509,7512],{},"We've also improved the ",[86,7510,7511],{},".env"," file import to support the use of multi-line values too.",[13,7514,7515],{},[36,7516],{"alt":7517,"src":7518},"multiline environment variables","\u002Fchangelog\u002F2024\u002F06\u002Fimages\u002Fsnapshot-compare-flows.png",{"title":39,"searchDepth":55,"depth":55,"links":7520},[],"2024-06-26","FlowFuse now supports multi-line Environment Variables.",{"tags":7524},[64],"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars",{"title":7496,"description":7522},{"loc":7525},"changelog\u002F2024\u002F06\u002Fmultiline-env-vars","Efmm52bWdaXpJ1SWWX7EB-hWbyGuZydc1dKdLXbfX-w",{"id":7531,"title":7532,"authors":7533,"body":7534,"date":7566,"description":7532,"extension":59,"issues":70,"meta":7567,"navigation":65,"path":7569,"seo":7570,"sitemap":7571,"stem":7572,"subtitle":70,"__hash__":7573},"changelog\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support.md","Running the Device Agent behind an HTTP proxy",[8],{"type":10,"value":7535,"toc":7564},[7536,7539,7542,7549,7556],[13,7537,7538],{},"The FlowFuse Device Agent allows you to manage your Node-RED instances wherever you want them to run.\nIt connects back to the platform over a secure https connection.",[13,7540,7541],{},"For some enterprise customers, that has posed a challenge as they protect their network with an HTTP proxy that all traffic\nhas to be directed to.",[13,7543,7544,7545,7548],{},"With the ",[86,7546,7547],{},"2.5.0"," release of the Device Agent, we now support running the Device Agent behind a proxy - letting it run in even more locations.",[13,7550,7551,7552,7555],{},"Support comes using the industry standard set of ",[86,7553,7554],{},"http_proxy"," environment variables - familiar to anyone running services behind a proxy.",[13,7557,7558,7559,227],{},"Full details are available in our ",[26,7560,7563],{"href":7561,"rel":7562},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002Frunning\u002F#running-behind-a-http-proxy",[30],"http proxy documentation",{"title":39,"searchDepth":55,"depth":55,"links":7565},[],"2024-06-18",{"tags":7568},[64],"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support",{"title":7532,"description":7532},{"loc":7569},"changelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","fBP6-s-PgdICHiVtSMQ_85NZ2y1OgQIOqB83vCUg8_M",{"id":7575,"title":7576,"authors":7577,"body":7578,"date":7622,"description":7623,"extension":59,"issues":70,"meta":7624,"navigation":65,"path":7626,"seo":7627,"sitemap":7628,"stem":7629,"subtitle":70,"__hash__":7630},"changelog\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints.md","Custom hostnames for your instances",[8],{"type":10,"value":7579,"toc":7620},[7580,7583,7589,7592,7604,7612],[13,7581,7582],{},"Enterprise teams on FlowFuse Cloud can now configure their own subdomain to point\nat their Node-RED application.",[13,7584,7585,7586,227],{},"Within FlowFuse Cloud, Node-RED instances are reached by their provided url: ",[86,7587,7588],{},"\u003Cname>.flowfuse.cloud",[13,7590,7591],{},"With this new option, it is possible to add a custom hostname for the instance that works alongside\nthe provided url.",[13,7593,7594,7595,7599,7600,7603],{},"For example, if you have built a ",[26,7596,6840],{"href":7597,"rel":7598},"https:\u002F\u002Fdashboard.flowfuse.com",[30]," you can now configure your instance to make that available via ",[86,7601,7602],{},"dashboard.example.com"," or any other subdomain you own.",[13,7605,7606,7607,227],{},"We only support subdomains at this time, but adding support for top-level domains is ",[26,7608,7611],{"href":7609,"rel":7610},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Fissues\u002F3982",[30],"on the roadmap",[13,7613,7614,7615,227],{},"Read more on ",[26,7616,7619],{"href":7617,"rel":7618},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fcustom-hostnames",[30],"how to setup custom hostnames",{"title":39,"searchDepth":55,"depth":55,"links":7621},[],"2024-06-05","Enterprise teams on FlowFuse Cloud can now configure custom subdomains to point to their Node-RED applications, enhancing accessibility and branding.",{"tags":7625},[64],"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints",{"title":7576,"description":7623},{"loc":7626},"changelog\u002F2024\u002F06\u002Flibrary-blueprints","c_FsZA2t8wbnBGlupvBKueZlNI15nYOT0S9af0oQUtA",{"id":7632,"title":7633,"authors":7634,"body":7635,"date":7622,"description":7656,"extension":59,"issues":70,"meta":7657,"navigation":65,"path":7659,"seo":7660,"sitemap":7661,"stem":7662,"subtitle":70,"__hash__":7663},"changelog\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare.md","Compare Snapshots flows",[284],{"type":10,"value":7636,"toc":7654},[7637,7640,7643,7649],[13,7638,7639],{},"We have now added the ability to select a snapshot and compare it to other snapshots making it easier to understand what is in the current snapshot and what has changed in relation to the 2nd snapshot.",[13,7641,7642],{},"Both snapshots are overlayed and you can step through the differences or use the new slider to visualise the differences.",[13,7644,7645],{},[36,7646],{"alt":7647,"src":7648},"Selecting a snapshot for comparison","\u002Fchangelog\u002F2024\u002F06\u002Fimages\u002Fsnapshot-compare-kebab-menu.png",[13,7650,7651],{},[36,7652],{"alt":7653,"src":7518},"Comparing selected snapshot with another",{"title":39,"searchDepth":55,"depth":55,"links":7655},[],"FlowFuse now allows selecting and comparing snapshots to visualize differences, facilitating easier understanding of changes between snapshots.",{"tags":7658},[64],"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare",{"title":7633,"description":7656},{"loc":7659},"changelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","20kKblOxeOP_8O1T--_pO0a4-trG5hNkd0CECDaJvac",{"id":7665,"title":7666,"authors":7667,"body":7668,"date":7729,"description":7730,"extension":59,"issues":70,"meta":7731,"navigation":65,"path":7733,"seo":7734,"sitemap":7735,"stem":7736,"subtitle":70,"__hash__":7737},"changelog\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3.md","Snapshot Upload",[284],{"type":10,"value":7669,"toc":7724},[7670,7676,7688,7691,7694,7698,7704,7708,7714,7718],[13,7671,7672,7675],{},[26,7673,6644],{"href":7674},"\u002Fdocs\u002Fuser\u002Fsnapshots\u002F#snapshots"," are a point-in-time backup of Node-RED\nthat can be used to easily revert back to previous version, or to push out to other\ninstances and devices as part of our Pipelines feature.",[13,7677,7678,7679,4354,7683,7687],{},"Following on from the recent work around snapshots to permit ",[26,7680,7682],{"href":7681},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Instance Snapshot Downloads",[26,7684,7686],{"href":7685},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload","Snapshot Uploads",",\nwe have now added the ability to download application device snapshots.",[13,7689,7690],{},"This means you can download a snapshot from any device or instance and upload it to any\ndevice or instance on any FlowFuse instance.",[13,7692,7693],{},"Also, to improve access to these actions, we have also updated the application\nand device snapshot table items menu to present all relevant snapshot actions.",[4652,7695,7697],{"id":7696},"application-snapshots","Application Snapshots",[13,7699,7700],{},[36,7701],{"alt":7702,"src":7703},"Application Snapshots Table Menu","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Fapplication-snapshots-menu.png",[4652,7705,7707],{"id":7706},"instance-snapshots","Instance Snapshots",[13,7709,7710],{},[36,7711],{"alt":7712,"src":7713},"Instance Snapshots Table Menu","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Finstance-snapshots-menu.png",[4652,7715,7717],{"id":7716},"device-snapshots","Device Snapshots",[13,7719,7720],{},[36,7721],{"alt":7722,"src":7723},"Device Snapshots Table Menu","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Fdevice-snapshots-menu.png",{"title":39,"searchDepth":55,"depth":55,"links":7725},[7726,7727,7728],{"id":7696,"depth":55,"text":7697},{"id":7706,"depth":55,"text":7707},{"id":7716,"depth":55,"text":7717},"2024-05-21","FlowFuse now supports uploading application and device snapshots across instances, enhancing flexibility in managing Node-RED versions and configurations.",{"tags":7732},[64],"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3",{"title":7666,"description":7730},{"loc":7733},"changelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","jR2axWxH8GlwnY7nXpBlPFL1jCFDdp7PUZp55Cc748M",{"id":7739,"title":7666,"authors":7740,"body":7741,"date":7771,"description":7772,"extension":59,"issues":70,"meta":7773,"navigation":65,"path":7685,"seo":7775,"sitemap":7776,"stem":7777,"subtitle":70,"__hash__":7778},"changelog\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload.md",[284],{"type":10,"value":7742,"toc":7769},[7743,7747,7750,7756,7759,7762],[13,7744,7745,7675],{},[26,7746,6644],{"href":7674},[13,7748,7749],{},"As promised we have now provided a way for you to upload your locally downloaded snapshots.",[13,7751,7752],{},[36,7753],{"alt":7754,"src":7755},"Upload snapshot","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Fsnapshot-upload.png",[13,7757,7758],{},"This means you can now easily take a snapshot and move it between FlowFuse platforms or,\nif you prefer, automate it via the APIs it is built on.",[13,7760,7761],{},"We hope you like this nifty little feature.",[13,7763,7764,7765,7768],{},"Stay tuned as we expect the final peices in the overall ",[26,7766,7767],{"href":7681},"Snapshot Improvements","\nto be delivered in the coming days.",{"title":39,"searchDepth":55,"depth":55,"links":7770},[],"2024-05-16","FlowFuse now supports uploading locally downloaded snapshots, facilitating easy migration between FlowFuse platforms or automation via APIs.",{"tags":7774},[64],{"title":7666,"description":7772},{"loc":7685},"changelog\u002F2024\u002F05\u002Fsnapshot-upload","YzQmQ0ie3pjPtBnAMwpRxhGxNkRBovAe9a8yhbhOMo0",{"id":7780,"title":7781,"authors":7782,"body":7783,"date":7815,"description":7816,"extension":59,"issues":70,"meta":7817,"navigation":65,"path":7819,"seo":7820,"sitemap":7821,"stem":7822,"subtitle":70,"__hash__":7823},"changelog\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck.md","Customizing instance health-check settings",[8],{"type":10,"value":7784,"toc":7813},[7785,7788,7791,7794,7801,7804,7807],[13,7786,7787],{},"When running Node-RED within FlowFuse, the platform actively monitors the instances\nto make sure they are running smoothly and automatically restarts them if it detects\na problem. It does this by regularly polling Node-RED to make sure it is still responsive.",[13,7789,7790],{},"This provides protection for the case where a user's flows accidentally creates a tight\nloop in its code and locks up the runtime.",[13,7792,7793],{},"We have to do this with care; it is entirely possible that a user's flows are intentionally\ndoing some hard work that causes our health check to temporarily fail. For that reason,\nwe only restart Node-RED if it fails a number of health-check polls in a row.",[13,7795,7796,7797,7800],{},"But even with that in place, there are still edge cases where a user's flows need to\ndo some ",[43,7798,7799],{},"really"," hard work that can exceed what the default health-check polling is\nconfigured to handle.",[13,7802,7803],{},"We have now added the ability to customize how often we check the instance health. By default\nthis is done every 7.5 seconds, but can now be extended via the instance settings.",[13,7805,7806],{},"This will require the instance to be updated to the latest stack to enable the option.",[13,7808,7809],{},[36,7810],{"alt":7811,"src":7812},"Health check interval in Instance settings","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Fhealthcheck.png",{"title":39,"searchDepth":55,"depth":55,"links":7814},[],"2024-05-09","FlowFuse now allows customization of instance health-check intervals to optimize performance for intensive workflows.",{"tags":7818},[64],"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck",{"title":7781,"description":7816},{"loc":7819},"changelog\u002F2024\u002F05\u002Finstance-healthcheck","dwg626Iz3B4RJkYmbHLdFXTlSIifNxM6HtEj4ZQm_rI",{"id":7825,"title":7826,"authors":7827,"body":7828,"date":7815,"description":7844,"extension":59,"issues":70,"meta":7845,"navigation":65,"path":7847,"seo":7848,"sitemap":7849,"stem":7850,"subtitle":70,"__hash__":7851},"changelog\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices.md","Managing Node-RED versions on Devices",[8],{"type":10,"value":7829,"toc":7842},[7830,7833,7836,7839],[13,7831,7832],{},"We have added the ability to manage the Node-RED version running on application-assigned\nDevices within FlowFuse.",[13,7834,7835],{},"Ordinarily, a device will get its Node-RED version from the snapshot deployed to it. However,\nfor an Application-assigned device, you may not yet have a snapshot to deploy.",[13,7837,7838],{},"The new option, available under Device\u002FSettings\u002FEditor lets you pick what version\nof Node-RED the device should use - overriding what is in the active snapshot.",[13,7840,7841],{},"For devices running v2.4.1 or later of the Device Agent, Node-RED will get updated\nwhen the setting is saved. For older versions of the Device Agent, it will require\na new snapshot to be deployed to trigger the update.",{"title":39,"searchDepth":55,"depth":55,"links":7843},[],"FlowFuse now allows specifying Node-RED versions for application-assigned devices, overriding active snapshots for greater flexibility.",{"tags":7846},[64],"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices",{"title":7826,"description":7844},{"loc":7847},"changelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","gzBfnvme13GzUr2nAIq7KunoWW37R80CabDZzTXqSS8",{"id":7853,"title":7767,"authors":7854,"body":7855,"date":7815,"description":7899,"extension":59,"issues":70,"meta":7900,"navigation":65,"path":7681,"seo":7902,"sitemap":7903,"stem":7904,"subtitle":70,"__hash__":7905},"changelog\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements.md",[8],{"type":10,"value":7856,"toc":7895},[7857,7861,7864,7868,7876,7879,7883,7886,7889],[13,7858,7859,7675],{},[26,7860,6644],{"href":7674},[13,7862,7863],{},"We have lots planned to improve the overall workflow with snapshots, and have a couple\nupdates to share that are available today.",[385,7865,7867],{"id":7866},"viewing-snapshot-contents","Viewing snapshot contents",[13,7869,7870,7871,7875],{},"Following the work done to ",[26,7872,7874],{"href":7873},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","enable viewing flows in the Team Library",", we've added\nthe same capability to snapshots.",[13,7877,7878],{},"Each snapshot now has a 'View Snapshot' option that will display the flows without having to open up\nthe full Node-RED editor.",[385,7880,7882],{"id":7881},"downloading-snapshots","Downloading snapshots",[13,7884,7885],{},"We've also added the ability to download snapshots locally - allowing you to take\nyour own offline backups of your flows.",[13,7887,7888],{},"The 'Download Snapshot' option is currently available on Instance Snapshots, but we'll be rolling\nit out to all snapshot types in the near future. We are also working on an Import feature\nthat will let you upload a snapshot back into the platform.",[13,7890,7891],{},[36,7892],{"alt":7893,"src":7894},"Download snapshot","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Fsnapshot-download.png",{"title":39,"searchDepth":55,"depth":55,"links":7896},[7897,7898],{"id":7866,"depth":598,"text":7867},{"id":7881,"depth":598,"text":7882},"FlowFuse now allows viewing snapshot contents and downloading them locally, enhancing backup and workflow flexibility.",{"tags":7901},[64],{"title":7767,"description":7899},{"loc":7681},"changelog\u002F2024\u002F05\u002Fsnapshot-improvements","qIDGMaoD1HGM4k-dfZwDqyQ_gVt0tpTCnV7M2PqBS5s",{"id":7907,"title":7908,"authors":7909,"body":7910,"date":7922,"description":7923,"extension":59,"issues":70,"meta":7924,"navigation":65,"path":7926,"seo":7927,"sitemap":7928,"stem":7929,"subtitle":70,"__hash__":7930},"changelog\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints.md","Blueprints added to Library",[5073],{"type":10,"value":7911,"toc":7920},[7912],[13,7913,7914,7915,7919],{},"Back in ",[26,7916,7918],{"href":7917},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints\u002F","October 2023",", we introduced Blueprints to help you get started with your new Node-RED applications. We've now made them accessible directly from the Library sidebar, where you can explore the available Blueprints and use them to kick-start your new flows.",{"title":39,"searchDepth":55,"depth":55,"links":7921},[],"2024-05-01","FlowFuse now features Blueprints directly accessible from the Library sidebar, facilitating easy exploration and utilization for kick-starting new Node-RED applications.",{"tags":7925},[64],"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints",{"title":7908,"description":7923},{"loc":7926},"changelog\u002F2024\u002F05\u002Flibrary-blueprints","JvpkQ2OskqQHlD-yAfB8HaYFFkdAR5GnkmvaBqUtIr8",{"id":7932,"title":7933,"authors":7934,"body":7935,"date":7922,"description":7951,"extension":59,"issues":70,"meta":7952,"navigation":65,"path":7873,"seo":7954,"sitemap":7955,"stem":7956,"subtitle":70,"__hash__":7957},"changelog\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer.md","Team Library - Flow Viewer",[5073],{"type":10,"value":7936,"toc":7949},[7937,7940,7943],[13,7938,7939],{},"The Library feature allows you to save and share common functionality and flows across your team on FlowFuse. We've just added the ability to preview any flows saved here, making it easier to understand what they do and explore your collections of flows before importing them into your workspace.",[13,7941,7942],{},"This new feature will better help you maintain and manage your team's shared flows, and give better visibility on flows that your fellow Team members are building.",[13,7944,7945],{},[36,7946],{"alt":7947,"src":7948},"Example entry being visualized from the Team Library","\u002Fchangelog\u002F2024\u002F05\u002Fimages\u002Flibrary-flowviewer.png",{"title":39,"searchDepth":55,"depth":55,"links":7950},[],"FlowFuse introduces Team Library - Flow Viewer, enabling easy preview and management of shared flows across your team.",{"tags":7953},[64],{"title":7933,"description":7951},{"loc":7873},"changelog\u002F2024\u002F05\u002Flibrary-flowviewer","fWP33ZLeK19dBItbjT5A7rse4Ogy3N8lfNlulplibLY",{"id":7959,"title":7960,"authors":7961,"body":7962,"date":7986,"description":7987,"extension":59,"issues":70,"meta":7988,"navigation":65,"path":7990,"seo":7991,"sitemap":7992,"stem":7993,"subtitle":70,"__hash__":7994},"changelog\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices.md","Custom Nodes Support on Devices",[8],{"type":10,"value":7963,"toc":7984},[7964,7972,7975,7981],[13,7965,7966,7967,7971],{},"We have supported the ability to configure your Node-RED instances with ",[26,7968,7970],{"href":7969},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support\u002F","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.",[13,7973,7974],{},"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.",[13,7976,7977],{},[36,7978],{"alt":7979,"src":7980},"Custom Node Catalog Support for Devices","\u002Fchangelog\u002F2024\u002F04\u002Fimages\u002Fdevice-npmrc-config.png",[7982,7983,7979],"figcaption",{},{"title":39,"searchDepth":55,"depth":55,"links":7985},[],"2024-04-11","FlowFuse now provides support for configuring Node-RED devices with custom node catalogues, enabling access to private node repositories across your device fleet.",{"tags":7989},[64],"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices",{"title":7960,"description":7987},{"loc":7990},"changelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","utthLx7Ub4ZzWfmIMyLyMY4tY7mV9NQZizeAt9-RHBA",{"id":7996,"title":7997,"authors":7998,"body":7999,"date":7986,"description":8025,"extension":59,"issues":70,"meta":8026,"navigation":65,"path":8028,"seo":8029,"sitemap":8030,"stem":8031,"subtitle":70,"__hash__":8032},"changelog\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups.md","Improving Device Groups",[8],{"type":10,"value":8000,"toc":8023},[8001,8004,8007,8013,8015,8021],[13,8002,8003],{},"Device Groups make it really simple to deploy a snapshot across multiple devices using our Pipelines feature.\nWhen the pipeline stage is triggered, you can watch as the snapshot is rolled out across all of target devices.",[13,8005,8006],{},"We've updated the Device Group view to include more information about what snapshot is currently deployed to the group, and the deployment status of individual devices in the group.",[13,8008,8009],{},[36,8010],{"alt":8011,"src":8012},"Summary details of all Device Groups in an application","\u002Fchangelog\u002F2024\u002F04\u002Fimages\u002Fdevice-group-summary.png",[7982,8014,8011],{},[13,8016,8017],{},[36,8018],{"alt":8019,"src":8020},"Details of all devices within a Device Group","\u002Fchangelog\u002F2024\u002F04\u002Fimages\u002Fdevice-group-details.png",[7982,8022,8019],{},{"title":39,"searchDepth":55,"depth":55,"links":8024},[],"FlowFuse now updated the Device Group view to include more information about what snapshot is currently deployed to the group, and more.",{"tags":8027},[64],"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups",{"title":7997,"description":8025},{"loc":8028},"changelog\u002F2024\u002F04\u002Fimproving-device-groups","tXdRBqnHpcxvGQu9p2xwJBNxkZ0LtPz8SvKescf2iCI",{"id":8034,"title":8035,"authors":8036,"body":8037,"date":7986,"description":8063,"extension":59,"issues":70,"meta":8064,"navigation":65,"path":8066,"seo":8067,"sitemap":8068,"stem":8069,"subtitle":70,"__hash__":8070},"changelog\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting.md","Tougher Rate Limiting on Public Routes",[8],{"type":10,"value":8038,"toc":8061},[8039,8042,8045,8052,8055,8058],[13,8040,8041],{},"Running any service on the internet requires constant vigilence on security issues. One feature\nwe've had in place for some time on FlowFuse Cloud is rate-limiting on our API. This limits how\noften someone can repeatedly call the API within a certain time frame.",[13,8043,8044],{},"We want to make sure we deter any misbehaviour, without getting in the way of genuine access.",[13,8046,8047,8048,8051],{},"For example, it would be entirely legitimate for a customer to use our ",[26,8049,8050],{"href":39},"API"," and automate some tasks via script. These API calls would arrive faster than if they were manually clicking around the FlowFuse UI, but that doesn't mean they should be restricted.",[13,8053,8054],{},"We also look to areas of the API that could be misused - for example, anything that can trigger an email to be sent, such as the \"I forgot my password\" API.",[13,8056,8057],{},"Tuning the rate-limiting is a continual process, and in that spirit we've recently made the rate limiting on certain routes to be much tougher and improved the feedback in the UI just in case a legitimate user accidentally hits it.",[13,8059,8060],{},"The tougher limits act as a better deterent, which in turn makes the platform more secure.",{"title":39,"searchDepth":55,"depth":55,"links":8062},[],"FlowFuse now enhances security with stricter rate limiting on public routes, ensuring robust protection against misuse while maintaining seamless access for legitimate users.",{"tags":8065},[64],"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting",{"title":8035,"description":8063},{"loc":8066},"changelog\u002F2024\u002F04\u002Ftougher-rate-limiting","w5PWtAIraI8a6SuhKuV1_galbtwswuEaZg4Aj2DsrAM",{"id":8072,"title":8073,"authors":8074,"body":8076,"date":8116,"description":8117,"extension":59,"issues":70,"meta":8118,"navigation":65,"path":8120,"seo":8121,"sitemap":8122,"stem":8123,"subtitle":70,"__hash__":8124},"changelog\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change.md","Pricing change Enterprise & Teams Tier",[8075],"marian-demme",{"type":10,"value":8077,"toc":8113},[8078,8086,8089,8100,8106,8110],[13,8079,8080,8081,227],{},"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 ",[26,8082,8085],{"href":8083,"rel":8084},"https:\u002F\u002Fflowfuse.com\u002Fpricing\u002F",[30],"pricing page",[13,8087,8088],{},"The new pricing scheme is as follows:",[251,8090,8091,8094,8097],{},[254,8092,8093],{},"Starter Tier: Remains unchanged",[254,8095,8096],{},"Teams Tier: Availability limited to Small $25 and Medium $50 Instances",[254,8098,8099],{},"Enterprise Tier: Availability limited to Medium $50 and Large $250 Instances",[13,8101,8102,8103,227],{},"We are also pleased to offer volume discounts. For more details, please ",[26,8104,4254],{"href":7443,"rel":8105},[30],[170,8107,8109],{"id":8108},"important-note-for-existing-teams","Important Note for Existing Teams",[13,8111,8112],{},"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.",{"title":39,"searchDepth":55,"depth":55,"links":8114},[8115],{"id":8108,"depth":194,"text":8109},"2024-04-03","FlowFuse Cloud updates pricing for Enterprise and Teams tiers, effective immediately, with options tailored to varying instance needs.",{"tags":8119},[64],"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change",{"title":8073,"description":8117},{"loc":8120},"changelog\u002F2024\u002F04\u002Fpricing-change","5ODeVlsjPsCslvKDZpGoDWp9TVLp8PKfTPIdk3mK4So",{"id":8126,"title":8127,"authors":8128,"body":8129,"date":8145,"description":8146,"extension":59,"issues":70,"meta":8147,"navigation":65,"path":8149,"seo":8150,"sitemap":8151,"stem":8152,"subtitle":70,"__hash__":8153},"changelog\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload.md","Configure HTTP Payload and Debug Message size",[8075],{"type":10,"value":8130,"toc":8143},[8131,8134,8137],[13,8132,8133],{},"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.",[13,8135,8136],{},"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.",[13,8138,8139],{},[36,8140],{"alt":8141,"src":8142},"Screenshot Settings","\u002Fchangelog\u002F2024\u002F03\u002Fimages\u002Flimits-payload-debug.png",{"title":39,"searchDepth":55,"depth":55,"links":8144},[],"2024-03-22","Introducing new FlowFuse configuration option control over HTTP request sizes and debug messages.",{"tags":8148},[64],"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload",{"title":8127,"description":8146},{"loc":8149},"changelog\u002F2024\u002F03\u002Flimits-debug-payload","cEbiT52JwSQc_zJxwSzuCPFHjUNOqd1c-KmqpVcfvbY",{"id":8155,"title":8156,"authors":8157,"body":8158,"date":8219,"description":8220,"extension":59,"issues":70,"meta":8221,"navigation":65,"path":8223,"seo":8224,"sitemap":8225,"stem":8226,"subtitle":70,"__hash__":8227},"changelog\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication.md","Bearer Token Authentication for Node-RED Instances",[8075,210],{"type":10,"value":8159,"toc":8217},[8160,8163,8169,8175,8211,8214],[13,8161,8162],{},"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.",[13,8164,8165],{},[36,8166],{"alt":8167,"src":8168},"Screenshot Instance Setting Bearer Token","\u002Fchangelog\u002F2024\u002F03\u002Fimages\u002Fbearer-token-authentication.png",[13,8170,8171],{},[36,8172],{"alt":8173,"src":8174},"Screenshot of New Bearer Token","\u002Fchangelog\u002F2024\u002F03\u002Fimages\u002Fbearer-token-exampe.png",[765,8176,8178],{"className":1839,"code":8177,"language":1841,"meta":39,"style":39},"$ curl -H \"Authorization: Bearer ffhttp_FKc_S4qlTBV1H411hmhneHcSJ6F_FGNQLPYbnoD3-B0\" https:\u002F\u002Fhealthy-rook-4329.flowforge.cloud\u002Ftest\nHelloWorld\n$\n",[86,8179,8180,8201,8206],{"__ignoreMap":39},[1845,8181,8182,8185,8188,8191,8193,8196,8198],{"class":1847,"line":1848},[1845,8183,8184],{"class":1851},"$",[1845,8186,8187],{"class":1855}," curl",[1845,8189,8190],{"class":1855}," -H",[1845,8192,3358],{"class":1871},[1845,8194,8195],{"class":1855},"Authorization: Bearer ffhttp_FKc_S4qlTBV1H411hmhneHcSJ6F_FGNQLPYbnoD3-B0",[1845,8197,3339],{"class":1871},[1845,8199,8200],{"class":1855}," https:\u002F\u002Fhealthy-rook-4329.flowforge.cloud\u002Ftest\n",[1845,8202,8203],{"class":1847,"line":194},[1845,8204,8205],{"class":1851},"HelloWorld\n",[1845,8207,8208],{"class":1847,"line":598},[1845,8209,8210],{"class":1851},"$\n",[13,8212,8213],{},"This feature is available for our Teams and Enterprise Tier customers. You can find the configuration under the Security tab in your instance settings.",[1993,8215,8216],{},"html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":39,"searchDepth":55,"depth":55,"links":8218},[],"2024-03-14","FlowFuse now supports Bearer Token authentication for Node-RED instances, ensuring secure access to HTTP endpoints.",{"tags":8222},[64],"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication",{"title":8156,"description":8220},{"loc":8223},"changelog\u002F2024\u002F03\u002Fbearer-token-authentication","GniCCz-HlK7jWO2giItS7acv7NUdl5EtUvtP3ftSqeM",{"id":8229,"title":8230,"authors":8231,"body":8232,"date":8219,"description":8245,"extension":59,"issues":70,"meta":8246,"navigation":65,"path":8248,"seo":8249,"sitemap":8250,"stem":8251,"subtitle":70,"__hash__":8252},"changelog\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode.md","Instance Protection Mode",[8075],{"type":10,"value":8233,"toc":8243},[8234,8237,8240],[13,8235,8236],{},"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.",[13,8238,8239],{},"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.",[13,8241,8242],{},"The Instance Protection option can be found under the Instance settings view for all our Teams and Enterprise Tier customers.",{"title":39,"searchDepth":55,"depth":55,"links":8244},[],"FlowFuse introduces Instance Protection Mode, empowering Team Owners to restrict production instance modifications for secure, careful management.",{"tags":8247},[64],"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode",{"title":8230,"description":8245},{"loc":8248},"changelog\u002F2024\u002F03\u002Finstance-protection-mode","ObAwzmDxlcSe9PjknN-ih-sPfjqZjJO41VXdirCEuwc",{"id":8254,"title":8255,"authors":8256,"body":8257,"date":8219,"description":8272,"extension":59,"issues":70,"meta":8273,"navigation":65,"path":8275,"seo":8276,"sitemap":8277,"stem":8278,"subtitle":70,"__hash__":8279},"changelog\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly.md","Remote Device Restart",[8075],{"type":10,"value":8258,"toc":8270},[8259,8262,8265],[13,8260,8261],{},"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.",[13,8263,8264],{},"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.",[13,8266,8267],{},[36,8268],{"alt":8255,"src":8269},"\u002Fchangelog\u002F2024\u002F03\u002Fimages\u002Frestart-devices-remotly.png",{"title":39,"searchDepth":55,"depth":55,"links":8271},[],"The latest FlowFuse device agent now supports remotely restarting Node-RED flows, aligning with capabilities for hosted instances.",{"tags":8274},[64],"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly",{"title":8255,"description":8272},{"loc":8275},"changelog\u002F2024\u002F03\u002Frestart-devices-remotly","rs8YIZ4x-mP_rbu-zTHXvoH5mMGy0c1u0UWDsw8wWfI",{"id":8281,"title":8282,"authors":8283,"body":8284,"date":8311,"description":8312,"extension":59,"issues":70,"meta":8313,"navigation":65,"path":8315,"seo":8316,"sitemap":8317,"stem":8318,"subtitle":70,"__hash__":8319},"changelog\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot.md","Direct Dashboard Access",[284],{"type":10,"value":8285,"toc":8309},[8286,8289,8301],[13,8287,8288],{},"We have added quick access buttons to help you navigate to your Dashboard 2.0 UI in a single click.",[13,8290,8291,8294],{},[36,8292],{"alt":39,"src":8293},"\u002Fchangelog\u002F2024\u002F04\u002Fimages\u002FDashboard-Link.png",[43,8295,8296,8297,8300],{},"Dashboard button is displayed alongside the Open Editor button when an instance has ",[86,8298,8299],{},"@flowfuse\u002Fnode-red-dashboard"," installed.",[13,8302,8303,8304],{},"Click the link to learn more about ",[26,8305,8308],{"href":8306,"rel":8307},"https:\u002F\u002Fdashboard.flowfuse.com\u002F",[30],"Flowfuse Dashboard 2.0",{"title":39,"searchDepth":55,"depth":55,"links":8310},[],"2024-03-06","FlowFuse introduces Direct Dashboard Access with an 'open dashboard' button for streamlined navigation to Dashboard 2.0 UI.",{"tags":8314},[64],"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot",{"title":8282,"description":8312},{"loc":8315},"changelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","NfC3pDSOwzJWc1VKxR180eU-jkqZMxdJWbh-LkO30fI",{"id":8321,"title":8322,"authors":8323,"body":8324,"date":8347,"description":8348,"extension":59,"issues":70,"meta":8349,"navigation":65,"path":8351,"seo":8352,"sitemap":8353,"stem":8354,"subtitle":70,"__hash__":8355},"changelog\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots.md","Instance Auto Snapshots",[8075],{"type":10,"value":8325,"toc":8345},[8326,8334,8337],[13,8327,8328,8329,8333],{},"Two weeks ago, we introduced ",[26,8330,8332],{"href":8331},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot\u002F","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.",[13,8335,8336],{},"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\nthey are marked as a target snapshot for your devices.",[13,8338,8339,8340,4354,8343,227],{},"Click the following links to learn more about ",[26,8341,4413],{"href":8342},"\u002Fdocs\u002Fuser\u002Fconcepts\u002F#instance",[26,8344,3739],{"href":7674},{"title":39,"searchDepth":55,"depth":55,"links":8346},[],"2024-02-28","FlowFuse Cloud now offers extended auto snapshots for hosted Node-RED instances. Automatically manage flow changes with up to 10 snapshots.",{"tags":8350},[64],"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots",{"title":8322,"description":8348},{"loc":8351},"changelog\u002F2024\u002F02\u002Finstance-auto-snapshots","IJP2b90iboRKSdSuhl9jAngUp07kfuJKgn_YrBEYbyI",{"id":8357,"title":8358,"authors":8359,"body":8360,"date":8393,"description":8364,"extension":59,"issues":70,"meta":8394,"navigation":65,"path":8396,"seo":8397,"sitemap":8398,"stem":8399,"subtitle":70,"__hash__":8400},"changelog\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot.md","Device Auto Snapshots",[284],{"type":10,"value":8361,"toc":8391},[8362,8365,8368,8371,8376,8381],[13,8363,8364],{},"FlowFuse V2.1 introduces Auto Snapshots for your Application Assigned Devices.",[13,8366,8367],{},"When you deploy a change to the device flows, a snapshot will be taken automatically.",[13,8369,8370],{},"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.",[13,8372,8373],{},[36,8374],{"alt":39,"src":8375},"\u002Fchangelog\u002F2024\u002F02\u002Fimages\u002FDevice-auto-snapshot1.png",[13,8377,8378],{},[36,8379],{"alt":39,"src":8380},"\u002Fchangelog\u002F2024\u002F02\u002Fimages\u002FDevice-auto-snapshot2.png",[13,8382,8339,8383,4354,8387,227],{},[26,8384,4416],{"href":8385,"rel":8386},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fdevice-agent\u002F",[30],[26,8388,3739],{"href":8389,"rel":8390},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fsnapshots\u002F#snapshots",[30],{"title":39,"searchDepth":55,"depth":55,"links":8392},[],"2024-02-15",{"tags":8395},[64],"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot",{"title":8358,"description":8364},{"loc":8396},"changelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","cyq0w7CWOzDGXSkIOkU9H5pw05bLmNkSEI_pnZMw9_4",{"id":8402,"title":8403,"authors":8404,"body":8405,"date":8393,"description":8419,"extension":59,"issues":70,"meta":8420,"navigation":65,"path":8422,"seo":8423,"sitemap":8424,"stem":8425,"subtitle":70,"__hash__":8426},"changelog\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade.md","PostgreSQL Version update",[210],{"type":10,"value":8406,"toc":8417},[8407,8414],[13,8408,8409,8410,8413],{},"Included in the v2.1.0 release the Helm Chart now uses ",[86,8411,8412],{},"14.10.0-debian-11-r30"," tag of the Bitnami PostgreSQL container.",[13,8415,8416],{},"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.",{"title":39,"searchDepth":55,"depth":55,"links":8418},[],"FlowFuse now deploys to ARM64-based Kubernetes clusters with local PostgreSQL databases. Helm Chart v2.1.0 uses Bitnami PostgreSQL tag 14.10.0-debian-11-r30 for AMD64 and ARM64.",{"tags":8421},[64],"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade",{"title":8403,"description":8419},{"loc":8422},"changelog\u002F2024\u002F02\u002Fpostgresql-upgrade","uymx68WAlsVPcwpeyVo9npxTkNIQKQ91syW7Xi31QcY",{"id":8428,"title":8429,"authors":8430,"body":8431,"date":8464,"description":8465,"extension":59,"issues":70,"meta":8466,"navigation":65,"path":8468,"seo":8469,"sitemap":8470,"stem":8471,"subtitle":70,"__hash__":8472},"changelog\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change.md","Pricing change for Devices",[8075],{"type":10,"value":8432,"toc":8461},[8433,8440,8451,8456,8458],[13,8434,8435,8436,8439],{},"Starting today, we have introduced a simplification of the pricing structure for devices on FlowFuse Cloud, effective immediately. All information is available on our ",[26,8437,8085],{"href":8083,"rel":8438},[30],".\nThe new pricing scheme is as follows:",[251,8441,8442,8445,8448],{},[254,8443,8444],{},"Starter Tier: No change",[254,8446,8447],{},"Teams Tier: Devices are now priced at $25 each.",[254,8449,8450],{},"Enterprise Tier: Devices are priced at $50 each.",[13,8452,8102,8453,227],{},[26,8454,4254],{"href":7443,"rel":8455},[30],[170,8457,8109],{"id":8108},[13,8459,8460],{},"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.\nFor teams without any prior device history, the addition of devices will be billed at the new rates.",{"title":39,"searchDepth":55,"depth":55,"links":8462},[8463],{"id":8108,"depth":194,"text":8109},"2024-02-09","FlowFuse Cloud introduces a simplified pricing structure: Devices are now priced at $25 each for Teams Tier and $50 each for Enterprise Tier.",{"tags":8467},[64],"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change",{"title":8429,"description":8465},{"loc":8468},"changelog\u002F2024\u002F02\u002Fdevice-pricing-change","wjmS3igwAditUh6Yx2fZGtgTjs7UQRzFMGBQW9KKJps",{"id":8474,"title":8475,"authors":8476,"body":8477,"date":8499,"description":8500,"extension":59,"issues":70,"meta":8501,"navigation":65,"path":8503,"seo":8504,"sitemap":8505,"stem":8506,"subtitle":70,"__hash__":8507},"changelog\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs.md","Device Instance Audit Logging",[284],{"type":10,"value":8478,"toc":8497},[8479,8482,8485,8488,8491],[13,8480,8481],{},"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.",[13,8483,8484],{},"This brings closer parity with the logging you get from a hosted instance.",[13,8486,8487],{},"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.",[13,8489,8490],{},"Update to Device Agent v2.2 to start receiving the events.",[13,8492,8493],{},[36,8494],{"alt":8495,"src":8496},"Device Audit log","\u002Fchangelog\u002F2024\u002F02\u002Fimages\u002Fdevice-auditlog.png",{"title":39,"searchDepth":55,"depth":55,"links":8498},[],"2024-02-08","Device Instance Audit Logging: The Device Instance now logs Node-RED events on your device, providing enhanced visibility into flow updates and configuration changes.",{"tags":8502},[64],"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs",{"title":8475,"description":8500},{"loc":8503},"changelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","HcJ9TdLqPAudXlTAfFoCRCUhxEYyRR3DYfh-VxGLtdU",{"id":8509,"title":8510,"authors":8511,"body":8512,"date":8540,"description":8541,"extension":59,"issues":70,"meta":8542,"navigation":65,"path":8544,"seo":8545,"sitemap":8546,"stem":8547,"subtitle":70,"__hash__":8548},"changelog\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements.md","Device Onboarding Improvements",[284],{"type":10,"value":8513,"toc":8538},[8514,8517,8520,8525,8530],[13,8515,8516],{},"Hot on the heals of our recent onboarding improvements and streamlining, we\nhave now introduced a new, simpler and faster way of getting your devices\nconfigured and connected to the FlowFuse platform.",[13,8518,8519],{},"Now, when you create a device on the platform, you will be offered a simple\n\"Setup command\". Run this command in a terminal and the let the Device\nAgent do all the hard work for you.",[13,8521,8522],{},[36,8523],{"alt":39,"src":8524},"\u002Fchangelog\u002F2024\u002F02\u002Fimages\u002Fdevice-onboarding-improvements-1.png",[13,8526,8527],{},[36,8528],{"alt":39,"src":8529},"\u002Fchangelog\u002F2024\u002F02\u002Fimages\u002Fdevice-onboarding-improvements-2.png",[13,8531,8532,8533,8537],{},"To learn more about this, head to the ",[26,8534,8536],{"href":8385,"rel":8535},[30],"FlowFuse Device Agent"," documentation.",{"title":39,"searchDepth":55,"depth":55,"links":8539},[],"2024-02-05","Improved Device Onboarding to Simplify and accelerate device configuration and connection to FlowFuse with our new setup command.",{"tags":8543},[64],"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements",{"title":8510,"description":8541},{"loc":8544},"changelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","ZyQaYjLlpMCurdYwz2KGSbSAR4TQB4gjXI5Z9jKZtu0",{"id":8550,"title":8551,"authors":8552,"body":8553,"date":8568,"description":8569,"extension":59,"issues":70,"meta":8570,"navigation":65,"path":8572,"seo":8573,"sitemap":8574,"stem":8575,"subtitle":70,"__hash__":8576},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment.md","Streamlined Device assignment",[8],{"type":10,"value":8554,"toc":8566},[8555,8558,8561],[13,8556,8557],{},"To start editing flows on a device, it needs to be assigned to an application\nin your team. Up until now this has been a two step process; creating the device\nand then assigning it. This wasn't as intuitive as it needed to be.",[13,8559,8560],{},"To help streamline the user experience, you can now assign a device to an application\nwhen you create it. It's a small update, but it helps users get to where they want\nto be much quicker.",[13,8562,8563],{},[36,8564],{"alt":39,"src":8565},"\u002Fchangelog\u002F2024\u002F01\u002Fimages\u002Fdevice-assignment.png",{"title":39,"searchDepth":55,"depth":55,"links":8567},[],"2024-01-23","Streamlined Device Assignment: Assign devices to applications upon creation for a quicker start to flow editing, enhancing user experience.",{"tags":8571},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment",{"title":8551,"description":8569},{"loc":8572},"changelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","OguZZmQ9XSPorpyY2PD_hL74VhQFHP1eNLWKHz5_Rnc",{"id":8578,"title":8579,"authors":8580,"body":8581,"date":8635,"description":8636,"extension":59,"issues":70,"meta":8637,"navigation":65,"path":8639,"seo":8640,"sitemap":8641,"stem":8642,"subtitle":70,"__hash__":8643},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints.md","New Blueprints added",[8075],{"type":10,"value":8582,"toc":8633},[8583,8586,8589,8592,8618,8626],[13,8584,8585],{},"We have added some new blueprints to FlowFuse Cloud to help users get started with a range of common manufacturing scenarios.",[13,8587,8588],{},"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.",[13,8590,8591],{},"List of new Blueprints:",[251,8593,8594,8600,8606,8612],{},[254,8595,8596],{},[26,8597,8599],{"href":8598},"\u002Fblueprints\u002Fmanufacturing\u002Fandon-live\u002F","Andon Live",[254,8601,8602],{},[26,8603,8605],{"href":8604},"\u002Fblueprints\u002Fgetting-started\u002Fcrud\u002F","CRUD for Mongo DB",[254,8607,8608],{},[26,8609,8611],{"href":8610},"\u002Fblueprints\u002Fmanufacturing\u002F5s-checklist\u002F","5S Manufacturing checklist",[254,8613,8614],{},[26,8615,8617],{"href":8616},"\u002Fblueprints\u002Fmanufacturing\u002Fperformance-overview\u002F","Performance Operator Terminal",[13,8619,8620,8621,227],{},"Curious about what Blueprints are? Read our recent blog post that ",[26,8622,8625],{"href":8623,"rel":8624},"https:\u002F\u002Fflowfuse.com\u002Fblog\u002F2023\u002F10\u002Fblueprints\u002F",[30],"introduced Blueprints to FlowFuse",[13,8627,8628,8629,227],{},"For an overview of all available Blueprints check out our ",[26,8630,8632],{"href":4576,"rel":8631},[30],"Blueprint Library",{"title":39,"searchDepth":55,"depth":55,"links":8634},[],"2024-01-22","Explore FlowFuse Cloud's latest blueprints designed for manufacturing scenarios, including Andon Live, CRUD for MongoDB, Performance Operator Terminal and more.",{"tags":8638},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints",{"title":8579,"description":8636},{"loc":8639},"changelog\u002F2024\u002F01\u002Fnew-blueprints","NNBoEBroFwQPJ_GYWBRFe03SIdBRDgvGkG1lIzeb-Ko",{"id":8645,"title":8646,"authors":8647,"body":8648,"date":8677,"description":8678,"extension":59,"issues":70,"meta":8679,"navigation":65,"path":8681,"seo":8682,"sitemap":8683,"stem":8684,"subtitle":70,"__hash__":8685},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log.md","Introducing the Device Auditlog Feature",[8075],{"type":10,"value":8649,"toc":8675},[8650,8653,8656,8670],[13,8651,8652],{},"The introduction of the Device Auditlog brings an enhanced level of monitoring and tracking for device-related activities, available to all FlowFuse users.",[13,8654,8655],{},"Events Recorded in the Device Auditlog:",[251,8657,8658,8661,8664,8667],{},[254,8659,8660],{},"Fleet mode \u002F Developer mode enabled\u002Fdisabled",[254,8662,8663],{},"Remote access enabled\u002Fdisabled",[254,8665,8666],{},"Credentials re-generated",[254,8668,8669],{},"Device assigned",[13,8671,8672],{},[36,8673],{"alt":8495,"src":8674},"\u002Fchangelog\u002F2024\u002F01\u002Fimages\u002FDevice-Auditlog.png",{"title":39,"searchDepth":55,"depth":55,"links":8676},[],"2024-01-18","FlowFuse's Device Auditlog: monitor mode changes, remote access, credential updates, and device assignments for enhanced oversight and security.",{"tags":8680},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log",{"title":8646,"description":8678},{"loc":8681},"changelog\u002F2024\u002F01\u002Fdevice-audit-log","x0e7x3e91gt2HRvXLVsJofuC7icu9aipRKFgLzjOtiA",{"id":8687,"title":8688,"authors":8689,"body":8690,"date":8677,"description":8706,"extension":59,"issues":70,"meta":8707,"navigation":65,"path":8709,"seo":8710,"sitemap":8711,"stem":8712,"subtitle":70,"__hash__":8713},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot.md","Device Groups - Automatic snapshot assignment",[8075],{"type":10,"value":8691,"toc":8704},[8692,8701],[13,8693,8694,8695,8700],{},"Four weeks ago, we launched the ",[26,8696,8699],{"href":8697,"rel":8698},"https:\u002F\u002Fflowfuse.com\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups\u002F",[30],"Device Groups"," feature, for our Enterprise customers. This innovation marked a significant step in simplifying device management within DevOps Pipelines. Now we enhacent the Device Groups functionality.",[13,8702,8703],{},"With this update, the behavior of Device Groups has been refined to further streamline your workflow. Now, whenever a Snapshot is assigned to a Device Group, any newly added devices to that group will automatically receive the update. This ensures that all devices within the group are consistently synchronized with the latest changes, eliminating the need for manual updates. This improvement not only saves time but also enhances the consistency and reliability of device management across your fleet.",{"title":39,"searchDepth":55,"depth":55,"links":8705},[],"With enhanced Device Groups functionality, automatically synchronize snapshot updates across your fleet for streamlined device management.",{"tags":8708},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot",{"title":8688,"description":8706},{"loc":8709},"changelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","uTNcgYTmDQlnd4jsHjPg2yAsdEPc01uQrW3VH3NHz_g",{"id":8715,"title":8716,"authors":8717,"body":8718,"date":8677,"description":8749,"extension":59,"issues":70,"meta":8750,"navigation":65,"path":8752,"seo":8753,"sitemap":8754,"stem":8755,"subtitle":70,"__hash__":8756},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2.md","Helm Chart v2.0",[210],{"type":10,"value":8719,"toc":8747},[8720,8727,8730,8739],[13,8721,8722,8723,8726],{},"The v2.0 release of the FlowFuse Helm Chart includes a breaking change for deployments making use of the ",[86,8724,8725],{},"forge.localPostgresql"," setting when upgrading. This is where the helm chart installs a dedicated PostgreSQL database instance.",[13,8728,8729],{},"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.",[13,8731,8732,8733,8738],{},"The steps are documented on the ",[26,8734,8737],{"href":8735,"rel":8736},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Finstall\u002Fkubernetes\u002F#upgrade",[30],"Upgrade instructions"," page, please read them carefully before upgrading",[13,8740,8741,8742],{},"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 ",[26,8743,8746],{"href":8744,"rel":8745},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fhelm\u002Ftree\u002Fmain\u002Fhelm\u002Fflowforge#readme",[30],"README.md",{"title":39,"searchDepth":55,"depth":55,"links":8748},[],"FlowFuse Helm Chart Update: v2 introduces streamlined upgrades and enhanced capabilities for managing resource constraints and Pod Security Context.",{"tags":8751},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2",{"title":8716,"description":8749},{"loc":8752},"changelog\u002F2024\u002F01\u002Fhelm-v2","m-E_kizEhKUZLJKGEzCP1RwCXec5e9ejs8lgbUI7lNc",{"id":8758,"title":8759,"authors":8760,"body":8761,"date":8806,"description":8807,"extension":59,"issues":70,"meta":8808,"navigation":65,"path":8810,"seo":8811,"sitemap":8812,"stem":8813,"subtitle":70,"__hash__":8814},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates.md","Security Updates",[8],{"type":10,"value":8762,"toc":8804},[8763,8772,8775,8778,8781,8792,8795,8798],[13,8764,8765,8766,8771],{},"As part of our dedication to providing a secure platform for our customers, we\noperate a ",[26,8767,8770],{"href":8768,"rel":8769},"https:\u002F\u002Fflowfuse.com\u002Fhandbook\u002Fengineering\u002Fsecurity\u002F",[30],"Bug Bounty programme","\nto encourage responsible disclosure of potential issues.",[13,8773,8774],{},"With all disclosures we evaluate their severity in terms of their direct impact,\nthe nature of the issue and overall risk.",[13,8776,8777],{},"We have received a number of reports recently that we have been evaluating. Whilst\nnone of the recent disclosures has been deemed high severity, we have applied a number\nof updates to the platform.",[13,8779,8780],{},"These include:",[251,8782,8783,8786,8789],{},[254,8784,8785],{},"Tougher rate limiting on routes that manage user information including email addresses",[254,8787,8788],{},"Better handling of the password-reset flow to prevent stale links being reused",[254,8790,8791],{},"Avoiding disclosure of a user's email address to other members of a team",[13,8793,8794],{},"This last item is one I wanted to say a bit more about. As you would expect, a\nuser's email address is sensitive information that we do not disclose to unauthorised\nusers. However, we also consider a Team as having a higher level of trust between its\nmembers. On review, we have decided there is not a technical reason for this higher\nlevel of trust to include a member's email address, so we have removed it from\nthe relevant API responses.",[13,8796,8797],{},"We value the effort people put into making responsible disclosures to us and look\nto reward the work where it meets our criteria.",[13,8799,8800,8801,227],{},"Find out more about our ",[26,8802,8770],{"href":8768,"rel":8803},[30],{"title":39,"searchDepth":55,"depth":55,"links":8805},[],"2024-01-17","Security Updates: We've strengthened user privacy and platform security with stricter rate limiting and improved password-reset flows.",{"tags":8809},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates",{"title":8759,"description":8807},{"loc":8810},"changelog\u002F2024\u002F01\u002Fsecurity-updates","3KMfNxubN4eiSiS0rz7cDKbT9chNd6dRGnmQIDYx-So",{"id":8816,"title":8817,"authors":8818,"body":8819,"date":8806,"description":8844,"extension":59,"issues":70,"meta":8845,"navigation":65,"path":8847,"seo":8848,"sitemap":8849,"stem":8850,"subtitle":70,"__hash__":8851},"changelog\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership.md","Managing Team Membership via SSO",[8],{"type":10,"value":8820,"toc":8842},[8821,8824,8827,8830,8839],[13,8822,8823],{},"For organizations using Single Sign-On with FlowFuse, we have now added the ability\nto manage their user's team memberships and roles via their Identity Provider.",[13,8825,8826],{},"This makes it easier to control access to the FlowFuse Platform from providers such\nas Okta and Microsoft Entra. For example, you can create a group of Team Owners\nand a separate group of Team Viewers.",[13,8828,8829],{},"Whenever a user logs in via SSO, the platform will update their roles to match\nthe groups they are in.",[13,8831,8832,8833,8838],{},"More information on configuring groups can be found in ",[26,8834,8837],{"href":8835,"rel":8836},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fadmin\u002Fsso\u002F",[30],"our Single Sign-on","\ndocumentation.",[13,8840,8841],{},"This feature is available to Enterprise Tier teams on FlowFuse Cloud, as well as\nself-hosted Enterprise instances.",{"title":39,"searchDepth":55,"depth":55,"links":8843},[],"Enhance Team Membership Management via SSO: Update roles in FlowFuse with providers such as Okta and Microsoft Entra, ensuring streamlined access control.",{"tags":8846},[64],"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership",{"title":8817,"description":8844},{"loc":8847},"changelog\u002F2024\u002F01\u002Fsso-team-membership","G_yGTXWveKavgWVYjQ1HoMcTrwqSviN71r1X1BLR5ts",{"id":8853,"title":8854,"authors":8855,"body":8856,"date":8877,"description":8878,"extension":59,"issues":70,"meta":8879,"navigation":65,"path":8881,"seo":8882,"sitemap":8883,"stem":8884,"subtitle":70,"__hash__":8885},"changelog\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode.md","Renaming \"Default Device Mode\" to \"Fleet Mode\"",[8075],{"type":10,"value":8857,"toc":8875},[8858,8861],[13,8859,8860],{},"In our continuous effort to enhance user experience and clarity, we are pleased to announce an update to our device mode terminology. Previously known as \"Default Device\" mode, we have now rebranded it as \"Fleet Mode.\" This change aims to establish a clearer distinction from \"Developer Mode,\" thereby streamlining the understanding of operational modes for our devices.",[251,8862,8863,8869],{},[254,8864,8865,8868],{},[150,8866,8867],{},"Fleet Mode",": Runs any target Snapshots defined. Blocks remote editing of device.",[254,8870,8871,8874],{},[150,8872,8873],{},"Developer Mode",": Blocks any new Target Snapshots running, but allows for remote editing on the Device.",{"title":39,"searchDepth":55,"depth":55,"links":8876},[],"2024-01-11","FlowFuse updated terminology: \"Default Device Mode\" is now \"Fleet Mode,\" enhancing clarity and operational distinctions for users.",{"tags":8880},[64],"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode",{"title":8854,"description":8878},{"loc":8881},"changelog\u002F2024\u002F01\u002Ffleet-mode","IJileFxSj8gDLT-xXM8mtICmKJOw3ZKY8oSrOvrWEU8",{"id":8887,"title":8888,"authors":8889,"body":8890,"date":8911,"description":8912,"extension":59,"issues":70,"meta":8913,"navigation":65,"path":8915,"seo":8916,"sitemap":8917,"stem":8918,"subtitle":70,"__hash__":8919},"changelog\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection.md","Blueprint Selection Update",[8075],{"type":10,"value":8891,"toc":8909},[8892,8895,8902],[13,8893,8894],{},"We have updated the blueprint selection interface to enhance the user experience by offering a clearer and more comprehensive overview. This improvement aims to facilitate easier navigation and selection of blueprints. Additionally, we are excited to announce that our blueprint library will be expanding in the coming days, with the addition of new blueprints to FlowFuse.",[13,8896,8897],{},[36,8898],{"alt":8899,"src":8900,"title":8901},"\"FlowFuse Blueprint Selection\"","\u002Fchangelog\u002F2023\u002F12\u002Fimages\u002Fblueprints-selection.png","FlowFuse Blueprint Selection",[13,8903,8904,8905,227],{},"For more detailed information about our blueprints and how to utilize them effectively, please refer to our dedicated ",[26,8906,8908],{"href":8907},"\u002Fblog\u002F2023\u002F10\u002Fblueprints\u002F","article",{"title":39,"searchDepth":55,"depth":55,"links":8910},[],"2023-12-21","FlowFuse enhances UX: Improved blueprint selection interface for easier navigation and selection. Stay tuned for our expanding blueprint library.",{"tags":8914},[64],"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection",{"title":8888,"description":8912},{"loc":8915},"changelog\u002F2023\u002F12\u002Fblueprint-selection","zRh1ZZ-SWYpHtomdsAfQijXoDzNSJ5aHRabBJ7aXvhg",{"id":8921,"title":8699,"authors":8922,"body":8923,"date":8911,"description":8938,"extension":59,"issues":70,"meta":8939,"navigation":65,"path":8941,"seo":8942,"sitemap":8943,"stem":8944,"subtitle":70,"__hash__":8945},"changelog\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups.md",[8075],{"type":10,"value":8924,"toc":8936},[8925,8928],[13,8926,8927],{},"We are pleased to announce the introduction of Device Groups for Enterprise Tier customers. This new feature enables users to logically group their devices assigned to an application. Additionally, Device Groups can be integrated into the DevOps Pipeline. This integration facilitates more streamlined and efficient deployments across your fleet of devices.",[13,8929,8930,8933],{},[36,8931],{"alt":39,"src":8932},"\u002Fchangelog\u002F2023\u002F12\u002Fimages\u002Fdevice-groups.png",[36,8934],{"alt":39,"src":8935},"\u002Fchangelog\u002F2023\u002F12\u002Fimages\u002Fdevice-group-pipeline.png",{"title":39,"searchDepth":55,"depth":55,"links":8937},[],"FlowFuse update: Introducing Device Groups for improved device management and streamlined integration into DevOps Pipelines",{"tags":8940},[64],"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups",{"title":8699,"description":8938},{"loc":8941},"changelog\u002F2023\u002F12\u002Fdevice-groups","_7CtZFlo9Br0g_ccqI6dmPkNgGi_UvPSfSpDt-JyhCs",{"id":8947,"title":8948,"authors":8949,"body":8950,"date":8911,"description":8965,"extension":59,"issues":70,"meta":8966,"navigation":65,"path":8968,"seo":8969,"sitemap":8970,"stem":8971,"subtitle":70,"__hash__":8972},"changelog\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash.md","Email Alerts for Audit Log Events",[8075],{"type":10,"value":8951,"toc":8963},[8952,8958],[13,8953,8954,8955,227],{},"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 ",[26,8956,6958],{"href":8957},"\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#alerts",[13,8959,8960],{},[36,8961],{"alt":39,"src":8962},"\u002Fchangelog\u002F2023\u002F12\u002Fimages\u002Falerts.png",{"title":39,"searchDepth":55,"depth":55,"links":8964},[],"FlowFuse update: Now receive email alerts for Audit Log events, ensuring timely notifications for Node-RED instance crashes.",{"tags":8967},[64],"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash",{"title":8948,"description":8965},{"loc":8968},"changelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","gZwrTGaRLKY1lz6edgGfR7flAmbR8UBm8VLkM9Up4lY",{"id":8974,"title":8975,"authors":8976,"body":8977,"date":9000,"description":9001,"extension":59,"issues":70,"meta":9002,"navigation":65,"path":9004,"seo":9005,"sitemap":9006,"stem":9007,"subtitle":70,"__hash__":9008},"changelog\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated.md","Node-RED 3.1.3 now available",[8],{"type":10,"value":8978,"toc":8998},[8979,8982,8990],[13,8980,8981],{},"With Node-RED 3.1.3 being released this week, we've updated our stacks to ensure it's available to everyone in FlowFuse Cloud. We have also made it the default version you'll get when creating new instances.",[13,8983,8984,8985,227],{},"If you want to update your existing instances to this new stack you can follow the ",[26,8986,8989],{"href":8987,"rel":8988},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Fchangestack\u002F",[30],"guide here",[13,8991,8992,8993,227],{},"For more information about the changes in Node-RED 3.1.3, check the ",[26,8994,8997],{"href":8995,"rel":8996},"https:\u002F\u002Fgithub.com\u002Fnode-red\u002Fnode-red\u002Fblob\u002F7fd0ecf721fc78e8415dca3106bc71b461e6554d\u002FCHANGELOG.md",[30],"release's changelog",{"title":39,"searchDepth":55,"depth":55,"links":8999},[],"2023-12-07","Node-RED 3.1.3 now in FlowFuse Cloud, with updated stacks and default installation for new instances. Update existing instances with our guide.",{"tags":9003},[64],"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated",{"title":8975,"description":9001},{"loc":9004},"changelog\u002F2023\u002F12\u002Fnode-red-updated","v7cT_bDElBIYlvd_UDC5X2HFzvmw8xW96L4znU-TonI",{"id":9010,"title":9011,"authors":9012,"body":9013,"date":9027,"description":9028,"extension":59,"issues":70,"meta":9029,"navigation":65,"path":9031,"seo":9032,"sitemap":9033,"stem":9034,"subtitle":70,"__hash__":9035},"changelog\u002Fchangelog\u002F2023\u002F12\u002Fbilling.md","No Credit Card required for billing",[8075],{"type":10,"value":9014,"toc":9025},[9015,9018],[13,9016,9017],{},"We now have more flexible billing options in FlowFuse Cloud for customers that wish to purchase an annual subscription or where entering credit card details is not appropriate. We're committed to accommodating your specific billing preferences and can set up a process that aligns with your organizational needs.",[13,9019,9020,9021,9024],{},"If you are interested in this new option or have any questions, please don't hesitate to ",[26,9022,4254],{"href":7443,"rel":9023},[30],". We're here to help you with your billing and subscription needs.",{"title":39,"searchDepth":55,"depth":55,"links":9026},[],"2023-12-06","FlowFuse Cloud now offers billing without requiring credit card details. Explore our flexible annual subscription options tailored to fit your needs.",{"tags":9030},[64],"\u002Fchangelog\u002F2023\u002F12\u002Fbilling",{"title":9011,"description":9028},{"loc":9031},"changelog\u002F2023\u002F12\u002Fbilling","KeqVwVk8vgQBZLVPAXg9JcwHBNvS4OkPOKBCnoZqX50",{"id":9037,"title":9038,"authors":9039,"body":9040,"date":9061,"description":9062,"extension":59,"issues":70,"meta":9063,"navigation":65,"path":9065,"seo":9066,"sitemap":9067,"stem":9068,"subtitle":70,"__hash__":9069},"changelog\u002Fchangelog\u002F2023\u002F11\u002F2fa.md","Two-Factor Authentication",[8075],{"type":10,"value":9041,"toc":9059},[9042,9045,9051],[13,9043,9044],{},"In our ongoing commitment to strengthen security, we're excited to announce the addition of two-factor authentication (2FA) for FlowFuse. This enhancement ensures an extra layer of security for your account. Setting up 2FA is straightforward, and the system supports all commonly used TOTP (Time-Based One-Time Password) tools, such as Google Authenticator. To enable 2FA, simply navigate to your User Settings and follow the easy setup process.",[13,9046,9047],{},[36,9048],{"alt":9049,"src":9050},"Config 2FA","\u002Fchangelog\u002F2023\u002F11\u002Fimages\u002F2fa.png",[13,9052,9053,9054,9058],{},"For more Details see our ",[26,9055,9057],{"href":9056},"\u002Fdocs\u002Fuser\u002Fuser-settings\u002F","Documentation","\n2FA is available for all FlowFuse Cloud users and for Enterprise Self-Hosted customers.",{"title":39,"searchDepth":55,"depth":55,"links":9060},[],"2023-11-23","Enhance your FlowFuse security with two-factor authentication (2FA). Set up 2FA using TOTP tools like Google Authenticator for an added layer of account security.",{"tags":9064},[64],"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"title":9038,"description":9062},{"loc":9065},"changelog\u002F2023\u002F11\u002F2fa","GOWK4f86L-NJAduvD5-acnl70vuKQ59Biuhrl1YjZk8",{"id":9071,"title":9072,"authors":9073,"body":9074,"date":9061,"description":9087,"extension":59,"issues":70,"meta":9088,"navigation":65,"path":9090,"seo":9091,"sitemap":9092,"stem":9093,"subtitle":70,"__hash__":9094},"changelog\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor.md","Device Editor enabled by default",[8075],{"type":10,"value":9075,"toc":9085},[9076],[13,9077,9078,9079,9081,9082,9084],{},"With the latest update, devices operating in ",[86,9080,8873],{}," will now have the ",[86,9083,2128],{}," feature enabled by default. This enhancement is designed to improve the User Experience.",{"title":39,"searchDepth":55,"depth":55,"links":9086},[],"FlowFuse Enhanced UX: Devices in Developer Mode now have the Open Editor feature enabled by default, improving accessibility and usability.",{"tags":9089},[64],"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor",{"title":9072,"description":9087},{"loc":9090},"changelog\u002F2023\u002F11\u002Fdefault-editor","5zv2a_wgRQ9KJKibXzAWPXz9p4ASEf_Ge4p5a-bs4jo",{"id":9096,"title":9097,"authors":9098,"body":9099,"date":9061,"description":9120,"extension":59,"issues":70,"meta":9121,"navigation":65,"path":9123,"seo":9124,"sitemap":9125,"stem":9126,"subtitle":70,"__hash__":9127},"changelog\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines.md","Devices in DevOps Pipelines",[8075],{"type":10,"value":9100,"toc":9118},[9101,9110,9115],[13,9102,9103,9104,9109],{},"Building on our ",[26,9105,9108],{"href":9106,"rel":9107},"https:\u002F\u002Fflowfuse.com\u002Fblog\u002F2023\u002F08\u002Fflowfuse-1-11-release\u002F#usability-improvements-to-device-management-%232294",[30],"previous release"," 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.",[13,9111,9112],{},[36,9113],{"alt":9097,"src":9114},"\u002Fchangelog\u002F2023\u002F11\u002Fimages\u002Fdevices-in-pipelines.png",[13,9116,9117],{},"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.",{"title":39,"searchDepth":55,"depth":55,"links":9119},[],"FlowFuse's latest update: Devices can now integrate into DevOps Pipelines, enhancing management flexibility and efficiency",{"tags":9122},[64],"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines",{"title":9097,"description":9120},{"loc":9123},"changelog\u002F2023\u002F11\u002Fdevices-in-pipelines","VdU12n0GPoDLiDAxzvwOXh06TFRvLWKuXoFB6eD0-s4",{"id":9129,"title":9130,"authors":9131,"body":9132,"date":9061,"description":9153,"extension":59,"issues":70,"meta":9154,"navigation":65,"path":9156,"seo":9157,"sitemap":9158,"stem":9159,"subtitle":70,"__hash__":9160},"changelog\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices.md","Project Nodes for Devices",[8075],{"type":10,"value":9133,"toc":9151},[9134,9137],[13,9135,9136],{},"From today onwards, Project Nodes will now be available for devices assigned to an application. Previously, it was necessary for devices to be bound to an instance to utilize this functionality.",[251,9138,9139,9145],{},[254,9140,9141],{},[26,9142,9144],{"href":9143},"\u002Fdocs\u002Fuser\u002Fprojectnodes\u002F#flowfuse-project-nodes","Learn more about the Project nodes",[254,9146,9147],{},[26,9148,9150],{"href":9149},"\u002Fdocs\u002Fuser\u002Fconcepts\u002F#application","learn more about the difference between Instances, Devices, and Applications.",{"title":39,"searchDepth":55,"depth":55,"links":9152},[],"Project Nodes now available for devices assigned to applications in FlowFuse, improving functionality previously limited to instance-bound devices.",{"tags":9155},[64],"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices",{"title":9130,"description":9153},{"loc":9156},"changelog\u002F2023\u002F11\u002Fproject-nodes-devices","WJcqH2kc0x-4jCoJgD2Vpj1GO3mWb4mOMgnRw8p2JS4",{"id":9162,"title":9163,"authors":9164,"body":9165,"date":9197,"description":9198,"extension":59,"issues":70,"meta":9199,"navigation":65,"path":9201,"seo":9202,"sitemap":9203,"stem":9204,"subtitle":70,"__hash__":9205},"changelog\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes.md","Certified Nodes",[8075],{"type":10,"value":9166,"toc":9195},[9167,9170,9181,9189],[13,9168,9169],{},"Teams Tier customers can now leverage a curated selection of certfied Node-RED nodes, enhancing workflow efficiency and security.",[251,9171,9172,9175,9178],{},[254,9173,9174],{},"Quality Assurance: Each certified node undergoes testing, ensuring it's free from harmful components, aligning with our commitment to reliability.",[254,9176,9177],{},"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.",[254,9179,9180],{},"Support: Assistance for certified nodes is provided, aiming for, but not promising, issue resolution.",[13,9182,9183,9184,9188],{},"How? You can find all certified nodes in your Node-RED palette manager or on the\n",[26,9185,9187],{"href":9186},"\u002Fcertified-nodes\u002F","dedicated page"," on our website.",[13,9190,9191],{},[36,9192],{"alt":9193,"src":9194},"Certified Nodes Screenshot","\u002Fchangelog\u002F2023\u002F10\u002Fimages\u002Fcertified-nodes.png",{"title":39,"searchDepth":55,"depth":55,"links":9196},[],"2023-10-26","FlowFuse now offers certified nodes: tested with proactive security measures to ensure system integrity and reliability, enhancing workflow efficiency and security.",{"tags":9200},[64],"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes",{"title":9163,"description":9198},{"loc":9201},"changelog\u002F2023\u002F10\u002Fcertified-nodes","K28fuATRSzhgz3ZVrA0rv5Is83GnpJQDfODjX9WVcVg",{"id":9207,"title":9208,"authors":9209,"body":9210,"date":9197,"description":9221,"extension":59,"issues":9222,"meta":9224,"navigation":65,"path":9226,"seo":9227,"sitemap":9228,"stem":9229,"subtitle":70,"__hash__":9230},"changelog\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix.md","Device Agent path bug fix",[8075],{"type":10,"value":9211,"toc":9219},[9212],[13,9213,9214,9215,9218],{},"The Device Agent now passes the PATH environment variable to the Node-RED instances. Erroneously, the agent didn't capture it to expose to Node-RED again for usage. This prevented some nodes from being installed, like ",[86,9216,9217],{},"node-red-serial-port"," when assigned to an application.",{"title":39,"searchDepth":55,"depth":55,"links":9220},[],"Fix: Device Agent now correctly passes the PATH environment variable to Node-RED instances, resolving issues with some of node installation when assigned to applications",[9223],"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fdevice-agent\u002Fissues\u002F185",{"tags":9225},[64],"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix",{"title":9208,"description":9221},{"loc":9226},"changelog\u002F2023\u002F10\u002Fpath-bug-fix","ECNf3cwtPY9X6w-S2v9oTQPSyRKKgxymLSzqR3rNUiY",{"id":9232,"title":9233,"authors":9234,"body":9235,"date":9197,"description":9253,"extension":59,"issues":70,"meta":9254,"navigation":65,"path":9256,"seo":9257,"sitemap":9258,"stem":9259,"subtitle":70,"__hash__":9260},"changelog\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts.md","Resource Monitoring in Audit Log",[8075],{"type":10,"value":9236,"toc":9251},[9237,9245],[13,9238,9239,9240,9244],{},"In the FlowFuse Audit Log (see ",[26,9241,9057],{"href":9242,"rel":9243},"https:\u002F\u002Fflowfuse.com\u002Fdocs\u002Fuser\u002Flogs\u002F#audit-log",[30],")of an instance, it will now display when the resource utilization of CPU or memory exceeds 75% over a period of five minutes. This should provide transparency regarding resource utilization and serve as an indicator for choosing the appropriate instance size.",[13,9246,9247],{},[36,9248],{"alt":9249,"src":9250},"Audit Log Screenshot","\u002Fchangelog\u002F2023\u002F10\u002Fimages\u002FScreenshot-alert.png",{"title":39,"searchDepth":55,"depth":55,"links":9252},[],"FlowFuse Audit Log now monitors CPU and memory resource usage. Track instances exceeding 75% utilization over five minutes for better sizing decisions.",{"tags":9255},[64],"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts",{"title":9233,"description":9253},{"loc":9256},"changelog\u002F2023\u002F10\u002Fresource-alerts","-tkHdcM5sDA1R0fxbDz8wAa2z5qi_6JWsCT7Lmr5vNs",{"id":9262,"title":9263,"authors":9264,"body":9265,"date":9287,"description":9288,"extension":59,"issues":70,"meta":9289,"navigation":65,"path":9291,"seo":9292,"sitemap":9293,"stem":9294,"subtitle":70,"__hash__":9295},"changelog\u002Fchangelog\u002F2023\u002F10\u002Fblueprints.md","Blueprints",[8075],{"type":10,"value":9266,"toc":9285},[9267,9270,9276,9279],[13,9268,9269],{},"FlowFuse Blueprints are now available on FlowFuse Cloud and, upon request, for Teams and Enterprise Self-Hosted customers. Blueprints simplify Node-RED deployments by offering pre-built, customizable flows for specific use cases, thereby accelerating both new user onboarding and solution development for our seasoned users.",[13,9271,9272,9275],{},[26,9273,9274],{"href":8907},"Click here"," to learn more about Blueprints.",[13,9277,9278],{},"When creating a new instance, you can now also select a Blueprint.",[13,9280,9281],{},[36,9282],{"alt":9283,"src":9284},"Blueprint Screenshot","\u002Fchangelog\u002F2023\u002F10\u002Fimages\u002FScreenshot-Blueprints.png",{"title":39,"searchDepth":55,"depth":55,"links":9286},[],"2023-10-16","Explore FlowFuse Blueprints, Accelerate onboarding and solution development with customizable pre-built flows.",{"tags":9290},[64],"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"title":9263,"description":9288},{"loc":9291},"changelog\u002F2023\u002F10\u002Fblueprints","so2w3fiIC8gwWHJ4Q0LkE9YXly2YJJAJ8C_1SGixaXs",{"id":9297,"title":9298,"authors":9299,"body":9300,"date":9287,"description":9313,"extension":59,"issues":70,"meta":9314,"navigation":65,"path":9316,"seo":9317,"sitemap":9318,"stem":9319,"subtitle":70,"__hash__":9320},"changelog\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection.md","Enhanced Snapshot Selection",[8075],{"type":10,"value":9301,"toc":9311},[9302,9305],[13,9303,9304],{},"Users can now effortlessly deploy snapshots for devices assigned to an application through a new \"Deploy Snapshot\" button, available in the device's \"snapshots\" tab, thereby enhancing the workflow with the option to set either instance-owned or device-owned snapshots as the target.",[13,9306,9307],{},[36,9308],{"alt":9309,"src":9310},"Snapshot selection","\u002Fchangelog\u002F2023\u002F10\u002Fimages\u002FSnapshot-Selection.png",{"title":39,"searchDepth":55,"depth":55,"links":9312},[],"Explore enhanced snapshot deployment options for application-assigned devices with FlowFuse's new 'Deploy Snapshot' feature.",{"tags":9315},[64],"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection",{"title":9298,"description":9313},{"loc":9316},"changelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","wPXtqrXedyj7QFmXfS__H8AywJc8cGIIqU3ccIlz5Vc",{"id":9322,"title":9323,"authors":9324,"body":9325,"date":9341,"description":9342,"extension":59,"issues":70,"meta":9343,"navigation":65,"path":9345,"seo":9346,"sitemap":9347,"stem":9348,"subtitle":70,"__hash__":9349},"changelog\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support.md","Custom Node Support",[8075],{"type":10,"value":9326,"toc":9339},[9327,9330,9333],[13,9328,9329],{},"An often requested feature is support for custom nodes. Although Node-RED instances today connect automatically to the official Node-RED catalogue, which boasts over 4,400 custom nodes, we understand that specific use cases may require access to additional or different NPM registries and catalogues.",[13,9331,9332],{},"Starting today, you can extend your Node-RED environment by adding custom Node Catalogues. We have introduced the capability to modify the .npmrc file, allowing you to install modules that are not hosted in the official registry.",[13,9334,9335],{},[36,9336],{"alt":9337,"src":9338},"Settings Custom Node Support","\u002Fchangelog\u002F2023\u002F09\u002Fimages\u002Fcustom-node-support.png",{"title":39,"searchDepth":55,"depth":55,"links":9340},[],"2023-09-28","Flowfuse now supports custom Node Catalogues, letting you easily install modules from extra NPM registries to expand your Node-RED setup as needed.",{"tags":9344},[64],"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support",{"title":9323,"description":9342},{"loc":9345},"changelog\u002F2023\u002F09\u002Fcustom-node-support","b_wAYuH9MwswDhlxPwhdxrVDUzDja7rOhigc7OpidQA",{"id":9351,"title":9352,"authors":9353,"body":9354,"date":9341,"description":9367,"extension":59,"issues":70,"meta":9368,"navigation":65,"path":9370,"seo":9371,"sitemap":9372,"stem":9373,"subtitle":70,"__hash__":9374},"changelog\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions.md","DevOps Pipeline with action selection",[8075],{"type":10,"value":9355,"toc":9365},[9356,9359],[13,9357,9358],{},"Starting today, you can configure a deployment stage to create a new snapshot, always copy the latest snapshot, or prompt you for an action. This provides a more flexible approach to managing snapshots, enabling you to directly push created snapshots through the pipeline rather than being limited to the current image on Node-RED instances.",[13,9360,9361],{},[36,9362],{"alt":9363,"src":9364},"Action selection DevOps pipelines","\u002Fchangelog\u002F2023\u002F09\u002Fimages\u002Fselect-action.png",{"title":39,"searchDepth":55,"depth":55,"links":9366},[],"FlowFuse now supports action selection in DevOps pipelines, enabling flexible snapshot management by creating or copying snapshots, and pushing them through the pipeline.",{"tags":9369},[64],"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions",{"title":9352,"description":9367},{"loc":9370},"changelog\u002F2023\u002F09\u002Fdevops-actions","J_5nCWc6YRDcbYpvgSH7zEgr1_FYoEzia0IYJ7NTxiM",{"id":9376,"title":9377,"authors":9378,"body":9379,"date":9341,"description":9403,"extension":59,"issues":70,"meta":9404,"navigation":65,"path":9406,"seo":9407,"sitemap":9408,"stem":9409,"subtitle":70,"__hash__":9410},"changelog\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier.md","Introducing the Enterprise Tier",[8075],{"type":10,"value":9380,"toc":9401},[9381,9395],[13,9382,9383,9384,9387,9388,9387,9391,9394],{},"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 ",[150,9385,9386],{},"Team Settings"," -> ",[150,9389,9390],{},"Danger",[150,9392,9393],{},"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.",[13,9396,9397,9398,227],{},"Comprehensive details about the features included in each tier can be found on our ",[26,9399,8085],{"href":9400},"\u002Fpricing\u002F",{"title":39,"searchDepth":55,"depth":55,"links":9402},[],"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.",{"tags":9405},[64],"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier",{"title":9377,"description":9403},{"loc":9406},"changelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","B-xk8iFMgW_ti-I_kcnZCqOeYv6WgWuggHrfhX2Pr4U",{"id":9412,"title":9413,"authors":9414,"body":9415,"date":9341,"description":9426,"extension":59,"issues":70,"meta":9427,"navigation":65,"path":9429,"seo":9430,"sitemap":9431,"stem":9432,"subtitle":70,"__hash__":9433},"changelog\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api.md","API Endpoint for DevOps Pipeline",[8075],{"type":10,"value":9416,"toc":9424},[9417],[13,9418,9419,9420,227],{},"The execution of DevOps Pipelines is now an official API endpoint. Therefore, automation and integration, for example via Node-RED, are now possible. For more details, see our ",[26,9421,9423],{"href":9422},"\u002Fdocs\u002Fapi\u002F","API Documentation",{"title":39,"searchDepth":55,"depth":55,"links":9425},[],"Discover our new API endpoint for executing DevOps Pipelines, enabling automation and integration possibilities via Node-RED",{"tags":9428},[64],"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api",{"title":9413,"description":9426},{"loc":9429},"changelog\u002F2023\u002F09\u002Fpipeline-api","yti00NuKlW2J1GCSpRilW3kQ_Tc-e2xX5F86lL_gwyg",{"id":9435,"title":9436,"authors":9437,"body":9438,"date":9341,"description":9459,"extension":59,"issues":70,"meta":9460,"navigation":65,"path":9462,"seo":9463,"sitemap":9464,"stem":9465,"subtitle":70,"__hash__":9466},"changelog\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices.md","Usability improvements to Device Management",[8075],{"type":10,"value":9439,"toc":9457},[9440,9448,9451],[13,9441,9442,9443,9447],{},"Four weeks ago, we began working on several ",[26,9444,9446],{"href":9445},"\u002Fblog\u002F2023\u002F08\u002Fflowfuse-1-11-release\u002F#usability-improvements-to-device-management-%232294","usability improvements to our Device Management",". This included the ability to associate devices at the application level, allowing for easier editing of Node-RED instances on edge devices.",[13,9449,9450],{},"Starting today, it will also be possible to create and manage snapshots for those standalone devices.",[13,9452,9453],{},[36,9454],{"alt":9455,"src":9456},"Menu Snapshots for Devices","\u002Fchangelog\u002F2023\u002F09\u002Fimages\u002Fsnapshots-devices.png",{"title":39,"searchDepth":55,"depth":55,"links":9458},[],"Explore enhanced Device Management with application-level device association for simplified Node-RED editing on edge devices, plus new snapshot creation for standalone devices.",{"tags":9461},[64],"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices",{"title":9436,"description":9459},{"loc":9462},"changelog\u002F2023\u002F09\u002Fsnapshots-devices","9vIePrNJE7JxAJ4_6XCfoZcLYX9U-vaiwe56aBvSePk",1785508476274]