v0.8.0

What's Changed

• Feat: Add dynamic limits based on entities by @alinbalutoiu in #77
  • Please see the README for more information (additionalDynamicLimits)

Full Changelog: v0.7.0...v0.8.0

v0.7.0

What's Changed

• Update README.md with more details about advanced configuration by @alinbalutoiu in #69
• Add card refresh interval to reduce CPU usage by @alinbalutoiu in #71

Full Changelog: v0.6.1...v0.7.0

v0.6.1

Breaking change

If you were already using the targetTimesEntities configuration option to track specific slots and highlight them, please note that this has changed to a map of entities so that you can now track as many target entities as you wish - and, as an additional bonus, choose custom background colours and/or a prefix (such as an emoji for easy spotting of the intention of the target!) for each one, really adding to the featureset of the card.

Please see the example and screenshot here (scroll down to the further examples): https://github.com/lozzd/octopus-energy-rates-card?tab=readme-ov-file#advanced-configurations

If you were using this option, you will need to tweak your lovelace config for the card to meet the new format.

Many thanks to @alinbalutoiu for adding this feature and making their first contribution! (and for a speedy bugfix which made this 0.6.1)

What's Changed

• Add additional capabilities for specifying entities with target time by @alinbalutoiu in #65
• Fix nil panic by @alinbalutoiu in #67

New Contributors

• @alinbalutoiu made their first contribution in #65

Full Changelog: v0.5.1...v0.6.1

v0.5.1

Bugfix for v0.5.0 for those using the new feature that takes the limit values from another entity (see v0.5.0 release notes)

What's Changed

• Fix: LimitMedMult + LimitHighMult is not defined by @corvus2606 in #62

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Lots of features in this release - thanks to the contributors, new and old

• Highlight the current time in the grid for clarity
• Support a variable for limits, with multipliers (e.g. if you want to be dynamic with the colours based on the average price in next 24 hours)
• Support a second target rate entity (e.g. if you have two target rate entity sensors to track a specific price, you can show both now)
• Support a configuration entry that limits the list length, for those with limited space (e.g. only show next 4 rates)

What's Changed

• Feat: current time indicator by @corvus2606 in #61
• Add rateListLimit option by @netmindz in #58

New Contributors

• @corvus2606 made their first contribution in #61
• @netmindz made their first contribution in #58

Full Changelog: v0.4.1...v0.5.0

v0.4.1

What's Changed

• Quick bugfix - Reset default rate limits by @lozzd in #42
  • Affects people relying on the defaults, where the default multiplier and the various rate limits no longer have the same unit.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

BREAKING CHANGE IN v0.3.0

If moving from a release before 0.3.0, please ensure you read the notes for that release to ensure the card continues to work.

New Feature

Thanks to @alfwro13 for introducing a great new feature to the card - support for more limits for additional colouring, and a really awesome way to demonstrate when your target rates have been met (pulling the data from the entity created by the Octopus Integration) (fixes #29)
Please see the README for more information on how to set this up!

What's Changed

• Update README.md by @reedy in #24
• Added support to display Target Rate entity and support for lowlimit option by @alfwro13 in #39

New Contributors

• @reedy made their first contribution in #24
• @alfwro13 made their first contribution in #39

Full Changelog: v0.3.1...v0.4.0

v0.3.1

BREAKING CHANGE IN v0.3.0

If moving from a release before 0.3.0, please ensure you read the notes for that release to ensure the card continues to work.

What's Changed

• Ensured Past/future entities are optional by @igloo32 in #37

Full Changelog: v0.3.0...v0.3.1

v0.3.0

BREAKING CHANGE

This release supports the new data structure introduced in the 9.0.0 version of the Octopus Energy integration. You will need to ensure you upgrade both the card and the integration at the same time and follow the steps below!

How to update

You will need to enable the event entity for the data to be available to the card, and update your Lovelace dashboard yaml to point to those three new entities.

The README has been updated to reflect this, but in brief, the configuration now needs to look something like

currentEntity: event.octopus_energy_electricity_<your_id_here>_current_day_rates
pastEntity: event.octopus_energy_electricity_<your_id_here>_previous_day_rates
futureEntity: event.octopus_energy_electricity_<your_id_here>_next_day_rates

Those are the three entities you need to enable in the Integration, as they're disabled by default. In the Integration settings, filter by disabled entities and then search for the last section (e.g. current_day_rates) then press the button to enable the entity. It may take up to an hour for the data to be present, so don't panic if the card doesn't work immediately.

Huge thanks to the contributors to this repo for getting this updated 👍 (@igloo32 @stevetrease)

What's Changed

• Work with v9 multiple "events". by @igloo32 in #35

New Contributors

• @igloo32 made their first contribution in #35

Full Changelog: v0.2.0...v0.3.0

v0.2.0

What's Changed

• Fix rates for Octopus integration v8.0.0 by @jamesog in #20

New Contributors

• @jamesog made their first contribution in #20

Full Changelog: v0.1.4...v0.2.0