I’m using the octopus integration (hats off to Bottlecap Dave) and trying to setup a rolling rate sensor but hitting a bit of a brick wall. Tried googling but to no avail…
What I want from the sensor:
- Rolling sensor looking at the next 18hrs
- Identify the cheapest 3hour slot
- Recalculate if all existing target times are either in the future or all existing target times are in the past
Use case:
I want my washing machine to start during the next 3hr cheapest slot regardless of when I load the machine
- Scenario 1: I fill the machine at 10am but the next slot is at 11:30 - start at 11:30
- Scenario 2: I fill the machine at 11:45 and it’s still in the cheapest slot - start immediately
- Scenario 3: I fill the machine at 15:00 and the next cheapest slot is at 19:00 - start at 19:00
Issue:
I’m on the octopus agile tarrif whereby the rates for the next day are published at 4pm, which then seems to cause the sensor to return unknown once the rolling window goes past 22:30 (the cut off for the previous day’s rates). As a workaround, i’ve set the rolling rate sensor window as 6.5 hours (4pm-11pm) so that it’s always generating. Anyone found a way to prevent it from showing unknown if it starts to fall into the period where the rates aren’t available?