Sailing Mode

[lippertmarkus]

Is your feature request related to a problem? Please describe.
Depending on the car, small discharges, i.e. during the night, can occur. Energy intensive features like Tesla's Sentry Mode can lead to such small discharges which trigger multiple micro charges during the night, always charging the car from 79% to 80% every 3 hours for example.

Depending on the BEV's app you might also get multiple notifications on your phone like "Your car stopped charging at 3:04 a.m. with 80%" that not always can be disabled separately.

Describe the solution you'd like
To avoid unnecessary "micro-charging" I'd like to set a "sailing difference" in %.

Example: When the charge limit is set to 80% and the sailing difference is set to 10% then evcc will start charging only when the car reached 70% and will then charge up to 80%.

I think Sailing mode would only make sense in "Min+PV" or "Fast" charge mode. In "PV" mode I'd like to use every excess solar energy without waiting to reach the sailing difference.

Describe alternatives you've considered
none

Additional context
Example screenshot of a similar feature for MacBooks:

[andig]

I‘m not entirely opposed to this, but it a) needs be optional and b) have a good story how this should be configured without bloating the ui. That said: I‘m not convinced there even is something to fix here. What is the actual problem this solves? Imho vendor app messages are an issue with the app, not with evcc.

[Merwases]

@lippertmarkus

You may set up an automation doing that at HA using Evcc Addon AND Evcc intergration (= entities).
Without HA, I don't know a simple way to set up what you are wishing.

[MartinRinas]

I‘m not entirely opposed to this, but it a) needs be optional and b) have a good story how this should be configured without bloating the ui. That said: I‘m not convinced there even is something to fix here. What is the actual problem this solves? Imho vendor app messages are an issue with the app, not with evcc.

Let me see if I got the issue correct @lippertmarkus , you're suggesting to implement a min deviation threshold before charging starts again, correct? I.e. SoC limit is set to 80%, car is charged during the night to that level. Battery cools down and may only report back 78% once polled. This would trigger a new charging session as the limit isn't reached.

The sailing mode / min deviation threshold / switching hysteresis of a configurable (?) value of a few percent points would prevent a new charging session until the SoC has dropped below limit - hysteresis. i.e. 80% limit, hysteresis of 3% (points), SoC reading after battery cool down 78% -> charging start threshold would be 80% - 3% = 77%. Current SoC reading of 78% is still above the start threshold, no charging session is triggered.