Disable / Enable evcc Loadpoints from HA
I do understand, that this feature might be very edgy, but some evcc users (including myself) have the need to be able to disable a evcc loadpoint for a certain amount of time. One of the possible reasons is (as discussed in evcc-io/evcc#27320), to enable the TibberGridRewards functionality, where you must grant Tibber the possibility to control your wallbox. This implies, that evcc should stop controlling it - since there could be only one.
The discussion has started already in February of this year and now with the release of evcc 0.314,x it's finally possible to (temp) disable a loadpoint in evcc. The announcement of this upcoming evcc feature in spring was the initial reason why I started to implement access to evcc-configuration via HA, that was released in May. This release now is the final puzzle piece to complete the overall functionality.
Disable a evcc-loadpoint as Service action: evcc_intg.deactivate_loadpoint
When you want to disable disable a loadpoint (e.g. since you want to pass control to TibberGridReward functionality), then you now just can specify the index of the loadpoint (as it returned by api/state call) and the integration will take care about the required steps:
- Write the
disabledflag to the loadpoint configuration - After a delay of 5 seconds: automatically restart your evcc server
- After an additional delay of 20 seconds: automatically reload the HA integration (so that the new settings will be finally read)
Please note, that you can only disable loadpoints that are configured via the evcc GUI (disabling loadpoints that are step up via eccc.yaml is not supported by evcc itself - so the integration has implemented the same check) - I am not sure what would happen without this restriction - but I don't wanted to find out.
Of course when you can disable a loadpoint via the new service, there is also an option to enable a loadpoint again.
Please consider supporting me
Thanks to everybody who have already supported me in the past weeks or month that is really highly appreciated! Sometimes it has been a though journey. To the other users of this integration: 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