Yuri

daisy chain RS485
think of the RS-485 Master as the esp32
device 1= master sunsynk 
device 2 = slave sunsynk 

daisy chain RS485
think of the RS-485 Master as the esp32
device 1= master sunsynk 
device 2 = slave sunsynk 

I have not manage to do it 
I will have a look at it tomorrow 

Lets first see if two will work...

Yes, Centurion South Africa 
I was using the 8KW manual...
Yes the Chint meter is using RS485 comms but if you read the Deye manual u will see Eastron is also compatible
 
You need the Deye manual to get the meter_RS485 connection  
 
I will test for you this weekend If it is possible to read the meter from 2 different devices simultaneous  
 
this is the Eastron meter I am using and where I got it 
https://www.aliexpress.com/i/32845403260.html
 
Yes the main supply to the house will feed through the power meter
 

The us2000 with out a C can only do 1  master and 7 slaves
the us3000C and up5000 can do 1 master and 15 slaves 

@Yuri thanks for sharing this. I've included some additional sensors and changed some of the friendly names for consistency with the latest Dashboard and other configs. @Sc00bs I've uploaded to Github for reference

https://github.com/slipx06/Sunsynk-Home-Assistant-Dash/blob/main/ESPHome-1P-Sunsynk-Deye.yaml
This is the single phase inverter yaml
I was using it with this  
 
 
Here is examples of integration 
 https://www.home-assistant.io/integrations/modbus/

I have played with this converter that is working and cheap from micro robotics 
https://www.robotics.org.za/communication-wireless-Industrial/serial-to-ethernet-converters/USR-DR302
You can use Slipx's yaml file for the ESP32 to read the registers used...
 

Works like a charm Thanks Yuri

I am using the brown and white/brown for my RS485 network on my 485 RS-485 TO TTL CONVERTER MODULE 
Then I just joined(soldered) all the brown wires together 
next joined (soldered) all the brown/white wires together 
 

you can see the white ethernet cable is from my esp32(rs485 to ttl converter)
one of the black is for master rs485 and one of the black ethernet cables are for the slave rs485

daisy chain RS485
think of the RS-485 Master as the esp32
device 1= master sunsynk 
device 2 = slave sunsynk 

I have just completed it8KW Sunsynk Master-Slave .txt

I have just completed it8KW Sunsynk Master-Slave .txt

I have been busy with the installation of my second 8KW…
I will only have a chance next year for testing

You can have a look if this will work
Add a slave id modbus controller
then double every register 
 

v3.13.0
🚀 Exciting New Features
- feat: add inverter images based on model. Set `modern: false` to enable

🐛 Patches & Bug Fixes
- fix: refactor and optimize code
- fix: position of ac temp when mppt is set to four on full card
### Other Changes
* Feature/refactoring by @Pho3niX90 in https://github.com/slipx06/sunsynk-power-flow-card/pull/131

**Full Changelog**: https://github.com/slipx06/sunsynk-power-flow-card/compare/v3.12.0...v3.13.0

I have 22x 600W(13200W) Canadian Solar but the 8KW Sunsynk can only do 10400W so it is restricted in the settings...
I am in Centurion

Today I only got 14.2KW in Centurion 
8KW Sunsynk with 22x600w panels 
I will look for a black Friday special to get a extra 8KW then i can get more panels…

You can use the utility meter function and make a daily, monthly or yearly counter  

@Sc00bs I manged to get this working. Add the following to your ESPHome config. Also updated in the github
sensor: - platform: modbus_controller # 255 Grid Peak Shaving raw register value modbus_controller_id: sunsynk id: grid_peak_shaving_raw register_type: holding address: 280 value_type: U_WORD select: - platform: modbus_controller #280 Select Grid Peak Shaving use_write_multiple: true modbus_controller_id: sunsynk name: "${friendly_name} Grid Peak Shaving" id: sunsynk_esphome_select_grid_peak_shaving address: 280 entity_category: config value_type: U_WORD optionsmap: "Disabled": 0 "Enabled": 256 lambda: |- // we are only interested in the 8th bit binary 0001 0000 0000 need to map the options 0, 256 in select //ESP_LOGE("main","Modbus Number incoming value = %d",x); //ESP_LOGE("main","Modbus eval value = %d",(x & 0x0100)); if ((x & 0x0100) == 0) return std::string("Disabled"); if ((x & 0x0100) == 256) return std::string("Enabled"); return {}; write_lambda: |- //ESP_LOGE("main","Modbus write gets = %d",value); uint16_t unmodified = id(grid_peak_shaving_raw).state; //ESP_LOGE("main","Modbus write unmodified = %d", unmodified); // optionsmap should only return 2 values... 0 , 256 so bitmask with complement 0x0100 to ensure we keep the original values in register. Then appply OR with the value that was chosen uint16_t modified = ((unmodified & ~0x0100) | value); //ESP_LOGE("main","Modbus write to write = %d", modified); return modified;  
You can now enable and disable and set the Grid Peak Shaving power using an automation