August 25, 20214 yr Hi Community. For those with 8KW Sunsynk & Deye inverters you can now graph all data with your RIOT Cloudlink by simply plugging in a RJ45 cable into the RIOT MUL port and configuring the RIOT RS485 to Deye. Note that some older RIOT units might not support the graphing. Ensure you have version 3.0 of the firmware on your Cloudlink device. If you do not have this yet, you will have it by next week as we're slowly rolling this out over the next week to everyone. You will then automatically get a upgraded dashboard. Ensure you set the RIOT as per below if you have Verision 3.0. You can now remote console into your RIOT Cloudlink with the portal. We are still working on the 5KW Sunsynk graphing and remote control update. We're hoping to release that update soon.
October 14, 20214 yr Please provide information in terms of how one should set this up? Is it a normal network cable from RIOT MUL port to the RS485 port on the 8kw Sunsynk inverter? Should the setup be as follows: - Serial port on the RIOT to RS232 port on the battery - MUL port on the RIOT to RS485 port on the inverter (normal network cable or special cable?) - CAN port on the RIOT to CAN port on the inverter (normal network cable or special cable?)
October 18, 20214 yr Author @new2solar Sorry for the delayed response! The above is correct. If you have any additional queries or issues please log a support ticket via email: [email protected]
November 22, 20214 yr On 2021/08/25 at 1:01 PM, HubbleLithium said: Hi Community. For those with 8KW Sunsynk & Deye inverters you can now graph all data with your RIOT Cloudlink by simply plugging in a RJ45 cable into the RIOT MUL port and configuring the RIOT RS485 to Deye. Note that some older RIOT units might not support the graphing. Ensure you have version 3.0 of the firmware on your Cloudlink device. If you do not have this yet, you will have it by next week as we're slowly rolling this out over the next week to everyone. You will then automatically get a upgraded dashboard. Ensure you set the RIOT as per below if you have Verision 3.0. You can now remote console into your RIOT Cloudlink with the portal. We are still working on the 5KW Sunsynk graphing and remote control update. We're hoping to release that update soon. I have: Sunsynk 8kW inverter with "COMM: e419 MCU: 6005" firmware 4 x Hubble Lithium AM-2 RIOT_Cloudlink_V1R2 with RIOT_CLoudLink_V3R1R5 firmware I've setup the RIOT as per above image and the connections are as follows: Hubble #1/Master battery CAN Port <--> Sunsynk Inverter CAN Port RIOT SER Port <--> Hubble #1/Master battery RS232 Port RIOT MUL Port <--> Sunsynk Inverter RS485 Port All battery ID are set as per manual and interconnected via Battery Port. Unfortunately the RIOT is not detecting the inverter. I tested the SunSynk RS485 with Solar-Assistant and the port works. I tested RIOT to Sunsynk with 2 different RJ45 Ethernet cables and no work. Any idea why the RIOT is not connecting to the inverter? EDIT: In the newer v4 RIOT manual, they indicate that the RS485 cable is not a regular Ethernet cable. The cable must only have pins 7 & 8 connected. See my post below for further information. Edited October 5, 20223 yr by system32 Typo
December 15, 20214 yr 18 minutes ago, hoohloc said: I can't seem to access the portal. I get an error ''503 Service Unavailable'' Just checked
January 27, 20224 yr Hi. I purchased 3 x AM-2's, a cloudlink and the 8Kw Sunsynk inverter from the powerforum store. I am having the same problems: After a week of back and forth, my installer spoke to a senior technician at hubble who confirmed the cloudlink is installed and configured correctly and that full monitoring is not yet working with the 8kw Sunsynk. Do we have an eta on when this will be fixed? Also as per https://www.hubblelithium.co.za/sunsynk-hubble-setup.html full monitoring is available. Kindly advise @HubbleLithium Edited January 27, 20224 yr by Gefahrlich
February 6, 20224 yr I'm having same issues, I logged a ticket with Hubble last week and the response was that due to unforeseen errors full monitoring is not available with the 8kw sunsync
May 13, 20224 yr Some good news. After updated my 8kw sunsynk to the latest versions, and obtaining new CAN and MUL cables from Hubble, the monitoring is working: The settings page is still an issue though:
September 3, 20223 yr @HubbleLithium is theresny timeline by when this will be available on 5 kw deye.
September 3, 20223 yr Maybe I am missing the point, but I cannot see any benefit in using this system over for example Solar Assistant.
October 4, 20223 yr On 2021/11/22 at 12:30 PM, system32 said: I have: Sunsynk 8kW inverter with "COMM: e419 MCU: 6005" firmware 4 x Hubble Lithium AM-2 RIOT_Cloudlink_V1R2 with RIOT_CLoudLink_V3R1R5 firmware I've setup the RIOT as per above image and the connections are as follows: Hubble #1/Master battery CAN Port <--> Sunsynk Inverter CAN Port RIOT SER Port <--> Hubble #1/Master battery RS232 Port RIOT MUL Port <--> Sunsynk Inverter RS485 Port All battery ID are set as per manual and interconnected via Battery Port. Unfortunately the RIOT is not detecting the inverter. I tested the SunSynk RS485 with Solar-Assistant and the port works. I tested RIOT to Sunsynk with 2 different RJ45 Ethernet cables and no work. Any idea why the RIOT is not connecting to the inverter? @system32did you ever get this sorted out? I'm struggling with this atm (but with a 5kW SunSynk). Battery info is there but the inverter & PV info isn't.
October 5, 20223 yr On 2022/10/04 at 8:22 PM, StepbyStep said: @system32did you ever get this sorted out? I'm struggling with this atm (but with a 5kW SunSynk). Battery info is there but the inverter & PV info isn't. In order to get the RIOT to work you need to connect as follows: Or (option 2): In the 2nd config, the RIOT acts as/emulates a BMS - it translates the RS232 console to Canbus. This is not necessary as SunSynk firmware has direct support for Hubble AM-2 via Canbus. A RIOT is not required at all in a SunSynk / Hubble AM-2 installation. I've tested both and prefer the first option where the SunSynk is direct connected via canbus to the AM-2 BMS. NOTE: You need special RS485 cable to get RIOT to communicate with SunSynk (only pins 7 & 8 connected) Normal Ethernet LAN cables do not seem to work with the RIOT MOD port. See page 11 of "Cloudlink Setup Guide v4.0.pdf" https://www.hubblelithium.co.za/_files/ugd/c0fc0a_ed19d4bfa78f4873846638e251a62ed4.pdf Remember to configure the RIOT: If you have Solar Assistant you can share the SunSynk RS485 modbus port with a splitter. I prefer Solar Assistant over RIOT as Solar Assistant allows access to sensor data via MQTT for integration to Home Assistant & Grafana Solar Assistant is local - no cloud required Edited October 5, 20223 yr by system32
October 6, 20223 yr On 2022/10/04 at 6:22 PM, StepbyStep said: @system32did you ever get this sorted out? I'm struggling with this atm (but with a 5kW SunSynk). Battery info is there but the inverter & PV info isn't. I have the same issue with my 5k Sunsynk. Hubble promised the same functionality for the 5k as with the 8k, but this does not seem to have materialised. I have had Hubble take a look, but they cannot seem to resolve the issue. Another outstanding issue is the fact that my 3 Hubble batteries charge well until 89%, then it reduces to a trickle charge of about 2-3 amps per battery for 6 to 7 hours. The ticket is outstanding for over 1 month now. And another issue is that the Battery Storage graph reports random spikes of very high amperage, around 12000 amps plus. This causes the graph to automatically adjust to higher scale and makes it unreadable. Very irritating and Hubble cannot seem to be able to fix it, outstanding for over two months.
October 6, 20223 yr 55 minutes ago, YellowTapemeasure said: I have the same issue with my 5k Sunsynk. Hubble promised the same functionality for the 5k as with the 8k, but this does not seem to have materialised. I have had Hubble take a look, but they cannot seem to resolve the issue. Another outstanding issue is the fact that my 3 Hubble batteries charge well until 89%, then it reduces to a trickle charge of about 2-3 amps per battery for 6 to 7 hours. The ticket is outstanding for over 1 month now. And another issue is that the Battery Storage graph reports random spikes of very high amperage, around 12000 amps plus. This causes the graph to automatically adjust to higher scale and makes it unreadable. Very irritating and Hubble cannot seem to be able to fix it, outstanding for over two months. Is your SunSynk direct connected to the battery BMS (Option 1) - Current SunSynk firmware has direct support for Hubble batteries or indirect connected via RIOT (Option 2)? Edited October 6, 20223 yr by system32
October 7, 20223 yr On 2022/10/05 at 7:43 PM, system32 said: In order to get the RIOT to work you need to connect as follows: Or (option 2): In the 2nd config, the RIOT acts as/emulates a BMS - it translates the RS232 console to Canbus. This is not necessary as SunSynk firmware has direct support for Hubble AM-2 via Canbus. A RIOT is not required at all in a SunSynk / Hubble AM-2 installation. I've tested both and prefer the first option where the SunSynk is direct connected via canbus to the AM-2 BMS. NOTE: You need special RS485 cable to get RIOT to communicate with SunSynk (only pins 7 & 8 connected) Normal Ethernet LAN cables do not seem to work with the RIOT MOD port. See page 11 of "Cloudlink Setup Guide v4.0.pdf" https://www.hubblelithium.co.za/_files/ugd/c0fc0a_ed19d4bfa78f4873846638e251a62ed4.pdf Remember to configure the RIOT: If you have Solar Assistant you can share the SunSynk RS485 modbus port with a splitter. I prefer Solar Assistant over RIOT as Solar Assistant allows access to sensor data via MQTT for integration to Home Assistant & Grafana Solar Assistant is local - no cloud required I've got it set up for option 2. Why do you prefer it? Is there any difference? According to Hubble I need to update my original AM2 - that's the Master battery - and that'll fix the error but I need to get the older firmware because the newer one is giving me a Bin Error message.
October 7, 20223 yr 20 minutes ago, StepbyStep said: I've got it set up for option 2. Why do you prefer it? Is there any difference? According to Hubble I need to update my original AM2 - that's the Master battery - and that'll fix the error but I need to get the older firmware because the newer one is giving me a Bin Error message. I prefer option 1 as my SunSynk has direct support for Hubble AM-2. I've tried option 2, but not used it for any length of time. I did notice some differences in the LiBMS readings.
October 7, 20223 yr Cool - thanks for letting me know - and for the help connecting the riot and the inverter.
October 8, 20223 yr On 2022/10/06 at 5:45 AM, system32 said: Is your SunSynk direct connected to the battery BMS (Option 1) - Current SunSynk firmware has direct support for Hubble batteries or indirect connected via RIOT (Option 2)? Thanks, I tried various configurations, cannot remember the state, I need to check when I am back at that site.
October 14, 20232 yr Are you able to connect the Cloudlink to the Hubble AM-2 via the RS485 port on the AM2 if the RS232 port is not available? Deye 8KW inverter, splitter to link both Solar Assistant and Cloudlink to the inverter. Cloudlink power from the Hubble terminals.
January 3, 20242 yr Hubble clearly gave up on this product after selling to many unsuspecting buyers. Where do we send this box back to for a refund? No development in the last year according to their own website and the monitoring site is down. 23 NOVEMBER 2022 Cloudlink Version 4.5.8
January 3, 20242 yr last night I could get to the login screen but after logging in got a connection failed error, this morning I could not even get to the site. Now I can get to the site again, login goes further sits with spinning wheel thingy for long then it goes in. Classifieds next I guess.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.