SoC Crash...Here's what happens

6 comments started 2023-08-10 last 2023-08-10
GivEnergy ProductsHybridBattery
#1 ProximusAl

For all of you people that report the battery diving to 0% and getting stuck there, this is exactly why.
Happened to me last night. As you can see in my graphs, both packs cell voltages hit 3.7V which is what forces the batteries offline from the inverter, so the SoC gets reported as 0%.

This is on 911 Hybrid Gen2 and 3013 Battery Firmware:

K
#2 KamenMacKay

I had a similar issue with the 3012 firmware where the battery temperature jumped very suddenly and, from what i can tell, the BMS probably forced the batteries to dump all their juice in order to avoid some kind of damage?

Nice graphs ProximusAl ; care to share your Grafana dashboard json as i just built mine from the data that is available but I'm not really sure what is useful to graph or not.

#3 ProximusAl

KamenMacKay Mine isn't Grafana. It's good old bog standard Home Assistant 🙂

K
#4 KamenMacKay

ProximusAl You must have Grafana installed inside of Home Assistant then. I'm also pulling the data from the Givtcp add-on but I have influxdb and grafana as separate installations as I like to graph lots of other things.

#5 ProximusAl

KamenMacKay No. No Grafana. This is a bog standard HASS core install on a docker.

This is the graph you see when you click on an entity.

M
#6 Mike M

After the first two crashes the battery recovered to operate normally, GivEnergy performed a re-calibration. After a couple of dull cloudy days the sun came out and crash happened again and later recovered, back onto GivEnergy who monitored the next crash however it has suffered BMS communication fail and not recovered as yet(24hrs). GivEnergy wanted to re-calibrate but the coms fail stopped that. Battery also showed no response to their request I use the off button. Arrangements are being made for an engineer to visit.