BottlecapDave
commented
10 months ago Hello, this feels like a very bespoke use case and would a fair amount of time to implement, where the target rate sensor configuration is already quite complicated (with some further complication already planned). Therefore I'll put it into the "under consideration" bucket, but have no plans for this anytime in the future.
Currently I have a continuous target set to find the cheapest two hour window, which is generally fine but in many cases isn't optimal - it's not uncommon for it to select a two period which encompasses 30 minutes of significantly more expensive energy.
I would be interested in diving into this, as it should pick the window where the overall cost is the cheapest (all rate added together). If you could raise a separate issue with
- An example day of agile rates
- Your configuration
- The rates that were picked
- What you expected
jellybob
Describe the feature
The target entity currently only supports being on/off intermittently or continuously for an n hour period of time. Ideally I'd like to be able to have the cost tracker find two one hour windows at the lowest price.
Expected behaviour
When configured in this way the target would find a number of continuous time periods that have the lowest rates, rather than one single continuous time period, or many half hour time periods.
Use Case
I have a storage heater connected to the off-peak circuit of an economy 7 meter. This circuit isn't on a timer since switching to Octopus Agile, but can be told to activate at any time, but when activated it will remain active for 1 hour from the point at which it's turned on. I need my heater to receive power for about two hours to provide heat for the next day.
Currently I have a continuous target set to find the cheapest two hour window, which is generally fine but in many cases isn't optimal - it's not uncommon for it to select a two period which encompasses 30 minutes of significantly more expensive energy.
Confirmation