Sungrow Logger1000 HomeAssistant ModBus

[NBS23]

Is it also possible to read out the Sungrow Logger 1000 (also called COM100) via ModBus in HomeAssistant?
https://info-support.sungrowpower.com/application/pdf/2022/04/15/COM100D_E-UEN-Ver11-202201.pdf
I have a Sungrow SH10RT + SG20RT and an energy meter connected to the logger.

[adriano26010]

@NBS23 have you managed to connect this logger to HomeAssistant?

[RafAustralia]

YES - I have it fully connected and working... can read all registers on multiple inverters and batteries... but there are no logger controls as such yet - I have not looked into that part yet... although I have received some updates from china... some time ago... I was time poor.

[purcell-lab]

Here is a modbus.yaml file that works for the Logger1000.

# File prepared for sungrow logger 1000a via modbus
#file written by Rafal Tomaszewski
# last update: 2024-07-031
#
# Note: This YAML file will only work with Home Assistant >= 2023.10

modbus:
  - name: SungrowLOGGER
    type: tcp
    host: !secret sungrow_modbus_host_ip_247
    port: !secret sungrow_modbus_port_247
    sensors:
      - name: Logger device type code
        unique_id: logger_dev_code
        device_address: !secret sungrow_modbus_slave_247
        address: 7999 # reg 8000
        input_type: input
        data_type: uint16
        scan_interval: 600

      - name: Logger total devices connected
        unique_id: logger_total_devices_connected
        device_address: !secret sungrow_modbus_slave_247
        address: 8004 # reg 8005
        input_type: input
        data_type: uint16
        precision: 1
        unit_of_measurement: Set
        scan_interval: 600

      - name: Logger total faulty devices
        unique_id: logger_total_faulty_devices
        device_address: !secret sungrow_modbus_slave_247
        address: 8005 # reg 8006
        input_type: input
        data_type: uint16
        precision: 1
        unit_of_measurement: Set
        scan_interval: 600

      - name: Logger digital input state
        unique_id: logger_digital_input_state
        device_address: !secret sungrow_modbus_slave_247
        address: 8020 # reg 8021
        input_type: input
        data_type: uint32
        precision: 1
        scan_interval: 600

      - name: Logger ADC1 Voltage
        unique_id: logger_adc1_voltage
        device_address: !secret sungrow_modbus_slave_247
        address: 8028 # reg 8029
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: V
        device_class: voltage
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC1 Current
        unique_id: logger_adc1_current
        device_address: !secret sungrow_modbus_slave_247
        address: 8029 # reg 8030
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: mA
        device_class: current
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC2 Voltage
        unique_id: logger_adc2_voltage
        device_address: !secret sungrow_modbus_slave_247
        address: 8030 # reg 8031
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: V
        device_class: voltage
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC2 Current
        unique_id: logger_adc2_current
        device_address: !secret sungrow_modbus_slave_247
        address: 8031 # reg 8032
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: mA
        device_class: current
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC3 Voltage
        unique_id: logger_adc3_voltage
        device_address: !secret sungrow_modbus_slave_247
        address: 8032 # reg 8033
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: V
        device_class: voltage
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC4 Voltage
        unique_id: logger_adc4_voltage
        device_address: !secret sungrow_modbus_slave_247
        address: 8033 # reg 8034
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: V
        device_class: voltage
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC3 Current
        unique_id: logger_adc3_current
        device_address: !secret sungrow_modbus_slave_247
        address: 8034 # reg 8035
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: mA
        device_class: current
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger ADC4 Current
        unique_id: logger_adc4_current
        device_address: !secret sungrow_modbus_slave_247
        address: 8035 # reg 8036
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: mA
        device_class: current
        state_class: measurement
        scale: 0.01
        scan_interval: 10

      - name: Logger Max total nominal active power
        unique_id: logger_max_total_nominal_active_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8057 # reg 8058
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
        scale: 1.0
        scan_interval: 10

      - name: Logger Min total nominal active power
        unique_id: logger_min_total_nominal_active_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8058 # reg 8059
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
        scale: 1.0
        scan_interval: 10

      - name: Logger Max total nominal reactive power
        unique_id: logger_max_total_nominal_reactive_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8059 # reg 8060
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: kVar
        device_class: power
        state_class: measurement
        scale: 1.0
        scan_interval: 10

      - name: Logger Min total nominal reactive power
        unique_id: logger_min_total_nominal_reactive_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8060 # reg 8061
        input_type: input
        data_type: int16
        precision: 1
        unit_of_measurement: kvar
        device_class: power
        state_class: measurement
        scale: 1.0
        scan_interval: 10

      - name: Logger inverter preset active power
        unique_id: logger_inverter_preset_active_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8065 # reg 8066
        input_type: input
        data_type: uint16
        precision: 1
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
        scale: 1.0
        scan_interval: 10

      - name: Logger inverter preset reactive power
        unique_id: logger_inverter_preset_reactive_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8066 # reg 8067
        input_type: input
        data_type: uint16
        precision: 1
        unit_of_measurement: kvar
        device_class: power
        state_class: measurement
        scale: 1.0
        scan_interval: 10

      - name: Logger state
        unique_id: logger_state
        device_address: !secret sungrow_modbus_slave_247
        address: 8067 # reg 8068
        input_type: input
        data_type: uint16
        scan_interval: 10

      - name: Logger unlatch state
        unique_id: logger_unlatch_state
        device_address: !secret sungrow_modbus_slave_247
        address: 8068 # reg 8069
        input_type: input
        data_type: uint16
        scan_interval: 10

      - name: Logger total active power
        unique_id: logger_total_active_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8069 # reg 8070
        input_type: input
        data_type: uint64
        precision: 1
        unit_of_measurement: W
        device_class: power
        state_class: measurement
        scale: 1
        scan_interval: 10

      - name: Logger daily power yield
        unique_id: logger_daily_power_yield
        device_address: !secret sungrow_modbus_slave_247
        address: 8073 # reg 8074
        input_type: input
        data_type: uint32
        swap: word
        precision: 1
        unit_of_measurement: kWh
        device_class: energy
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Total rective power
        unique_id: logger_total_reactive_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8075 # reg 8076
        input_type: input
        data_type: int64
        precision: 1
        unit_of_measurement: var
        device_class: power
        state_class: measurement
        scale: 1
        scan_interval: 10

      - name: Logger total power yield
        unique_id: logger_total_power_yield
        device_address: !secret sungrow_modbus_slave_247
        address: 8079 # reg 8080
        input_type: input
        data_type: uint64
        precision: 1
        unit_of_measurement: kWh
        device_class: energy
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Min adjustable active power
        unique_id: logger_min_adjustable_active_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8083 # reg 8084
        input_type: input
        data_type: uint32
        swap: word
        precision: 1
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
        scale: 0.1
        scan_interval: 10
        
      - name: Logger Max adjustable active power
        unique_id: logger_max_adjustable_active_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8085 # reg 8086
        input_type: input
        data_type: uint32
        swap: word
        precision: 1
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Min adjustable reactive power
        unique_id: logger_min_adjustable_reactive_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8087 # reg 8088
        input_type: input
        data_type: int32
        swap: word
        precision: 1
        unit_of_measurement: kvar
        device_class: power
        state_class: measurement
        scale: 0.1
        scan_interval: 10
        
      - name: Logger Max adjustable reactive power
        unique_id: logger_max_adjustable_reactive_power
        device_address: !secret sungrow_modbus_slave_247
        address: 8089 # reg 8090
        input_type: input
        data_type: int32
        swap: word
        precision: 1
        unit_of_measurement: kvar
        device_class: power
        state_class: measurement
        scale: 0.1
        scan_interval: 10


# Holding Registers for Logger 1000

      - name: Logger Set On Off For Sub Inverter Array
        unique_id: logger_set_on_off_sub_inverter
        device_address: !secret sungrow_modbus_slave_247
        address: 8001 # reg 8002
        input_type: holding
        data_type: uint16
        precision: 1
        unit_of_measurement: Set
        scan_interval: 10

      - name: Logger Set Active Power Value For Sub Inverter Array
        unique_id: logger_set_active_sub_inverter_power_value
        device_address: !secret sungrow_modbus_slave_247
        address: 8002 # reg 8003
        input_type: holding
        data_type: uint32
        precision: 1
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Set Active Power Ratio For Sub Inverter Array
        unique_id: logger_set_active_sub_inverter_power_ratio
        device_address: !secret sungrow_modbus_slave_247
        address: 8004 # reg 8005
        input_type: holding
        data_type: uint32
        precision: 1
        unit_of_measurement: "%"
        device_class: power_factor
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Set Reactive Power Value For Sub Inverter Array
        unique_id: logger_set_reaactive_sub_inverter_power_value
        device_address: !secret sungrow_modbus_slave_247
        address: 8006 # reg 8007
        input_type: holding
        data_type: int32
        swap: word
        precision: 1
        unit_of_measurement: kvar
        device_class: reactive_power
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Set Reactive Power Ratio For Sub Inverter Array
        unique_id: logger_set_reactive_sub_inverter_power_ratio
        device_address: !secret sungrow_modbus_slave_247
        address: 8008 # reg 8009
        input_type: holding
        data_type: int32
        swap: word
        precision: 1
        unit_of_measurement: "%"
        device_class: power_factor
        state_class: measurement
        scale: 0.1
        scan_interval: 10

      - name: Logger Set Active Power Factor
        unique_id: logger_set_active_power_factor
        device_address: !secret sungrow_modbus_slave_247
        address: 8010 # reg 8011
        input_type: holding
        data_type: int32
        swap: word
        precision: 1
        unit_of_measurement: "%"
        device_class: power_factor
        state_class: measurement
        scale: 0.001
        scan_interval: 10

[RafAustralia]

I will post it shortly.... I am just discussing with Martin Kaiser how to place it for greater good rather than in a reply....

[Billkyriaf]

Do you have any manuals with the complete register mapping of the logger? After an hour's search, I haven't found anything.

[RafAustralia]

@Billkyriaf

hello.
it has never been officially released.
You will not find one as far as I know.
I have reverse engineered / coded these from my emails with sungrow r&d department.
we have worked on these for a long while.
not all registers behave correctly but it the most complete list there is at the moment out there.
scroll down to the link (few posts down)

[Billkyriaf]

bummer thanks for all the work it is indeed the only source of information at the moment

[RafAustralia]

@Billkyriaf
Yeah. Took a very long while but its good enough to get the most important registers to work.
I think its not going to be released for a very long while as they are still developing these and testing them.

I do have new set of registers which was sent to me but they fail miserably thus far so Im not going to post these until Ive made progress with them. (If ever)

[RafAustralia]

@strom-peter , @NBS23 , @purcell-lab

hi all. Happy new year.

yes I wrote modbus for dtsu666-20 simply by the way of long exchange of emails with sungrow r&d from china and translating these one by one from their hex values and chinese manuals (painful as it sounds) - it was painful.

There are many manuals out there which are wrong by the way and not designed for dtsu666-20

Yes I can read the registers of dtsu666-20.
pretty much all registers I was given.

These are pretty good but do not replace the fully setup TYPICAL inverter registers. So what I mean here is there are some registers which will not be working both via logger1000a and dtsu666-20.

To read either logger or dtsu666-20 you need full access to logger and find out what modbus number the logger has assigned for each equipment.
it will have a list - on its webpage.
logger is typically modbus 247, and in my case dtsu666-20 is modbus 5, and you will need each modbus to correspond with that.
Each one of you may be different.

without confirming these you are stuffed. Nothing will read.

also inside the logger. You need to open more ports. 502,503,504,etc. depends on how many numbers are used.
Please remember modbus is meant to be one on one connection so each equipment needs a different port not to interfere.
do not try to connect multiple devices to port 502 - it will create confusion at best.

Again. If you do not enable these then you are stuffed.

Finally.
Logger needs to be set to pass through mode if you want to control your inverters via ha.
otherwise it will be overriding your commands and also could make your inverters non responsive

I will post modbus for dtsu666-20 when Im back at my laptop. Too hard to do from the phone.

But please note.
This stuff is definitely not as easy as u all believe it to be. and it doesn't solve all your problems.
It potentially opens pandoras box… if you do not know what u doing.

Will add to it soon

Raf

[RafAustralia]

Is it also possible to read out the Sungrow Logger 1000 (also called COM100) via ModBus in HomeAssistant? https://info-support.sungrowpower.com/application/pdf/2022/04/15/COM100D_E-UEN-Ver11-202201.pdf I have a Sungrow SH10RT + SG20RT and an energy meter connected to the logger.

YES this is the answer.
but Logger 1000a was not designed for RS or Rt inverters - it was more meant for new line of T type inverters and I had no idea someone has attempted to connect logger to 6yo gear.

Theory behind it is that Sungrow as the company is moving away from master slave ideology and into multiple parallel connected inverters, all equal and all connected to the logger which drives it all.
RS and RT inverters do not work well in that scenario - or at least so I was told to believe. so I cannot predict your challenges ir issues you would find on your way.

[RafAustralia]

Hi all

I have now formally posted this and will shortly post dtsu666-20 also:

https://github.com/RafAustralia/Sungrow-Logger1000a-Modbus

[RafAustralia]

hi all
@purcell-lab @NBS23 @strom-peter

here is a proper link to the repo for DTSU666-20

https://github.com/RafAustralia/Chint-DTSU666-20-modbus

[robnelso]

Thanks for posting this @RafAustralia.

Within iSolarCloud my DTSU666-20 is providing live data in relation to a "Channel 2 which is monitoring a second inverter I have on my house (and old SMA SunnyBoy). I am trying to identify what the Register addresses for these would be in the TCP ModBus feed I am getting from my Sungrow SH10RS inverter to feed into Home Assistant. I need these to get an accurate read on the total combined power of both inverters is. iSolarCloud is correctly reporting both Inverters, so the data is clearly being passed through to the SH10RS inverter.

I am guessing their is registers for these and hoping they are exposed on the TCP Modbus from the Inverter, given iSolarCloud is reporting on them.

Would anyone have any pointers on what the registers in the Inverter may be that are capturing this second DTSU6660-20 Channel?

[RafAustralia]

@robnelso

hey Rob. Sadly Ive never looked into the second channel of chint meter - sorry.

All I got from sungrow china were these and we worked one by one to get to this point.

Chint comes from various manufacturers too so their registers wont work on sungrow chint either as they all have varying versions of registers - each to their own.

There is a chint integration for HA where he allows to pick the channels 1-4, but he has no intention of catering for sungrow either.

Maybe show that guy who owns chint ha integration my set of registers and see if he incorporates them as Sungrow chint? He might break them into channels. Who knows

Sorry bud. Wish I could help more.

Raf

[Zvone777]

Hello people,
I see you have experience with Logger 1000 Sungrow. I am trying to adjust the power of the power plant by writing to the logger registers, but without success. I just found a document on the Internet with modbus logger registers under the name Logger communication protocol AW0 1.0.2.7. In that document it says that it is register 48003, but it seems that I cannot write to it. I did the testing with the Modbus Poll software. Do you have any solution for my problem?

[RafAustralia]

@Zvone777
Hi there.
whatever u see on internet maybe something created for something “similar” but it would not come from Sungrow.

there is a saying “do not believe everything u read on internet”……..

Ive seen many versions of protocol not even yet created. Soooooo… it happens.

I say that cos I know from Sungrow r&d team, all the way in china, that there is no official version of any protocol released from their side.
In messages above u will see link to what can be accessed. But that does not involve controlling the logger. They have not got there yet.

I just got a second batch of register addresses to test… which I cannot release, but it will be months before we reach any success with these. It is a very slow back and forth process as they do not work with HA nor yaml.

I have my whole equipment connected to logger (sh25t + sh15t + 2x sbr256 + chint dtsu666-20 and while I have logger registers I DO NOT control them via logger as it is not available yet.
so I would say u r looking at it in the wrong way.

Easier would be to set ems of the logger to pass through mode and allow HA to control your inverter directly just like I do.

Anyhow. Thats your answer. Hope it helps

Raf