Battery SolarEdge

SolarEdge Home Battery / inverter curtailment

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. The selected-system connection entry opens its connection form. In v2.12.1411 that SolarEdge menu entry is missing an English label; use the connection-method page to inspect the selected route.

Connection choices

Connection method	What this route provides
HA telemetry plus direct curtailment	HA telemetry/storage entities plus a separately configured curtailment connection; check each control independently.
SolarEdge Modbus Multi — Home Assistant only	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.

SolarEdge support covers SolarEdge Home Battery telemetry, battery dispatch, and active-power curtailment. PowerSync reads battery/site telemetry from SolarEdge Home Assistant entities so the dashboard, sensors, usage stats, and mobile app live flow can populate. It controls force charge, force discharge, backup reserve, Hold SOC, and Smart Optimization dispatch through writable SolarEdge storage-control entities. It can also limit SolarEdge inverter output during uneconomic export periods.

Prerequisites

• Modbus TCP enabled on the SolarEdge inverter, gateway, or Modbus leader.
• Inverter-side active-power control enabled in SetApp or the LCD menu.
• The inverter reachable from Home Assistant on the local network, or a SolarEdge Modbus Home Assistant integration exposing an active power limit number entity.
• SolarEdge battery telemetry entities exposed in Home Assistant, such as battery state of energy/charge, battery power, grid power, and solar power. sensor.solaredge_b1_state_of_energy or sensor.solaredge_i1_b1_state_of_energy style entities are auto-detected when present.
• Writable SolarEdge storage-control entities exposed in Home Assistant for battery dispatch, including storage control mode, command mode, charge/discharge power limits, and optionally command timeout, backup reserve, and grid-charge permission.

Features

• Battery telemetry bridge - PowerSync maps SolarEdge HA entities into the standard battery_level, battery_power, solar_power, grid_power, and load_power fields used by sensors, usage stats, and the app live-flow view. On a DC-coupled battery system it prefers complete PV-string telemetry, or reconstructs PV from inverter DC plus every discovered battery DC channel, so battery discharge is not reported as solar generation.
• Battery dispatch bridge - PowerSync maps SolarEdge HA storage-control entities into force charge, force discharge, restore normal, backup reserve, Hold SOC, AEMO spike export, Saving Sessions, Smart Optimization, and mobile controls.
• Active-power curtailment - PowerSync sets the SolarEdge active power limit to 0% during low-value or negative export periods and restores it to 100% when export recovers.
• Load-following conversion - PowerSync uses the rated AC power setting to convert load-following requests into SolarEdge's 0-100% active power limit.
• Entity fallback - If direct Modbus is unavailable, PowerSync can use a configured HA entity prefix to find an entity such as number.solaredge_active_power_limit.
• Optimizer compatibility - SolarEdge uses the same force-mode services as other controllable battery systems when the required writable storage-control entities are present.

Setup

1. Add PowerSync and select SolarEdge as the battery system when SolarEdge is the primary controlled device, or configure it later through Configure > AC inverter curtailment when it is a separate AC-coupled inverter.
2. Enter the inverter IP address, Modbus port, slave ID, rated AC power in watts, and optional HA entity prefix.
3. Enable SolarEdge export curtailment if PowerSync should automatically limit export during uneconomic periods.
4. Confirm that sensor.power_sync_battery_level and the PowerSync live-flow dashboard populate. If curtailment is enabled, confirm that sensor.power_sync_inverter_status reports SolarEdge status after setup.

The configured inverter host and Modbus port are used for direct curtailment/control. Energy telemetry still comes from the SolarEdge entities in Home Assistant.

Known Limitations

• Some firmware versions or grid profiles reject third-party active-power writes. If setup fails, check SolarEdge Modbus TCP, power-control permissions, firmware support, and installer/grid profile settings.
• PowerSync does not upload tariff schedules to SolarEdge hardware. Dispatch is live control through Home Assistant storage-control entities.
• If the storage-control entities are missing, telemetry and curtailment can still work, but force charge/discharge, backup reserve, Hold SOC, and optimizer dispatch fail with a missing-entities error.
• If both direct Modbus and entity fallback are unavailable, setup stops with a SolarEdge connection error.
• On a battery system, incomplete battery DC telemetry—or incomplete inverter DC when PV-string telemetry is unavailable—is treated as not ready instead of falling back to inverter AC power, because inverter AC can include battery discharge.

---

Sungrow with Globird VPP

Globird's VPP program pays premium rates during AEMO price spikes ($3000/MWh or above). PowerSync can automatically participate:

1. Enable AEMO Spike Auto-Discharge in the mobile app Controls screen
2. Select your NEM region (NSW1, VIC1, QLD1, SA1, TAS1)
3. When AEMO prices hit $3000/MWh, PowerSync automatically forces battery discharge
4. When the spike ends, battery returns to normal operation
5. Push notifications are sent for both spike start and end

Tip: If you also have a separate AC-coupled solar inverter, configure it in the AC Inverter Curtailment section. PowerSync will warn you if your Sungrow battery and AC inverter are configured with conflicting settings.

Check the result

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.

Field reference

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.

SolarEdge battery and curtailment — initial setup

Field	Meaning / input	Fallback / limits
Inverter IP address	Local IP of the SolarEdge inverter or Modbus leader. Leave blank only when using HA entity fallback.	Saved/detected value or the form’s shown fallback
Modbus port	Default Modbus TCP port is 502.	1–65535; step 1
Modbus slave ID	Default is 1. Only change if the inverter uses another Modbus unit ID.	1–247; step 1
Rated AC power	Rated AC output in watts. Used to convert load-following requests into SolarEdge's 0-100% active power limit.	1–100000 W; step 1
HA entity prefix fallback	Optional. Used to match SolarEdge HA telemetry, storage-control, and active-power-limit entities when more than one naming group exists.	Saved/detected value or the form’s shown fallback
Enable SolarEdge export curtailment	When enabled, PowerSync sets SolarEdge active power to 0% during uneconomic export periods and restores it to 100% when export recovers, independently of battery export curtailment. Monitoring Mode also requires curtailment-control permission.	Saved/detected value or the form’s shown fallback