Skip to content

Releases: knudsvik/EnergyScore

v1.3.3

28 Apr 21:46
ca54b1f
Compare
Choose a tag to compare

What's Changed

  • Fix invalid import ahead of HA 2023.5 release

Full Changelog: v1.3.2...v1.3.3

v1.3.2

14 Mar 10:32
05184a3
Compare
Choose a tag to compare

What's Changed

  • Fix for error (#108) when setting up several sensors with YAML without specifying unique_id

Breaking change

  • From this release the unique_id is required when setting up EnergyScore sensors in YAML

v1.3.1

28 Feb 09:57
22b856d
Compare
Choose a tag to compare

🐛 Bug fix

The savings potential sensor had a bug where it kept the cost from previous day in first update after midnight, this release provides fix.

v1.3.0

26 Feb 21:39
acee567
Compare
Choose a tag to compare

🚀 Two useful new sensors

This release marks the biggest change for the EnergyScore integration so far (about doubled the code base). Two new sensors have been added:

  • Cost sensor: Calculates the current day cumulative costs for the device(s) EnergyScore is set up for, will reset every midnight.
  • Potential savings: Calculates how much money that can potentially be saved for the current day if all of the energy usage was moved to the cheapest hour of the current day. This sensor also have some additional parameters that may be of interest: Current day energy usage, minimum cost (if all energy used on the cheapest hour), average cost and maximum cost.

You can find both new sensors in the same device as the EnergyScore sensor. Units are automatically derived from the energy and price entities that are used when setting up EnergyScore.

Full Changelog: v1.2.1...v1.3.0

v1.2.1

15 Feb 09:48
02d990f
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.2.0...v1.2.1

v1.2.0

04 Feb 22:53
e3aae78
Compare
Choose a tag to compare

🚀 New feature: Rolling Hours Option

A new option is introduced with this version. You can now specify how many hours you want your EnergyScore to be calculated over. The default is 24 hours, but can be set anywhere between 2 and 168 hours (1 week). This should be good for when energy use is optimised over several days, e.g. charging an EV.

🐛 Bugs fixed

  • A bug when cutting off old energy usage has been fixed, this previously could make the energy score a bit off in certain scenarios.
  • Removed a bug in testing config flows that hid a flaw in last release

👎 Breaking changes

  • The way options are treated for UI configured sensors has been made much more robust. It comes with a cost though, if you have previously configured the Energy Treshold, it is being set to default = 0 with this release, so you have to update it again. No changes for yaml setups.

Full Changelog: v1.1.3...v1.2.0

v1.1.3

28 Jan 22:30
991a7f8
Compare
Choose a tag to compare

🐛 Yet another unique_id bug

I had to revert some of the functionality in v1.1.2 to fix another unique_id bug.

v1.1.1

27 Jan 17:07
93de6f6
Compare
Choose a tag to compare

🐛 Bug fix

A small fix to the treshold feature (see v1.1.0 release notes)

v1.1.0

27 Jan 15:39
b36dcbf
Compare
Choose a tag to compare

🚀 Energy treshold

The EnergyScore sensors can now be customized with more advanced configurations. The first configuration option which is released today introduces an energy treshold which removes all hourly energy usage below the configured treshold. This can be useful for appliances that may use some tiny amount of standby power that should not be part of the EnergyScore. More advanced configuration options are coming.

🐛 Bug fixes

This release prepares EnergyScore for a breaking change in Home Assistant 2023.2 release

Full Changelog: v1.0.3...v1.1.0

v1.0.3

11 Jan 22:06
10b7d5f
Compare
Choose a tag to compare

🐛 Bug fix

Yet another quality attribute bug fix. Should hopefully now be 1.0 when a full day's worth of data is captured.