Changed strategy for 'update charging session', fix for Vehicle device info & support for enhancements in the hass-evcc-card
LatestUpdate of charging sessions
Kudos (once more) to @mkshb for implementing a change_listener in the WebSocket message receiving code, now allowing the integration to refresh the charging sessions once a loadpoint's charging state will switch to charging: false (from true).
Fixed Device Info for Vehicles
With the introduction of the enable/disable switched for the repeating plans, I have messed up the device info object for vehicles - they have been showed as loadpoints. This is finally fixed with this release. I have also added model information which is basically identical to the device name.
Support for multiple enhancements in the the hass-evcc-card
The hass-evcc-card project from @mkshb is a great companion for this evcc-ha-integration. While the integration focus allowing you to remote control your evcc (e.g. via automations) the hass-evcc-card provides a comprehensive home assistant dashboard for evcc.
This new release of the integration offering some extended data options that can be used by the hass-evcc-card without interfering the core functionality of the integration at all.
Frustrated by a new issue? - please have in mind...
That all this has been implemented while we have temperatures in Germany that we never had before - so if there are any new issues - just have a little bit of mercy.
My latest HA-Integration... (some sort of advertisement)
If you have some investments in ETF's (in €) and you want to see the development of different ISIN in near real time (of course only during trading hours), then I would kindly ask you to try my latest HA integration: ha-justetf-live and provide some feedback - The integration have it's focus on daily/monthly changes. TIA
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: 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