v5.5.3

🐛 BUG FIXES

• prevent zero division error when first 2 items of the data have the same time due to change from DST.

What's Changed

• Add missing template key for Tibber example by @TheFes in #152
• Update README.md for HACS 2.0 by @TheFes in #159
• Prevent zero division due to DST change by @TheFes in #164

Full Changelog: v5.5.2...v5.5.3

v5.5.2

🐛 BUG FIXES

• The output for mode='all' in combination with split=true wasn't properly converted to JSON, so it was not possible to convert it back to a list using the from_json filter

📚 DOCUMENTATION

• Added config examples for Amber Electrid, Omie, PVPC and the core Tibber integration

What's Changed

• Add config example for Amber Electric by @dgoodlad in #143
• Add Omie and PVPC to docs by @TheFes in #145
• Add template sensor config for Tibber servcie call by @TheFes in #146
• Fix template sensor for Tibber core integration by @TheFes in #149
• Fix JSON output for split mode all by @TheFes in #151

New Contributors

• @dgoodlad made their first contribution in #143

Full Changelog: v5.5.1...v5.5.2

v5.5.1

🐛 BUG FIXES

• The macro would run into error when the price data was not including the current price, because that is needed for the extreme_now mode.

📚 DOCUMENTATION

• The default value for plot_attr mentioned in the documentation was incorrect. This has been fixed by @rrooggiieerr

What's Changed

• Fix default value for plot_attr by @rrooggiieerr in #138
• Fix for extreme_now when current price is not included by @TheFes in #141

New Contributors

• @rrooggiieerr made their first contribution in #138

Full Changelog: v5.5.0...v5.5.1

v5.5.0

🌟 IMPROVEMENTS

• Add option to use 'all' as input for the hours parameter. When hours='all' is set, all hours between the start and end will be used. This can for example be practical when you want the average price of the whole day, and will avoid issues when hours=24 and there are only 23 hours in the day because of DST.

🐛 BUG FIXES

• Fix a bug in the time_key finder when the data also includes yesterday's prices.
• Fix a bug in de debug output

What's Changed

• Add hours='all' by @TheFes in #135
• Fix time_key finder for sensors which have data from yesterday by @TheFes in #136
• Fix hours='all' when end is after available data by @TheFes in #137

Full Changelog: v5.4.4...v5.5.0

v5.4.4

Sorry for all the releases today, but I had to squash some bugs :) For completeness I added all the changes in these release notes.

🐛 BUG FIXES

• (v5.4.4) fixed rounding of estimated_costs when precision parameter was set.
• (v5.4.3) fix a pedmas error which would add a second to the start time
• (v5.4.2) the start time returned by the macro was sometimes in the past when look_ahead was set to true
• (v5.4.2) look_ahead wasn't used when a datetime object or datetime string was used as input for the start parameter

📚 DOCUMENTATION

• (v5.4.2) added some additional clarification on look_ahead in the documentation

What's Changed

• Fix rounding in estimated cost calcualtion by @TheFes in #133

Full Changelog: v5.4.3...v5.4.4

v5.4.3

🐛 BUG FIXES

• fix a pedmas error which would add a second to the start time

What's Changed

• fix extra second by @TheFes in #132

Full Changelog: v5.4.2...v5.4.3

v5.4.2

🐛 BUG FIXES

• the start time returned by the macro was sometimes in the past when look_ahead was set to true
• look_ahead wasn't used when a datetime object or datetime string was used as input for the start parameter

📚 DOCUMENTATION

• added some additional clarification on look_ahead in the documentation

What's Changed

• fix start time and look_ahead by @TheFes in #131

Full Changelog: v5.4.1...v5.4.2

v5.4.1

🐛 BUG FIXES

• Split mode was sometimes missing the last datapoint
• Debug mode was not always working correctly

What's Changed

• Small fix for debug mode when there is an error by @TheFes in #127
• Fix for split mode by @TheFes in #129

Full Changelog: v5.4.0...v5.4.1

v5.4.0

✨ IMPROVEMENTS

• A new mode: estimated_costs has been added. This will return the estimated costs for the provided number of hours. It needs the kWh energy usage for that period, which can either be provided using the kwh parameter, or using the program parameter, which will take it from the energy plots sensor. In case no program is used, it is also possible to provide weight which will be used in the calculation.

What's Changed

• Add feature: Total expected costs based on weighted points by @TheFes in #126

Full Changelog: v5.3.1...v5.4.0

v5.3.1

🐛 BUG FIXES

• The code for the extreme_now mode caused an error when the current time was outside the time in scope. This has been fixed

📚 DOCUMENTATION

• EasyEnergy has been added to the providers, and some additional notes have been added to the section about the template sensor needed for EnergyZero and EasyEnergy
• Usage of single and double quotes was not consistant in the documentation.

What's Changed

• Consistent usage of single/double quotes in examples by @TheFes in #122
• Add EasyEnergy and some additional notes on the template sensor by @TheFes in #123
• Bugfix for extreme_now by @TheFes in #124

Full Changelog: v5.3.0...v5.3.1