Integrate inverter e.g. sungrow SH10RT

[HolBaum5]

Hello everyone, I have a sungrow inverter that I have already integrated under openHAB. How can I integrate it into the EOS_connect system? Do I have to make a new Intercae inverter_sungrow.py?

[HolBaum5]

Here briefly my procedure

1. Install Modbus Binding in openHAB,
2. Create Modbus TCP Slave Bridge thing from the Modbus Binding,
3. Generate Sungrow Inverter thing (in Modbus Binding) and items,
4. Integrate the topic eos_connect/control/eos_discharge_allowed into openHAB via MQTT and use it to control the inverter (I haven't done this yet),
5. Integrate config.yaml openHAB.

# Load configuration
load:
# Data source for load power - openhab, homeassistant, default
  source: openhab
# URL for openhab or homeassistant
  url: http://192.168.10.68:8080
# item / entity for load power data
  load_sensor: EosWallPower
# item / entity for wallbox power data
  car_charge_load_sensor: EosWallboxPower
# access token for homeassistant (optional)
  access_token: abc123
# EOS server configuration

Battery:
# Data source for battery soc - openhab, homeassistant, default
  source: openhab
# URL for openhab or homeassistant
  url: http://192.168.10.68:8080
# item / entity for battery SOC data
  soc_sensor: Sungrow_Inverter_Battery_Level_String
# access token for homeassistant (optional)
  access_token: abc123
# battery cpaacity in Wh
  capacity_wh: 11059
# efficiency for charging the battery
  charge_efficiency: 0.88
# efficiency for discharging the battery
  discharge_efficiency: 0.88
# max charging power in W
  max_charge_power_w: 5000
# URL for battery soc
  min_soc_percentage: 5
# URL for battery soc
  max_soc_percentage: 100

[ohAnd]

Hi @HolBaum5 ,

thanks for your contribution and describing the integration with openHAB and SUNGROW.

Only as a note:
The openHAB load integration in EOS connect was integrated in the early days, so in difference to the homeassistant load integration the fetching of load data is currently limited to the last 2 days. So if there is a need to change this also to the same as for Homeassistant -> average from weekdays from the last 2 weeks <- then please raise an issue for that. (so it can priotized)

Note2: According to your example above you are using the 'default' fixed load forecast... to use openHAB or homeassistant set this at source

[HolBaum5]

Hi @ohAnd,

Note1: I opend a issue for that

Note2: I used openHAB data but this did not cover the range of 2 days (inverter was just installed) and got the following error message.
2025-05-12 21:29:58 ERROR [EOS] RESPONSE No control data in optimized response
Maybe there is a way to intercept this?

2025-05-12 21:29:58 INFO [LOAD-IF] Creating load profile from openhab ...
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-10 18:00:00+02:00: 182.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-10 19:00:00+02:00: 199.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-10 20:00:00+02:00: 2206.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-10 21:00:00+02:00: 533.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-10 22:00:00+02:00: 176.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-10 23:00:00+02:00: 183.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 00:00:00+02:00: 216.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 01:00:00+02:00: 178.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 02:00:00+02:00: 146.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 03:00:00+02:00: 192.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 04:00:00+02:00: 160.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 05:00:00+02:00: 177.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 06:00:00+02:00: 132.2
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 09:00:00+02:00: -167.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 10:00:00+02:00: -341.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 11:00:00+02:00: -421.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 12:00:00+02:00: -393.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 13:00:00+02:00: -376.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 14:00:00+02:00: -315.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 15:00:00+02:00: -226.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 16:00:00+02:00: 653.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 17:00:00+02:00: 114.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 19:00:00+02:00: 109.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 20:00:00+02:00: 119.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 21:00:00+02:00: 224.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 22:00:00+02:00: 202.0
2025-05-12 21:29:58 DEBUG [LOAD-IF] Energy for 2025-05-11 23:00:00+02:00: 153.0
2025-05-12 21:29:58 INFO [LOAD-IF] Load profile created successfully.
2025-05-12 21:29:58 DEBUG [Main] optimize request payload - startsolution: None
2025-05-12 21:29:58 DEBUG [MQTT] Publishing message to topic 'eos_connect/optimization/state': request send
2025-05-12 21:29:58 INFO [EOS] OPTIMIZE request optimization with: http://10.219.219.10:8503/optimize?start_hour=21 - and with timeout: 300
2025-05-12 21:29:58 INFO [EOS] OPTIMIZE response retrieved successfully in 0 min 0.00 sec
2025-05-12 21:29:58 ERROR [EOS] OPTIMIZE Request failed: 422 Client Error: Unprocessable Entity for url: http://10.219.219.10:8503/optimize?start_hour=21 - response: <Response [422]>
2025-05-12 21:29:58 ERROR [EOS] RESPONSE No control data in optimized response

I then simply used other data for testing that was available for this range and it worked.

2025-05-12 22:07:46 INFO [LOAD-IF] Creating load profile from openhab ...
2025-05-12 22:07:46 DEBUG [LOAD-IF] Energy for 2025-05-10 00:00:00+02:00: 65.3192
2025-05-12 22:07:46 DEBUG [LOAD-IF] Energy for 2025-05-10 01:00:00+02:00: 37.503
...
2025-05-12 22:07:46 DEBUG [LOAD-IF] Energy for 2025-05-11 22:00:00+02:00: 123.0648
2025-05-12 22:07:46 DEBUG [LOAD-IF] Energy for 2025-05-11 23:00:00+02:00: 32.495
2025-05-12 22:07:46 INFO [LOAD-IF] Load profile created successfully.
2025-05-12 22:07:46 INFO [FORECAST] Temperature forecast fetched successfully 
2025-05-12 22:07:46 DEBUG [Main] optimize request payload - startsolution: None
2025-05-12 22:07:46 DEBUG [MQTT] Publishing message to topic 'eos_connect/optimization/state': request send
2025-05-12 22:07:46 INFO [EOS] OPTIMIZE request optimization with: http://10.219.219.10:8503/optimize?start_hour=22 - and with timeout: 300

[ohAnd]

ok, as a short thing - there could be an error shown if the incoming data are not fulfilling the 48 hours that are needed for EOS --- with some more effort it could be filled with the value from the last given hour or average across all given/ available values in the range of time

maybe it is low prio issue - so it can not be forgotten ;-)

[WolfImBusch]

@ohAnd released a new dev version yesterday (0.1.0.70) which supports the evcc API for controlling the battery. So if you have evcc already in place the Sungrow inverter should be supported now by EOS_Connect "out of the box". Maybe you may give it a try ... please note the config file must be extended accordingly ...

[HolBaum5]

I work with openHAB and have tried to implement the whole thing via MQTT and Modbus for the Sungrow SH15RT.
With openHAB and the Modbus binding, I read all the information from the inverter and process it in openHAB.
Since a second Modbus communication between the inverter and evcc causes problems, I forward the data required for evcc via MQTT from openHAB.
evcc Example:
Meter

power: # current power
  source: mqtt
  topic: openhab/sungrow/meter/power
  timeout: 30s # don't accept values older than timeout

## optional attributes (read-only)
energy: # meter reading in kWh
  source: mqtt
  topic: openhab/sungrow/meter/energy
  timeout: 30s # don't accept values older than timeout

PV System

power: # current power
  source: mqtt
  topic: openhab/sungrow/pv/power
  timeout: 30s # don't accept values older than timeout
## optional attributes (read-only)
energy: # meter reading in kWh
  source: mqtt
  topic: openhab/sungrow/pv/power
  timeout: 30s # don't accept values older than timeout 

I use the following Modbus registers (see github.com/bohdan-s/Sungrow-Inverter/tree/main/Modbus%20Information) for the different modes:

MODE_AVOID_DISCHARGE (EOS_Connect_MQTT_EOS_overall_state)
Source of information: github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml
Register 13050 = 2; Compulsory mode (SungrowSelfConsumptionMode = ON)
Register 13051 = 0xCC; Stop
Register 33047 = 5; 5kW
Register 33048 = 1; 1 = 0.01kW, min allowed value for register

MODE_DISCHARGE_ALLOWED
Source of information: github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml
Register 13050 = 0; Self-consumption mode (SungrowSelfConsumptionMode = ON)
Register 13051 = 0xCC; Stop
Register 33047 = dynamik_max_charge_power from EOS
Register 33048 = 500; 500 = 5.0kW

MODE_CHARGE_FROM_GRID
Source of information: github.com/evcc-io/evcc/blob/master/templates/definition/meter/sungrow-hybrid.yaml
Register 13050 = 2; Self-consumption mode (SungrowSelfConsumptionMode = OFF)
Register 13051 = 0xAA; Discharge
Register 13052 = dynamik_max_charge_power from EOS OR Register 5628
or service.sungrowpower.com.au/GD_232312_Hybrid%20System_Forced%20Charge_Android_V1.0.pdf
Register 33208 = 0xAA; Enable, Forced Charging Valid time Enable (SungrowForcedCharging = ON)
Register 33209 = 1; Everyday, Forced Charging Valid Time
Register 33212 = 23; Forced Charging End Time h
Register 33213 = 59; Forced Charging End Time min
Register 33214 = 90; Forced Charging Target SOC"

Javascript
var thread = Java.type('java.lang.Thread')

var batteryMaxChargePower = 5.0;

if (items.getItem('eosConnectPvControl').state == 'ON') {
if (items.getItem('EOS_Connect_MQTT_EOS_overall_state').state == 'Discharge Allowed') {
/*
* MODE_DISCHARGE_ALLOWED: with a specific target maximum discharging power
/
items.getItem('SungrowMaxChargingPower').sendCommand(parseFloat(items.getItem('EOS_Connect_MQTT_EOS_dynamik_max_charge_power').state));
items.getItem('SungrowMaxDischargingPower').sendCommand(batteryMaxChargePower);
items.getItem('SungrowForcedModeCommand').sendCommand('Stop'); // Stop = 0xCC, Charge/discharge command
items.getItem('SungrowSelfConsumptionMode').sendCommand('ON'); // Self-consumption mode
} else if (items.getItem('EOS_Connect_MQTT_EOS_overall_state').state == 'Avoid Discharge') {
/
* MODE_AVOID_DISCHARGE
/
items.getItem('SungrowMaxChargingPower').sendCommand(batteryMaxChargePower);
items.getItem('SungrowMaxDischargingPower').sendCommand(0.01); // 1 = 0.01kW, min allowed value for register
items.getItem('SungrowForcedModeCommand').sendCommand('Stop'); // Stop = 0xCC, Charge/discharge command
items.getItem('SungrowSelfConsumptionMode').sendCommand('ON'); // Self-consumption mode
} else if (items.getItem('EOS_Connect_MQTT_EOS_overall_state').state == 'Charge from Grid') {
/
* MODE_CHARGE_FROM_GRID: with a specific target charging power
*/
items.getItem('SungrowSelfConsumptionMode').sendCommand('OFF');
items.getItem('SungrowForcedModeCommand').sendCommand('Charge'); // Charge = 0xAA, Charge/discharge command
if (parseFloat(items.getItem('EOS_Connect_MQTT_EOS_dynamik_max_charge_power').state) > 0 ) {
items.getItem('SungrowForcedModePower').sendCommand(parseFloat(items.getItem('EOS_Connect_MQTT_EOS_dynamik_max_charge_power').state));
} else {
items.getItem('SungrowForcedModePower').sendCommand(parseFloat(items.getItem('SungrowBdcRatedPower').state))
}
} else {
console.info(items.getItem('EOS_Connect_MQTT_EOS_overall_state').state);
console.info('something else');
}
}
} else {
if (parseFloat(items.getItem('SungrowMaxChargingPower').state) != batteryMaxChargePower) {
items.getItem('SungrowMaxChargingPower').sendCommand(batteryMaxChargePower); // 10.6kW, max allowed value for register
}
if (parseFloat(items.getItem('SungrowMaxDischargingPower').state) != batteryMaxChargePower) {
items.getItem('SungrowMaxDischargingPower').sendCommand(batteryMaxChargePower); // 10.6kW, max allowed value for register
}
if (items.getItem('SungrowSelfConsumptionMode').state == 'OFF') {
items.getItem('SungrowSelfConsumptionMode').sendCommand('ON');
}
}

[ohAnd]

Nice - do you also checked if the same is directly possible with the evcc functionality

---

and with modbus connection - do you see the possibility to set the max charge power?
(for the modbus interface - what do you used for that? HA integration - local special script or ...? - I'm asking in that way, maybe it makes sense to think about a direct integration in EOS_connect to have a full and direct control)

[HolBaum5]

@ohAnd I will revise this again. I work with openHAB and read the inverter data in openHAB via Modbus. A second Modbus connection to evcc is problematic. I now transfer the meter data to evcc via MQTT. I will update the post with the registers as soon as everything is up and running.