# Node-red-contrib-victron install disables entire instance

**URL:** <https://discourse.nodered.org/t/node-red-contrib-victron-install-disables-entire-instance/48671>\
**Category:** General\
**Created:** [20 July 2021 17:32 UTC](https://discourse.nodered.org/t/node-red-contrib-victron-install-disables-entire-instance/48671 "2021-07-20T17:32:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SeRiusRod](https://avatars.discourse-cdn.com/v4/letter/s/278dde/32.png) [@SeRiusRod](https://discourse.nodered.org/u/SeRiusRod)\
**Post date:** [20 July 2021 17:32 UTC](https://discourse.nodered.org/t/node-red-contrib-victron-install-disables-entire-instance/48671/1 "2021-07-20T17:32:22Z")

</div>

Installing node-red-contrib-victron messes the flows file because when the module installs it creates a configuration node, and every time it restarts, it creates another with the same name.  
Doing anything at this point just totally empties the flows file leaving you with a blank installation.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/e/eed87f9df93417622c7550c3f3917eaa65e627d3.png)

The developer has been notified on github months ago and they just ignore.  
Any plans to make node-red proof of this problem? How about banning the node from the repo until it gets fixed?

I don't know why node-red allows for creating a duplicate node at first time. Not to mention blanking the flows file instead of erasing the culprit nodes.

---

<div class="post-metadata">

**Author:** ![dirkjanfaber](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dirkjanfaber/32/46291_2.png) [@dirkjanfaber](https://discourse.nodered.org/u/dirkjanfaber)\
**Post date:** [12 August 2021 08:33 UTC](https://discourse.nodered.org/t/node-red-contrib-victron-install-disables-entire-instance/48671/2 "2021-08-12T08:33:38Z")

</div>

Hello SeRiusRod,

The node had been updated in [this fix](https://github.com/victronenergy/node-red-contrib-victron/commit/04724dd78754b86d48ce9140ff4ca051b67e9b69). And a new 1.4.1 release was made.  
Even though the latest released version is 1.4.1, the website [Library - Node-RED](https://flows.nodered.org/search?term=victron) still showed version 1.3.2.  
I've clicked the "check for update" on that page and it now finds the 1.4.1 version. It will probably take a few more hours before all caches are updated and you can update the npm package from the palette.

Best regards,  
Dirk-Jan

---

<div class="post-metadata">

**Author:** ![SeRiusRod](https://avatars.discourse-cdn.com/v4/letter/s/278dde/32.png) [@SeRiusRod](https://discourse.nodered.org/u/SeRiusRod)\
**Post date:** [20 August 2021 15:37 UTC](https://discourse.nodered.org/t/node-red-contrib-victron-install-disables-entire-instance/48671/3 "2021-08-20T15:37:27Z")

</div>

Thanks Dirk-Jan, and I apologize for a late response.  
As you said, I've tried again the install and the new version made his way. Since then I've had no issue and I can use the integration with Victron.  
I'm currently making an energy diverter to charge my car with it.  
Thanks again.

---

<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:** [3 September 2021 15:37 UTC](https://discourse.nodered.org/t/node-red-contrib-victron-install-disables-entire-instance/48671/4 "2021-09-03T15:37:59Z")

</div>

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