Question concerning interaction between EOS_connect and EVCC

[jgantenberg]

First of all, best thanks for sharing EOS_connect since it helps alot in addressing my actual needs concerning energy optimization.

In the past I used EVCC without optimization. I left my pv and home battery on its own, "optimized" EV charging by calculating lowest prices in the next 24h and activate price threshold in EVCC, choosing PV as default charging mode.

Since using EOS_connect with EOS I integrated my PV and home battery and let EOC_connect decide to charge home battery from grid. This works quite well although I didn't calculate actuel savings. But it looks reasonable.

To my understanding EOS_connect also interacts with EVCC to start charging the car at "optimal" times. How is this done? Is the loadpoint mode switched between "off", "PV", "PVmin" and "fast" by EOS_connect and should I disable my external lowest price calculations (via node red) and let EOS_connect start charging?

If this is explained anywhre I didn't find ist yet.

Thanks for clearing and best reagards
Joachim

[ohAnd]

Hi @jgantenberg ,

thanks...

How EOS_connect interacts with EVCC:

Short answer: EOS_connect monitors EVCC charging state and adapts (override) optimizer decisions accordingly — it doesn't directly control EV charging modes.

How it works:

• When EVCC is in fast charge mode ("now", "pv+now", etc.) → EOS_connect prevents battery discharge to prioritize available power for the car
• When EVCC is in PV mode ("pv", "minpv") → EOS_connect allows battery discharge to help solar power the EV
• This happens automatically based on what EVCC reports — no external Node-RED logic needed

Important: Keep your existing EVCC price optimization active. EOS_connect complements it by optimizing your battery/grid — it doesn't override EVCC's charging mode decisions.

for next main release:
I've also updated the Advanced documentation with detailed scenarios and the control state mappings. Check section "Charging State Monitoring" for the full explanation.

[jgantenberg]

Although the answer helps understanding things EOS_connect tries to manage, but my thinking is, that external price optimization is not the correct decision. For example I use a node red flow with power-saver-node-module https://powersaver.no/nodes/ps-strategy-lowest-price to calculate the lowest price within the next 24 hours. In my thinking the final decision whether to start charging from grid with EVCC in PV mode depends not only on price but also in PV power forecast and actual battery soc. E.g. if SOC is 90%, the forecast for the rest of the day is 25 kWh charging from grid is not meaningful, although prices are low. So can there be at least a flag set by the optimizer to determine charging from grid is meaningful. It should be possible to take the battery from the car and the total price and value of the energy into account. You know what I mean? Or do I oversee something?

Thanks for the discussion and best regards,
Joachim

[ohAnd]

Hi,
when and if the car will be charged is still fully decided on evcc side - currently car charging demand is not part of EOS-connect (with EOS or evopt)

Your described dependencies are right, but something for future (I don't want to replace evcc - even not possible ;-) ) - focus is currently only react on evcc to have e.g. not a drained house battery during charging the ev or support pv surplus ev charging with house battery for cloudy phases. And have also with this influence an immediate adaption of the planning/ and control due to the changed behavior (e.g. other soc or load as known before ev charging) ...