maxxis

Any further developments here?

That is a mistake i regret a lot. Might just get this one fixed and sell the pair. Replace with something reputable. When I installed everyone was shouting "HUBBLE HUBBLE HUBBLE" Should have listened to installer and gone with Pylons.

Strong suspicion that they didn't do a thorough test on it.

Since July has anyone found a solution to this? One battery still drops from 40% to zero. Both voltage and lithium settings used to see if that bug is still there. Battery was returned to Hubble before and they just said it passed their load test and returned it. Take it back again?

Exact same problem. One battery will drop from 40% to 0% consistently. Unit was taken to Hubble and they did a load test and firmware update. No change. This after a lot of back and forth… Not impressed.

My whole journey with this is documented earlier in this thread. Sunsynk 5k Shutdown is set at 10% They are balancing yes.

Current state of things.

Not too impressed right now. Battery 2 that was dropping to 0% from +- 35% was taken in to Hubble for assessment. Load test showed an equalisation issues and the firmware was updated to 2.07 and the battery was returned to me showing that it passed all the tests. Hooked it up and did some testing last night. At 35% the battery shut down. Not even the on LED was on. Battery 1 continued flawlessly down to 15% SOC until my PV took over this morning. Set the inverter to AGM this morning and disconnected the CAN cable. Will charge both up and let it balance again and test again tonight. Battery 2 is still on 2.05 firmware. Endless begging Hubble to supply me with the latest firmware to update... Does anyone perhaps have the file for me?

Still have the drop from 38% to 0% on the one battery.... Time to log a ticket I guess.

Thank you. I figured as much. Glad to know my batteries are 100% healthy at 286 cycles. Will hopefully not drop from 38% to 0% instantly anymore. My fiance was not happy with the beeping at 2:00 this morning.

Upgrade completed to P1247V110-12290V205T-0316.bin Inverter set back to lithium and updated the charge capacity to 210ah to cater for the 105ah capacity on the batteries. Solar Assistant now reports capacity correctly as 105 per pack. However, Charge Capacity reports as 90ah? huh Interesting observation. Sunsynk logger shows SOC as 100%. Solar Assistant and RIOT shows 85% @ 53.4v and no charging is happening as the Sunsynk reads the batteries as full. Anyone else pick that up? I assume a full cycle will restore this?

Woke up to a beeping Sunsynk this morning. Batteries reporting 0% SOC. Suddenly dropped from 40% to 0% in minutes at around 06:00 this morning. No difference in usage patterns compared to the night before. SA reports both at 100% SOC now but also 45ah capacity left. Time to upgrade the Firmware. Will request the push via RIOT or do a manual flash with the SA cable.

Bottom right corner on the app tap on "me" and enable notification. Right now mine is telling me every 30 minutes that I disconnected from the grid while the grid is perfectly fine. Might be a little sensitive to frequency and voltage fluctuations on Eskom at the moment. LOTS of variations recorded for the past 12 hours.

Update time. Over the past week I've done a lot of monitoring and calculations to determine my capacity and to track down where the problem lies with my pack. The original problem I experienced was a "loss" of 30% of capacity. First step was to use Solar Assistant as well as the Sunsynk Data Logger to keep an eye on my voltages. I'm ignoring SOC and the Capacity readouts for the time being and working on voltage specifically as this is the most accurate indicator of state of charge for me. 53.6v = full and 42v = empty. My batteries are used between 18:00 and 08:00 with an average load of +-350w over 14 hours. Observations: Both batteries are perfectly balanced at every step of charge and discharge. Minimum, Average, Maximum cell voltage reads within 0,01v of each other. Temperature on both batteries match 100% Testing: First step was to calculate my average hourly consumption for the time that my batteries are discharged. Further calculation to determine the discharge in kWh based on voltage. Determine the total discharge in kWh and then converted to voltage. Determine the target v by 08:00 to calculate % that my batteries are discharged during the night. Process: Set Sunsynk inverter to AGM V mode. Ensure that charge and float voltage etc is at 53.6v. Ensure that shutdown is at 42v to work on 100% discharge if needed. Use battery voltage readouts on Solar-Assistant, Sunsynk dashboard, & Inverter. Findings: By 08:00 this morning I had 47.5v available on the battery. This converts to (rounded) 45% charge used. Sunsynk Logger confirmed voltage at 47.5v available. Sunsynk Logger confirmed SOC at 55% which when the voltage remaining is converted, is correct. Solar Assistant confirmed the voltage at 47.5v available. Solar Assistant confirmed SOC at 0%... ERROR here. Inverter confirmed 47.5v available. Charge in kWh for today matches the amount of kWh discharged for last night. The only conclusion I can draw from this is that the Sunsynk in Lithium mode reads the incorrect protocol from the Hubble and therefor shuts down when it believes that the SOC = the shutdown SOC set on the Sunsynk. Based on the above I can also confirm that my batteries are 100% balanced and in fact at 100% Capacity. Solar Assistant I believe is also reading the capacity wrong in my case and most likely misreads the same way that Sunsynk does in Lithium mode. I'm happy that my batteries are in fact 100% working as expected and that this whole issue of "capacity loss" is a software issue that can easily be corrected with a firmware update.

I’ve lost 45% capacity to do date with under 100 cycles on both my batteries Solar Assistant reports 107ah capacity for the bank and my discharge vs SOC calculations confirm this. My guess would be BMS issue and not dead cells Ticket logged. Support so far has been brilliant. It is a pain to get resolved but the benefit of quick turnaround time is a huge plus for me. Holding thumbs that this is a once off issue.