Ok, so looks like (for me anyway), GivEnergy have switched off the software beta balancer for dual inverters (via their API).
Slight change of implementation technique but….
I’ve implemented my own balancer automation now using my Home Assistant Green and I’ve now created a tuneable version of it that I can modify various setting including the trigger sensitivity. After a few days monitoring, I’m now live. It’s been live for about 3 days. It’s not had any live interventions yet, as the solar has been excellent over the last few days and the cross charging typically is at its worst during the cross over from zero solar to a reasonable amount of solar or on very low solar days (ie winter). And obviously cross charging doesn’t happen when both battery pairs are full either.
So in summary here’s what it is, and how it works;
I’ve built a Home Assistant “cross charge balancer” for my dual GivEnergy Hybrid 5.0 setup to mitigate the classic inverter tug-of-war issue.
The problem:
Sometimes one inverter/battery stack starts charging while the other simultaneously discharges into it. In extreme cases I previously observed:
- one stack charging at 3.7kW
- the other discharging at 3.7kW
- little/no useful export, just each pair pure cross charging each other up to the max charge rate vs the other at max discharge rate.
Essentially energy circulating internally between each inverters battery pairs.
My observations suggest GivEnergy’s old cloud balancer was doing something very simple:
- detect cross charging
- briefly pause charging on one inverter
- resume
- repeat if needed
So I recreated a local version in Home Assistant.
How my balancer works:
- monitors both inverter battery power sensors continuously
- detects opposing flow:
- one inverter charging
- the other discharging
- ignores intentional windows:
- overnight cheap-rate charging
- Octopus Intelligent dispatches
- evening export window
- if sustained cross charging is detected above the “tuneable” threshold:
- temporarily disables ONLY the charging inverter’s battery charging
- waits a short period
- re-enables charging automatically on the charging battery pairs
No schedules are modified.
No permissions are permanently disabled.
No inverter modes are forced.
It’s basically acting as a damping controller to calm inverter instability.
Current tuning:
- trigger threshold: 200W
- sustain time: 20s
- pause duration: 10s
- cooldown: 90s
The goal is not to “fight” the inverter logic, but gently interrupt unstable feedback loops before they become large circulation currents. Ie prevent the charging battery pair from becoming a sink for the discharging inverter battery pair. Removing the charging pair being an energy sink temporarily thus reduces the extra discharging load from the other inverter’s batteries.
The automation is fully adjustable via HA helpers:
- threshold sensitivity
- sustain duration
- pause duration
- cooldown
- monitor-only mode
- master enable/disable
I also built:
- Energy Brain dashboard
- predictive risk sensors
- monitor-only testing mode
- HA + mobile notifications
- cooldown protection
- safe-window exclusions ie: 1) My dynamic evening discharge automation: xx:xx—>23:30), 2) My overnight cheap charging window (23:31–>05:30) and 3) Any extra IOG bonus slots.
Interesting observation:
During high summer PV the issue is mostly masked because there’s enough solar for both inverters. The instability becomes much more obvious:
- after overnight charge ends
- during low-PV mornings
- late afternoon before dynamic export starts
- during cloud-edge transitions esp on low solar days
- winter and low solar days
So far the HA balancer behaviour appears very similar to the original GE cloud mitigation layer.
It’s early days so far (3 or so). Should have a better idea of sensible tuning setting in anger after a few
months.
Here is the control panel I’ve created in HA…

