Octopus Agile without extreme automation

Using the Octopus Compare app, I noticed that Agile has been beating Cosy for our usage profile. This has been the case since March, despite our usage being tailored to the Cosy tariff.

I have switched to the Agile tariff and we have made some minor changes to our usage to, potentially, save even more.

Points to note:

  • The cap on Agile is technically 100p per kWh but, in practice Octopus have been capping it at 32p. This should not be a problem as long as we keep an eye on the rates.
  • The switch to Agile was initiated on a Web page and happened very quickly (less than 24 hours, and retrospective to midnight on the day the email was received).
  • Octopus allow you to switch frequently, but impose a 28 day limit on frequency (which seems very reasonable).
  • Agile would be cheaper than Cosy even if we don't change our usage.
  • Right now, Agile has long periods well below 32p. Cosy had only two 3-hour periods. Cosy sits at 32p for long periods, Agile (for now, anyway) spends a lot of time below 32p.
  • In theory, the lowest possible average price can only be reached using a high level of automation. In practice, it should be possible to reach a decent level with minimal effort. The average on Cosy, albeit only with one-month's data, was 24.11p (25.31 with VAT).
  • The only change to our usage that we have made so far is to put on the washing machine and dishwasher timers a bit earlier than we would have done on Cosy.

Even if we don't save money, this will be an interesting experiment.

How Agile gradually overtook Cosy

Note: We are NOT on Agile Export. We are still on Octopus Outgoing Fixed 12M at 15p.

Comments

Post a Comment

Popular posts from this blog

August

Image
August was a little higher than the prediction. Key statistics: Since mid-March, our energy bill has reduced to approximately 24% of what it was this time last year. We only pay for about 36% of the energy used. This is due to direct solar, stored solar, and export payments.
Read more

Automations

It's a couple of months now since I took the plunge into the rabbit-hole that is Home Assistant. I have a lot of automations set up - some useful, some just for the fun of it. It has been more interesting than I thought it would be and tying together the Amazon Alexa side and the Home Assistant side has been easier than I thought it would be. Some highlights: Alexa to Home Assistant (and vice versa) fairly well linked now Physical switches now in most, if not all, rooms. This makes the system much easier for naiive users and visitors SolarPV system now has more spohisticated operation based on kWh pricing ZigBee/WiFi now split about 60/40. With light bulbs as active repeaters, the ZigBee mesh is reasonably solid Automatic rebooting of the Solar Assistant Raspberry Pi when it crashes Extra fans, temperature controlled, on the SolarPV inverter Optional (switch-controlled) Washing machine and Dishwasher "Finished" announcements based on operating curr...
Read more

No, YAML ain't, but what is it?

YAML is said to stand for "YAML Ain't a Markup Language". This unhelpful acronym (and brazen use of the old "GNU = GNU is Not Unix" joke) doesn't really help in understanding YAML as it pertains to Home Assistant. Well, in this context, YAML is a way of defining the hierarchical configuration settings that drive Home Assistant. So, suppose we have some settings such as: Lights: Left: Brightness: 4 Colour: "Red" Right: Brightness: 6 Colour: "Green" Fans: Extractor: 2 YAML is just the thing to define such a hierarchical structure. For the moment, don't worry too much what these might represent. Consider, however, that we might want the actual settings (such as 4 or "Red") to be controlled by some variable quantity derived from something else within the system. In this case it would be useful to be able to replace the settings with snippets of Python code. And this is, effectively, what H...
Read more