@0xdefec71f

Hi, my battery is now installed and I am already testing. I can change the upper and lower limit of the battery. I can also see the chanages in the iSolarCloud App. But the inverter of sungrow will not limit the loading for example by 80%.

13057 1 Max SOC Max SOC % uint16be 1 0.1 0 value true false false false
13058 1 Min SOC Min SOC % uint16be 1 0.1 0 value true false false false

What am I doing wrong here?

The Batterie_EMS_Mode_Selection I set to 0 and
the Batterie_Forced_charge_discharge to "204"

@hessenkletterer

For me register 13057 works fine with your settings. But it could be the case, that your set upper limit is ignored, because the system needs to calibrate the new/whole battery after your installation. It does that from time to time, because LiFePo Batteries need to calculate the SOC from the taken energy and can not simply rely on the cell voltage as other lithium types. You can only see that in register 10743 (Battery1 SOC nominal), which shows the real SOC.

Register 13022 will only show you the battery SOC subtracted your limits. So if your max SOC is set to 80% and your (real nominal) battery SOC is 80%, then register 13022 will show you 100%. And this is also the value, which is always shown in the sungrow app. I don't know why sungrow did this, but it confuses a lot of people.

if it is not that, the problem may lie within Openhab.

@0xdefec71f

Thanks for your informations. But I will not get access to the register 10743:

10743 is not a holding register! It is input register with ID 200.
13057 is a holding register with ID 1.

Thank you. I changed now to this:

I also deactivated it for 4 hours and tried it again. But I will still get the failure info.

Another question. I also do not find this 2 informations in the Register:

Right now I calculate it very complicated. But I want the right informations directly from Sungrow Modbus Binding

1. Loading or Unloading of the battery in W and
   I used 13021. But this register will show me something with 65000 W if I load or stoped the battery loading. Unloading is fine.

2. Only the power from the panels without the power from the battery

@hessenkletterer again, i cannot help you with OpenHAB. Maybe it's the configuration, maybe your inverter or battery. With id 200 you are talking directly with the battery through the inverter. That's why only sungrow batteries are compatible with id 200.

Also this could be a reason:

Try to delete all registers, you do not need. The most interesting values could be cut down to about 10 or 20 registers. If there is an error message, read it!

1. is 13021, but it looks like you disconfigured the datatype. this is a signed register: int16be
2. is 5016

@hessenkletterer (disclaimer I use home assistant and never seen your tools. Below tips are pure speculation and deductions). Simply use your inverter modbus and don’t attempt for the battery directly.

1. Check on Ethernet. Use the back ethernet port. It allows to access more registers. Don’t use dongle WiFi and don’t use the dongle ethernet.
2. Check the ip. If you did connect to the back ethernet, your dhcp (I guess your FRITZ!Box) did assign an ip to it.
3. Check your parent bridge. Use above ip and set modbus device to "1" to talk to your inverter.
4. Set start to 13022 which is the register of battery level/soc.
5. Set length to 1. tldr: Sungrow uses word register lengths; 2 bytes big endian per register.

this would be analog to any other register. However, I recommend home assistant or iobroker. There’s just more support here on GitHub.

hi,
do someone knowswhy 13017 and all other "Monthly" register not works anymore with FW > 95.01 ?
inverter = SH10RT-V112

Thank you