node-red-contrib-power-saver icon indicating copy to clipboard operation
node-red-contrib-power-saver copied to clipboard

Feature request: Minimum saving threshold per postponed hour (not just average)

Open kattelk opened this issue 2 years ago • 3 comments

I have a heat pump which will run with reduced efficiency for every hour of production which is postponed. I used strategy-best-save with a minimum saving threshold of $0.50 per hour (average).

Let us say I had the following prices over 3 hours: Hour 1: $2.00 Hour 2: $1.00 Hour 3: $0.99

Strategy-best-save wanted to turn off heating for Hours 1 and 2, so they could be moved to Hour 3. The total gain was $1.01 and the average $0.505 per hour, satisfying the average saving condition. Moving only 1 hour, however, would have saved $1.00, nearly the entire amount. Moving the second hour may have resulted in a loss, as it only gained $0.01 per kWh, but with decreased efficiency leading to more kWh used.

Could a threshold for every postponed hour be included into the strategy?

kattelk avatar Oct 12 '22 12:10 kattelk

Thank you for the suggestion. I think this can be done, but it may not be the highest priority :-)

ottopaulsen avatar Oct 17 '22 06:10 ottopaulsen

Understood :) Another way to do something similar might be to give a delta for how optimal the solution needs to be. For example, if the most optimal solution is $100, and the next best is $99.99, maybe that is good enough (as long as requires fewer hours/switches).

kattelk avatar Oct 17 '22 10:10 kattelk

I also would like this feature. I use powersaver for my heatpump that uses the warm outgoing air to create hot tap water. I just turn that whole unit off once it's expensive, but then also my ventilation stops in the house. So I really want to minimize that time when possible. I see that with this feature I could configure it start the ventilation earlier for many days.

niklasgisselman avatar Sep 30 '23 07:09 niklasgisselman