second variant of modbus_sungrow.yaml -- modbus_sungrow_battery.yaml

[Korsberg]

Hello , i have a second yaml file with some sensors for battery that are not in the standard yaml file. I have one Inverter and one battery.
What is the preferred way to use this 2 yaml file parallel ? I don't want to add these to original yaml file.

I got this error now
*
Please update SungrowSHx and/or 192.168.1.129_502 for the entry in your configuration.yaml file and restart Home Assistant to fix this issue.
'

In the the header I have same info in both files before 'sensors:'

modbus:

• name: SungrowSHx
  type: tcp
  host: !secret sungrow_modbus_host_ip
  port: !secret sungrow_modbus_port
  delay: 5
  timeout: 10

  sensors:
  '

[Gnarfoz]

I'm confident enough with Home Assistant's configuration merging feature to suggest a "proper" solution...

You could try giving replacing SungrowSHx with something else, so the Modbus integration treats this as an entirely separate device. I'm not sure how well that would work given that the Modbus stack in the inverter is notoriously fickle when multiple clients try to access it. You could try it. The only thing that could go wrong is that the inverter might stop responding to Modbus. Fixable by disconnecting it from the network for a while.

[TCzerny]

Consider to use a modbus proxy in case multiple call produces errors

[Korsberg]

in this case i will have 2 yaml files that read/write to the same inverter/battery.. I wil ltry to replace SungrowSHx

i do not know how to setup a modus proxy ... hmm

[TCzerny]

For modbus proxy I created a fork to be able to use up to three devices. (Original addon could only handle one device)
you can find it here:
https://github.com/TCzerny/ha-modbusproxy

[Korsberg]

I will continue merge into default yaml file.

Thanks for input :-)

Its not like 2 connection to same IP

2025-01-15 18:43:00.207 WARNING (MainThread) [homeassistant.components.modbus.validators] Modbus SungrowSHx host/port 192.168.1.129_502 is duplicate, not loaded!

[TCzerny]

I’ve added some additional sensors for my SBR Battery as well.
like so:
- name: Battery 1 Voltage
unique_id: sg_battery_1_voltage
slave: !secret sungrow_modbus_slave_battery
address: 10740 # reg 10741;Bat Spannung 0.1 V; 2010
input_type: input
data_type: uint16
scale: 0.1
precision: 1
unit_of_measurement: "V"
device_class: voltage
state_class: measurement
scan_interval: 10

and added the needed sungrow_modbus_slave_battery number to the secrets file.

Maybe that gives you a hint.

[Korsberg]

i have that as well . But issue is to have more than one yaml file to connect to same IP , that is is not working

for battery I using 'sbr_modbus_slave'
default is 'sungrow_modbus_slave' used
In combined file! that works .

sungrow_modbus_host_ip: 192.168.1.129 # 192.168.1.1.129 - modbus 128 winet TODO update with the IP of your inverter. No default. Check your router.
sungrow_modbus_port: 502 # 502 TODO update with the Modbus port of your inverter. Default is '502'
sungrow_modbus_slave: 1 #TODO update with the slave address of your inverter. Default is '1'
sbr_modbus_slave: 200

[TCzerny]

And you use sbr_modbus_slave on the battery registers?

You still have only one ip (192.168.1.129) and port (502)
Then two different slave ids 1 for the inverter and 200 for the battery.

I’m using the same. and it’s working fine

sungrow_modbus_host_ip: 192.168.178.83
sungrow_modbus_port: 502
sungrow_modbus_slave: 1
sungrow_modbus_slave_battery: 200

and added additional registers to the original mkaiser file
Make sure you only have one time the modbus connection information which you find at the beginning of the file. So only one hub with name SungrowSHx with ip and port will starte only one connection.

[Korsberg]

It works fine for me also when have everything in same yaml file. Invert and battery. ( added additional registers to the original mkaiser file)

But what I will test to separat all battery sensors to a separate file. But is not working. When connecting to same IP