Repeating vehicle charging plans
Evcc offer the configuration of repeating charging plans per vehicle since begin of this year. This feature never made it into this integration so far (I would like to say for good reasons). This morning I thought it would be at least nice to allow automations to enable/disable existing repeating plans. This have been added in this release.
Without going into the details - this feature is different implementation wise - specially the handling by the evcc-API (you need to post always the full JSON of all plans, even if you just want to modify one attribute). Anyway, after the update you have by default three additional switch entities shown in the vehicle devices. If you need more, you must enable the additional switched via the HA GUI.
Another thing, that is very special about these new switches are the actual setting (time, SOC, or days of week). They are not instantly visible. The plan data is accessible via the attributes (via the context menu 'details', reachable via the 3-dot's). In templates you can use {{state_attr("entity_id", "attribute")} to get a specific value.
IMHO most important is to be aware that the number of a repeating plan will/can change! As example, when you have plan#2 starting at 8:00, a plan#3 starting at 16:00 and a plan#4 starting at 18:00. When you now delete (in the evcc GUI) the plan#3, then previous plan#4 will become plan#3 - so in HA the time-attribute of the switch for the repeating plan#3 will change from 16:00 to 18:00!
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