Repository navigation
Battery Sungrow
Battery connections · Connection methods and sensors · Configuration index
Choose the battery during initial setup. Later, use Settings > Devices & Services > PowerSync > Configure > Battery connection method & sensors to choose its telemetry/control route. Edit connection details under Configure > Sungrow Modbus connection.
| Connection method | What this route provides |
|---|---|
| PowerSync direct inverter Modbus | Direct device connection. Operations depend on the supported model, firmware and enabled write permissions. |
| iHomeManager forwarding — monitoring only | Monitoring and planning only; this route does not enable battery dispatch. |
| Home Assistant Sungrow entities — monitoring only | Monitoring and planning only; this route does not enable battery dispatch. |
Select one route for PowerSync. A second integration using the same device connection can cause conflicts; the companion-integration route is appropriate when that integration should own communications. See source discovery and switching.
Full support for Sungrow SH-series hybrid inverters via direct local connection. No cloud API required.
- Direct Local Control — All control via your local network
- Force Charge/Discharge — Manual or automatic battery control
- Rate Limiting — Set maximum charge and discharge rates (kW)
- Export Limit Control — Limit grid export power
- Backup Reserve — Configure minimum state of charge for backup power
- Battery Health Monitoring — Read state of health directly from the battery
- AEMO Spike Auto-Discharge — Automatic VPP participation for Globird users
| Series | Type | Battery Control |
|---|---|---|
| SH-series | Hybrid Inverter | Full support |
| SG-series | String Inverter | AC curtailment only (no battery) |
| Setting | Default |
|---|---|
| Port | 502 |
| Slave ID | 1 |
Choose Sungrow iHomeManager (telemetry only) when the Sungrow gateway forwards read-only Modbus telemetry instead of exposing a direct inverter control connection. Use the gateway's plaintext forwarding port, normally 503 or 504.
This connection type is deliberately monitoring-only:
- PowerSync reads solar, battery, grid, load, SOC, and health telemetry.
- Monitoring Mode is permanently enabled for the connection.
- Force modes, reserve changes, rate limits, export limits, and optimizer hardware writes are blocked.
- Switching an existing direct-control setup to iHomeManager restores normal inverter operation before the connection is saved.
Use the normal direct Modbus connection on port 502 when PowerSync should control the Sungrow battery.
Earlier instructions described a Secondary Sungrow Inverter setup step and combined dual-inverter power/SOC controls. The current HA configuration flow no longer offers that step and explicitly removes retired dual-Sungrow keys when saving connection settings. Do not look for secondary-host, primary SOC-cap or capacity-weight fields in this form.
For an installation already using multiple inverter controllers, establish the actual telemetry and hardware owner for each device before changing the PowerSync route. Use the supported direct or companion monitoring path for the selected system, or the custom external-controller route when your existing controller must retain ownership. These choices do not promise combined multi-inverter dispatch. Keep a configuration backup before migrating an older setup.
After saving connection changes, allow the integration reload to complete. Check fresh battery SOC, grid/solar/battery power and home-load readings for the selected site. Compare signs and totals with the vendor/upstream readings. Planning sensors can update on a monitoring route; that does not establish dispatch capability. Verify any permitted control separately using readback and measured power.
The tables use the current form labels and help text. They list the conditional field union: a field can be hidden for a different battery, provider, route or available integration. The instructions above explain those conditions. Existing saved/discovered values take precedence over fresh fallbacks. Rate units follow the provider; check the displayed currency/energy unit.
| Field | Meaning / input | Fallback / limits |
|---|---|---|
| Connection type | Direct supports telemetry and control. iHomeManager uses a configured port 503 or 504 forwarding channel, forces Monitoring Mode, and blocks all register writes. | Saved/detected value or the form’s shown fallback |
| Inverter IP address | Local IP of your Sungrow inverter, WiNet-S dongle, or iHomeManager. | Saved/detected value or the form’s shown fallback |
| Modbus port | Direct Modbus normally uses 502. For iHomeManager, enable a non-SSL forwarding channel on port 503 or 504 and enter that port. | Fallback 502; 1–65535; step 1 |
| Modbus slave ID | Default is 1. Only change if you have multiple devices on the same bus. | Fallback 1; 1–247; step 1 |
| Field | Meaning / input | Fallback / limits |
|---|---|---|
| Connection type | Direct supports telemetry and control. iHomeManager uses a configured port 503 or 504 forwarding channel, forces Monitoring Mode, and blocks all register writes. | Saved/detected value or the form’s shown fallback |
| Inverter IP address | Local IP of your Sungrow inverter, WiNet-S dongle, or iHomeManager. | Saved/detected value or the form’s shown fallback |
| Modbus port | Direct Modbus normally uses 502. For iHomeManager, enable a non-SSL forwarding channel on port 503 or 504 and enter that port. | 1–65535; step 1 |
| Modbus slave ID | Default is 1. Only change if you have multiple devices on the same bus. | 1–247; step 1 |