5 hours ago, jdido87 said:

The battery has been on 64% all day. It was on 65% just prior to the solar taking over the house load. The installer updated the firmware as well earlier on but no change. The moment turn on the pool pump the solar generation increases to match the load but no excess solar are going to the batteries.

Also, I enabled grid charge and turned off time of use. The batteries aren't charging from the grid either. This worked fine a day ago with the storms.

Switch OFF lithium/BMS communication and use “Lead Acid/User Defined”.

Manually enter safe lithium voltages ONLY as a short test. If the battery immediately starts charging the problem is definitely BMS communications or permissions.

This is one of the fastest ways to isolate the fault.

Based on the symptoms, my suspicion order would now be battery BMS charge inhibit

1.CAN/RS485 comm issue after firmware update

2.Max charge current accidentally set to 0A

3.Corrupted TOU/force-charge state

Less likely: actual PV issue

The fact that PV instantly ramps when the pool pump starts is actually very good news the solar side itself appears healthy.

Then Fully restart BOTH battery and inverter

Not just the inverter.

Proper sequence:

Turn off PV isolator

Turn off AC breaker/input

Turn off inverter

Turn off battery breaker/power

Wait 5 minutes

Then restart:

Battery first

Wait until battery fully boots

Inverter second

AC input

PV last

This often restores CAN/BMS comms.

18 hours ago, TaliaB said:

Switch OFF lithium/BMS communication and use “Lead Acid/User Defined”.

Manually enter safe lithium voltages ONLY as a short test. If the battery immediately starts charging the problem is definitely BMS communications or permissions.

This is one of the fastest ways to isolate the fault.

Based on the symptoms, my suspicion order would now be battery BMS charge inhibit

1.CAN/RS485 comm issue after firmware update

2.Max charge current accidentally set to 0A

3.Corrupted TOU/force-charge state

Less likely: actual PV issue

The fact that PV instantly ramps when the pool pump starts is actually very good news the solar side itself appears healthy.

Then Fully restart BOTH battery and inverter

Not just the inverter.

Proper sequence:

Turn off PV isolator

Turn off AC breaker/input

Turn off inverter

Turn off battery breaker/power

Wait 5 minutes

Then restart:

Battery first

Wait until battery fully boots

Inverter second

AC input

PV last

This often restores

18 hours ago, TaliaB said:

Switch OFF lithium/BMS communication and use “Lead Acid/User Defined”.

Manually enter safe lithium voltages ONLY as a short test. If the battery immediately starts charging the problem is definitely BMS communications or permissions.

This is one of the fastest ways to isolate the fault.

Based on the symptoms, my suspicion order would now be battery BMS charge inhibit

1.CAN/RS485 comm issue after firmware update

2.Max charge current accidentally set to 0A

3.Corrupted TOU/force-charge state

Less likely: actual PV issue

The fact that PV instantly ramps when the pool pump starts is actually very good news the solar side itself appears healthy.

Then Fully restart BOTH battery and inverter

Not just the inverter.

Proper sequence:

Turn off PV isolator

Turn off AC breaker/input

Turn off inverter

Turn off battery breaker/power

Wait 5 minutes

Then restart:

Battery first

Wait until battery fully boots

Inverter second

AC input

PV last

This often restores CAN/BMS comms.

Thank you very much. I will give this a go when I get home.

On 2026/05/14 at 4:32 PM, jdido87 said:

I find this really weird. 64% @ 55.19V with almost 1 amp going out. Something does not add up

The BMSbattery current limit to 0 might be stopping the inverter charging

Edited May 15May 15 by Stefan Cornelissen

1 hour ago, Stefan Cornelissen said:

I find this really weird. 64% @ 55.19V with almost 1 amp going out. Something does not add up

The BMSbattery current limit to 0 might be stopping the inverter charging

Yes I agree the 55.2v = 100% Soc. @jdido87 i will get the installer involved to get the batteries tested by the supplier. Insist on getting al 3 modules tested in parallel with communication enabled to ensure data packages are not dropped.

Example of a healthy CAN network communication from a Victron System.

Edited May 15May 15 by TaliaB

Thanks guys.

The issue was resolved. According to the installer the system detected moisture and the batteries shutdown to protect itself.

Apparently he had a lot of similar call outs after the storms in Cape Town last week.

I installed more vents in my solar room today. Going to get a smart thermometer and humidity sensor that intend to connect to and extractor fan to control the climate a bit better.

New to all of this so the learning curve is steep. I tried to control temperatures in the solar room but forget about the humidity.