# Mixed Cluster between AC-only and hybrid ESS

**URL:** <https://community.openems.io/t/mixed-cluster-between-ac-only-and-hybrid-ess/10889>\
**Category:** English Forum\
**Created:** [June 30, 2026, 9:29am UTC](https://community.openems.io/t/mixed-cluster-between-ac-only-and-hybrid-ess/10889 "2026-06-30T09:29:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MrT](https://community.openems.io/user_avatar/community.openems.io/mrt/32/1617_2.png) [@MrT](https://community.openems.io/u/MrT)\
**Post date:** [July 1, 2026, 9:06pm UTC](https://community.openems.io/t/mixed-cluster-between-ac-only-and-hybrid-ess/10889/2 "2026-07-01T21:06:52Z")

</div>

Hi Klinki,

I developed a **PreferDcPower** optimizer that is specifically designed for HybridEss systems and also supports **a mixed ESS-Cluster** consisting of both HybridEss and AC-coupled ESS.

You might find the discussion and implementation useful for your use case:

- Forum discussion: [Neuer Optimizer/Logik für mehrere Hybrid ESSes - #54 by MrT](https://community.openems.io/t/neuer-optimizer-logik-fur-mehrere-hybrid-esses/10138/54)
- PR: [PreferDcPowerOptimizer for improved multi-ESS hybrid coordination by timo-schlegel · Pull Request #3661 · OpenEMS/openems · GitHub](https://github.com/OpenEMS/openems/pull/3661)

Maybe this already solves (or at least addresses) the issue you’re seeing.

---

_[View the full topic](https://community.openems.io/t/mixed-cluster-between-ac-only-and-hybrid-ess/10889)._