Seen this crop up a few times and had something similar with my own Multi-II 48/3000. Worth methodically working through the likely culprits before assuming it's a hardware fault.
Most common causes I've come across:
- BMS communication issue — if you're running a Victron-compatible lithium pack (Fogstar Drift, EG4, etc.) over VE.Bus or VE.Can, the BMS can assert a DVCC charge/discharge flag that silently blocks inversion even when the green LED suggests it's ready. Check Venus OS on your GX device — look under Battery Monitor → Details for any active charge/discharge flags.
- Low cell voltage protection — even if overall pack voltage looks fine, a single weak cell tripping the BMS will prevent discharge. What's your cell-level monitoring showing?
- ESS assistant vs standalone invert mode — if you've loaded an ESS assistant previously and then tried to switch to standalone invert, they can conflict badly. A full VEConfigure wipe and reconfigure from scratch has sorted this for me before.
- DC voltage drop under load — seen cases where the Multi appears healthy at rest but the DC cabling has enough resistance that the moment it tries to pull serious current, voltage sags below the low-battery cutoff threshold. Worth checking your configured DC input low shut-down voltage in VEConfigure.
What BMS are you running, and are you on a GX device? Also — when you say "returned to default for lithium," did you use the lithium preset in VEConfigure or just hit reset? Those aren't the same thing and the preset sets some parameters the reset won't.
Anyone else had the ESS conflict issue cause this? Curious whether it's more widespread than