Preparation to upcoming breaking changes in evcc
As result of the Redesign PV Mode discussion @ evcc the team created the PR#32490.
This change will have also an impact to the HA-Integration, since the available options for the loadpoint mode will be change from off|pv|minpv|now to off|smart|now + a new select alwaysCharge: off|on|once. So basically the options pv & minpv will be replaced by smart (and then allowing via the new alwaysCharge control to get the functionality of the old minpv mode. You can find all the details at the inked evcc discussion & the resulting PR.
With this release of the integration, nothing will change now - the code will detect on restart of HA/integration, which version of evcc is running, and if the new modes are supported by your evcc server, than the new options for the mode are used.
Possible breaking change in your automations!
If you have any automation, that will set the mode pv or minpv hardcoded, then you should be aware, that you must adjust your automation after you have updated your evcc version to the build, that will include the evcc PR#32490.
Fix #307
When your meter name (when still using evcc.yaml) contain an _ this caused a warning in HA - as reported in #307. While renaming the meter already solving the issue, with this release the code makes sure, that no invalid (containing __ ) entity IDs will be created by the integration for the optional-meter support.
Please consider supporting me
Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users of this integration: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.
If you haven't starred this integration in Github yet - please do so - TIA