SolarEdge Control Recovery

SolarEdge control recovery

Configuration index · Battery connections

PowerSync stops SolarEdge control writes when an entity service call may have reached the inverter but its result cannot be confirmed. A failed call does not establish that the inverter rejected the command or returned to normal operation. PowerSync preserves the prior baseline and records the uncertain write. It does not attempt rollback, zero the charge or discharge limits, or retry the command.

The control block survives Home Assistant restart. Startup does not replay persisted SolarEdge force commands or expiry timers.

A dispatch that completed normally also blocks control if Home Assistant restarts before PowerSync releases it, because the fields PowerSync still owns are recorded as outstanding. From v2.12.1328 supervised recovery resolves that state: when a fresh readback shows the inverter still holding exactly those values, or already back at the baseline captured before they were written, the service restores the baseline and clears the block. Before v2.12.1328 nothing could clear it, and the charge and discharge limits stayed where the dispatch left them. Enabling monitoring remains available while control is blocked and does not attempt inverter cleanup. A controller lock serializes battery and curtailment operations; automatic requests skip a busy controller. Expiry timers carry the controller generation so they cannot restore a later command.

The Battery Integration Details sensor exposes control_health, control_mutation_active, and last_control_mutation. A value of reconciliation_required means that further control requests remain blocked. This state does not say that battery power is zero or that the last command stopped.

From v2.12.1272, an automatic curtailment or restore request rejected because its permission was disabled before the inverter call records outcome: rejected and possibly_transmitted: false. It leaves control ready and does not require reconciliation. This also covers permission changing while PowerSync saves its control journal. A failed or uncertain inverter call still blocks further control, and upgrading does not clear an existing reconciliation block.

Supervised recovery

Inspect the inverter and its upstream SolarEdge Modbus Multi connection. Establish safe storage settings using the inverter's supported controls under supervision. Keep automatic dispatch disabled during this inspection.

Then call power_sync.reconcile_solaredge_control with the PowerSync configuration entry ID and acknowledge: true:

To find that entry ID, open Developer Tools → Template and enter:

{{ config_entry_id('sensor.power_sync_battery_integration_details') }}

Use your actual Battery Integration Details entity ID if it has been renamed or has a suffix. Copy the returned configuration entry ID into entry_id below.

action: power_sync.reconcile_solaredge_control
data:
  entry_id: YOUR_POWERSYNC_ENTRY_ID
  acknowledge: true

This service reads storage settings through a fresh update of the existing upstream integration. It clears the block only when it identifies the correct inverter, obtains fresh readback, and validates a benign storage baseline. Cached Home Assistant entity values, elapsed time, and a restart are insufficient. Unsupported upstream readback or an unsafe baseline leaves the block in place.

It sends inverter writes in one case: restoring the saved baseline of a dispatch PowerSync itself completed, when the fresh readback proves the inverter still holds it and no uncertain write is outstanding. The response then reports released_owned_dispatch. Otherwise every saved field must already match the baseline and the service writes nothing.

A successful reconciliation clears the retained transaction and allows the next command to capture its baseline. Review the control-health attributes before resuming automatic dispatch. Reconciliation does not restore an earlier force command or timer.

Storage readback cannot validate an uncertain active-power curtailment write. The reconciliation service leaves that block in place; recovery requires separate validation of the active-power controls.