maxxis

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. 

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? 

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. 
 

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.

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.

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.

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.

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.

Hi all .Just an update on the Hubble issues you have been experiencing I have been in talks with Hubble Senior Engineer and these are some Highlights of our discussion.
1. All firmware updates and remote battery analysis can and will be done via the Cloudlink.
2. Hubble will not request you to send the batteries in for testing all testing can be done remotely if you own a Cloudlink
3. If Hubble finds that your battery is faulty they will arrange a swap out unit this will be implemented in the next few weeks.
4. If you do not own a Cloudlink then you have no choice but to send the battery to Hubble so they can test the battery and ascertain what the problem may be. 
5. Hubble Engineers are currently retraining their support staff to correctly assist clients with regards to support issues.
6. Hubble Engineers are resolving the Communications issues with Sunsynk inverters and redeveloping the software for the Cloudlink to work properly with the Sunsynk range newer models of Sunsynk inverters have different pinout configurations to the older models and the Cloudlink was setup for the older models only they have a software engineer specifically doing just that.
7. We have found that there is a problem with the BMS communication and Sunsynk inverters inadvertently causing the Sunsynk to limit battery capacity by as much as 40 % the interim solution to the problem is by simply using the AGM-V Setting on the Sunsynk for battery settings Empty Voltage 42 and 53.6V for the full voltage Float etc all the same this will unlock the lost capacity of the batteries until Hubble releases a new firmware version to resolve the problem they are aware of it and working on it.
8. Please use the Hubble support system to communicate your queries and problems the forum is not here for Hubble support problems the staff do not monitor the forum for anyone with a complaint or support issue with their products.
This information was relayed to me by the Senior Hubble engineer they are aware of the complaints of support and some problems that have come to light and are committed to resolve every issue and problems again please use the correct channels for your enquiries.  
 
 

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.

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.

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. 

Another thank you to @Powerforum Store Your insights and advice is truly remarkable and the support from @HubbleLithiumalso deserves and honorable mention. 
 

I am noticing a trend here on the posts and I find it concerning borders on Product bashing. 
It maybe due to lack of Knowledge or lack of understanding how lithium batteries work.
The reason for this forum is to help people with technical problems and sound technical advice.
It is not a platform to badmouth and product bash that is just childish to be honest.
The amount of complaints that come to light on this product via the forum is but a small percentage of the total amount of these batteries out in the market I would estimate it at about 10 in 10 000 units with that said as far as I know the Manufacturer has thus far assisted every one of their clients that have problems with their batteries so far there is not one person that has not been assisted or where a problem has not been resolved.
They have had some issues with the time it takes to resolve support issues and that is purely due to the fact that they just did not have enough staff on technical support to handle everyone's support requests Secondly due to the fact that their support staff should only know the battery and not the finer technical function of every hybrid inverter in the market a lot of these support requests is how to set the inverter up correctly and has nothing to do with the battery. Surely this is the responsibility of the installer and or person installing the equipment to know how to set everything up correctly and not the responsibility of the battery manufacturer they provide you with all the parameters that need to be set up and that is as far as their responsibility goes. As far as I know they are addressing this problem and is working to improve their technical support and also working to simplify their installation manuals so DIY installers can also understand how to install the equipment correctly.
I have come into contact with a few guys who have had problems with their batteries and found in a lot of cases the configuration of the inverters were done incorrectly or there was some procedures when commissioning new batteries that were not followed correctly and out of those a very small number of people had real problems with the batteries.  
Discussing Current Lithium Chemistry is far above the knowledge level  most of us here on the forum and you will definitely not find Confidential information on the chemistry of current lithium technology on google most of this info is under patent or hidden from competitors and will cause people to come to false conclusions unless that is the intention. 
Reasons why Lithium Batteries should not sit at 100% all day and every day is it will cause Denitrification of the Electrodes some manufacturers Hide this from you by getting the BMS to report that the battery is 100% full yet it is sitting on 90% most of them also limit the battery capacity by 5 or 10 % 
The reason for this is to extend the life of the Lithium Cells considerably this manufacturer has recently added this feature to their batteries to extend the lifespan of the battery for a lot longer and to prevent the risk of denitrification.
With that said if you have a problem with your battery contact the company directly get a support ticket and they will assist you there are not many manufacturers in SA offering that level of support. 
As you all know when you contact power forum store we always do what ever we can to offer you support on product purchased through us we even help people who did not buy product through us with technical assistance and support we have also escalated all of your queries with this manufacturer to resolve the problems you have as fast as possible they have indicated that they see after sales support and quality of support as a priority and are attending to all the issues.

Hi Louis. 
This is not correct. The 8kw and 5kw limitation is purely a DC to AC limitation. The passthrough function is AC to AC so on the essential side, when the grid is available, the 5kw can peak at 8kw and the 8kw can peak at 12kw. Definitely will not overload as the balance is drawn from the grid. 

If there is grid available the max passthrough current is 35 amp . So about 7.7-8kw .