Releases: marq24/ha-evcc
EVCC 0.200+ addons [incl. nightly support]
We all are happy with all ne new features introduced in EVCC 0.200+ release. With the 2025.2.2 release of the HA Integration some of the new available fields have been added to this Integration:
- Tariff's for GRID and SOLAR are now accessible via two new sensors (new sensors are disabled by default). The complete range is then available via the sensors attribute(s) - please note, that this data will be updated only every hours to save resources.
- Added some of the new API fields that are related to the Plan feature of EVCC:
- EffectivePlanTime,
- EffectivePlanSoc
- PlanProjectedStart
- PlanProjectedEnd
- PlanActive & PlanActiveAlt - please note, that the 'alternative' PlanActive boolean sensor is not enabled by default - it has been added, since I made her locally the experience, that the API value 'planActive' is not always correct (at least IMHO)
- All date related fields (PlanTime, VehiclePlansTime, EffectivePlanTime, PlanProjectedStart & PlanProjectedEnd) are now
SensorDeviceClass.TIMESTAMP
...and please don't forget to star the repository and support the development - TIA
EVCC 0.200+ addons
We all are happy with all ne new features introduced in EVCC 0.200+ release. With the 2025.2.2 release of the HA Integration some of the new available fields have been added to this Integration:
- Tariff's for GRID and SOLAR are now accessible via two new sensors (new sensors are disabled by default). The complete range is then available via the sensors attribute(s) - please note, that this data will be updated only every hours to save resources.
- Added some of the new API fields that are related to the Plan feature of EVCC:
- EffectivePlanTime,
- EffectivePlanSoc
- PlanProjectedStart
- PlanProjectedEnd
- PlanActive & PlanActiveAlt - please note, that the 'alternative' PlanActive boolean sensor is not enabled by default - it has been added, since I made her locally the experience, that the API value 'planActive' is not always correct (at least IMHO)
- All date related fields (PlanTime, VehiclePlansTime, EffectivePlanTime, PlanProjectedStart & PlanProjectedEnd) are now
SensorDeviceClass.TIMESTAMP
...and please don't forget to star the repository and support the development - TIA
Added 'effectiveLimitSoc' (readonly)
Maintenance Release
Minor change to handle HA restart when EVCC-backend is not available
Simpler implementation to check grid-data-as-object
Support for changed JSON structure for Vehicle PLAN (vs. PLANS array)
Thanks to the report #85 from @gorzan14 I was made aware, that the internal structure of the vehicle plan(s) object have been changed recently (well early December 2024 - evcc-io/evcc#16091) - nevertheless in previous evcc versions an active charging plan for a vehicle was included in a plans array object - now this is just a simple single plan object... The adjusted code is able to deal with both versions of evcc.
I am sorry, that we have this kind of compatibility issues - evcc is under active development and there is no simple way to 'listen/watch' upcoming API changes - for the 'last' change I was notified by the evcc team - that was just great (but this type of manual notification can't be guaranteed). So we will probably see this kind of issues & fixes again and again.
Contributors
Assets 2
2025.1.8: I am such a BAD python developer...
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
Fix for issue #80 caused by 2025.1.7
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
Contributors
Assets 2
2025.1.7
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
Contributors
Assets 2
2025.1.4
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
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
Contributors
Assets 2
2025.1.3
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]
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)
@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.
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