Max charge current is set depending on a variety of factors using NodeRed, and has been working flawlessly for months. I recently noticed that it stopped fluctuating as expected, and checked the code to see if it was still set correctly, as well as whether or not it made it into the "remote console" (in DVCC -> "Maximum charge current"). I also checked that there was no interference from the BMS, and that the current voltage wasn't close to any of the limits either.

When disabling the NodeRed code and setting the charge current manually in remote console, this didn't have an effect either.

Ultimately, since I couldn't make sense of the situation and none of the data I reviewed gave any explanation, I decided to restart the VE.Bus system which - as expected - returned things to normal.

The MPs are running firmware 498, I checked the changelog and it doesn't seem that there have been any changes pointing to what I'm describing above (except maybe for "miscellaneous changes"). Is anyone aware of a firmware change that would fix the issue I have described?
Thanks!

Im trying to get a persistent totaly energy produced (kWh) from my multiplus. Im using the node "ve.bus: Energy Inverter to AcIn1 (kWh)" rigth now, but that value resets on cerbor restart's.

does anyone know how to get this value?

ps: i want to build a graph which show my energy consumpttion (production + bought power) throughout the day in grafana. bought i have, production however ...

edit: fixed it myself ... i think :)

[image]

[image]

Hallo Liebe Community,

ich bin dabei mir eine PV-Anlage + ESS System mit Victron Energy Komponenten zu installieren.

Zum Einsatz kommen 3 Multiplus2 48/5000. Ausserdem gibt es DC gekoppelte PV Module und AC gekoppelte PV Module über einen Fronius WR. Das System soll vorerst Netzparallel installiert werden.

Ein Lastumschalter ist aber geplant um das Haus im Notfall umschalten zu können. (Hier wird aber die Umschaltung alleine sicher nicht reichen. Man wird wahrscheinlich das ganze ESS umprogrammieren müssen damit die MP2 wissen, dass das Haus jetzt auf AC-OUT hängt.)

Wir haben eine Wasser/Wasser Wärmepumpe die aktuell noch über einen separaten Zähler mit einem Wärmepumpen-Stromtarif betrieben wird. Hier ist der Umbau auf ein Kaskaden-Messkonzept geplant. Aufgrund des hohen Verbrauchs der Wärmepumpe in den Wintermonaten lohnt sich der 2 Zähler und Tarif sehr wahrscheinlich immer noch deutlich. Jetzt kommen wir zu meinem Problem bzw. meiner Frage.

Ich möchte u.a. in Abhängigkeit vom Akku-Speicherstand, und aktueller PV Leistung bestimmen können ob die Wärmepumpe mit aus dem ESS System versorgt werden soll oder nicht. Wenn ich im Winter nur noch 40% Speicherstand habe und keine Sonne in Sicht ist, möchte ich meinen Strom nicht für die Wärmepumpe verwenden und dann teureren Komfortstrom für die Versorgung in der Nacht aus dem Netz kaufen müssen.

Ich habe mal verschiene Schaltbilder angefertigt auf denen man den EM24 an verschiedenen Stellen montiert sieht.

[image]

[image]

[image]

Montiere ich den EM24 nach dem 1. Zähler dann werden alle Verbraucher (auch die Wärmepumpe) immer vom ESS ausgeglichen solang PV Strom oder Batterieladung vorhanden ist. Wird der EM24 nach dem 2. Zähler installiert dann wird immer nur der Komfortstrom ausgeglichen und ich kann die Wärmepumpe nicht aus dem Speicher bedienen auch wenn dieser komplett voll ist und am nächsten Tag die Sonne wieder scheinen soll. (eingespeister Überschuss wird natürlich für die Wärmepumpe verwendet aber es geht um die Stunden ohne Sonne oder wenn die gesammte PV Energie auch in den Akku geladen werden könnte anstatt der Einspeisung.)

Wie kann es gelingen, z.b. über NodeRed Routinen dieses Problem zu lösen? Evtl. über einen zusätzlichen ET340 im Wärmepumpenstrang? Eine Lösung wäre evtl. 2 EM24 zu installieren. Einen nach dem 1. und einen nach dem 2. Zähler. Evtl. könnte man dann über NodeRed bei den verschiedenen Status der Anlage enscheiden lassen welcher der beiden EM24 als Gridmeter aktiv ist. Dies würde aber sehr wahrscheinlich zu lasten des Logging im VRM Portal gehen und die korrekte Auswertbarkeit der Anlage zerstören?

Vielleicht gibt es aber auch eine ganz einfache Lösung über das VenusOS. Ich bin auf Eure Vorschläge gespannt.

Danke im voraus

Silvio

What am I trying to achieve?

Charge the battery, or discharge the battery based on external input (via MQTT, but ultimately based on variable electricity tariff status)

I am up and running in Node-Red on the Venus GX 'large' image and am able to set the Multiplus to the following modes;

[image]

However if I set the multiplus to 'charger only' it obviously won't charge if I'm not in a scheduled charge slot.

If I set up a scheduled charge slot to be active at all times, then I can charge / not charge on demand by setting the 'Disable Charge' flag to either 0 or 1.

[image]

However when in the 'don't charge' state, it also won't discharge the battery as I'm in a scheduled charging slot.

I've tried setting the AC power setpoint instead of charging within a scheduled charging time, but it doesn't seem to do anything if I try the following;

[image]

Can anyone offer any recommendations on how I can switch between charging or discharging to meet my requirement?

I have been delving more into node red to try make ESS a bit smarter particularly for those of us in areas with lots of loadshedding.

One of the use cases was for higher loads or poorer PV generation, where you want to top-up batteries faster but don't necessarily want to do that from grid.

I created a flow that allows you set an inverter limit, a target SOC and/or a timer where the limit will be active.

So you can choose to get to X SOC or however far it gets in Y hours and minutes.

After that it disables the limit and carries on.

I am debating adding a cron like scheduler so you can choose to set different limits at different times - work in progress.

[image]

Anyway. Flow attached, for anyone interested.

flows.json.zip

Hello - I am using a Multiplus GX with a pylontech battery stack.

I am collection the process data via the internal mqtt-broker from the gx unit - this values are used in different systems (influx, nodered, grafana, home assistant). My problem is, that the battery values (current, voltage, power) are sometimes corrupted (like a overflow). First I thought, that my data processing is doing "somthing wrong" - but I have broken it down to the internal broker and i can see (e.g. with mqtt-explorer) that the .json data from the multiplus seems to be wrong...

Attached you can see a screenshot of the described phenomenon.

[image]

It happens first with the 2.9X version of the venusOS - actually I have installed the 3.00-21 as beta to see if the behavior changes - it does not change.

I have although activated the VRM-Data (which was deactivated in the past) to see if I have the same strange data - no: the data in the VRM seems to be ok. I haven never ever get some warnings or alerts from the system, so I thing the internal values "inside" the multiplus are ok - but the mqtt data is definitely corrupted.

Perhaps an interesting bug - If anyone has an idea, what to do or to check: feel free to comment my question ;)

Dear All

I would like to "play" with some loads when I have available sun and do not wish the MTTP to throttle (idle).

My idea is to send any excess solar to the boiler element (depending on weather, temp, time, SOC, etc) and maybe a circulation pump. I was thinking, if during the day when the house is in "idle" any overrun from the MPPT can be directed to the element. Some sort of IFTTT concept.... if you know what I mean.

How would you go about this? I do not wish to be a burden on anyone, so if you have a good HOW TO START youtube video or ......, I would highly appreciate it as I can try to figure it out on my own.

I also assume that some sort of relay is necessary to activate the load (maybe AC2_out is an option)?

I have heard of NodeRed (not sure what it can do or what is necessary) and grafana but as stated I am not sure how to go about this. Do I need HomeAssist? or ..... for the Victron equipment?

I guess in the end, I would like to (almost) go for a smart home approach.

As stated above, any help would be appropriated.

Kind regards

Grid - tied (230V)

2 x MP2 5000

Smart shunt

MPPTs x 2

Lynx

GX cerbo

Hallo zusammen,

ich will über Node Red eine Ertragsprognose für den Folgetag realisieren und auf dieser Basis den Mindest-SOC schon am Abend setzen, damit der Akku nicht dauerhaft leergelutscht da steht.

Das BatteryLife gefällt mir nicht, da es ja nur im Nachgang regelt, nicht auf Wetterschwankungen schnell reagiert und der Akku u.U. mit Netzstrom auf einen höheren SOC geladen wird.

Globalstrahlung des Folgetages habe ich soweit von einem Wetterdienst ausgelesen, aber welche Einflussgrößen gibt es dann auf die Mindest-SOC? Ich stehe da derzeit ein wenig auf dem Schlauch, vielleicht wäre das ein interessantes Community-Projekt?

Hier wäre mein Flow zum Auslesen der Globalstrahlung des aktuellen und des Folgetages.

https://github.com/chr78/node-red-flows/blob/main/solarprognose.json

I am considering installing a 3 x 48/5000/70-50 multiplus 2 in 3 phase configuration (UK) with a large battery to enable profitable export to grid at times of high income. My understanding that this is difficult without NodeRed, but possible with NodeRed. Am I correct in this assumption? Further, does the NodeRed flow work with a 3 phase setup? I currently use NodeRed, but cannot play with the Victron flows as you need a physical inverter connected to the VenusOS to progress. Thanks in anticipation.

I'm operating a Multiplus 2 GX with activated Modbus TCP (see Picture 1). A separate Raspberry Pi which is running Node-Red connects to the Modbus/TCP endpoint. The modbus TCP connection is used to read information from the Multiplus and to control the ESS based on my dynamic energy tariff. While the communication itself works quite well, the connection to the Multiplus is unstable and breaks regularly (see Picture 2). To be able to reconnect I have to move the the modbus connection in the editor slightly and re-deploy in Node-Red. I've tried to optimize the connection settings (see Picture 3) towards the Multiplus but without any impact.

From my current perspective there is no reason for the instability. Within the VRM portal there are no connection issued and the state of the Multiplus is reported without data gaps or connection issues.

Picture 1

[image]

Picture 2

[image]

Picture 3

[image]

Dear all,

My installation consists of solar panels, Pylontech batteries, a Multiplus II, and a Solar Charger MPPT 450/100. This set is controlled by a CERBO GX. I have installed Venus Large and Node-RED.

I already control a hot water tank from a CERBO GX relay programmed with Node-RED.

I would also like to program the primary relay of the Multiplus II via Node-RED. I can do this with the Relay Assistant but cannot find it with Node-RED. Do you have an idea?

Jérôme

Ich hab einen Victron Multiplus-II GX (Firmware 2.92).

Dieser hat zwei Ports (AUX1 und AUX2) die eigentlich (wenn ich die verfügbaren Posts hier korrekt interpretiere) relativ frei verwendet werden können. Auf meinem MP2 ist nur ein Assistent installiert (ESS).

Ich hab das Large-Image mit aktivem Node-Red im Einsatz.

Im speziellen möchte ich einen externen, potentialfreien Kontakt über (z.B.) AUX2 in einer NodeRed Automation (Flow) verwenden. Ich will AUX2 also einfach als Digital-In verwenden (also z.B. AUX2 per Schalter auf GND legen).

Geht das? - Wenn ja wie?

As per the question title, I have Node-Red running on a Venus GX, it has been running just fine for over a year, I've been gradually adding functionality and it looks like something might have been messed up.

The flow is still running, I can see the results of the flow broadcast to my MQTT broker and logged on my dashboard - however I cannot open up the Node-Red flow in my browser. I've tried locally (http://192.168.86.XX:1880/) and via the VRM with the same result (perpetual loading, or sometimes the following stage: (even after left for >20 mins)

[image]

I've tried stopping and starting the Node-Red instance via the Remote Console, it successfully stops and starts it but doesn't help me access it.

Are there any solutions to fix? Ideally to access the stopped flow to make modifications to allow debugging. One thing I want to try is dramatically reduce the load in the flow by reducing message frequency, some of which are occuring far more frequently than needed.

I want to reduce the charge current from the Multiplus II based on SOC from smartshunt using NodeRec via Cerbo.

I have tried in NodeRed but cannot find a setting to change charge current.
Have anyone tried this?
I see that I can reduce charge current via an analog in and use an assistant in the MP, but this is not a desired solution.

Any advice?

[image]

I am working on installing a Multiplus II 48/5000 at my home, where I already have an on-grid photovoltaic inverter SMA Sunny Boy 4kW and I have some questions I haven't found answers anywhere:

1. Is it possible to install two Multiplus II inverters in series (one of them connected to the other critical loads output) with non-shared batteries? How should I configure them? That would enable me to add a new Multiplus II in the future with another new battery on grid-parallel mode connected to first Multiplus II critical loads output.

1.1 If 1. question is possible, should I configure second one to not exporting to grid? Or first one could use frequency shifting (or similar) to control how much energy could export the second one?

1.2 Continuation of 1.1 question. Would be possible to have SMA Sunny Boy 4kW connected to the same critical loads output than second Multiplus II, having both controlled by frequency shifting? Or that is not possible as maximum power would exceed Multiplus II maximum power?

It appears a similar configuration could be done by using CerboGX large firmware, to be able to use Node-red to control some inputs:
- first Multiplus II critical loads frequency (could be updated depending on first Multiplus II is able to receive more power from critical loads or it cannot accept many more
- first Multiplus II AC In grid status (availabe/not available)
And to be able to control some things:
- second Multiplus II power exportation limit, being configure to 0 power exporattion into second Multiplus II if grid on first Multiplus II is disconnected

I've seen some other questions about similar solutions, but they were trying to control batteries load between two Multiplus II at the same time at the same battery load. I'm not interested on that. What I'm looking for is to:
1. If second Multiplus II (with AC In connected to first Multiplus II critical loads AC OUT) has batteries fully loaded, then it will share power with the other one if the other requires it; if the other doesn't require it and external grid is connected, power could be exported to grid; and if the other doesn't require it and external grid is disconnected, 0 power export should be configured into second Multiplus II
2. If first Multiplus II (connected to grid and with second Multiplus II connected to it's critical loads AC OUT) has batteries fully loaded, if second Multiplus II requires power, first Multiplus II can provide that power as if it were coming from real grid