Random cell voltage drops

I’m running 2 cellmate-k9 connected each to a 16s eve lf280k LiFePO4 battery pack.
Every coupe of days I receive an alarm regarding low battery voltage. 1st investigation shows a short voltage drop in one of the cells:

Batrium is showing a voltage drop down to 1,8V but Victron is showing just 2.3V. This might be related to the just 1minute resolution at Victron.

Anyway, I’m afraid, that I have a bad balance lead. I manually soldered inline fuses directly to the ring lugs.
What is the best way to identify the bad guy?

1 Like

Since I’m a new user, I’m not allowed to add multiple pictures in a single post

1 Like

Hi @luphi,

Maybe it’s best if we direct this technical enquiry to our Batrium support team via email as we cannot be certain of what is happening without more information about your setup.

Can you let us know what hardware you got and the software and the firmware version (build) you are currently using?

It might be best to send us a manual extract report and send it to our tech support email so we can have a look at your configuration.

Hi @Renzee ,

thank you for your quick response.
Just send the email.
You also should receive an email from Victron VRM, which invites you to my Victron setup.


1 Like

I would like to hear, when something is found out, because I have the same issue “sometimes”.

got an answer by email this morning:

Currently, we are working with Victron directly, revising some algorithm issues that might be helpful in resolving this.
Alternatively, a new firmware version will be released very soon that hopefully might address this.
We’ll keep you posted for updates.


yesterday or the day before, I was lucky. I had the watchmon toolkit open monitoring the cells while it happend again.
For a blink of an eye one cell disappeared and I was able to identify it’s number.
So, I went to the battery to check the balance lead and al screws of that particular cell and also it’s neighbors, unfortunately everything seamed to be fine :frowning:
For me, it looks like Victron is not involved at all, maybe an issue with the K9?


1 Like

I have an issue towards the top of charge (when balancing) where a cell will briefly display WAY over its real voltage - For example, a cell might be at 4.11v and all of a sudden will appear as 4.5v – but only briefly. Its some sort of phantom interference. Its not the Victron integration, as I can see the voltages in the watchmon toolkit.

If I had to guess, Batrium will be applying some sort of averaging technique to eradicate these erroneous spikes/dips.

Same Problem here today, which causes my Main Switch to cutoff everything… :rage:
Luckily a snaphot was generated, which shows a CellVoltage of 1.76V on my Cell 1 (LFP).
Now the cell is back to “normal” 3.3V.

So how should one handle this?
Turn of the critical LowVoltage Watch? Or is there a way to wait for at least xseconds before the criticalOffline State is triggered?

OpStatus AuthMode CMU Mode
CriticalOffline Default Normal

SysFaults: Nil

Live status information
Min @ ID Max @ ID Avg Repeat
CellVolt 1.76v @ 1 3.30v @ 3 3.26v 143

You can play with the delay transition stop values

That is exactly what you are asking for.
But that is just fighting symptoms and should be just treated as a workaround
In my point of view this is a measurement fault. Are you using K9 or individual CellMons?


That value is 120sec in my System, I use CellmatesK9.
I turned on the critical Main Switch last weekend, before I monitored some LowVoltage issues too, randomly spreaded over different cells.
I agree, this must be an K9 issue, but I will check my connections on that cell again…

have the same issue with 2.17.28.
4 banks 16S1P, randomly false measuring on cell 1 of each K9 for two cycles release the shunt trip.

Hopeful 2.17.39 fixes this bug. Will test the next days.

Yesterday, again CellDrop even with 2.17.39.

I’ve recorded via mqtt and Node-Red all drops below 2.8V.

My Cellmates are
HW9.0 FW0.7 BL160.15


But because I turned off Low Cell Volt Monitor, no Critical event was reported.

But I’m not brave enough to reactivate the Relay Trigger to the Main Switch, because I don’t like BlackOuts because of false positive measurements.

@physi Thanks for this information. I have forwarded this to our tech team.

The timestamp has been helpful, indicating that it drops for 4 secs and then recovers. We now have something to help us investigate this issue.

1 Like

Would you mind to explain, how to setup this up, so I can reproduce it in my installation.
I have a very good understanding of Linux but never used Node Red nor MQTT.

@Renzee here are some more data, maybe that will be helpful as well.
The 4 sec. seems to be right in each drop.

	"c": {
		"1.73": {
			"1": [
		"1.49": {
			"1": [
		"2.695": {
			"1": [
		"1.95": {
			"1": [
		"2.185": {
			"1": [
		"2.195": {
			"1": [
		"1.465": {
			"1": [
		"2.595": {
			"1": [
		"1.45": {
			"1": [
		"2.14": {
			"1": [

Keep in mind, hat you just count the time while the cell is below 2.8V but usually it starts dropping from 3.2 to 3.3V. That will give you probably a drop time of 5 sec, which then fits to the K9’s 5 sec measurement cycle.
Just my two cents

just happened also to me at 12:07 local time.
SOC 80%
current -5 Amps
So, definitely no bypassing
You can clearly see it in VRM.

Hope that helps.

Once more, this morning at 5:54 :frowning: