v2.0

[dala318]

Non backwards compatible change!

WARNING: This version is completely new and yet not compatible with version 1.x manual configuration in configuration.yaml
When installing this version all existing integrations has to be created again from the GUI.

What's Changed 2.0.1

• Rebase on main by @dala318 in Rebase on main #25
• Add testing by @dala318 in Add testing #35
• Config flow by @dala318 in Config flow #31
• Events by @dala318 in Events #39
• Adding sensor entities for starts_at by @dala318 in Adding sensor entities for starts_at #42
• Protect against zero division by @dala318 in Protect against zero division #43
• Update documentation to match version 2 integration by @dala318 in Update documentation to match version 2 integration #44

What's Changed 2.0.2

• Fixing spelling in code by @dala318 in Fixing spelling in code #46
• ENTSO-e by @dala318 in ENTSO-e  #48
• Add note in README by @dala318 in Add note in README #49

What's Changed 2.0.3

• Fix a bug with reading property as function by @dala318 in Fix a bug with reading property as function #50
• Entso by @dala318 in Entso #51

Full Changelog: 1.0.2...2.0.3

---

This discussion was created from the release v2.0.1.

[dala318]

Still remains to fix #52 (mostly cosmetic I believe). If someone who has better knowledge about how to make sure unique devices/services are created please help out.

[dala318]

Should be solved in latest release now

[dala318]

Keep off using the ENTSO-e part of planner for now as it don't seem to trigger updates correctly. #57
Or create some automation that forces updates / reloads the integration

[dala318]

The "make sure to update every hour" part should be ok now, but I have seen on my instance that ENTSO-e and Nordpool planner states are not 100% identical, but could have to do with the accept-cost settings and that the two sources report in different currencies.