1 hour ago, Reuben Emkie said:

I have an am 2 hubble battery and an sna5000 luxpower inverter that show the battery as 50ah instead of 100ah

Try PBMStools to see what's going on - see above thread for details.

You need to take it in and they will reset it to 100ah

1 minute ago, IGR said:

You need to take it in and they will reset it to 100ah

In my case my battery arrived at 110Ah, kept dropping Ah was reset to 100Ah via RIOT, kept dropping Ah, a firmware update reset it to 105Ah and stopped the dropping of capacity.

Can someone please hook me up with the latest update SW and FW ?

 

I logged a ticket with Hubble two weeks ago via their raiseaticket portal, but no response.

My battery is still fine after ~170 cycles, but PBMSTools shows I'm on FW 1.43 (P13S120A-12290-1.43), so I want to do a pro-active update.

I think there's at least a FW 1.50 available, according to this screenshot here:

 

@swazz99jhb

 

Much appreciated

 

I have found that it is better to log a call on:

[email protected]

1 hour ago, Mier said:

Can someone please hook me up with the latest update SW and FW ?

 

I logged a ticket with Hubble two weeks ago via their raiseaticket portal, but no response.

My battery is still fine after ~170 cycles, but PBMSTools shows I'm on FW 1.43 (P13S120A-12290-1.43), so I want to do a pro-active update.

I think there's at least a FW 1.50 available, according to this screenshot here:

 

@swazz99jhb

 

Much appreciated

 

Expires 20 Dec-  We transfer

10 minutes ago, swazz99jhb said:

Expires 20 Dec-  We transfer

Awesome. Grabbed.

Thanks a lot !

Good morning all.

This is not a product/company bashing post but simply a post to raise awareness and highlight some issues with the Hubble am 2 and the after sales service.

My set up is as follows..

8kw sunsynk,14 x 425 canadian solar and 2 x Hubble am 2.I have a geyserwise system in for my hot water and my household is small.My daily usage is about 16kw/h which is nothing.

I bought my first am 2 along with the installation about 6 months ago and the about 7 weeks ago i got a second am2.

All was good and with my usage my soc% in the morning would be about 68%,the sun comes up or eskom if its a lousy day and the batteries get charged if there is a shortfall from the pv.

I dont have an essential/non essential split as i manage it myself with gas hob, air frier etc so no massive draws.

About 3 or 4 weeks ago I noticed my soc% wasnt getting higher than 92% and then I identified that it was the 6 month old battery.It kept on dropping and after finally getting hold of one of the hubble guys in ct and also info from this forum,I was advised to changed my setting to voltage instead of soc.

I did that and it worked for a few days as the soc went back up to 99/100%

It then started to drop off again and I got myself a cloud link R2700 which is a ton of  money for such an iffy product.

My installer and I tried for days to connect it and it wouldnt work.My installer also bought one and his worked fine on his home system.I was advised by hubble that the wifi wasnt strong enough so to make sure it was i bought a range extender and the speed in my garage is about 38mbps.We followed the set up videos which were sketchy at best and ongoing calls with tech support but they didnt have any answers.

We gave up and then about 2 weeks after this soc issue started i heard a weird sound in my garage VERY early in the morning around 4.30 am.There was acrid smoke and glowing inside my 6 month old battery which i could see from the ventilation holes on the side.I switched both batteries off and all the breakers/cut offs.

For hours it had a nasty smell.My installers came around early in the morning and took the battery to the hubble supplier here in dbn who had a look inside and said it had to go to cape town.

My installer was told that the bms was burnt out due to over charging or discharging and it was going to cost me just over R 6000 to fix as its not covered by the warranty.I downloaded the warranty and was shocked to see the number of exclusions.

I have seen many posts re the lack of useful data that the cloudlink puts out for us end users and one assumes that hubble can see a ton more if they log in.

The fun started when i started to dispute that i had caused this damage.I had been in almost daily calls with tech support prior to this and nobody advised me to switch off the battery and take it for a check with our local distributor who can do basic fixes.If we had taken it earlier then maybe this could have been avoided.Once reading the warranty the onus is on the end user to get a cloud link for tech to monitor things or go through the hassle of removing a battery and sending it locally or to ct.

I had no way of refuting the claim that i had stuffed it up and also the overcharging or discharging bit didnt make sense to me or a big distributor here in Dbn.In essence if ones battery goes to ct one has to really on hubble being honest and saying that whatever has gone wrong is covered by the warranty or not as we have no way of knowing.Download the warranty as we really are boxed in a corner and cloud link seems to be the bridge which may or may not help us with future issues of which there have been many based on 17 pages just on the am 2.

Trying to get hold of someone in ct to chat about this was very frustrating and besides the cost ,it was a bad customer experience (irrespective of the industry).It took weeks of no returned phone calls etc.

I laid this out with one of the managers there who saw my point and to his credit they only charged R3840 instead of the full amount.Its not the money but the bad taste this has left me and i dont trust my batteries.My fixed one should be on its way back to me as we speak.My plan was to get a 3rd battery but it wont be hubble as my confidence in all aspects is gone.

As I see it unless we have a cloudlink then its a case of trying a few settings and if no luck the battery has to be removed and sent off and its pot luck with the outcome.

I think they are potentially very good batteries and once the ongoing issues are sorted then all will be good.

I understand that firmware updates cannot be done via cloudlink as per a post in this section.if i read that correctly then that also  doesnt make sense.I went back onto the hubble website and it mentions the cloudlink for bms firmware updates but apparently this isnt correct.Also the disparity between float etc voltages on the battery, website etc seems to not match up.

 

Edited December 23, 20223 yr by Nicholas Strachan
added something

23 minutes ago, Nicholas Strachan said:

This is not a product/company bashing post but simply a post to raise awareness and highlight some issues with the Hubble am 2 and the after sales service.

I have been monitoring this thread from the beginning as I have the same battery and the rate at which problems were being reported was of interest and concern.

My own battery has had zero issues with the original firmware. Battery manufacture 06/21 and in use since 08/21 nearing 500 cycles.

What nobody knows is what percentage of these batteries are actually exhibiting the issue as we only see the ones that take the time to find the forum and then state their problems here. And not a single battery manufacturer/importer in this country dares to publish their statistics. 

What I did notice though throughout this thread is the majority of related issues ends up being a combo of Inverter and this battery. And no, I am neither bashing the battery or the Inverters involved. The fan boys will cry foul, but I would love to see a survey with the AM-2 troubles and what your combo was, as I believe it to be more than just the battery. Within this thread, from the start, new Hubble Firmware was issued based on what the users reported. Subsequently the Inverter firmwares were also done. First the 110Ah ended up as 100Ah after the first Hubble firmware and then became 105Ah with subsequent firmwares. And still some have problems even after the updates. At this stage someone at Hubble should have interrogated the combo and tried to find out why the specific Li Protocol used causes these issues. 

With my combo I am still on the original battery firmware and the Inverter Li Protocol has obviously not caused any issues. Am I just lucky? Perhaps, but a statistical analysis would make the issue transparent to all parties involved, from manufacturer to consumer. The industry has not been subject to any mandated reporting as is customary in the motor industry or even the computer industry where failure rates are reported and the consumers can easily find the data to do their research before making a purchasing decision.

  

 

19 minutes ago, zsde said:

I have been monitoring this thread from the beginning as I have the same battery and the rate at which problems were being reported was of interest and concern.

My own battery has had zero issues with the original firmware. Battery manufacture 06/21 and in use since 08/21 nearing 500 cycles.

What nobody knows is what percentage of these batteries are actually exhibiting the issue as we only see the ones that take the time to find the forum and then state their problems here. And not a single battery manufacturer/importer in this country dares to publish their statistics. 

What I did notice though throughout this thread is the majority of related issues ends up being a combo of Inverter and this battery. And no, I am neither bashing the battery or the Inverters involved. The fan boys will cry foul, but I would love to see a survey with the AM-2 troubles and what your combo was, as I believe it to be more than just the battery. Within this thread, from the start, new Hubble Firmware was issued based on what the users reported. Subsequently the Inverter firmwares were also done. First the 110Ah ended up as 100Ah after the first Hubble firmware and then became 105Ah with subsequent firmwares. And still some have problems even after the updates. At this stage someone at Hubble should have interrogated the combo and tried to find out why the specific Li Protocol used causes these issues. 

With my combo I am still on the original battery firmware and the Inverter Li Protocol has obviously not caused any issues. Am I just lucky? Perhaps, but a statistical analysis would make the issue transparent to all parties involved, from manufacturer to consumer. The industry has not been subject to any mandated reporting as is customary in the motor industry or even the computer industry where failure rates are reported and the consumers can easily find the data to do their research before making a purchasing decision.

  

 

I swapped my 5kw luxpower sna for an 8 kw sunsynk as i want more capacity on the panel side.The meltdown happened when the luxpower was in place but dont think they are related.The sunsynk gives soh,soc, temp etc which comes from the bms.All seems fine now and they communicated instantly once connected with no issues.Once my fixed battery is back and connected then it will be interesting to monitor.I get it that solar is newish to SA and there are so many products out there and stuff does happen.i have explained to friends who are getting a new system that its going to take a week or 2 of tweaking and its not like plugging in a new toaster and off you go.Stuff happens with all brands of components but how its handled by the supplier will be for me what gets brand loyalty and further recommendations.

Following this topic with a gnashing of teeth. My hubble is less than a year old. After a few months it started providing about half the capacity. Took it in to hubble and and the tech reset the bms settings and it behaved for a few weeks but now it's back to its shenanigans.

Looks like it needs to go back to hubble. Maybe permanently this time. 

@HubbleLithium

On 2022/12/24 at 10:50 PM, Dani said:

Following this topic with a gnashing of teeth. My hubble is less than a year old. After a few months it started providing about half the capacity. Took it in to hubble and and the tech reset the bms settings and it behaved for a few weeks but now it's back to its shenanigans.

Looks like it needs to go back to hubble. Maybe permanently this time. 

@HubbleLithium

I am very dissapointed with the overall performance that I see on the thread and sincerely hope my 2nd Hubble doesnt break down like the first one after a short while.If it does then I shall toss them out and start again with some sunsynk batteries.

On 2022/12/24 at 10:50 PM, Dani said:

Following this topic with a gnashing of teeth. My hubble is less than a year old. After a few months it started providing about half the capacity. Took it in to hubble and and the tech reset the bms settings and it behaved for a few weeks but now it's back to its shenanigans.

Looks like it needs to go back to hubble. Maybe permanently this time. 

@HubbleLithium

Sounds just like mine.
Resolved with a firmware update P1247V110-12290V205T-0316.bin / P13S120A-12290-2.05T
My 4xAM-2 have been fine since the upgrade on 15 May 2022.
Highly recommend pbmstools (see thread for details) to see firmware version number and many other readings.

Clearly hubble knows of the bad batch sold in 2021. They should have recalled those units .

Our problem was with 3 sets of dual batteries (1 bought in Des 21 and 1 in Sept. 22) where the older batteries only had 28-31 Amp capacity when the second battery was added - on own they were 100A. Inverter BMS averages readings so we only identified the problem when we added SolarAssistent
 

My experience with 2 battery setup was to log a call on email in my previous post. State all possible info with screenshots. I used this to show my batteries had different capacities

Hubble responded quickly. They first sent new firmware releases (may be different for batteries) to ensure both batteries are at correct releases. 

Hubble also suggested the AGM process using V to charge both batteries to 53.8V. 

When this failed I took problem battery in and they got the problem sorted out. 

So to recap:

* Get correct firmware versions

* Get Hubble to identify the problem by providing as much info as possible

* Then get the problem sorted out by Hubble

Hope this helps
 

2 hours ago, TiaanSmit said:

Clearly hubble knows of the bad batch sold in 2021. They should have recalled those units .

Why would Hubble do it if they offer the kind of support as we are reading here. 

My personal gripe is why should I read about certain T&Cs on social media and then go and look for them. Surely they should have been included with the 2 batteries I bought? 

It just makes you think about Hubble and their ways. 

So i got the USB- RS232 cable from SA. PBMSTools shows the following.

My RIOT reports SOH of 78%

If i look at the PBMSTools info am i correct in saying there is an issue with battery no 1?

Battery 1 was installed in Dec 2021 and batttery no 2 was installed in Feb or March of 2022.

Where to from here?

 

Your full capacity on batt 1 is the problem at 48. See 2nd is 100 which is correct. Same problem I had. The can fix it in Jhb or Cape Town

1 hour ago, WAP said:

Battery 1 was installed in Dec 2021 and battery no 2 was installed in Feb or March of 2022.

Does PBMS tools only read the primary battery info?
Your two battery screenshots both show the same Ver:  BMS S/N and Pack S/N at the bottom.

So many anomalies in the Hubble data and firmware releases.
As far as I can establish, LiNMC cells have a max voltage of 4,2V, i.e. I assume that to be the full state (100%). 

In Hubble's attempts to address the reported problems they propose amongst other things the Voltage charge with 53,8V.
The battery label itself states Bulk 53,6V and Float 52,6V, yet on their website it states 53,6V for both.

Looking at @WAP second battery pack which is supposedly 100% SOH, the battery Voltage is just about 52,6V but the cell voltages are not even close to 4,2V, being in the range of 4,029V - 4,063.
Then looking at the "problematic" pack 1, the cell voltages are 4,093 - 4,140V, much closer to the 4,2V max. The pack voltage is 53,6V which is the exact voltage for bulk on both the label and their site, yet this battery reports only 48A/h.

With values like this one can only guess that there is a problem in the data interpretation. Whether that is caused by the BMS firmware, Inverter Firmware or a combination of the two remains a mystery. 

Looking at my own Battery which happens to be of the same batch as the problematic pack of @WAP I have had no issues of any sorts if the Solar Assistant data representation of the BMS info is to be trusted, and that after 500cycles.

What I do as a matter of routine is the once monthly Voltage charge as the Lithium Protocol exhibits a gradual lower voltage over time for the 100%SOC. The cell voltages also drift lower over the same period, yet the BMS still reports 110Ah and 100% SOC. I will start off at 53,6V with the cells being in the 4,120 - 4,145V range. After a month it will be as low as 52,2V and cell voltages in the 3,9 to 4,01V range.

that's when I switch to User mode and apply the manual voltage settings, now as per the 53,8V that Hubble suggests to others. Two days of that and everything is back to normal. I then switch back to the Lithium Protocol. 

Here is the data right now with the BMS just top balancing currently. Tomorrow I shall switch back to the Li Protocol regime again.

My humble opinion is that Hubble is still struggling to figure out their BMS data interpretation and data interfacing with some Inverter Protocols.

On 2023/01/01 at 9:14 AM, WAP said:

If i look at the PBMSTools info am i correct in saying there is an issue with battery no 1?

Yes, there is. It has gone in to cell over voltage protection and there is also a pack over voltage alarm which means your battery charge voltage was too high. It could be that you have 1 or 2 cells that are charging faster than others, it would be interesting to see what these screens look like while the batteries are still charging.

On 2023/01/01 at 11:39 AM, zsde said:

With values like this one can only guess that there is a problem in the data interpretation. Whether that is caused by the BMS firmware, Inverter Firmware or a combination of the two remains a mystery.

I agree, they definitely seem to be having trouble with figuring out their BMS. I wonder if the over voltage error status somehow makes the battery report 100%SOC and then because it compares the Ah in vs the original capacity and reduces the SOH.

So i got an e-mail from Hubble support asking for more info and pics of my system. Replied today and later this morning i got a call from them. They connected to my Cloudlink and changed the master battery capacity to 100. Fsck knows why it was set to 48.

According to them it should be fine now. PBMSTools also shows both batteries capacity as 100 now. Will keep an eye on it and see if its resolved.

They did however mention that my Cloudlink needs a hardware update. I need to send it to them. My Cloudlink number is in the 100's and they are standing in the 3000's now. So i have one of the very first units. To me the thing is a paperweight anyway. Will see if i am gonna send it to them.

My bms caught on fire on a 6 month old battery (am2).

The difference on data output from ones inverter or cloudlink or a solar assist device will cause issues if a claim on warranty is needed.Whose data will they use?

As for this constant need for updates and having to rip your battery off the wall and send it to ct for a fix and the service that I have had ,has made me and my installer run a mile from hubble.

Do yourself a favour and read the warranty and see how easily it is invalidated.

3 hours ago, Nicholas Strachan said:

My bms caught on fire on a 6 month old battery (am2).

The difference on data output from ones inverter or cloudlink or a solar assist device will cause issues if a claim on warranty is needed.Whose data will they use?

As for this constant need for updates and having to rip your battery off the wall and send it to ct for a fix and the service that I have had ,has made me and my installer run a mile from hubble.

Do yourself a favour and read the warranty and see how easily it is invalidated.

The version 1.1 manual released 2021-05-24 for the AM-2

Version 2 Manual has a clause added.

This is sad as it an attempt by Hubble to keep vital information hidden from their customers.
RIOT over the 2 years that I've had it has removed SoH and other useful information.
My battery is still the Version 1, so not sure if this clause applies to me.

28 minutes ago, system32 said:

The version 1.1 manual released 2021-05-24 for the AM-2

Version 2 Manual has a clause added.

This is sad as it an attempt by Hubble to keep vital information hidden from their customers.
RIOT over the 2 years that I've had it has removed SoH and other useful information.
My battery is still the Version 1, so not sure if this clause applies to me.

Yeah.many things that arent cool with hubble