Feature Request: Option to Disable the Hardcoded SMA/SEMP Integration in Config UI

[MillertV2]

Hello EVCC Team,

I am writing to propose a configuration option that would allow users to disable the integrated SEMP server functionality, as this is currently creating an irreconcilable conflict with closed-loop Energy Management Systems (EMS) like 1komma5°'s Heartbeat AI.

The Setup Causing the Conflict

• EMS: 1komma5° Heartbeat AI (acts as the battery/home master).
• Charger: ABL eMH1 (controlled by EVCC via RS485).
• Link: The Heartbeat AI automatically discovers the running EVCC SEMP Server on the local network (verified to follow port changes and be persistent).

Let me describe my experience with and without using evcc to control the wallbox.

Scenario 1: Without EVCC (The Desired State)
Before EVCC was connected, the system worked based on Heartbeat's exception rule. When I manually scheduled a charge in the car during a low-price period, Heartbeat saw the $3.7 \text{ kW}$ as an unclassified, high-priority load that must be pulled from the Grid. This allowed the home battery to simultaneously charge from the Grid (or remain idle) during the cheapest hours, achieving maximal cost savings.

Scenario 2: With EVCC (The Current Inefficiency)
Now that EVCC is running and the SEMP server is active, Heartbeat automatically discovers it and classifies the ABL wallbox as an integrated, smart wallbox. This makes the old exception rule fall away. Heartbeat’s fundamental logic then takes over: When energy prices rise slightly above the absolute low point, Heartbeat switches to its Self-Consumption mode.It then sees the $3.7 \text{ kW}$ charger as a house load that must be covered by the cleanest source, which is the home battery. Result: The battery immediately begins to discharge to the wallbox, leading to the inefficient and wasteful charge/discharge ping-pong that severely reduces the financial benefit of the battery.

I've tried using the Heartbeat's 'Quick Charge' profile for the wallbox, which partially mitigates the problem—the charge is drawn from the grid. But as an unwanted side effect, the home battery no longer charges at the same time, forcing us into a sequential charging strategy instead of an optimal simultaneous one.

Since the current hardcoded SEMP service creates this conflict, I request that you add a configuration option to completely disable the SEMP listener. This would allow users to leverage EVCC for its superior tariff-based charging planner while letting the external EMS (Heartbeat) manage the battery according to its own logic without interference.

[deThommy]

+1

and thanks for your detailed post. I am also experiencing said problems with my current 1KOMMA5 Setup and after being in touch with their Heartbeat Specialist he confirmed that the second "wallbox" (here SEMP Server) is causing Problems, since 1KOMMA5 only supports one Wallbox (in my case go-E Gemini) which I had previously disconnected on the 1KOMMA5 end because I prefer using EVCC a lot, since its a marvelous piece of software. :)

So a way to disable SEMP would be great, otherwise I wouldnt get my Enphase Battery charging from the grid anymore during low-price phases.

[MillertV2]

Thanks! What annoys me is that I can't always understand Heartbeat's logic.

I charged my EV with a planned charging sessions for two nights on a row. The charging session would coincide with the cheapest window, including the lowest absolute price point. I set the wallbox in the 1KOMMA5 app on Smart Charge with roughly the same values as EVCC, like amount to charge and departure time. Hoping to see that this would influence Heartbeat's logic. This led* to / showed the desired outcome, both the car and homebattery charged simultaneously and the homebattery didn't discharge towards the EV once it was filled up.

*although I have no way to confirm that making the changes in the 1KOMMA5 influenced Heartbeat. And previous efforts with the 'quick charge' method didn't work as expected.

[deThommy]

I stopped trying to understand what heartbeat is doing since it all kinda feels like 3-4 if-else conditions being applied (no "AI" at all :P):

• if price = low: give heatpump a go and
• if user desires: charge car at low price point.

I tried downgrading evcc to get rid of the SEMP point since 1komma5 only started showing the EVCC SEMP Server about a month ago. But even at version 0.208.1 it still shows up in the 1komma5 app.

When did EVCC start implementing SEMP? Do I have to downgrade even more? (@andig can you help out?)

... or did 1komma5 update their system that it started "reading" the network for other SEMP Endpoints about a month ago?

[andig]

/cc @naltatis @premultiply demand for disabling SEMP

[deThommy]

Any news regarding this ongoing issue?

[listrainer]

Ich habe auch das Problem,dass 1komma5grad ständig das Umfeld scannt und mit dem semp Protokoll in evcc Wallboxen ungefragt ins System mit aufnimmt aber nicht steuern kann, vielmehr die eigentlichen Funktionen vom heartbeat stört bzw. sogar zerstört.
Wäre schön wenn das Semp Protokoll abschaltbar wäre.

[listrainer]

Gibt‘s hier was Neues, ist mit der neue Version 0.300 irgendetwas möglich?

[andig]

Das sollte 1,5 doch sicher besser können. Die Übergeiffigkeit ist nicht nett.

[listrainer]

Das sehe ich im Prinzip genauso, nur komme ich bei 1,5 nicht weiter