Releases: marq24/ha-evcc
Data update via Websocket communication [experimental]
Websocket FTW!
The EVCC server supporting websocket communication - This allow the server to push data-updates as they happen, which makes polling the data by the integration obsolete.
Important
The new new communication layer, is disabled by default - if you want to support the development, I would kindly ask to go to the configuration of the integration and enable the websocket support by checking Use Websocket (experimental) - Polling Interval will be ignored. After a short while the Integration should be reloaded in HA and the integration will listen to the websocket of your configured EVCC server.
If you don't want to try the new feature - the update 'should' not harm your current setup.
Note
After the initial stuff has been implemented and is working fine in the past 2 days, I have learned something additional today about how HA can handle/work with web sockets. This have been reflected now in the update [make use of coordinator.async_set_updated_data(...) once data have been received via the web socket]
If you have issues when enabling the new feature, please create an issue in the repository and disable the Websocket support in the configuration of the integration.
Also would be quite nice to get feedback, when the websocket will work for you :-)
Data update via Websocket communication [experimental]
Websocket FTW!
The EVCC server supporting websocket communication - This allow the server to push data-updates as they happen, which makes polling the data by the integration obsolete.
Important
The new new communication layer, is disabled by default - if you want to support the development, I would kindly ask to go to the configuration of the integration and enable the websocket support by checking Use Websocket (experimental) - Polling Interval will be ignored. After a short while the Integration should be reloaded in HA and the integration will listen to the websocket of your configured EVCC server.
If you don't want to try the new feature - the update 'should' not harm your current setup.
Note
I have implemented this just in few hours this morning/afternoon - so there are for sure the possibility that something might not work as expected - specially this is my first websocket client implementation. So if you have issues when enabling the new feature, please create an issue and disable the Websocket support in the configuration of the integration.
Also would be quite nice to get feedback, when the websocket will work for you :-)
Adjustment for upcoming changes in EVCC tariff response objects
I was made aware, that the price attribute in the tariff response object will be renamed to just value in one of the next EVCC releases - so this release will take care about this upcoming change.
When you process one of the new evcc_tariff_* sensor attributes you must also adjust your parser once the attribute will be renamed by EVCC.
Added pvAction (+CODE), pvRemaining (as Timestamp), and enable-/disableDelay
As requested in #101 this new build tries to support few additional sensors/settings
EVCC 0.200+ addons [incl. nightly support + bugfix]
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
This release fix #98
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
