[FR] Plan grid-charge slots around the excluded device's expected charging window (evcc plan)

[Replica17]

Follow-up to #324 (excluded-device claim on the solar forecast), which works well for me. This is about when the EV charges, not how much.

Setup (Omnibattery 1.5.0, HA 2026.10.1): Anker Solarbank Max AC (3.5 kW), Nordpool dynamic pricing, evcc driving a 1-phase 5 kW wallbox. The EV excluded device is configured with remaining_demand_sensor: sensor.evcc_<loadpoint>_charge_remaining_energy, presence binary_sensor.evcc_<loadpoint>_connected, activity binary_sensor.evcc_<loadpoint>_charging, Solar Surplus + DPC on, exclusion 100%.

What happens today

• evcc has a price-based plan: 12:00-15:30 and 03:45-07:48 at 5 kW (projected start/end are exposed as sensor.evcc_<loadpoint>_plan_projected_start / _end).
• Omnibattery's claim works as documented: excluded_demand_claim_kwh was 11.5 kWh, i.e. the whole remaining forecast, so solar_available_to_battery_kwh = 0 and it correctly schedules a grid-charge deficit.
• It then picks its grid slots by price only. Its dynamic-pricing slots (12:00-15:00) landed on the same cheapest hours as the evcc plan, so battery grid charge (~3.5 kW) and the car (5 kW) overlap, giving ~8.5 kW grid import plus house load.

Request
Let predictive charging avoid, or deprioritise, hours in which the excluded device is expected to draw (e.g. an optional start/end sensor pair next to Expected remaining demand), so grid slots are chosen outside the EV's window when comparable prices exist elsewhere. This would also let the solar claim be placed in the right intervals instead of spread proportionally over the remaining solar (the docs note it "does not predict when the device will consume").

Workaround I'm using: an automation that turns switch.*_predictive_charging off while the activity sensor is on and restores it 3 min after it goes off. It works but loses the re-planning, since the plan is not recomputed around the EV window.

Happy to provide diagnostics (predictive_charging_active attributes, evcc plan sensors) if useful.

[github-actions[bot]]

Thanks for the suggestion! 🙌

Here's how this works:

• Vote by clicking 👍 on the original post — not in the comments
• The more votes an idea gets, the higher it moves in the priority queue
• I review feature ideas periodically and implement the ones that benefit the most users

If your idea is very specific to your setup, it may not make it into the core integration — I'll try to suggest a workaround in that case.

Feel free to discuss details or alternatives below.