Repository navigation
Battery Fronius
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 > Fronius GEN24 storage connection.
| Connection method | What this route provides |
|---|---|
| Fronius Modbus 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 Fronius Reserva battery systems via the upstream Fronius Modbus Home Assistant integration. PowerSync does not open a second Modbus connection; it discovers the Fronius/Reserva entities created by that integration and sends commands through Home Assistant services.
- The Fronius Modbus integration installed and working in Home Assistant before adding PowerSync.
- Your Fronius GEN24 / Reserva system paired and online in the Fronius Modbus integration.
- Reserva storage-control entities must be present. If required entities are missing, PowerSync stops setup with the first missing entity name.
No extra credentials needed in PowerSync. Modbus communication is handled by the Fronius Modbus integration. PowerSync reads and writes its entities.
- Smart Optimization — PowerSync's built-in LP optimizer schedules charge/discharge using Fronius telemetry and the configured Reserva capacity and power limits.
- Force Charge / Discharge — Charges from grid or discharges to grid on demand using Fronius Manual storage-control modes.
- Idle / Hold SOC — Uses the PV charge and discharge limit mode and sets both limits to 0 W where the upstream entities are available.
- Restore Normal — Returns Reserva storage control to Auto.
- Backup Reserve — Writes the Reserva minimum SOC entity when exposed by the upstream integration.
- AEMO Spike Export — Supported through the generic spike manager for Australian dynamic or VPP setups.
- Live Telemetry — Solar, grid, battery, load, SOC, battery temperature, daily energy totals, and configured BMS charge/discharge limits.
- Install and configure the Fronius Modbus integration in Home Assistant.
- Confirm the Fronius / Reserva entities are present and updating.
- Add the PowerSync integration and select Fronius Reserva as your battery system.
- Select the Fronius Modbus config entry if you have more than one.
- Enter usable battery capacity, maximum grid charge power, and maximum grid discharge/export power. These values are used by force modes, the mobile app controls, and the LP optimizer.
- PowerSync validates the required entities and completes setup.
PowerSync auto-discovers common Fronius Reserva entity names from the selected Fronius Modbus config entry.
| Purpose | Typical Entity Suffix |
|---|---|
| Battery SOC |
reserva_state_of_charge_2 or reserva_state_of_charge
|
| Battery charge power |
storage_charging_power or reserva_storage_charging_power
|
| Battery discharge power |
storage_discharging_power or reserva_storage_discharging_power
|
| Grid power |
meter_1_power, smart_meter_63a_1_meter_1_power, or smart_meter_power
|
| Solar power |
pv_power_2 or pv_power
|
| Home load |
load_2 or load
|
| Battery API mode |
reserva_battery_api_mode select |
| Storage control mode |
reserva_storage_control_mode_2 or reserva_storage_control_mode select |
| Grid charge power |
reserva_grid_charge_power_2 or reserva_grid_charge_power number |
| Grid discharge power |
reserva_grid_discharge_power_2 or reserva_grid_discharge_power number |
| PV charge limit |
reserva_pv_charge_limit_2 or reserva_pv_charge_limit number |
| Discharge limit |
reserva_discharge_limit_2 or reserva_discharge_limit number |
| Minimum SOC / backup reserve |
reserva_soc_minimum number |
| PowerSync Action | Fronius mode / entity behavior |
|---|---|
| Force charge | Sets Battery API mode to Manual, storage control mode to Charge from Grid, then writes grid charge power |
| Force discharge | Sets Battery API mode to Manual, storage control mode to Discharge to Grid, then writes grid discharge power |
| Idle / hold SOC | Sets Battery API mode to Manual, storage control mode to PV Charge and Discharge Limit, then sets PV charge and discharge limits to 0 W |
| Restore normal | Sets storage control mode back to Auto
|
| Backup reserve | Writes reserva_soc_minimum when available |
Go to Settings > Devices & Services > PowerSync > Configure > Fronius Reserva connection to change the selected Fronius Modbus entry, battery capacity, or max charge/discharge power.
- PowerSync depends on the upstream Fronius Modbus integration's entity names and service behavior.
- If required storage-control entities are missing or unavailable, setup or control commands will fail until the upstream integration is fixed.
- PowerSync does not upload a tariff schedule into Fronius hardware. Tariffs are used inside PowerSync for display, automation, and Smart Optimization.
- DC solar curtailment is not a separate Fronius Reserva battery path. Use AC-Coupled Inverter Curtailment if you need export control for a Fronius solar inverter.
Fronius Reserva support is available in PowerSync 2.12.389 and newer. 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 |
|---|---|---|
| Battery capacity | Usable battery capacity in kWh. Used by the LP optimizer. | Fallback 9.6; 1–100 kWh; step 0.1 |
| Maximum charge power | Maximum grid charge power in kW. Used by dispatch commands and the LP optimizer. | Fallback 5.0; 0.1–50 kW; step 0.1 |
| Maximum discharge power | Maximum grid discharge/export power in kW. Used by dispatch commands and the LP optimizer. | Fallback 5.0; 0.1–50 kW; step 0.1 |
| Fronius Modbus integration | The fronius_modbus integration entry to read sensors and send GEN24 storage-control commands through. | Saved/detected value or the form’s shown fallback |
| Field | Meaning / input | Fallback / limits |
|---|---|---|
| Fronius Modbus integration | The fronius_modbus integration entry to read sensors and send GEN24 storage-control commands through. | Saved/detected value or the form’s shown fallback |
| Battery capacity | Usable battery capacity in kWh. Used by the LP optimizer. | 1–100 kWh; step 0.1 |
| Maximum charge power | Maximum grid charge power in kW. Used by dispatch commands and the LP optimizer. | 0.1–50 kW; step 0.1 |
| Maximum discharge power | Maximum grid discharge/export power in kW. Used by dispatch commands and the LP optimizer. | 0.1–50 kW; step 0.1 |