Working on issues
Issue #140 started with the request, to be able to show the vehicle soc limit and ended with an agreement, that for what ever reason the evcc API return loadpoints[n]:limitSoc as 0 when the vehicle will be connected to the loadpoint, while the loadpoints[n]:effectiveLimitSoc is showing the value, that's displayed in evcc as the main loadpoint slider value.
Moving the this slider in evcc UI, will cause the update of the loadpoints[n]:limitSoc and the loadpoints[n]:effectiveLimitSoc values to the selected value of the slider.
So the initial state (after a vehicle is connected to a loadpoint):
loadpoints[n]:limitSoc= 0loadpoints[n]:effectiveLimitSoc=vehicles['connected_veh_id']:limitSoc
Once the slider is moved in evcc UI
loadpoints[n]:limitSoc= slider-valueloadpoints[n]:effectiveLimitSoc= slider-valuevehicles['connected_veh_id']:limitSoc= not changed
I made the mistake, to assume, that when the API provides loadpoints[n]:limitSoc = 0, that I then can use 100 as value (since that was matching my setup at that time).
In the new version of the integration, the value for the slider with the entity id number.evcc_[lp:id]_limit_soc will use still loadpoints[n]:limitSoc from the evcc API, but when this API value is 0, then the integration will use the value of loadpoints[n]:effectiveLimitSoc as fallback (instead of the previously hard coded value 100).
There are way to much different soc limit values/fields - and I am pretty sure this will be quite confusing for plenty of users and I am confident, that in +10 days I have forgotten again, how this is all working together...
New Sensor per Loadpoint: Vehicle Charging limit
Since #140 initially started with the request, to add also a sensor, that will provide the current connected vehicle soc limit, the integration now provide sensor.evcc_[lp:id]_vehicle_limit_soc
Please consider to support me
Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes as well as supporting the evcc development directly. And there might be just more that will come around the corner...
If you haven't starred this integration in Github yet - please do so - TIA