ScanlanGP

Finally got the generator to work properly.
Hopefully this will help some else. 
Here is what I had to do
1. Connect the generator to the AUX port
2. Connect the AUX port earth to the earth on the GRID port. I do not have the generator connected to a earth spike. 
3. Connect earth and neutral together on the generator 
4. On AUX menu, tick Gen Input and tick Gen peak shaving and set the shaving value to 80% of your generator capacity. Then set Gen Load OFF to 95% and Gen Load ON to 80% (choose your own values that work for you) 
5. On System menu, work mode 2, tick Zero Export, AND Limit to load. My generator would disconnect if Limit to load was not ticked. 
6. On System menu, work mode 1, make sure the SOC for the time slot you are running your generator in, is set to 100% and tick GEN box to charge from generator. 
7. On Battery menu, make sure the Charge Amps on Batt Type is the same as the Amps in the first block on the second screen Batt Charge. Also important is to make sure the charge amps is not set too high. Consider the power drawn from the generator to charge the batteries PLUS the power required to run the load and inverter. 
8. Tick Gen Charge, Gen Signal and Signal Island mode on Battery menu under Batt charge. 
 
What a mission to figure all this out.

Yay, getting data again😀
Thank you @abd7 and @mzezman, I just happened to have a splitter in a drawer (finally justified in keeping all that "junk").
For anyone looking for those splitters, I see Takealot as a 2-pack (also a single but for more money).
https://www.takealot.com/techme-rj45-2x-female-to-female-splitter-adapter-pack-of-2/PLID72195763

Hi @TinkerGuy
I have been thinking of doing this exact thing at home 🙂
I think that the easiest would be to use ESPhome as it is pretty easy to do, was actually playing around with some options using either a number of individually addressable LED's to create a type of fuel gauge or alternatively use a OLED or LCD Screen. 
I liked the idea of using WS2812 strips, trhey can be individually switched on and off and the colour can be changed when SOC gets low. Maybe have a second strip to indicate load shedding and then a 3rd one for the amount of power going in/out the battery. 
ChatGPT can actually write most of the code for you 🙂 

Thanks for sharing. Did not know about the horseshoe or plotly cards. Added to Dashboard

 

For sure.... That is the custom Flex-Horseshoe-Card. Been using it since a couple of inverters ago.
Edit: I am running it on an old 27-inch Dell monitor.
 

Thanks to @Bloubul7and all the other contributors. This is my HA dashboard. It has all I need to view at a glance. (PS: really impressed with the Sunsynk)
 

That depends on your installation.
I have the E/N Bond installed by the inverter for when the grid fails. This is the normal setup that most people have.
 
My generator is connected to the DB via a change over switch (not to the GEN port on the inverter). So when I change over to the generator on the DB, the inverter will see that as GRID and will not go into island mode (no E/N bond)
I therefor have a E/N bond on the generator
 
 

Interesting. I don't have this problem with the Sunsynk Firmware which was updated a few weeks ago. (SW Ver.M 6.0.2.2 / S  1.7.2.4 / C E.4.2.6)
Unfortunately I have not figured out how to write to the inverter using ESPHome. I'm sure it's possible though. 
I've also created a simpler version of the card for those that have everything on Essential and no AUX connection.
Attached SVG for those who want it sunsynk-comp.svg
 

sorry forgot to add you need to create the following template sensors as well
 
sensor: - platform: template sensors: sunsynk_totalsolar: friendly_name: "Total Solar Generation" value_template: "{{ (states('sensor.pv1_power') | float(0) + states('sensor.pv2_power') | float(0)) | round(0) }}" unit_of_measurement: 'W' sunsynk_solar_load: friendly_name: "Solar Load" value_template: "{{ (states('sensor.daily_pv_power_kwh') | float(0) - states('sensor.battery_charge_day') | float(0)) |round(1) }}" unit_of_measurement: 'kWh' device_class: energy sunsynk_essential_load: friendly_name: "Essential Load" value_template: "{{ (states('sensor.inverter_output_power') |float(0) - (states('sensor.aux_output_power') |float(0) - states('sensor.grid_inverter_load') |float(0) )) | round(0)}}" unit_of_measurement: 'W' device_class: power  

Finally got the generator to work properly.
Hopefully this will help some else. 
Here is what I had to do
1. Connect the generator to the AUX port
2. Connect the AUX port earth to the earth on the GRID port. I do not have the generator connected to a earth spike. 
3. Connect earth and neutral together on the generator 
4. On AUX menu, tick Gen Input and tick Gen peak shaving and set the shaving value to 80% of your generator capacity. Then set Gen Load OFF to 95% and Gen Load ON to 80% (choose your own values that work for you) 
5. On System menu, work mode 2, tick Zero Export, AND Limit to load. My generator would disconnect if Limit to load was not ticked. 
6. On System menu, work mode 1, make sure the SOC for the time slot you are running your generator in, is set to 100% and tick GEN box to charge from generator. 
7. On Battery menu, make sure the Charge Amps on Batt Type is the same as the Amps in the first block on the second screen Batt Charge. Also important is to make sure the charge amps is not set too high. Consider the power drawn from the generator to charge the batteries PLUS the power required to run the load and inverter. 
8. Tick Gen Charge, Gen Signal and Signal Island mode on Battery menu under Batt charge. 
 
What a mission to figure all this out.

If you want to try this card in home assistant follow these steps.
1. Create a new directory under www/community/ and name it sunsynk-card. If you don't have HACS installed you can create directory directly under www and reference in step 3 below.
2. Copy the attached sunsynkcard.js into the directory
3. Add the resource to your Dashboard 

4. Add the Custom: Sunsynk Card to your Dashboard view. Select Show Code editor

5. Replace all the code with the contents from the card configuration file card configuration.txt

6. Scroll down to bindings and replace the sensors with your own
bindings: - bind: return hass.states["sensor.pv1_power"].state + ' W' selector: '#pv1_power_186' type: html - bind: return hass.states["sensor.pv2_power"].state + ' W' selector: '#pv2_power_187' type: html - bind: return hass.states["sensor.sunsynk_totalsolar"].state + ' W' selector: '#pvtotal_power' type: html - bind: return hass.states["sensor.battery_voltage"].state + ' V' selector: '#battery_voltage_183' type: html - bind: return hass.states["sensor.battery_soc"].state + ' %' selector: '#battery_soc_184' type: html - bind: return hass.states["sensor.battery_output_power"].state + ' W' selector: '#battery_out_190' type: html - bind: return hass.states["sensor.inverter_output_power"].state + ' W' selector: '#inverter_out_175' type: html - bind: return hass.states["sensor.inverter_output_current"].state + ' A' selector: '#inverter_out_164' type: html - bind: return hass.states["sensor.aux_output_power"].state + ' W' selector: '#aux_power_166' type: html - bind: return hass.states["sensor.sunsynk_essential_load"].state + ' W' selector: '#ess_power' type: html - bind: return hass.states["sensor.grid_inverter_voltage"].state + ' V' selector: '#inverter_grid_voltage_154' type: html - bind: return hass.states["sensor.load_frequency"].state + ' Hz' selector: '#inverter_load_freq_192' type: html - bind: return hass.states["sensor.grid_inverter_load"].state + ' W' selector: '#inverter_load_grid_167' type: html - bind: return hass.states["sensor.grid_external_power"].state + ' W' selector: '#grid_external_power_172' type: html - bind: >- return parseInt(hass.states["sensor.grid_external_power"].state) - parseInt(hass.states["sensor.grid_inverter_load"].state) + ' W' selector: '#non_ess_power' type: html Maybe someone smart can package this as a proper HACS frontend resource

I have seen quite a few people asking about being able to see the SunSynk Flow UI in Home Assistant. So I went playing a bit to see if it is possible to create a custom component in home assistant that would mirror this.  Reading a whole lot of documentation on Home Assistant as well as getting to grips with all the possible measurements that is available from the Inverter, I finally have a VERY ALPHA version of it running in Home Assistant and it appears to reflect the UI on my inverter pretty well.

Maybe one day I will publish this in HACS and make this custom component available for use. For now there is still a whole lot of learning that needs to happen on building custom components for Home Assistant.
Yes I know ... I'm a bit of a #GEEK, but at least now I can see my Inverter's flow screen without going to the garage. 😉

Cause the installer didn't bond the earth and neutral
 

I have an 8Kw Sunsynk inverter installed with 24 x 455W panels & 2 x 6kw/hr Bull batteries.
Due to a number of my high load devices being connected to DB Boards in my cottage & stables, I was unable to make use of the essential/non-essential splits on the Sunnsynk Inverters and have been on a journey to connect to the inverter so I can control all my high load devices with Home Assistant & Sonoff eWelink connected breakers and switches.
My connection to my Inverter is now up and running, thanks to Bloubul7's Flow's and all the information that everyone has posted, has been a huge help and I wouldn't have been able to get it working without all the information you guys have provided. I must admit that there has been a HUGE learning curve on Hassio/NodeRed/InfluxDB/Grafana and I probably have enough knowledge right now to be classified as dangerous, lol.
I am only using the Modbus Read & Inverter Monitoring Flows but they were a great starting point to get everything up and running  and relatively easy to add any extra data that you want to collect from the inverter to it. 
I did find that when I enabled all of Bloubul's flows, while I was figuring out how everything worked, some of the settings on my inverter changed to switch it to a "loadshedding" mode where the batteries stayed at 100% charge, not sure what was the cause or if it was even related to the flows but am only using the two flows mentioned earlier now. Perhaps something to do with the switching of the inverter when it detects load shedding on the Eskom website. In any case, not serious and was easy to just switch it back again.  
I am running everything on an Intel Nuc i5 which seems to be more than capable  and have Hassio/MQTT/InfluxDB/NodeRed all running on it with other integrations for my Sonoff gear, my Paradox house alarm and my CCTV system.
I am using a USB-RS485 connector which I purchased from https://www.robotics.org.za/RS485-MINI?search=rs485  for R38
 
Was pretty simple to connect up using a T-568B wired ethernet cable, I wired it orange/brwn&white - A, Orangewhite/brown - B, not sure if you need both connections going to A&B but it works so not going to worry about changing anything

 
One thing that I am concerned about is the system slowing down over time due to the size of the database increasing at a rather rapid rate (sampling data every 3s). I did notice that Bloubul7 was saying that his original Raspberry Pi system came to a crawl after a week of use and suspect that this was probably as a result of the database getting to large for the Pi to handle comfortably.  I understand that InfluxDB is able to rationalise it's data as time progresses and as it does not seem necessary to have per second data kept foreveer I am going to try and get the consolidation of the data, as it ages, on my box sorted out so as to keep it running snappily.
Has anyone else had any experience with slimming down the influxDB database over time? 
My next challenge is going to be to set up some Flows in NodeRed to switch on/off my connected Sonoff devices based on the Grid Power connections status/Battery SOC/Solar incoming power. 
My first Dashboard in Grafana, still working on my Grafana skills 

 
These two threads have been hugely helpful in getting everything working.
sunsynk_modbus - no chinese.docx

There is not suppose to be an earth leakage on the input to the inverter:
On the "eskom" non essential circuit, a earth leakage is required, but the supply to the inverter must be taken before the earth leakage. An earth leakage is also required after (at the output)  of the inverter.
What is happening is that the inverter is bonding the neutral and earth, which is causing the tripping.

Hi @ScanlanGP
Another option if you don't want to use the AUX port is to use a transfer switch to switch between the generator and Eskom. 
I then use "Grid Peak Shaving" to limit the amount of power the inverter pulls from the generator.

Finally got the generator to work properly.
Hopefully this will help some else. 
Here is what I had to do
1. Connect the generator to the AUX port
2. Connect the AUX port earth to the earth on the GRID port. I do not have the generator connected to a earth spike. 
3. Connect earth and neutral together on the generator 
4. On AUX menu, tick Gen Input and tick Gen peak shaving and set the shaving value to 80% of your generator capacity. Then set Gen Load OFF to 95% and Gen Load ON to 80% (choose your own values that work for you) 
5. On System menu, work mode 2, tick Zero Export, AND Limit to load. My generator would disconnect if Limit to load was not ticked. 
6. On System menu, work mode 1, make sure the SOC for the time slot you are running your generator in, is set to 100% and tick GEN box to charge from generator. 
7. On Battery menu, make sure the Charge Amps on Batt Type is the same as the Amps in the first block on the second screen Batt Charge. Also important is to make sure the charge amps is not set too high. Consider the power drawn from the generator to charge the batteries PLUS the power required to run the load and inverter. 
8. Tick Gen Charge, Gen Signal and Signal Island mode on Battery menu under Batt charge. 
 
What a mission to figure all this out.

Finally got the generator to work properly.
Hopefully this will help some else. 
Here is what I had to do
1. Connect the generator to the AUX port
2. Connect the AUX port earth to the earth on the GRID port. I do not have the generator connected to a earth spike. 
3. Connect earth and neutral together on the generator 
4. On AUX menu, tick Gen Input and tick Gen peak shaving and set the shaving value to 80% of your generator capacity. Then set Gen Load OFF to 95% and Gen Load ON to 80% (choose your own values that work for you) 
5. On System menu, work mode 2, tick Zero Export, AND Limit to load. My generator would disconnect if Limit to load was not ticked. 
6. On System menu, work mode 1, make sure the SOC for the time slot you are running your generator in, is set to 100% and tick GEN box to charge from generator. 
7. On Battery menu, make sure the Charge Amps on Batt Type is the same as the Amps in the first block on the second screen Batt Charge. Also important is to make sure the charge amps is not set too high. Consider the power drawn from the generator to charge the batteries PLUS the power required to run the load and inverter. 
8. Tick Gen Charge, Gen Signal and Signal Island mode on Battery menu under Batt charge. 
 
What a mission to figure all this out.

Finally got the generator to work properly.
Hopefully this will help some else. 
Here is what I had to do
1. Connect the generator to the AUX port
2. Connect the AUX port earth to the earth on the GRID port. I do not have the generator connected to a earth spike. 
3. Connect earth and neutral together on the generator 
4. On AUX menu, tick Gen Input and tick Gen peak shaving and set the shaving value to 80% of your generator capacity. Then set Gen Load OFF to 95% and Gen Load ON to 80% (choose your own values that work for you) 
5. On System menu, work mode 2, tick Zero Export, AND Limit to load. My generator would disconnect if Limit to load was not ticked. 
6. On System menu, work mode 1, make sure the SOC for the time slot you are running your generator in, is set to 100% and tick GEN box to charge from generator. 
7. On Battery menu, make sure the Charge Amps on Batt Type is the same as the Amps in the first block on the second screen Batt Charge. Also important is to make sure the charge amps is not set too high. Consider the power drawn from the generator to charge the batteries PLUS the power required to run the load and inverter. 
8. Tick Gen Charge, Gen Signal and Signal Island mode on Battery menu under Batt charge. 
 
What a mission to figure all this out.

Some that ive setup:
When loadshedding hits and the grid voltage drops below 180 my google home announces that LS has started and people must conserve power. If it is after 6pm it then switches off some of the lights outside to save a bit more juice in the event of a longer outage. When the grid voltage comes back to range then those lights are switched back on and google home announces that LS is over.  If battery SOC < x% and LS hits then the pool pump is turned off (if it was on). Pump then turns on again when the SOC > y% Mine are setup on Homae Assistant via the Solar Assistant MQTT integration though - but the principles holds. Ive seen some pretty intricate automations running on Node Red that you might be itnerested in:
 

Here is a sample of the code if anyone else wants to try this approach.
uart:   id: mod_bus   tx_pin: 17   rx_pin: 16   baud_rate: 9600   stop_bits: 1 modbus:   id: modbus1 modbus_controller:   - id: sunsynk     address: 0x01     modbus_id: modbus1     setup_priority: -10     update_interval: 20000ms sensor:   - platform: modbus_controller     modbus_controller_id: sunsynk     name: "Grid power"     id: grid_power     register_type: holding     address: 169     unit_of_measurement: W     device_class: power     state_class: measurement  

@Sc00bs - seems like I finally have my Home Assistant energy dashboard working with my Sunsynk 🙂

Using only the following sensor config & the addon - https://github.com/kellerza/sunsynk
 
SENSORS:   - total_pv_power   - total_grid_export   - total_grid_import   - total_pv_power   - total_battery_charge   - total_battery_discharge  

Home Assistant recently included a Solar Forecast in the app https://www.home-assistant.io/integrations/forecast_sola
Although not obviously 100% accurate it does give me an insight into what the days solar power production is going to look like to that Node Red can decide which loads to switch on for the day based on the predictions. 
I have a 1kw pool pump, so if my production for the day is going to be under 30kw, I just don't switch it on for the day. 
Switch it on from 9 - 3 If I have more than 40kw and just 3hrs of pump if it is between 30 & 40kw/hr.
https://www.home-assistant.io/integrations/forecast_solar/
Would also like to add the data from my inverter into the Home Assistant Energy system but still working that out
 

Super easy Solarman data logger integration with HA.
https://github.com/StephanJoubert/home_assistant_solarman
Edit: Just to clarify, I'm not the author. The author is quite active and responds to queries within a day or so.

Interesting video. I think that the Sunsynk's touchscreen interface is far better than the Sol-Ark app though, but maybe I am biased, would love to see the new Sunsynk dongle app. Hint-hint @Tariq
So let me try to get this right, second time around, edits in green red, version 1.1 1.2:
The inverter will use any source at its disposal to keep essentials, or "Load" alive, within constraints set regarding the battery in the System Mode screen, Work Mode 1 and 2 tabs; The whole System Mode screen revolves around the battery: The inverter will draw from, or charge battery to the desired SoC, at the desired time: from PV (or Grid, or Gen if ticked, and if both ticked, then in that order. Note that Grid and Gen cannot be used simultaneously, it's either one or the other) drawing from the battery, or charging the battery at the rate (W) specified in the stated power level; If Load Priority is ticked, it will use PV at the specified rate (W) to first service essential loads; and if any PV is left over, it will use the left-over PV to charge the battery (even if the battery SoC is higher than what is set); if PV is too little, or the rate (W) set too low to service essential loads, then it will draw what it needs from Grid / Battery / Gen  to supplement PV; If load priority is unticked: It will use all PV to charge battery, at the specified rate (W) (and will continue to charge past the desired SoC which is set on the timer) If Grid or Gen or both is ticked, it will use Grid or Gen (or if both ticked, then in that order) to achieve the desired SoC of the battery. Note that Grid and Gen cannot be used simultaneously, it's either one or the other; If the desired SoC is achieved for the timeslot, unlike PV it will stop using Grid / Gen to charge the battery. It does not like to waste PV. Note that battery charge / discharge rates in the timer are overridden by the values in the Battery Setup screen, Batt Type, Batt Charge and Shut Down tabs. I hope to get this right in order to help newbies, I know that I spent 3 days trying to figure it out through trial and error 🙄 So please double check me, any edits are welcome.