# Victron node-RED asset management

**URL:** <https://discourse.nodered.org/t/victron-node-red-asset-management/85817>\
**Category:** General\
**Created:** [23 February 2024 14:18 UTC](https://discourse.nodered.org/t/victron-node-red-asset-management/85817 "2024-02-23T14:18:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![martinKraft](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/martinkraft/32/88586_2.png) [@martinKraft](https://discourse.nodered.org/u/martinKraft)\
**Post date:** [23 February 2024 14:18 UTC](https://discourse.nodered.org/t/victron-node-red-asset-management/85817/1 "2024-02-23T14:18:32Z")

</div>

Hello, I represent a company where we have about 100+ sites with victron systems. These have the VENUS OS Large, enabling modification of hardware behaviour using node-RED flows. Each site has the same few flows, and there is unlikely to become much difference between the flows for each site in the future.

It is infeasible for us to update and maintain the flows by manually accessing the node-RED instance at each individual site. Is anyone here familiar with a system for asset management allowing simpler maintenance of several assets using node-RED?

Thank you!

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 February 2024 14:38 UTC](https://discourse.nodered.org/t/victron-node-red-asset-management/85817/2 "2024-02-23T14:38:29Z")

</div>

Hi, i work for [FlowFuse](http://flowfuse.com), this is exactly what our product does. Have a look and a play, especially the "devices", "device groups" "device remote editor" and "pipelines" features.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [23 February 2024 17:42 UTC](https://discourse.nodered.org/t/victron-node-red-asset-management/85817/3 "2024-02-23T17:42:32Z")

</div>

Not used those systems so this is a generic answer. I would normally look to something like Ansible if I wanted multi-device configuration on UNIX-like OS's.

> **[Ansible is Simple IT Automation](https://www.ansible.com)**
>
> Ansible is the simplest way to automate apps and IT infrastructure. Application Deployment + Configuration Management + Continuous Delivery.

---

<div class="post-metadata">

**Author:** ![rxw](https://avatars.discourse-cdn.com/v4/letter/r/c77e96/32.png) [@rxw](https://discourse.nodered.org/u/rxw)\
**Post date:** [24 February 2024 17:15 UTC](https://discourse.nodered.org/t/victron-node-red-asset-management/85817/4 "2024-02-24T17:15:59Z")

</div>

Hi, I would you combination of versioning system (git) and some kind of automation tool (e.g. suggested Ansible) to manage NodeRED instance on Cerbo devices.

Let me know if you need more details how to do it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [24 May 2024 17:16 UTC](https://discourse.nodered.org/t/victron-node-red-asset-management/85817/5 "2024-05-24T17:16:34Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.