Good day all,

Just wondering if anyone else is experiencing issues logging in to the cloudlink portal.

Secondly has anyone also got issues with a very poor SOH reading from their Hubble batteries and inconsistent readings on consumption and power production when compared to the Solarman readings?

I have the following setup 10xAM2 connected to 2x8kw Sunsynk 1x cloudlink connected to the master inverter.

 

Hi Ben i have 2 Hubbles and one had max 28 Ah. I sent it in and this was fixed. 

What I now have are 2 batteries with exact same Volts but differing SOC %. I gave tried the suggested AGM charging to balance SOC but no success. Have logged another call. 

I have 2 hubble am 2 and had an issue the other day with my batteries not going beyond about 72% soc .It was suggested that I change a setting from soc to voltage on the inverter under the charge tab and it worked.I identified the battery that wasnt charging and switched the good one off and it seemed to work

Hubble Cloudlink has not worked since I purchased AM5 batteries with a new installation, and adding the Cloudlink device to the system also.

Its set-up correctly, connects to our network, but Hubble says they are having developer issues, and no ETA as to when the problem will be resolved.

Not impressed at all - so far.

I have 3 AM2 packs and one was giving isues. It just would not charge properly and when in use, it drained extremely fast, much faster than the others. I only was able to determine this by comparing the LED's at the base of the packs. I then used PbmsTools to check the SOH of my packs and one was at 53% while the other 2 were at 100%. So basically this was my confirmation that something was wrong with my one battery pack. I returned it to Hubble and they sorted it. All good now.

As for the Hubble Cloudlink device, one small piece of advice I can offer is that you should not let your router connect to it using DHCP. Most routers have a means of reserving a STATIC IP for a device even while using the DHCP option on your router as long as you specify the MAC address and the IP you would like the cloudlink to use in the IP reservation. This will ensure that no other device can make use of the specific IP address that you have reserved for your cloudlink device. I found this out the hardway. Before making use of a reserved IP for my cloudlink device, I found that it struggled to find an available IP using DHCP (other devices just occupied these IP's that the cloudlink was trying to connect to) which just manually assigns an IP to any device that was allowed to connect to my network. By reserving an IP, the cloudlink will only connect to the IP you specified and your router will not allow any other device to connect using that specific IP. Reserving an IP for my cloudlink saved me from countless headaches. If anyone has not done this yet, I suggest going this route.

Edited June 4, 20233 yr by Paul Tappan

My Hubble Cloudlink won't even let me log in. Says there is no such user but there definitely is. Anyone else?