Skip to content

Releases: markgdev/home-assistant_OctopusAgile

Added change to support multiple agile rates

19 Oct 17:58
cf7887e
Compare
Choose a tag to compare
v0.1.3-beta.1

Merge pull request #97 from LucidityCrash/issue_96_allow_for_selectio…

Added ability to switch to Go

10 Jul 15:49
Compare
Choose a tag to compare
Pre-release

Added ability to switch to Go. Add the following to your configuration.yaml:

  # Easily switch between agile and go rates.
  # If you include gorate, it'll override
  # the times for the times specified in gotimes
  gorate: 5
  # You can leave godayrate out to go by 
  # Agile rates outside of offpeak period
  godayrate: 16.26
  gotimes:
  - "23:30:00"
  - "00:00:00"
  - "00:30:00"
  - "01:00:00"
  - "01:30:00"
  - "02:00:00"
  - "02:30:00"
  - "03:00:00"

New feature: Agile consumption statistics

24 May 13:17
ae4b8ee
Compare
Choose a tag to compare

New feature: Agile consumption statistics, thanks to @bodak.

Avg rate sensor improvements

16 May 18:40
1563eef
Compare
Choose a tag to compare
Pre-release
  • Avg rate sensors now get stored in octopusagile.json and get repopulated at restart
  • Avg rate sensors now include unit_of_measurement attribute

v0.1.1

15 May 19:28
933adf3
Compare
Choose a tag to compare
  • Added new entity “octopusagile.all_rates” to store the whole days rates which can then be used by sensors. This entity will not get updated in the same way as the rates entity does each 30 minutes.
  • Previous rate, current rate and next rate updated to pull rates from the new entity
  • Run_devices update will throw a useful error if it fails to update, this also allows timers to continue running after a run_device update error
  • Rates and all_rates will update if they’re not in octopusagile.json (file must currently exist though)
  • New configuration option “consumption”, set to false to stop pulling historic consumption data if you don’t use it, which involves many api calls.

Api rate limit improvements

29 Apr 20:05
Compare
Choose a tag to compare
Pre-release

Currently in testing:

  • Added new entity “octopusagile.all_rates” to store the whole days rates which can then be used by sensors. This entity will not get updated in the same way as the rates entity does each 30 minutes.
  • Previous rate, current rate and next rate updated to pull rates from the new entity
  • Run_devices update will throw a useful error if it fails to update, this also allows timers to continue running after a run_device update error
  • Rates and all_rates will update if they’re not in octopusagile.json (file must currently exist though)
  • New configuration option “consumption”, set to false to stop pulling historic consumption data if you don’t use it, which involves many api calls.

v0.1.0

26 Feb 21:27
Compare
Choose a tag to compare

First tag to enable better management of versioning in HACS