Retrieved data through modbus not containing data of both inverters

[bqzero]

I always had an issue that the retrieved data was not matching the data in isolarcloud. Since I believe that some deviation is to be expected (iSolarcloud showing some "nicer" numbers) I was not questioning the data at all. However last weekend I analysed it more detailed. and found out that the data of my second (slave) inverter is not showing up in the modbus numbers at all.

My Sungrow inverters:

• Model: SH-10.RT v112

• The inverter is connected via (mark one)

  • [X] LAN (internal port)
  • [X] WiNet-S (LAN)
  • [] WiNet-S (WLAN)

• Model: SG6.0RT

• The inverter is connected via (mark one)

  • [] LAN (internal port)
  • [X] WiNet-S (LAN)
  • [] WiNet-S (WLAN)

• Are you using a Modbus Proxy (mark one)
  • [] yes
  • [X] no
  • [] I don't know what that is

Home Assistant version:

• Core 2024.2.4
• Supervisor 2024.02.1
• Operating System 12.0
• Frontend 20240207.1

modbus_sungrow.yaml:

• Version/ time stamp : 2023-09-29

Inverter Firmware Status:

• [X] I made sure that the newest firmware is installed via the installers account

Additional context The setup consists of a SH-10.RT-V112, a SG6.0RT and a SBR128 Battery. SG6.0RT and SBR are connected to the SH via modbus by cable as indented by the manufacturer.

iSolar shows all information correctly for each inverter. Modbus is only showing the information of the SH and Battery, production of the SG Inverter is not added or shown.

`# Home Assistant Sungrow inverter integration

https://github.com/mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant

by Martin Kaiser

last update: 2023-09-29

modbus:

• name: SungrowSHx type: tcp host: !secret sungrow_modbus_host_ip port: !secret sungrow_modbus_port retries: 10 sensors:
  • name: Sungrow device type Code unique_id: sg_dev_code slave: !secret sungrow_modbus_slave address: 4999 # reg 5000 input_type: input data_type: uint16 scan_interval: 600
  • name: Inverter temperature unique_id: sg_inverter_temperature slave: !secret sungrow_modbus_slave address: 5007 # reg 5008 input_type: input data_type: int16 precision: 1 unit_of_measurement: °C device_class: Temperature scale: 0.1 scan_interval: 10
  • name: MPPT1 voltage unique_id: sg_mppt1_voltage slave: !secret sungrow_modbus_slave address: 5010 # reg 5011 input_type: input data_type: uint16 precision: 1 unit_of_measurement: V device_class: Voltage scale: 0.1 scan_interval: 10
  • name: MPPT1 current unique_id: sg_mppt1_current slave: !secret sungrow_modbus_slave address: 5011 # reg 5012 input_type: input data_type: uint16 precision: 2 unit_of_measurement: A device_class: Current scale: 0.1 scan_interval: 10
  • name: MPPT2 voltage unique_id: sg_mppt2_voltage slave: !secret sungrow_modbus_slave address: 5012 # reg 5013 input_type: input data_type: uint16 precision: 1 unit_of_measurement: V device_class: Voltage scale: 0.1 scan_interval: 10
  • name: MPPT2 current unique_id: sg_mppt2_current slave: !secret sungrow_modbus_slave address: 5013 # reg 5014 input_type: input data_type: uint16 precision: 2 unit_of_measurement: A device_class: Current scale: 0.1 scan_interval: 10
  • name: Total DC power unique_id: sg_total_dc_power slave: !secret sungrow_modbus_slave address: 5016 # reg 5017 input_type: input data_type: uint32 swap: word precision: 0 unit_of_measurement: W device_class: power state_class: measurement scale: 1 scan_interval: 10
  • name: Phase A voltage unique_id: sg_phase_a_voltage slave: !secret sungrow_modbus_slave address: 5018 # reg: 5019 input_type: input data_type: uint16 precision: 1 unit_of_measurement: V device_class: Voltage state_class: measurement scale: 0.1 scan_interval: 10
  • name: Phase B voltage unique_id: sg_phase_b_voltage slave: !secret sungrow_modbus_slave address: 5019 # reg: 5020 input_type: input data_type: uint16 precision: 1 unit_of_measurement: V device_class: Voltage state_class: measurement scale: 0.1 scan_interval: 10
  • name: Phase C voltage unique_id: sg_phase_c_voltage slave: !secret sungrow_modbus_slave address: 5020 # reg: 5021 input_type: input data_type: uint16 precision: 1 unit_of_measurement: V device_class: Voltage state_class: measurement scale: 0.1 scan_interval: 10
  • name: Grid frequency unique_id: sg_grid_frequency slave: !secret sungrow_modbus_slave address: 5035 # reg 5036 input_type: input data_type: uint16 precision: 2 unit_of_measurement: "Hz" device_class: frequency state_class: measurement scale: 0.01 scan_interval: 10
  • name: Load power unique_id: sg_load_power slave: !secret sungrow_modbus_slave address: 13007 # reg 13008 input_type: input data_type: int32 swap: word precision: 0 unit_of_measurement: W device_class: power state_class: measurement scale: 1 scan_interval: 10
  • name: Battery level unique_id: sg_battery_level slave: !secret sungrow_modbus_slave address: 13022 # reg 13023 input_type: input data_type: uint16 precision: 1 unit_of_measurement: "%" device_class: battery state_class: measurement scale: 0.1 scan_interval: 60
  • name: Battery state of health unique_id: sg_battery_state_of_health slave: !secret sungrow_modbus_slave address: 13023 # reg 13024 input_type: input data_type: uint16 precision: 0 unit_of_measurement: "%" state_class: measurement scale: 0.1 scan_interval: 600
  • name: Battery power raw unique_id: sg_battery_power_raw slave: !secret sungrow_modbus_slave address: 13021 # reg 13022 input_type: input data_type: uint16 precision: 0 unit_of_measurement: W device_class: power state_class: measurement scale: 1 scan_interval: 10
  • name: Battery temperature unique_id: sg_battery_temperature slave: !secret sungrow_modbus_slave address: 13024 # reg 13025 input_type: input data_type: int16 precision: 1 unit_of_measurement: °C device_class: Temperature scale: 0.1 scan_interval: 60
  • name: Running state unique_id: sg_running_state slave: !secret sungrow_modbus_slave address: 13000 # reg 13001 input_type: input data_type: uint16 precision: 0 scale: 1 scan_interval: 10
  • name: Export power raw unique_id: sg_battery_export_power_raw slave: !secret sungrow_modbus_slave address: 13009 # reg 13010 input_type: input data_type: int32 swap: word precision: 0 unit_of_measurement: W device_class: power state_class: measurement scale: 1 scan_interval: 10
  • name: Battery current unique_id: sg_battery_current slave: !secret sungrow_modbus_slave address: 13020 # reg 13021 input_type: input data_type: uint16 precision: 1 unit_of_measurement: A device_class: Current scale: 0.1 scan_interval: 10`

Has anyone an idea on what to do so I can get the information of the second inverter to my HA too?

BR, Christian

[vistree]

Yes, you need to connect the second inverter also to your local network and use a second entry in security.yml and a second modbus yml Have a look at this fork - which is not fully up to date with the original git from mkaiser

https://github.com/reesaroo74/Sungrow-SHx-Inverter-Modbus-Home-Assistant