# Struggling with Power-Solver

**URL:** <https://community.openems.io/t/struggling-with-power-solver/2159>\
**Category:** English Forum\
**Created:** [November 29, 2023, 6:49am UTC](https://community.openems.io/t/struggling-with-power-solver/2159 "2023-11-29T06:49:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![klinki](https://community.openems.io/letter_avatar_proxy/v4/letter/k/858c86/32.png) [@klinki](https://community.openems.io/u/klinki)\
**Post date:** [December 1, 2023, 1:16pm UTC](https://community.openems.io/t/struggling-with-power-solver/2159/3 "2023-12-01T13:16:51Z")

</div>

Hi Thomas,

Thanks for the advice - but it’s not quite what I am looking for. The immediate issue is the problems that occur with my PV inverter/ESS. The solver works properly in simulation. However, there appears to be a problem in the actual implementation, described [here](https://community.openems.io/t/solaredge-hybridwechselrichter-mit-batterie-steuern/1436/41). I’ve implemented a workaround with a moving average, which works well, but nobody’s happy using workarounds…

I want to find out what the solver takes as input, e.g., Grid-Power. The strategy is “moving towards target”.

But it´s in fact interesting seeing all the constraints

Regards, Thomas (klinki)

EDIT: I think I have to look further into the component which controls the ESS 🫣  
EDIT: I´ve implemented a DebugLog in the BalancingController. So I can have a real-time look on what´s being passed to the Solver class

---

_[View the full topic](https://community.openems.io/t/struggling-with-power-solver/2159)._