Repository navigation
Battery ESY Sunhome
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 > ESY Sunhome connection.
| Connection method | What this route provides |
|---|---|
| ESY Sunhome integration | Uses the selected companion integration. Required control entities must be present and writable; telemetry alone is insufficient. |
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 ESY Sunhome HM-series hybrid inverter-battery systems. PowerSync connects via the ESY Sunhome integration as a companion — that integration handles the cloud connection, and PowerSync bridges through it for real-time telemetry and battery control.
- The ESY Sunhome integration installed in Home Assistant via HACS (search "ESY Sunhome"). This integration manages the ESY cloud connection and creates the HA entities PowerSync reads.
- Your ESY Sunhome device paired and online in the ESY Sunhome integration before adding PowerSync.
No extra credentials needed in PowerSync. All authentication is handled by the ESY Sunhome integration. PowerSync just reads its entities.
- Smart Optimization — PowerSync's built-in LP optimizer runs full charge/discharge scheduling based on price forecasts, solar generation, and home load.
- AEMO Spike Export — Uses the shared spike-response settings when enabled and permitted on this writable route. PowerSync requests discharge and attempts owned-state recovery; configuration or a notification is not physical export proof.
- Saving Sessions — Participates in grid demand-response events.
- Live Telemetry — Solar, grid, battery, and load power; battery state of charge; daily energy totals.
- Mode Control — LP optimizer commands map to ESY's native operating modes:
| PowerSync Action | ESY Mode |
|---|---|
| Force charge | Emergency Mode |
| Force discharge | Electricity Sell Mode |
| Restore normal / Idle / Self-consumption | Regular Mode |
Mode-only control: ESY Sunhome does not expose W-level charge/discharge setpoints. The optimizer issues charge/discharge commands, but the actual power level is determined by the battery firmware.
set_backup_reserveis a no-op (logged, not sent).
- Install the ESY Sunhome integration from HACS and complete device pairing.
- Add the PowerSync integration and select ESY Sunhome as your battery system.
- PowerSync will auto-select the ESY entry if only one exists, or show a picker if you have multiple.
- Setup completes automatically — no IP address or API key required in PowerSync.
In addition to the standard PowerSync energy sensors, ESY Sunhome users get:
| Sensor | Description |
|---|---|
| Inverter Temperature | Inverter heat sink temperature (°C) |
| Battery Status | Operating state text from firmware (e.g. "Charging", "Discharging") |
| Battery Health (SOH) | State of health percentage reported by the BMS |
If you re-add or replace your ESY Sunhome integration entry, go to Settings > Devices & Services > PowerSync > Configure > ESY Sunhome connection to re-bind PowerSync to the new entry.
- No W-level power setpoints — charge/discharge rate is firmware-managed.
- No backup reserve control (
set_backup_reserveis a logged no-op). - No DC solar curtailment support.
- Requires the ESY Sunhome integration to be installed, running, and connected to the ESY cloud. If the ESY cloud goes offline, entities become unavailable and PowerSync falls back to last-known data.
ESY Sunhome support was introduced in PowerSync 2.12.112. Report issues on Discord.
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 |
|---|---|---|
| ESY Sunhome integration | The ESY Sunhome integration entry to read sensors and send mode commands through. Install it via HACS if it does not appear here. | Saved/detected value or the form’s shown fallback |
| Field | Meaning / input | Fallback / limits |
|---|---|---|
| ESY Sunhome integration | The ESY Sunhome integration entry to read sensors and send mode commands through. Install it via HACS if it does not appear here. | Saved/detected value or the form’s shown fallback |