Batch/bulk edits VRM

Hello,

I have a few hundred victron installations. I want to add the same alarm rule for all of them. Is there a way to do this in a bulk edit? Tedious to add alarms for all of them individually.

Hi There,

I just discovered your question on fleet management + Node-RED over at the archive.

@dfaber mentioned FlowHub.org which I happened to have created and maintain! I created it for my personal use case of managing multiple Node-RED flows across multiple instances, I have no idea what your use-case is or how a Victron device works (new here in the forum) so it might not do what you need.

Back in March (when the original question was posed) FlowHub was quite difficult to use (as a non-me person ;)) - I have spent much time to make it as simple as possible. It is now possible to integrate FlowHub into NodeRED by authorising the Node-RED GitHub App.

Hope it helps and for questions, just DM me here.

Hey, perhaps you could help me understand how flowhub could help us? We are managing several 100s of victron installations across the world. We have begun to use node-red on some of them. We want an easy way to see what flows (and versions of flows) are deployed where, and to be able to mass deploy flows across a large set of our installations. From the information you shared, I couldn’t see whether flowhub supports that.

Hi Martin,

FlowHub is flow oriented meaning it manages flow tabs and not strictly collection of flows, i.e., flows.json. It does however allow for creating “meta” flows that reference other flows through the FlowHubPull node. This allows for the definition of flows that define which flows are to be installed on a remote Node-RED installation.

Something that is demonstrated by the deployment flow example. What that flow does is create a flows.json from a collection of individual flows. In addition, package dependencies are collected and packages are installed on the remote Node-RED installation before installing the flows.json on the remote Node-RED installation. Thus ensuring that Node-RED has all prerequisites for executing the generated flows.json.

That meta flow is also a flow which is, in turn, managed by FlowHub. That’s the approach FlowHub would take to maintaining a collection of Node-RED installations. Each installation would have a meta flow defining the required flows and each referenced flow would also be maintained in FlowHub.

All flows managed by FlowHub are stored in a GitHub repository and is versioned with each modification. This workflow is fully integrated within Node-RED using the FlowHub node package.

Hope that answers your question, if not, please ask :slight_smile: