Optimisation at times exceeds p_nom for deferrable loads

[purcell-lab]

Describe the bug
At times the optimisation allocates power levels which are above p_nom for deferrable loads.

To Reproduce

Expected behavior
p_deferrable should not exceed p_nom, so in this case it should not exceed 600 W for the 17:00 timesteps.

Then a few minutes later, optimisation is delivering the expected behaviour.

Home Assistant installation type

• Home Assistant Supervised

Your hardware

• OS: Linux
• Architecture: amd64

EMHASS installation type

• Add-on

Additional context
deferrable4 (my hot water heat pump) has an additional constraint to complete by sunset, which occurs at the 17:00 timestep.

I suspect the optimisation is allocating additional power to deferrable4 at this point, because it is constrained..

Another set of sub optimal results 5 minutes later:

[purcell-lab]

Another user with the same issue.
https://community.home-assistant.io/t/emhass-an-energy-management-for-home-assistant/338126/2528?u=markpurcell

@GeoDerp , can you assist I think there is a logic error in the stop intervals code that it tries to squeeze in all the power required in the time remaining before the stop interval without consideration of the p_nom restriction.

[GeoDerp]

Hey @purcell-lab , Unfortunately im not verse in that area of the EMHASS code.
Out of curiosity, What happens if 'def_start_penalty': [] in runtime ?

[sladey]

Maybe related to this issues I am see power allocated to deferrable loads when the def_total_hours runtime param contains zero for that particular def load.