# We're assuming it's cold because otherwise Octopus wouldn't need the saving session
return "It will soon be time for a Saving Session so get the house warm in advance."
Although, having written that I changed my mind because the blocker might just leave it on if it’s already on when the session starts. I’ve done this instead:
def reasonWeShouldTurnOff(calculationMoment: datetime.datetime, deviceInfos: DeviceInfos) -> Optional[str]:
return "The heating shouldn't be on during a Saving Session"
ofc I can test the future too:
bash test.sh --calculation-moment 2022-11-22T17:05:16
2022-11-21T22:46:45.118 DEBUG root Turning on so we can do some heating. It will soon be time for a Saving Session so get the house warm in advance. (Power → true from ManageSpaceHeatingPower.manage)
Gosh, using EmonCMS I can see that sometimes I use over 4kWh in the same hour as tomorrow’s window, it’s not my average though.
Yes, this was part of the reason I avoided looking into it more: the principle of telling people to avoid the peaks and be paid £$€ is good. Paying you based on your previous 10 days use just encourages the wrong behaviour.
I thought about how it could be done better, and all I can think is to compare your use profile against the “typical domestic” use profile, scaled to total use, and pay you for the difference in the peak. That way, the nega-watts are more fairly calculated, and actual behaviour change is encouraged. Anyway, I’m off to light the candles for my slow-cooked dinner…
There’s a two hour session this week. Not sure our house will keep warm enough to have the heat pump off completely, especially with the freezing temperatures outside, but maybe reducing the flow temps for a bit will work?
Eh? The house temperature (averaged from 5 rooms) dropped by a whole degree during those 2 hours, and then almost another degree until 2am when it hit the set back temperature. Not sure I’d count that as “barely moved”. Who’s the silly goat now?
has been getting our house pre-emptively warmed before the saving session begins so that has helped.
To be honest, this is the sort of thing that caused me to start running my own controller. I wouldn’t expect a normal controller to cope with this sort of nonsense because the drivers feeding the behaviour are so weird.