Multiplus shows Low Battery warning and won't turn on. 

I wake up every morning with my hot coffee ☕ looking forward to Andy's videos of the day..

Hi Andy, I had the exact same problem about a month ago. The firmware used was 498. Unfortunately, to this day I don't know why the Multiplus didn't start converting again.... Thanks as always for the great video!

Andy pls consider making a follow up Video on this ... keen to know the final outcome ... thanks A

Yesss a new video!

Thanks Andy 🤔 🎄

Effectivement c'est intriguant ! merci du partage ANDY's.👍

Ι am kind of happy you had this problem because it happened to my 24/3000 phoenix smart and i tried to find a solution for 4 months with no luck. at the beginning it would restart after a few minutes or hours but in the end it was unable to restart, automatically or manually. I send it buck to offgridtech in germany, a victron reseller and guess what? "There is nothing wrong with your inverter, it works fine." They did replace it though. That was even more frustrating . So now I hope I will get some answers from the smart Australian guy on you tube. Good luck and thanks for your videos.

Hi Andy. I had that issue several times. Unfortunately I did not have the luxury of time to carry out a proper troubleshooting. Just jump off straight to turn it off and back up again, that is physically in the workshop. Fixed the issue every time, but defeats the purpose of a reliable system as you have to be there! I put it into the “bug category” for now. Cheers, Raz PS My inverter is Multiplus II 24V/5000/120

Hi Andy I made a test on my 3 phase Victron Mulitplus 2 System. Firmeware 500 installed. All 3 inverters switch off by 37 Volt and start simultan a soon the DC voltage is back over 43 Volt. Works perfekt without a Issue. Regards from Switzerland Samuel

Hello Andy, please check the assistents that you use. For example the ESS Assistent uses his own parameters of voltages.

Thank you for sharing this. It is probably good signal to do not upgrade firmware if everything is just works well.

Hi Andy, great video but a question comes to my mind. What happens to the MP when the BMS switches off under full load? Can this destroy the inverter?

Updated all my three 3000 MPII to firmware 500 three hours ago. I really hope it's not buggy , up to now I have no Problems. Please keep us informed.

I've had the same experience with the ID. Also, I've had quirky low battery alarms when I remove the battery's can bus. Although the settings of the multi are ok, it behaves very strangely without a CAN connection.

Found a SPAT today! Emptied it ready for inspections.

Crazy event. Worth it to run test again to see if it repeats. Did you ever put a voltmeter on the battery cables coming into M+? Keep us posted. Thanks for sharing.

that's a great video... you have a solar dream garage, it has a lot of love in that installation and components used

Hi Andy, all, great video and info as all of yours, many thanks! interesting update fresh from this morning (2023-11-07). Had low batt error, too. being offside, VRM portal only. running V506 on MPII. (V3.12 on Cerbo) as known, MPII does not reset lowbatt automatically. Remote console and switching off/on again didn't help. BUT: used the VRM switch for same off-on and guess what? the error is not shown anymore.. Off-On seems different from VRM portal, than from remote console. But managed to get rid off the error remotely, finally. BR Joerg

I had the same problem once. It was a blown fuse but stil in contact to draw a lillte current. After replacing to a new fuse it works again. The active alarm needs to be acknowledged on the three dots in the alarm log on the VRM portal.

Hello ! I have the same problem as you with my 2 multiplus II. They work in parralel and charge a 15kwh Seplos battery. Sometimes i have to reset the multi' a few times until it runs againd as it should. And it only happens at night when the battery drops to around 80% state of charge.

Isn't there a setting you need to activate to power on after alarm? Auto restart something like that in config software

Hi Andy Since a firmware-update wipes ALL previous settings, I would say, you will have to reset EVERYTHING and it will continue working. If you really want to update your MP2 (Victron recommends not to), you should save all the settings before and play them back after the update. I once had a similar problem and looked it up in the same column like you, just where you expect it: "Inverter" (showing in your video at 4:45). But that was wrong. This is meant for the TOTAL shut down of the MP2. You can use "Victron connect" and check the column "AC-Input ... something". It is called "AC-Eingangssteuerung", so I don't know what the exact wording in your system is, but it should be "AC-Input-regulation" or similar. There you will find the values which tell the MP2 when to stop inverting and when to start again. Watching your channel from germany and really like your sense of humor! All the best!

Andy I have the same problem, did you find the answer?

You should try to go in the Cerbo (or rasperri pi) to the "notifications" and acknowledge clicking the "V" at the bottom

Reset the inverter maybe Andy? I got home yesterday with a problem as well. Very sucky to have to work on it at 5 pm.

Interesting. I am using a non Victron inverter which does also have this issue, I have to power cycle the inverter. I wonder if there is a setting somewhere for both of us to recover from low voltage alarms?

Andy, did you reupload the VE.Configure settings after the firmware update? I have seen strange things after updating the firmware and not updating the settings.

Hi Andy, have experienced the exact same issues, running two Multiplus same as yours, one a master and the other a slave. Also started after the upgrade to the 500 firmware mine started with errors, on the date I upgraded on the 6th or 7th Dec. I upgraded from V497 to V500. Started with High voltage errors and then Low battery errors. Now as soon as my Fronius inverter kicks in and reaches a certain number of watts the Multiplus will trip. How do you revert beck to V497 firmware. Anything to get my system back to normal. Neglected to mention am running two Pylotntech UP5000 batteries, total of 9.6 Kw/h. Thanks

I have a new rack battery and see where others are complaining about the MP II doing a low battery disconnect and the battery people have said to have the people check with Victron. ... I can't ever get a reply from Victron and I have been wanting to go into being a Victron installer ... anyway. I have yet to connect up the Muliplus II though 12V ... but I did have some issues and think I found out ... my readings and current settings in the smart shunt needed recalibration with known full charge. I did have an error of the rack not turning on with things connected but to fix it I connected the wall wart Victron charger and the rack would stay lit. ... I appreciate the approach here to figure the solution/problems and not just go off on a tirade rabbit trail.

Could it be the the RsPi renumbers the USB interfaces ? Have not seen this Behaivior und Cerbo's or Color Controls.

yes exactly same problem with updated firmware , the id number changing is interesting ?

Yeah, similiar wondering here also with MPII. Running bit older firmware (can't remember). But yeah, I have sometimes bigger surge of power and battery voltage goes low and alarm comes. Then what is pretty weird... like Andy show in video. When voltage goes back to up, over the "low voltage" treshold values (what has been configured into MPII) ... the alarm stays and sometimes a long time. It just uses grid loooong time, even the battery voltage is back to normal level. I kind of understand some sort of an victron logic here (under heavy spike/loads), that it cannot start to ping / pong with low voltage, turn off battery -> grid -> batt voltage comes back -> grid off -> voltage drops... and repeat this. But what I would like to know from Victron.... * what exact logic is behind clearing out low voltage warning * Why it sometimes takes ages, and sometimes never come back to normal (despite batt voltage and SOC is ok).... Great stuff Andy, hope you/we can get some answers from Victron.

Hallo Andy, Great channel you have here and very informative especially for a noob like me. I just wanted raise a suggestion for the next time this issue might occur. I have had one of my systems shut down on low voltage on a couple of occasions simply because .. well.. the voltage was low.. Winter time here in the Netherlands and several overcast rainy days in a row so the math wasn't that difficult. On most occasions the system started up again as soon as charging started but with some loads higher than the charging amount starting also the system shut down again as soon as the voltage became too low again. On one occasion the MS didn't restart only until I acknowledged the alarm in the remote console, local. The circled V at the footer of the alarm page. I noticed in your video that you didn't acknowledge and that the alarm was still active before you restarted the MS. At least it appeared that way. Could this have been a similar situation? Your advanced widgets didn't really show auto restarts before it remained off line. Please keep up the good work! Alles gute, Johann

Hi Andy, When I installed v500 I had to reconfigure everything in VEconfigure, as per usual when I update firmware. Also note I usually can't use a previously saved VEconfig file, I need to make a new one. DId you check the DC shutdown and alarm setting with VEconfig in the MPII?

Thanks to you i bought my first Victron. bad luck for me it seems to be faulty piece. The item is a Victron 100/30 Smartsolar. Yesterday I connected the battery to it, correct polarization. The terminal sparked, the lights flashed and went out. It only turns on when I connect voltage to the PV output. As it's my first Victron, I thought I might have done something wrong, but I checked and we really should always connect the battery first. Any golden tips?

Yes And its a problem when I put my Multi off and do not realized, that 49.9 V is to low and MPPT in the morning and all day gives only 30 - 50 W from 7000 Wp. So it was dark too.

I had the same problem after installing the ESS assistant. I tried all of the suggestions mentioned above, to no avail. Realising that the problem was likely connected to installing the ESS assistant, I compared the new ESS enabled file with the previous file and noticed that in the new ESS enabled file I had checked ‘enable battery monitor’ in the general tab. I unchecked it and uploaded the modified file - problem solved, no low battery alarm on the Multi. I have a pair of pylontech 5000 batteries which have their own BMS, presumably there was some sort of conflict. Obviously not relevant to your setup Andy, but it underlines what a minefield VE config is!

Andy. Sometimes the Firmware/software gets hung up and the only thing you can do is completely power down the system,remove the DC, wait for it to totally discharge and restart. Remember the precharge resistor. Now go back and look at all your settings to make sure they are yours and not the defaults. Yes, you are correct, you need to do a repeat of the scenario to make sure it doesn’t repeat. It should restart automatically and it should never change it’s address on its own. I’ve found with a lot of devices that after updating software, it’s always a good idea to completely shut down (zero power) and reboot. I sure hope that’s all it was.

is it possibleto run the systems without updates or you cant avoid it ? i might go no internet connection after instal.. only occasionally if need for serious situations

This bit me the same way. I have a BMV-712 shunt and when I tried to add the louisvdw serial-battery to forward the JKBMS measurements to the GX it triggers the low battery alarm that does not go away. After three alarms I had to restart the MP2s (3-phase) with a power-out of the house 😒(the MP2 being my UPS, yet for this reason useless as an UPS). Once I got both BMV712 and JKBMS measuring at the same time (over bluetooth or rs485), it is possible to reset the LBV-alarm by changing the "System setup" -> "Battery monitor" away from the BMV712 to the JKBMS and clear the alarm in the VRM. The bug seems to be in the Victron "serial-starter" handling that tries to reassign the ttyUSB devices and the BMV-712 gets briefly disconnected and forces the MP2 to go in the alarm state (probably thinks the battery dropped out), even if "VE.Bus DC Voltage and Current" log does not show anything but normal voltages. I'm now trying @Nico's suggestion to disable the MP2 "Alarm setup" to ignore the "VE.Bus error". The device ID [289] changes often when the RPI GX is booted. I have to reboot it one or more times, to get it back to the original [289] and keep the logs going.

My issue with MP2: I have 3x MP3 for 3F. When MP3 discharging from battery, two MP3 invert from battery, but one doesn't want to. Has anyone any idea why? Any clue what could we check?

never change a running system! victron wrote „It is not required to keep your Victron equipment updated to the latest firmware version. Stable systems should be left with their current firmware“

From 12.15 to 13.30 on your screen you have the warning, al, you had to do, is to acknowledge it by clicking on the tick on bottom bar, then alarm disappears if values are within parameters. Or, on the 3dots in the VRM, once you acknowledge the lv alarm, it resets, and MP resumes.

Suggest you read configuration and check settings then re-write. There have been some changes between firmware updates recently and you have to do this if it is not done automatically to migrate your settings to the new parameters. If you don’t settings are set to default and can throw some things out

Hi Andy - Do you have an ESS (Energy Storage System) Assistant configured ? I was having unexplained VE BUS Low Voltage errors and random disconnects from my SEPLOS Battery, and found that it was related to the Victron ESS Dynamic Cut Off Config defaults. After tuning these values, I'm no longer getting disconnects (nor the VE BUS errors). Note that when Dynamic Cut-Off is used (which is a default), the "DC Input Low Shut-Down" Related parameters in VEConfigure are ignored.

Hi Andy, this seems to be business as usual. Have had a similar experience with my MP II`s a bunch of times: 
whenever a low battery event occurs, the MP II stops working, sets an vrm alarm message and turns a red light on (Low battery)
 It will never awake from this, remain in that state, to make sure your complete system is in a safe condition and you recocnize the problem. So first check the whole system state and clear the reason of the fault. 
Then turn off the MP II, (wait a moment) and clear the alarm (the active alarm needs to be acknowledged on the three dots in the alarm log on the VRM portal)
 After turning on the MP II again, it will just work fine as usual.
 This seems to be a security procedure to save your system. By the way: after fw update, your device ist set to the defaut settings again. You have to reconfigure it and you can not use the old configuration file from the past (before update), you have to create a new configuration file now. (so don´t look to the values of the old file. Download the actually one and have a look to this settings) You also might setup the generator-assistent for the Phoenixinverter again

It may be unrelated but I have created some of those generic usb to ve-direct cables for using with a raspberry pi and I found them quite flaky. I swapped for genuine Victron cables and had no issues.

Hi Andy, I had a similar experience with a MP2 12/3000. In the VE config I had the "shut down on SOC" ticked, in the inverter section, which would shut the inverter down after a decent load. Since the inverter does its own calculation of SOC based on usage and battery information, I decided to disable the "battery monitor" in the general section. Didn't have any issues after those changes. Hope this helps!

Andy, do what I do and run your wifi router off a DC power source - a cheap 5A 48v to 12v buck converter will mean you have wifi right up until the Battery shuts down.

hi i had the same issue right now - can you post the link of the posted problem in the victron community? is there a solution to that? thx a lot markus

I had something similar with an error 'Low battery Voltage' and had to turn off and on the multiplus. That happened when my raspberry went down during a restart of my system. The multiplus couldn't get the battery voltage from can bus on the raspberry and wen in 'Low battery" mode and off. My solution was to disable "VE.Bus error" in Device List>Multiplus>Alarm Setup. That way, if for any reason the multiplus can't communicate with the can bus because of a VE.Bus error, it does not go anymore in 'Low battery Voltage' error. But you didn't seem to have a VE.Bus error. I'm not sure it help, but i'm going to keep disabled the VE.bus error, because like you, I want the multiplus to be always on, even if it loose the battery or the raspberry (i'm grid tied with ESS). I had as well a different id for the multiplus and it went back to the same id. I never understood why!

The inverter shutting down is a low-stress event on the inverter. Just like any inverter, it is easy for it to simply stop pumping voltage without stressing components. The BMS's shutting down, however, is a high-stress event if maximum amps are running through it. In this case maximum amps were not running through the BMS, but it is something to think about. BMS's tend to blow MOSFETs when they try to shutdown while a lot of power is flowing through them (see explanation at the end of why this can happen). For the DC paths, similarly, if the BMS would otherwise be pulling in excess of 50% during a shutdown event, it might be better to have a sacrificial low-voltage shutdown that operates before the BMS would otherwise kick-in. Saving the BMS to truly be a last resort. In prior years not having internet during a power failure really bugged me. To the point where I now have power stations backing up my cable modem, wifi routers, and home server and switches. I use a little GoLabs in the garage for the cable modem since it only pulls 5W (direct DC connection, the GoLabs power stations have a bug where the AC shuts off after 8 hours of unattended operation). And I have two Oukitel P2001's backing up the security system, WIFI routers, home servers, and workstation. The two POE+ wifi routers burn around 20W in total. And one more for the fridge, soon. However, every power station has its warts... I've almost given up even buying them anymore :-(. The Oukitel is no exception. Its firmware has a bug where the fan does not turn off soon-enough and that causes the AC to drop-out every once in a while. I had to hack the temperature sensor (added another resistor in parallel) to force the trigger temps to be lower to fix it. And the Oukitel... it has a great UPS mode, but the idiots also reversed the HOT and the NEUTRAL lines on the AC output and don't connect the GROUND line through. Sigh. Still, it works for the equipment it is connected to. -- Physics explanation of why BMS's sometimes blow up their MOSFETs when they shut-down during high loads, but not during low loads. A certain amount of charge must be injected into or pulled out of the gate of a MOSFET to turn it on or off. However, the amount of charge required increases significantly while current is flowing through a turned-on MOSFET. BMS makers often do not provide enough drive current (particularly when driving many MOSFETs from a single MOSFET driver). So when the BMS tries to shutdown while a lot of current is flowing through the MOSFET, it winds up happening very slowly and it actually puts the MOSFETs into their linear region for too long a period of time which causes them to act like a transistor and directly dissipate the difference while turning off. In addition, the gate voltage trigger points for each MOSFET will be significantly different, so during a shutdown not all the MOSFETs will turn off at the same time. This combination can easily blow up one or more MOSFETs. The solution is to ensure suffiicient gate drive for all the MOSFETs such that they shutdown as quickly as possible. But this is expensive so BMS makers often cost-cut the gate drive. And BOOM. Hence why relying on the BMS for your first line of defense in a low-voltage shutdown situation is not a good idea just in terms of good practices. -Matt

Similar experience with my Phoenix Inverters. I had a miscalculation of the Smart Shunt and the BMS disconnected the Battery at night. My Phoenix inverter get in error state and wont turn on until i disconnect it from the input Power for ~3min.

Did you ever explain this fault Andy ? Am having similar issues with a brand new Quatto-II. Shuts down with "Low Battery" and stays shutdown, but only when I have the MK3 plugged in. Mmmmm

Hi Andy, I had exactly the same problem about 6 months ago. Firmware upgrage then the Victron control of the batteries was useless for a month till I got an engineer out to reset the firmware. Initially that didn't work and he spent the whole day her talking to Victron. He got it working in a fashion, but not properly yet. I have to wait for him to come back in a month or so to tweak the settings. How did you solve it? Chris

Have had this happen to one customer of mine, just threw the exact alarm as yours did only a restart and clear of the alarm log rectify the issue has not happened since I will keep you posted if I find outcome likewise with you

I have the same issue when my MK3 is connected to my laptop using the config tool and having it "idle" for to long. So usually I connect the MK3, make the changes and immediately disconnect it again. So my first guess would be an issue in the MK3 firmware. Had this problem also with older firmware on the Multiplus. So I don't think it's related to the new v500.

Hi, I have a similar issue. Im on a boat. Multiplus II suddenly showed a low voltage alarm. Solar, Shore power and generator work fine but when I isolate all systems the Low voltage alarm activates and no power. I've checked the voltage and all seems to be fine as are the batteries. Any ideas welcome...

Great Vid. Andy... as usual! I haven't tested that behavior on my system yet. I see everyone trying to figure out what could be the problem, yet the ones (Victron Energy) who can really shed some light on the issue are absent. Can any of the Victron dealers contact Victron support and ask them to explain?

Please, anybody can help me to explain what is happening. I have a 24V setup with 16 lithium battery, a BMS balancer JKONG and a Powland Inver. My app show a 75% charge,432ah in the battery but the Voltage is down to 23v. ... The inverter is reading 22,1v and prepare to shoot down. Why??

From my experience with dangerous machines: Some safety features are designed to enforce human interaction before powering a machine back up. Do you have to discard the alarm manually?

Hi Andy. Just watched this and have a few comments. I wonder if the pi experienced an issue during this fault. The logs on the pi now might not go back that far but they might indicate a disconnect of the multiplus. I suspect it crashed disconnected from the victron software and that then triggered the first new ID. You created the second when you intervened and did a hard power cycle.

I feel sad for you Andy, it's not a great situation, but you are always really good at handling this and other "learning curves". You have so much experience that this stubbornness from the system can only really be seen as extreme to the point of not being reasonable or helpful. I'm a newbie, bought a Victron 75 10 having seen how things normally go for you and many others. Was very happy until finding out that it would never charge my battery. I read up, and got the advice from a Victron video than my panel voltage was not good enough (19v and some decimal change) They advised 2 panels in series. I bought the identical panel for a second time and added it to the first, in series. It still won't charge. I'm only giving this much detail to show why I think that sometimes it's just possible that software can be so strict, and maybe correctly so in theory, but it also renders the entire system pointless because it no longer does what it is intended to do. Just to be clear; mine has NEVER allowed me to charge a battery so far. I shall watch your progress in this issue with great interest. Good luck, we all need some at times. 🤞

Perhaps your low voltage shutoff of 37 volts is out of range for the inverter so it gets disregarded and a system default value is used to trigger shutdown. Granted it should notify you if that is really what happened, but it would make sense why your setting was diregarded.

My multiple plus is doing the same thing. Tried shutting it down and restarting it. But the low battery light appears back. I was working on a camper and using a chop saw plugged into it. And it caused it to have the low battery alarm any help?

Hi Andy it happened to me with a 500va small multi and a new 3000va MPII, however, I noticed that is because I shut down the battery manually and also I have AC input while the multis were in through mode, the system would freeze and would not restart untill I flashed software and configuration. On and off did not work for me. With the 500VA I isolated the battery manually cause I though I could have my loads by-passed while I was upgrading the batteries. With the multi 3000VA I was testing if it was possible to do the same and obiously I couldnt 😂. However, I always leave the multi to stop the load with low soc and i do by-pass from the grid without issues, and in the morning it charges back up when sun shines (i am grid connected) I think the problem is only if DC shuts itself or you do it instead of the Multiplus. Regards :)

I had a similar situation recently. I'm using an ess mains connected set-up and my multiple started showing a low voltage warning. It stopped inverting about 1 hour before a planned charge but it did start inverting again after that. The thing is I was never any where near a low voltage cut out point . The battery was at about 45% . The other thing on my system is that the smart shunt always shows the battery voltage about 5-6 volts lower than it actually is ! Just now my battery voltage is showing as 46.26 on the smartshunt, 52.50 volts on the multiplus 2 and 52.50 on a multimeter at the battery terminals. The batteries at 55.5 % capacity !!

I’m currently trying to chose between buying 2 multiplus inverters or two Quattros. Why did you go with multiplus? Do you know anything about the Quattro

Andy, I went through all the comments, and I'm still at a lost to resolve the same issue as yours. Is it a firmware issue? Can you do a follow up video? Bob H.

Oh no!

At 13:14 you show a VRM instance 292. That was no longer the correct instance. At this time it was reporting as 289. When you turned it off and on it reset to 293 for a second then went back to 292. I don't know why this would cause the system to not work. If it's just for monitoring it shouldn't interfere with operations. It may not be the cause but another symptom. Is it adjustable on that screen? If it is, I wonder what would happen if you changed to 289 at that time? Would the inverter start working? When the inverter reset, would the reporting have gone back to 292 like it did and stop the inverter from working and required another manual change back to 292 to continue working.

i have the same prob,, i bought mine 3 days ago, i still cant get it up and running,,,, gerrr,, it says it can run on 38 to 66 volts,, my bats are at 49.00 volts,,but the light just keeps blinking,, i get nothing,, i dont want to have to buy a cable if its not gonna work for me

I had the same problem with a 12v/375w inverter had done the same, after 3 alarms of battery low had shut down and did not restart again. Only after manual disconect/reconect. The mppt charger It charged the battery but the inverter was off.

Do you have any assistants running in the VE configure ?

Idk if what I'm about to describe could explain what was happening with your inverter not powering itself back on without you having to manually intervene, but... I recently ran into a seemingly similar issue (I think...). My batteries were reading at 27.6v (24v nominal system) but the multiplus kept showing low battery warning. Apparently if the inverter fails to auto-start 3 times in a row after low voltage is detected on batteries, it has a built-in lockout feature that helps prevent it from doing an infinite power on/off loop that could potentially damage equipment downstream of the inverter. To get it to come back on, I had to manually turn the switch to the off position and then back on a couple of times. To address my particular issue, I'm trying some different low voltage alarm/warning disconnect settings via VE.Configure.

Whilst I totally agree that the Multiplus should not cut out until the voltage you set, having a setting below the safe minimum battery voltage means that you are totally reliant on the BMS to protect the battery. Having two different settings above the minimum voltage gives you redundancy. On recovery having to reset the Multiplus regardless of voltage stare cannot be right otherwise what is the point of being able to set a reset voltage. I will be very interested to see what you find out on that.

​ @Off-Grid Garage Just a guess: You are having a off-grid situation, it seems the multiplus cannot guarantee that you have enough juice to run the device; it seems to me a safety to avoid any issues which can escalate because of instable/not enough power? The not having an auto-restart might be because of that, but kinda odd. You'd want a reliable system that will resume once there is power again.

Hi Andy. I believe it is a software bug in the upgrade. Victron software developers will find the bug and fix it. To see if this is the case, ask Victron to run the previous software upgrade and see if it shows the Low Battery. Good luck.

i wonder if this problem don't have something to do with the second inverter. maybe the setting in it are not allowing system to reset? i know it should but---. try disconnecting it and updating it as stand alone. make sure your settings are done manually and then reconnect? it could be why you where not able to see a problem.

Hello Andy, I also had a strange experience with the Multiplus that works as an ESS system. After the firmware update to V500, the batteries were no longer charged. The solar chargers could no longer recharge the batteries either. Even though I had the same configuration as before. I have reset the Multiplus to factory settings and after several attempts to load the remote configuration into the Multiplus (via VRM portal) I still had no success. When I went on site with the laptop and recreated the ESS configuration and loaded it, the Multiplus worked again as before. I don't know whether it is due to the remote upload of the configuration file or some other cause, but I got it working by loading the configuration on site. Maybe someone has had my experience too, I'd like to know. I wish you and all viewers on this great channel a nice and pleasant end of the year and success in everything you do. Greatings Jean-Pierre

I have the same issue 😢

Have been experiencing the same issue with a multiplus I have at a remote property. Use the system to power the internet and some cameras. I haven't had time yet to did into it as far as you have, but it is annoying to have to drive there and reset it after too many days of no sun. Was thinking the firmware needed an update, but you said you just did that. Hope you get to the bottom of it.

If you are going to use it for your house I would use one of your old inverters as a backup that cuts in if the main multi plus fails

That is why you buy Victron, 'cause it should just work. Will be interesting to see if it a arcane config that you have got "wrong".

My mom said dad told her it's probably best to verify wiring and connections now. She said he thinks this is best practice because during the low voltage situation occurring simultaneously with the heavy load ( several kilowatts - pool pump) the cabling and connections can have a rapid expansion and contraction event due thermal property extremes and the ensuing low voltage shutdown on the conductors early in the a.m. morning immediately after a long heating period of the said conductors having experienced a large load during the low voltage condition of the DC power supply circuit. I suppose I'd listen to him and start at the inverter connections. I'm not concerned with the VE firmware erroneous ID problem because it makes sense that during repeated hard fault restart conditions it creates this type of marker trail ( ID change).

Do not have Victron myself, but it may be that Low Voltage Disconnect is outside the normal range and it is therefore the limit in the setup that is being reported as the problem. The logic is not able to think in the equipment, but there are limit values that batteries should be within, same with BMS and inverters. If one sets up a value outside the inverter range - it may be the value itself that is the alarm cause.

I had same issue this week. I have near 100% charge and the inverter would shut down low voltage alarm. All connections are solid, i do not have anything connected to inerter to monitor at present as this was first test out of the box. It would run all ok on low loading but as soom as I put a heat gun high load on it would shut down. Battery voltage all show OK so not sure what is going on yet. not great for first time with this inverter

Hi Andy ! Is your smart shunt updated also ?

Do you have DVCC still active ? I have no experience with this feature, but this may have overridden the multiplus features, and suddenly stopped communicating right?

@OffGridGarageAustralia Id Love a follow up to this one... I have jst had this happen to my Multiplus II 48/5000 but the difference is it hasn't had a FW update! Im at a loss...

Hi Andy, Greetings from India. i have gained a lot from you. All your Experiences & Knowledge let me Run my EV car with Diy LiFePo4 Battery & an Off-Grid Solar system at home at my own. I have a query for a long time which you can please resolve if you find some spare time, Actually i have a 16s 150Ah LFP Battery Bank, i didn't Top balanced while building it, also all cells are now welded & can't be taken apart. Due to issues regarding resources i can't add a Balancer. Using Daly Smart BMS. Now the pack is not in a good Balance. Tried with your Lamp method, worked great but Is there a way to manually balance it properly ?? Because once they are in balance, small balance current of 100mA will take care of it.

Haven't looked at my multyplus for months. It's been off. But someone moved my 48v pack of Leaf gen 1 batteries into an uncovered area and they are bloated and stuffed. I'll lock the remainder into a metal cabinet.

Firmware updates love em, where they take your old config, and load a default one anyways cos your settings file has something extra or something missing. When upgrading firmware ALWAYS go thru and check all the settings, make a single change and back save to ensure its written cleanly

Hi Andi, I also have a Victron MultiPlus-II 48/5000/70-50 on an Island system and have the same Behavior. When the low voltage error comes in, Multiplus shutsdown and even afer the battery is back with 50% ans higher, the Multiplus stays at error. The only way to get back on power ist to turn off the Multiplus and turn it on again. Really looks like there is a firmware problem. Even on v502 it still is faulty.

I think , you should check cables , one of them may be loose

does this beep coming from the multiplus? I have the same model no sound. I wish it had one when In low charge.

Just looked at my logs, June/July/first of August, 4 low battery alarms, don't remember now , I may have just power cycled to clear. I believe it was somewhere around that time I went to 497 FW, no low battery alarms since, have not upgraded to 500 FW yet and, may now wait .... Mine is an original MultiPlus, not a II.

😮 Oh boy Andy did u burn out the Multiplus with all that power running ? 🤔

Who doesn't love mystery/detective story? Stay Tuned!

Strange fault for sure - hope you can figure out why it happened.