Controller.Symmetric.Balancing accepts Ess.Cluster but fails with missing power coefficients

[Christoph-87]

Description

Setup:

• OpenEMS Edge with two real ManagedSymmetricEss components: ess0, ess1
• Ess.Cluster component: essCluster0
• Grid meter: meter0
• Controller.Symmetric.Balancing configured with ess.id=essCluster0, meter.id=meter0

Observed:

• ctrlBalancing0/State reports Ok
• Scheduler cycle logs repeated errors:
  Coefficient for [essCluster0,ALL,ACTIVE] was not found
  Coefficient for [essCluster0,ALL,REACTIVE] was not found
• No useful setpoints are applied to the real ESS components.

Expected:
Either:

1. Controller.Symmetric.Balancing should support Ess.Cluster / MetaEss targets, or
2. configuration validation should reject Ess.Cluster as ess.id, and the component state should report Warning/Fault instead of Ok.

Workaround:
Disabled Controller.Symmetric.Balancing and implemented external control that writes setpoints directly to ess0/SetActivePowerEquals and ess1/SetActivePowerEquals.

Screenshots

No response

Operating System

No response

How to reproduce the Error?

1. Configure an OpenEMS Edge with at least two real ManagedSymmetricEss components, for example:

   • ess0
   • ess1

2. Configure an Ess.Cluster component that includes those ESS components, for example:

   • essCluster0 with ess0 and ess1 as members

3. Configure a grid meter, for example:

   • meter0

4. Configure Controller.Symmetric.Balancing with:

   • ess.id = essCluster0
   • meter.id = meter0
   • targetGridSetpoint = -5

5. Add the balancing controller to Scheduler.FixedOrder and start/restart OpenEMS Edge.

6. Observe the controller state and logs.

Actual result:

• ctrlBalancing0/State reports Ok
• The scheduler cycle logs repeated errors like:
  Coefficient for [essCluster0,ALL,ACTIVE] was not found
  Coefficient for [essCluster0,ALL,REACTIVE] was not found
• The controller does not apply useful setpoints to the underlying ESS components.

Expected result:
Either Controller.Symmetric.Balancing should support Ess.Cluster as ess.id, or the configuration should be rejected / reported as Warning or Fault instead of showing Ok.

Additional observation:
Direct setpoint writes to the real ESS components work, for example ess0/SetActivePowerEquals and ess1/SetActivePowerEquals. The failure appears when the balancing controller targets the Ess.Cluster / MetaEss.

[Christoph-87]

Update from my setup:

The system is running stable again with both real ESS components in essCluster0.

Current setup:

• essCluster0 contains both ess0 and ess1
• both batteries report valid states and SoC values
• direct setpoint writes to ess0/SetActivePowerEquals and ess1/SetActivePowerEquals work
• grid balancing is currently working via an external controller that distributes setpoints directly to the real ESS components

So this confirms that Ess.Cluster itself and the underlying ESS components can work fine in this setup.

However, the original issue still seems valid:
Controller.Symmetric.Balancing with ess.id=essCluster0 did not work reliably in my setup because of the missing coefficients for the cluster target. I still had to keep the OpenEMS balancing controller disabled and use the direct per-ESS setpoint workaround instead.

So from my side this is not blocking my installation anymore, but it would still be useful if OpenEMS either:

1. supports Ess.Cluster properly in Controller.Symmetric.Balancing, or
2. rejects/reports this configuration as invalid/warning instead of showing Ok.