Hi @Rrrr thanks for the contribution. All the data we need is being picked up via the GraphQL interfaces into the Kraken system. Tomorrow’s prices for all tariffs are published in the late morning or early afternoon. In the Kraken data tomorrow’s prices are published for the whole day in one go.
In addition the app triggers events when the tariff rate changes so that users can automate their smarthome reactions to price changes via Flows.
Things are looking pretty good. I Have run the app with my Dispatch Test data in place with good results. I shall leave it running overnight to test the midnight turnover.
I have changed the “picker” user interface into “slider” for the period start day. It’s much easier to use and much more immediate in presentation and use than the old version. Downside it doesn’t show you which value is currently selected, sigh! I have moved the Period Start Date capability to the top of the Sensor view so that it’s easy to see what day is currently selected.
Feedback welcome!
Dispatch timing seems to be working well. The EnergyAccount device always uses Extended dispatch periods and I have modified the SmartEnergyDevice device to focus only on Planned dispatch periods.
To illustrate the difference, imagine there is a Planned dispatch from 16:45-17:25 (40 minutes of dispatch). This Planned dispatch period is the period when the device will be switched ON by Octopus to receive dispatched energy. This is why I have modified SmartEnergyDevice devices to focus only on Planned dispatches.
In contrast, the Extended dispatch period will run from 16:30-17:30 (60 minutes). This is the period during which the Meter will receive reduced price energy. Note the smart device is switched off by Octopus from 16:30-16:45 and from 17:25-17:30 so only other devices on the Meter will receive the reduced price energy during these times.
The difference between planned and extended dispatches is explained by the constraint in the UK metering system that divides the day into 30 minute chunks (starting at :00 and :30 minutes passed the hour). Within a chunk all energy must be supplied at a uniform price. Planned dispatches represent the times when Octopus will use their control to switch the device on. Extended dispatches represent whole chunks which must be supplied at the dispatch rate.
Energy consumption and cost per chunk is explicitly reported by capabilities on the EnergyAccount device.
There are several new When flow cards available from the App. To manage general device usage (e.g. charging an domestic battery that is NOT a SmartEnergyDevice) the events Dispatch Pricing Starts and Dispatch Pricing Ends can be used.
To manage a SmartEnergyDevice the events Dispatch Starts and Dispatch Ends can be used.
The event Pricing Quartile Changed includes both Tariff Rates and Dispatches in its signal. So if you want to control energy usage so that it always makes use of the cheap(est) rate energy your flow can look like this:
