Anyone else running Victron Cerbo GX with EV charging — how are you handling the grid/solar priority?

Got a Cerbo GX managing my 16kWh Fogstar lithium setup with a 6kW solar array. Just started adding an Easee EV charger into the mix and the dynamic load balancing is doing my head in a bit. The Cerbo sees the car as a massive uncontrolled load and the system keeps throttling back solar export when really I just want it to dump excess into the car first.

Currently using Node-RED on a Pi to try and bridge the two — polling the Easee API and feeding limits back through MQTT to the Victron. Works okay but feels like duct tape. Wondering if anyone's done this more cleanly, maybe with the VRM portal or direct Modbus.

Anyone cracked a decent priority logic — solar first, top up battery to say 90%, then push remainder to car, grid as absolute last resort? Feels like it should be a solved problem by now but I'm not finding much that's UK-specific and accounts for the Easee/Victron combo.

@MarineGaz not running an EV charger myself on the static, but I've been down the rabbit hole of Cerbo dynamic load management reading because I was curious about it for future.

From what I understand the key is setting your ESS minimum SOC correctly so the Cerbo doesn't let the EV drain your Fogstar pack below a threshold you're not happy with. The Easee should respond to the Node-RED flow if you go that route — there's a com.victronenergy.settings path that lets you throttle the charger input based on solar surplus.

Have you looked at the VRM portal scheduled charging feature? You can essentially tell it "only charge the EV when grid input plus solar exceeds X watts."

What's your inverter setup — Multiplus II? That'll affect how the load balancing actually behaves in practice.

Great setup @MarineGaz — I've got a similar Fogstar/Cerbo combination running here with a Zaptec charger, so fairly comparable situation.

What's worked well for me is using Node-RED on the Cerbo to create a proper priority ladder. Essentially I've got it watching the MQTT feed for battery state of charge and available solar excess, then pushing MODBUS commands to throttle the charger accordingly. Keeps the EV charging sitting nicely below house loads without constantly fighting the built-in ESS assistant.

The key thing I found was setting a solid minimum SoC threshold — I won't let EV charging kick in until batteries are above 85% or there's sustained solar surplus over about 1.5kW. Took a bit of tweaking but it's been solid for three months now.

What firmware version are you running on the Cerbo? There were some meaningful improvements to the ESS scheduling in recent releases worth checking.