v7.2.3

🐛 BUG FIXES

• Fix an issue where the macro would change start or end when it shouldn't in case look_ahead was set to true.

What's Changed

• Fix look_ahead=true in combination with a period which spans the night by @TheFes in #268

Full Changelog: v7.2.2...v7.2.3

v7.2.2

🐛 BUG FIXES

• Hotfix for a bug introduced in 7.2.1

What's Changed

• Hotfix for 7.2.1 bug by @TheFes in #263

Full Changelog: v7.2.1...v7.2.2

v7.2.1

🐛 BUG FIXES

• Fix for certain cases where weight was used. (causing round is undefined error)

What's Changed

• Fix for issue when weight is used by @TheFes in #261

Full Changelog: v7.2.0...v7.2.1

v7.2.0

🌟 NEW FEATURES

• Adds a min_split_hours parameter which can be used in combination with split=true. If set it will ensure that the periods returned are at least that number of hours. It is not limited to integer values, so you can use 1.5 for example.

What's Changed

• Add min_split_hours parameter by @TheFes in #253
• New calculation for min_split_hours by @TheFes in #254
• Fix missing last datapoint when min_split_hours is used by @TheFes in #255
• Add documentation for min_split_hours by @TheFes in #258

Full Changelog: v7.1.1...v7.2.0

v7.2.0b2

What's Changed

• Fix missing last datapoint when min_split_hours is used by @TheFes in #255

Full Changelog: v7.2.0b1...v7.2.0b2

v7.2.0b1

What's Changed

• New calculation for min_split_hours by @TheFes in #254

Full Changelog: v7.2.0b0...v7.2.0b1

v7.2.0b0

🌟 NEW FEATURES

• Adds a min_split_hours parameter which can be used in combination with split=true. If set it will ensure that the periods returned are at least that number of hours. It is not limited to integer values, so you can use 1.5 for example.

What's Changed

• Add min_split_hours parameter by @TheFes in #253

Full Changelog: v7.1.1...v7.2.0b0

v7.1.1

🐛 BUG FIXES

• When mode='is_now' was used, the macro would return false on the first minute of the time period. In combination with look_ahead=true this would lead the binary sensor to turn of for one minute every 5 minutes in the period it should return true. This has been fixed now.

What's Changed

• Add debug to blueprint by @TheFes in #248
• is_now not working in first minute of time period by @TheFes in #252

Full Changelog: v7.1.0...v7.1.1

v7.1.0

✨ NEW FEATURES

• A new setting source_settings is added to add all values for attr_today, attr_tomorrow, attr_all, time_key and value_key in one go. See the source data documentation for more info on which integrations are supported.
• For the core integrations which use an action and action response to retrieve the data I've made a blueprint to easily create a template sensor which has all the prices in an attribute. This blueprint currently supports EasyEnergy, EnergyZero, NordPool and Tibber. More information can be found in the documentation for the blueprint. Big thank you to @rrozema for giving feedback and testing this for Tibber, as I don't have a Tibber subscription myself.

🌟 IMPROVEMENTS

• The macro converts all dates in the source data to UTC datetime now to avoid issues on start and end of Daylight Time Savings.

What's Changed

• Add source settings and blueprint for price sensor by @TheFes in #247

Full Changelog: v7.0.4...v7.1.0

v7.0.4

🐛 BUG FIXES

• The same DTS related bug was causing issues when use_hourly_avg=true was set

📚 DOCUMENTATION

• Source sensor settings for the custom GE-spot integration were added by @jvandijk. Thanks!

What's Changed

• Add GE-Spot integration details to source data by @jvandijk in #243
• Fix use_hourly_avg setting by @TheFes in #244

New Contributors

• @jvandijk made their first contribution in #243

Full Changelog: v7.0.3...v7.0.4