Not sure about Dyness but in most cases you need a cable that can connect from your computer to the battery to update the firmware. The importer can adviseHow is battery firmware updated?
(especially the Dyness batteries!)
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Not sure about Dyness but in most cases you need a cable that can connect from your computer to the battery to update the firmware. The importer can adviseHow is battery firmware updated?
(especially the Dyness batteries!)
I queried Dyness' process on another forum and they said they dont let users do that (currently) and youd have to take them in. Im mot sure if they are working on a remote method but mine have been solid so far (touch wood)How is battery firmware updated?
(especially the Dyness batteries!)
Same. Haven't seen the need to update firmware and I don't believe in fixing what isn't broken...I queried Dyness' process on another forum and they said they dont let users do that (currently) and youd have to take them in. Im mot sure if they are working on a remote method but mine have been solid so far (touch wood)
Are your batteries behaving now?Argh Fsck me sideways and never call me again. I thought mine were not part of that bad batch of batteries.
They say firmware will help, but it doesn't my issue was a damaged cell - it's been with them for 4 weeks, that's how fast they are. It's actually ridiculous.Argh Fsck me sideways and never call me again. I thought mine were not part of that bad batch of batteries.
If I could get rid of mine and replace them i would.There's an installer on power forum that replaced all his client's Hubble batteries. He is tired of them.
They seem fine for now. Haven't seen another anomaly.Are your batteries behaving now?
I'm sure there is a willing buyer out there for a bargain price. It's just a fsckng shlep.If I could get rid of mine and replace them i would.


Likely a software issue.I ordered a USB-RS232 cable from Solar Assistant to check my battery info with PBMSTools.
I noticed the Cloudlink showing SOH of 74%.
This is what PBMSTools gives me.
Battery 1:
View attachment 1449809
Battery 2:
View attachment 1449811
Battery 1 shows SOH of 48%. Guess i am gonna have to talk to the guys at Hubble. Fsck me
Also, on battery 1 there are alarm codes while there are none on battery 2. What is likely happening is that each time an alarm is triggered (like cell overvoltage) the SOH will be set to whatever the capacity is at the stage that the alarm is triggered. This results in the perpetual reduction in SOH day after day in small increments.I ordered a USB-RS232 cable from Solar Assistant to check my battery info with PBMSTools.
I noticed the Cloudlink showing SOH of 74%.
This is what PBMSTools gives me.
Battery 1:
View attachment 1449809
Battery 2:
View attachment 1449811
Battery 1 shows SOH of 48%. Guess i am gonna have to talk to the guys at Hubble. Fsck me
Likely a software issue.
Can you view the paramater settings (in PBMSTools) to see at what level the BMS will stop allowing a discharge. There is likely only an under voltage protect setting (that will stop the discharge when the set voltage is reached). There wont be such a setting for the capacity?
If you use the batteries without BMS communcation you should still be able to use the full 100AH of battery 1.
Also, on battery 1 there are alarm codes while there are none on battery 2. What is likely happening is that each time an alarm is triggered (like cell overvoltage) the SOH will be set to whatever the capacity is at the stage that the alarm is triggered. This results in the perpetual reduction in SOH day after day in small increments.
You can confirm this by looking at the paramater settings to see at what level the alarm and protection will be triggered. Then you will have to look at the real time PBMSTools screen while the battery is charging to see what happens when the alarm or protection is trigerred.
F20 DC over current fault of the hardware This is normally caused by the battery not being able to deliver email to current inverting needs. Overcurrent on the battery. To clear this fault you must focus on the battery and battery discharge settings. You need to check the C rating of the battery, can the battery provide the current your system needs you may have an 8 kW inverter but unless the battery can supply 8 kW it will simply crash out.
- Check the battery C rating
- Check the maximum discharge the inverter is set to
- On the controller check the maximum power inverter can supply this is a global setting you can see this on the main controller
- Check the battery cables are heavy enough to meet the demands
- Hi current overload on start up may also cause this causes fault

I got a call from Hubble this morning. They connected via the Cloudlink and changed my master battery to 100Ah. Have no idea why it was set to 48Ah. According to them, that's why it showed 48% SOH.Also, on battery 1 there are alarm codes while there are none on battery 2. What is likely happening is that each time an alarm is triggered (like cell overvoltage) the SOH will be set to whatever the capacity is at the stage that the alarm is triggered. This results in the perpetual reduction in SOH day after day in small increments.
You can confirm this by looking at the paramater settings to see at what level the alarm and protection will be triggered. Then you will have to look at the real time PBMSTools screen while the battery is charging to see what happens when the alarm or protection is trigerred.
Good news for us in team Hubble. Maybe they've sorted their support related issues?I got a call from Hubble this morning. They connected via the Cloudlink and changed my master battery to 100Ah. Have no idea why it was set to 48Ah. According to them, that's why it showed 48% SOH.
So for now all should be fine. Will keep an eye on it.
They did however mention that my Cloudlink needs to be sent to them for a hardware upgrade. My Cloudlink number is in the 100's and they are currently in the 3000's so I have one of the first units. It really is just a paperweight to me. Not sure if I am going to go through the hassle of sending it to them. Will see.
They responded via e-mail to my ticket yesterday. Called and sent a follow-up mail today after the call.
I would rate that as good service.
I had one of the original red ones, serial number was somewhere in the 80s (written by hand on a sticker), and it started showing random current spikes of around 80,000 amps which completely skewed the auto scaling of the graphs. I logged a ticket and had them actually calling me a number of times and chasing me up. I nearly fell off my chair in surprise, a complete turnaround from their usual poor attitude. They sent me a shiny new blue one, and I installed it last week. The new one has a far more complete set of cables, and they are still short, but just-just long enough. Power cable was also provided, together with crimped lugs and tiny bootlaces (I searched everywhere for the latter for two weeks but could not find anything). So I agree, they are constantly improving their product, and it was an excellent service experience. I hope that they will keep it up.I got a call from Hubble this morning. They connected via the Cloudlink and changed my master battery to 100Ah. Have no idea why it was set to 48Ah. According to them, that's why it showed 48% SOH.
So for now all should be fine. Will keep an eye on it.
They did however mention that my Cloudlink needs to be sent to them for a hardware upgrade. My Cloudlink number is in the 100's and they are currently in the 3000's so I have one of the first units. It really is just a paperweight to me. Not sure if I am going to go through the hassle of sending it to them. Will see.
They responded via e-mail to my ticket yesterday. Called and sent a follow-up mail today after the call.
I would rate that as good service.