Skip to content
View in the app

A better way to browse. Learn more.

Power Forum - Renewable Energy Discussion

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Settings to lower battery cycles count - hubble 5.5

Featured Replies

I just spoke to Blake at Hubble said they busy doing a software upgrade , i assume to the online platform.

He mentioned this is the reason why some can see the cycles and other cannot. Going by my experiences that i have had with them over the past 3 weeks, i think this is

BS %#$

  • Replies 61
  • Views 10.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • You didn't lose your logic. The OEMs are bending the rules and get away with it. If you have the money, you could probably take them to court, but they have the legal team that will fight it and they

  • Unfortunately you cant do both it seems . Personally i would complain to Hubble because there is no reason the BMS should be counting cycles like a 3 year old toddler. For interest sake it might be wo

  • Those stats will definitely be at least 2 cycles per day. My Hubble has been in use since last year in Aug and I am now at 344 cycles, i.e. 21 cycles away from 365 which gets me to 6 days short of o

Posted Images

I just spoke to Blake at Hubble said they busy doing a software upgrade , i assume to the online platform.

He mentioned this is the reason why some can see the cycles and other cannot. Going by my experiences that i have had with them over the past 3 weeks, i think this is

BS %#$.

*** Guys make sure that your Hubbles have the latest software version loaded, 1 of my 4 batteries seems to have an older version which is causing some issues w.r.t data and SOC. Upgrade needs to be done via a USM to RJ11 cable ( Your laptop to the battery) even though you might have the RIOT installed. Upgrade cannot be done via the RIOT. Silly !!!!

1 hour ago, Bluefronted said:

I just spoke to Blake at Hubble said they busy doing a software upgrade , i assume to the online platform.

He mentioned this is the reason why some can see the cycles and other cannot. Going by my experiences that i have had with them over the past 3 weeks, i think this is

BS %#$.

*** Guys make sure that your Hubbles have the latest software version loaded, 1 of my 4 batteries seems to have an older version which is causing some issues w.r.t data and SOC. Upgrade needs to be done via a USM to RJ11 cable ( Your laptop to the battery) even though you might have the RIOT installed. Upgrade cannot be done via the RIOT. Silly !!!!

Ja that just sounds like BS. Why do we even have Riots then in the first place.

1 hour ago, Bluefronted said:

*** Guys make sure that your Hubbles have the latest software version loaded

Our original Hubbles are 110A/h i.e. true 5,5kW capacity. And mine still reports it's full capacity
With the update firmware this is reduced to 105A/h meaning an artificial reduction in capacity that probably attempts to cover up the early losses that some experienced, especially the Sunsynk users.
The question is how long before the 105A/h capacity reduction is then solved with a new Firmware update where it then becomes 100A/h?
How do you continue to market and sell a Battery that states 5,5kWh when in fact that has been superseded by lower numbers in the real world by the push of the new Firmware?
They sent me the new Firmware which I am reluctant to use as my battery has had zero issues except the daily cycle count which triggers no matter what the SOC.
And nowhere does the Firmware solve this cycle count either.

Edited by zsde

  • Author
4 minutes ago, zsde said:

Our original Hubbles are 110A/h i.e. true 5,5kW capacity. And mine still reports it's full capacity
With the update firmware this is reduced to 105A/h meaning an artificial reduction in capacity that probably attempts to cover up the early losses that some experienced, especially the Sunsynk users.
The question is how long before the 105A/h capacity reduction is then solved with a new Firmware update where it then becomes 100A/h?
How do you continue to market and sell a Battery that states 5,5kWh when in fact that has been superseded by lower numbers in the real world by the push of the new Firmware?
They sent me the new Firmware which I am reluctant to use as my battery has had zero issues except the daily cycle count which triggers no matter what the SOC.
And nowhere does the Firmware solve this cycle count either.

I think if your hubble isn't causing issues, then don't update the firmware. Otherwise you'll also be on 105ah like us. 

Just now, Terminal3k said:

I think if your hubble isn't causing issues, then don't update the firmware. Otherwise you'll also be on 105ah like us. 

My thoughts exactly. Don't mess with it if it works.
There is the issue though of Hubble and their "maybe" warranty.
If ever something goes wonky in the future, the response will be, "We told you to update the firmware and you didn't". Thus the customer will become the origin of the problem.
If I do update, I reduce my battery capacity with no guarantee that it's any better and the false cycle count continues as now.
 

16 minutes ago, WAP said:

Ja that just sounds like BS. Why do we even have Riots then in the first place.

Exactly. I got one cause it would give you proper details on the AM-2 and would support remote upgrades via Hubble support. Well its now disconnected and boxed since it cant do any of the two things.

  • Author
6 minutes ago, zsde said:

My thoughts exactly. Don't mess with it if it works.
There is the issue though of Hubble and their "maybe" warranty.
If ever something goes wonky in the future, the response will be, "We told you to update the firmware and you didn't". Thus the customer will become the origin of the problem.
If I do update, I reduce my battery capacity with no guarantee that it's any better and the false cycle count continues as now.
 

But have the contacted you to tell you that you have to upgrade? Or any formal communication? 

If not you can't be held liable for not upgrading. 

I only upgraded because of my SOC issues. I was only getting 77ah

Edited by Terminal3k

11 minutes ago, Terminal3k said:

But have the contacted you to tell you that you have to upgrade? Or any formal communication? 

If not you can't be held liable for not upgrading. 

I only upgraded because of my SOC issues. I was only getting 77ah

Had a phone call and email comms.

5 hours ago, Bluefronted said:

image.thumb.png.ec820eabc46f32366cb047deb1e5a4d3.png

 

Below is all i can see once i follow your steps

Not sure why it does not display for you - may be a RIOT device / firmware issue.
My RIOT is connected to the RS232 RJ12 console port on the first AM-2 battery.

I notice that my RIOT seems to be stuck at 60 cycles.

image.thumb.png.9bc6818e3d82d850164df4387b9c5524.png

PBMS Tools - connected to AM-2 Serial Console Port:
image.thumb.png.d63aa1385bd715269ae41d19266b3161.png

 

Solar-Assistant - connected to AM-2 Serial Console Port:

image.thumb.png.9645410ea7f3e841a56e30afa645fef5.png

There is a know issue with SA with the Cell temperatures
There is a know issue with SA and Pack numbering on serial port
Both issues have been reported to SA Support.

I would be interested to compare individual cell voltages and total voltage at 100% SOC as per the BMS.
Just took my snapshot right after the battery was at 100%

image.png.618a14e642d21942839c5ad4fd8125bf.png

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.