I have installed the Large version earlier but I have not checked yet however I would expect Venus updates to automatically chose the correct version based on the one running at the time of the update.
I fear that, by replacing Venus , it might have wiped out any additional software installed so I would have lost Node Red including all its additional components like extra nodes etc.
This version has been through about 80 updates to get where it is. It works.
That your system is flagged as modified is a clue that needs understanding. Please also confirm the hardware it is running on.
It downloads the version selected in the firmware download page âonline updatesâ so that setting can be different to what is installed. Best to have automatic updates disabled so you can check before you update that your selections ate correct.
1 Like
I appreciate the amount of work involved in creating such a new update and I can confirm that it did not wipe out my Node Red flows.
It looks as if I need to read about the update as I can see that so many things have changed.
Victronâs video only appeared to show the new Switch Pane.
Please, can you clarify what needs to be understood about the âmodifiedâ flag
What hardware are we talking about, the standard Victron or any additional external hardware related to Node-Red?
Thanks, yes everything is still there and, no, I donât have auto update on for this very reason but unfortunately i assumed that the fresher version would automatically match the previously installed one in every aspect, this is what happened before in other updates.
1 Like
Do you have a ccgx, cerbo gx, ekrano, venus;, raspberry Pi, or is an internal GX built into a multiplus GX?
I get you now, the system is all arranged with standard Victron moules as follows:
1x Cerbo GX with Display
1x Power in
1x Lynx Shunt 1000
1x Distributor
2x Multipluss II 5000 kv
2x 250/100 MPPT
2x 314A Battery Packs
1x 100A Battery
20x 415w Ground-Mounted PV modules adjustable 28Âș to 72Âș
The only external added device at the moment is a Digitaian Relay that controls a water heater via Node Red according to the battery SOC
Well, somebody has made changes to your system that are not part of a regular Venus OS install.
The Large image with Node Red does not get flagged as a modification, neither are Node Red flows you might be running.
What I suspect is that either you or somebody else installed an OS mod to integrate the Dingtian relay board so it gets recognized as âinternalâ relays by Venus OS.
If thatâs the case I donât think you really need that mod since you are driving the relays with MQTT.
Another possible mod is a CAN driver for your batteries, since you didnât specify the brand.
This might have happened when I was trying to establish USB connection with Arduino, something that was working at first but subsequently stopped. The aim was to obtain more digital outputs currently missing from Cerbo.
I followed some SSH instructions, difficult to know what was done but for sure it was around the USB Port-0.
I disconnected the Batteries CAN from Cerbo because of an intermittent problem with one of them which was halting the whole installation assuming that one battery cell was out of range; it was only a bad connection.
So this should not cause any problem since I reverted to MPPT / Lynx control and the batteries are protected by the BMSs.
The 100A battery never did communicate anyway and my two custom 304A and 314A both running on Seplos 10E BMS are fine even without CAN for the moment.
A soon as I have time to revisit the 304A wiring loom I shall reinstate the CAN communication, the issue hasnât been there for 12 months now.
Here she is when it was first commissioned 14 months ago:
Reflash the GX according to the procedures, or the setting in the integrations and reset section.
This is the source of your problem.
1 Like
When you say âreflashâ do you mean wipe everything from Cerbo and reload Venus?
I canât afford to loose all my settings, it would take me ages to make note of every page of settings assumed I donât forget some.
Which of these messages relate to what please? I have never seen them before the update 
Nothing is miss-behaving by the way . .
Am I to understand that this will only remove any error previously made in connection with the USB Port 0 and live all the rest including Node Red?
This would be an awesome feature since we havenât been given a full âcerbo setting saveâ implementation as yet
It is supposed to purge any non-Victron software/changes from the GX code and provide a clean operating system, with all your original settings still applied, including nodered.
1 Like
That sound good and I shall exercise it but it does non explain exactly how the system perceived a non-Victron software unless it is referring to potential modifications, btw suggested online, in order to give certain USB priorities to port 0.
I am referring to instructions like: âdmesg | grep ttyâ to verify â/dev/ttyUSB0â
Is this or something along the same line what could be intended as modifications?
Thanks again for your great helpđ
No, the system has detected changes to boot/startup files. So something has been edited or added.
Just running commands wonât cause this. I connect via SSH regularly, no issues.
That is interesting, so what on earth could have modified the integrity of Venus from the external world since I did nothing else?
Let me re-install as per instructions and only that will probably expose the offending item, assuming there ever was one.
There obviously is something off else your VRM large page would be working, so hopefully this fixes it.
1 Like
It seem to have cleared the mods message but it does not have Node-Red running so I suspect that it needs the âall modifications enabledâ turned to ON.
Can you confirm this please?
That should be on yes. By default it would be off.
You can then check that MQTT and Nodered, in the integrations menu, are still enabled.