I updated my Cerbo GX to 3.70~60, and I noticed that this Node‑RED flow no longer works.
In Node‑RED I used to write to Venus Settings → ESS → BatteryLife State.
But in this beta version, that entry is no longer in the list.
I would inject either 10 or 9 (“Keep batteries charged”) to force the battery to charge or to switch back to normal operation.
I stil can read ESS state as showed on picture. ESS BatteryLive state writing is missing. 
Hi all
I have a heat pump running as EVCS on vrm now, to be able to see its values as a block in the overview. While that’s great, I discovered, that there is also a role “heat pump” available.
Switched to the role and the heat pump does not have it’s own block anymore, it’s integrated into the AC load block…
is this by intention and could the be changed, or at least is it possible to introduce a switch if we want to display it as it’s own block?
Thank you
Hey all, thanks - again - for all the feedback.
This is a short heads up: Saturday, tomorrow morning we’ll make a v3.67-beta available for testing.
So. If you don’t want to loose the current beta features that are part of v3.70-beta, then you need to disable the auto updates.
I’ll post all the details tomorrow!
Matthijs
I totally agree on this. On the small screen the block size of the EVCS takes to much space (because of not so relevant information). Therefore block sizes like DC Loads, External Loads, and AC Loads shrink and the font becomes to small (I need my glasses to read it). While some information in the EVCS block are not so relevant (like charged time and total energy) and can be found 1 click away (just click the EVCS box).
Not sure how long this issue is present, I have just noticed it now since I usually don’t need to limit charge current, however, when I enable Limited Charge current in DVCC, the set value does not match the actual value.
For example when I set the maximum charge current to 100A, I only get about 60A. If I then increase the maximum charge current to 150A, I get about 90A:
With 150A in DVCC:
You can ignore the 100% SOC as I am currently testing and my batteries are only at 80%.
I use a Victron Lynx Shunt for measuring Amps going into the battery (the JK BMS reports the same amps).
For some season, the actual charge current is only about 60% of the set value.
My system consist of 3x Multi RS 6000 (3 fase), 136kWh battery bank. Venus OS 3.70~60
Good morning!
Per yesterday we have released Venus OS v3.67. As always: thank you for all feedback and support on that one!
And per just now, v3.70 is back in beta, v3.70~61 to be specific. I’ll update the change log a bit later today.
Have a good day, Matthijs
There is a bug in Solar Charger node in Node Red.
The node is configured to read Relay state from Smart Solar 250/80 TR VE.Can - only changes.
Relay on mppt is configured to “Day detection (panels irradiated)” mode.
The node should send 0 or 1 in related conditions, but sometimes it sends null.
It happens at least once a day with any connection to real panels irradiation.
Now I am on Venus 3.70 ~60. The same issue was also noticed in all 3.6X as I remember.
Before 3.6 the same flow was working like a charm.
I attached a picture with all required information and debug log.
P.S. I couldn’t find the cause of the errors in my flow for a long time, and today it happens!
Sure I have filtered this null in my flow but buggy node with unexpected message content is not so good deal.
thank you for the report! we’ll look into this.
I’m running v3.70-60
I can’t see virtual switches (node-red) or Shelly devices on vrm.
Is this a known issue or am I doing something wrong?
I was using 3.70~61. Yesterday I noticed that the grid meter lost alarm did not function anymore. The system also does not switch to Passthru anymore. Today I reverted to 3.67 and removing the USB-385 cable gives expected behavior. I guess an old bug (solved in ~28) was reintroduced.
BTW I will replace my EM340 for a EM24 hoping to get rid of regular grid meter lost events.
There seems to be an issue with limiting system import current in the latest 3.70-61. If I remember right, I have also run into this issue before on some earlier builds.
I have a 3PH system with 1x MP2 on L1, parallel to loads. Nothing on MP2 output. Grid is measured by VM-3P75CT. Multiphase regulation is of course enabled. Limit import current (per phase) appears to not be per phase, but actually combines phase currents in its calculations.
As an example, if I set it to 50A as not to limit anything, DESS charges my house battery on L1 with full speed. EV on L3.
Then if I set it to more realistic 20A per phase, we see an issue. Btw 20A is just a demo. I have 25A fuses and that is what I would like to use as limit.
As you can see, the 20A per phase limiter got applied as total phase currents sum limit. Charging on L1 is almost stopped. If I set the limit even lower, it actually starts to feedin to compensate for consumption on other phases.
Or is there some other way I should set up a phase current limit such that main fuses are not burned by MP2 charging when there are other loads (for example 3PH EV charging)?
Not sure if this was mentioned already, but after updating from the stable release to the beta one, I’m seeing white margins around the remote console on my iPad. The remote console no longer fills the entire screen. These margins are displayed in both Safari and Chrome. I’m pretty sure there were no such margins in the stable version.
Hi @robmeerwijk ,
The system not going to passthru anymore is deliberate. We changed it so that when the meter is lost, it will use the internal current sensor instead, and keep operating. This is mostly because going to passthru disables peak shaving, and that is not a good thing in some systems.
The grid meter lost should still raise a warning though. I will look into that.
Hi @jkoljo, in your installation, having one Multi installed on a three phase system; peak shaving indeed doesn’t work.
And also there is no plan to make that work. What we have to do though is to at least make that clear in UI and documentation; which we’ll take care of.
It does work with the Multi RS, but that is not going to help you.
This is the best I can offer I’m afraid.
Hi @Outward6027 , that’s known.
The only way to access them - at the moment - is by opening Remote Console (New UI).
Eventually there will be a direct access as well.
noted! thanks.
#vp–616
Hi @wolferl ,
I understand how that would be nicer for you. However, for now this is how its intended to be. We might revisit when something becomes its own block but not right now.
Hi @EDSTOBI , thanks for the report, we’ll look into that.
Hi Matthijs, thank you for your reply. I don’t really need a feature that would protect my main fuses when something else than Victron stuff is consuming too much. The MP2 doesn’t have to export to peak shave. However, currently my MP2 can and will burn a main fuse when my 3ph EV is charging at night, if DESS decides to charge as well. I need to have something to prevent that. What would be the preferred method?
I already have an expensive VM-3P75CT monitoring the entire house consumption, so I think using it + some Victron control/setting is the way to go. If grid import limits are really not available or even planned, are there other ways to accomplish this?
I suppose one half ugly patch solution would be to use some Victron MQTT channel to limit MP2 consumption when EV charger is running. This could be done by Home Assistant. Which channel would you recommend, perhaps DVCC charge current limit or even the grid current limit? Thank you.
I doubt I am the only one with 3ph EV charger and an MP2 based battery system, so surely someone else has ran/will run into this issue as well?
