Support for evcc 0.132.1 (release 2025.1.2)
With evcc 0.132.1 the change evcc-io/evcc@65bdb40 introduced a new property chargerPhaseSwitching and removed the chargerPhases1p3p... Even if this adjustment has been rolled back already with evcc-io/evcc@e9d67ee, this HA integration became incompatible with the updated evcc version.
The release 2025.1.2 (and this one) make sure, that the integration will work with chargerPhases1p3p and/or chargerPhaseSwitching - so that what ever will be released in evcc in the near future, the integration should be able handle it.
Situations like this will probably occur also in the future, since I (as developer of the HA integration) am not part of evcc team. We are separate projects and obviously the integration rely on functionality provided by evcc. The developers of evcc a really great people who give me all support I could ask for - but nevertheless there is always the possibility of bad luck or bad timing.
Fixing sets option flow config_entry explicitly warning (release 2025.1.2)
Also this new build fix a small issue reported Detected that custom integration 'evcc_intg' sets option flow config_entry explicitly...
https Support [by @RustyDust] (release 2025.1.3)
When you are running your evcc instance via https you now can simply add the schema https:// as part of your evcc-url during the initial setup of the integration (obviously you should not specify 443 as additional port in this case)
Support for upcoming change in evcc /api/state response (grid data related) (release 2025.1.3)
@andig from evcc made me aware of an upcoming change in the evcc api that would lead to another incompatibility between evcc and the HA integration.
But this time I (hopefully) could adopt the code to the change and make sure that it will work with both implementations (the old=current and the new=future). So you could already update the HA integration and when ever you update evcc you just need a HA restart to allow the integration to 'detect' the change and take appropriate action.
Fix for issue #77 caused by 2025.1.3
Fix for issue #78 caused by 2025.1.4, 2025.1.5, 2025.1.6
Credits
- Thanks @RustyDust for providing the https support
- Thanks @andig for sharing the PR evcc-io/evcc#18063 with me - so I was able to prepare the integration code for the upcoming change
