It’s a long list: Venus OS v3.70~81 available for public testing
Hi @jkoljo , I have the exact same issue! Burned the main fuse trusting the setting in the peakshaving would work as expected. It did not, and now I read all over the Victron forum (and Tweakers) that this issue is known and not planned to be fixed.
@mpvader My installation is sitting idle when I can not actively monitor it. When the batteries are charging and the sun comes out I get this situation (example):
- L1 = 22A
- L2 = -10A
- L3 = -5A
Resulting a sum of just 7A, so peakshaving is ramping up the charge current with 15A to 22A+15A=37A. This is very dangerous behaviour and blew my main fuse. L1 should never ever exceed the limit setpoint in ESS.
I don’t want to rely on a Homeassistant or Node Red flow to prevent this. This needs to be handled by ESS on the Victron as per setting. Can you please look into a fix for this? The grid setpoint works perfectly fine, we only need a setting to limit the current for L1 in a 1xMP2 in 3-phase network.
Looking forward to get a fix for this. 
Thanks in advance for picking up this urgent matter.
2 Likes
A post was merged into an existing topic: Venus-os-v3-70-91 Node-red not working
Hi @User01,
Allow me to start by saying that it is not true that we don’t plan on fixing the issue. What I said was that it is not trivial (when you have a Multi only on L1), and that it will come later. I also could not reproduce the problem you reported.
With that said, quite some time was spent on this already, and there are fixes to peak shaving in the Venus 3.70 betas. I notice that your site still runs 3.67.
So the first thing to do, would be to try the beta. The beta also includes additional logging that will help future debugging, in case something does go wrong. That would go a long way towards helping find and resolve this issue.
As for the implementation details, there is never a time we will add up the currents as you wrote in bold. Whatever is going wrong is more subtle than that.