Optimizer: report loadpoint charging state

[andig]

pairs with evcc-io/optimizer#157

The optimizer's continuity tie break counts charge starts inside a plan, but it assumed every device enters the horizon switched off. A car that charges right now therefore scored one start whether the plan kept it running or stopped it and restarted a slot later, so an interruption stayed free whenever both slots carried the same price. Reporting the loadpoint state lets the optimizer prefer the uninterrupted plan.

• c_active is set from the charge status, so only a loadpoint actually charging anchors the plan. An enabled but idle loadpoint does not.
• The anchor decides ties only: cost, preference and grid peak bounds keep the economics of the schedule unchanged.
• The module points at the optimizer rollup branch, which carries the anchor, so a preview deployment of that rollup can be tested against this branch.

TODO

• re-bump github.com/evcc-io/optimizer to a released revision once feat: anchor charge continuity on the running session optimizer#157 and feat: prefer fewer charging interruptions optimizer#151 are merged

🤖 Generated with Claude Code

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook