High CPU when running EVCC as HA Add-on

[DriesA]

Hi all,

I think I am ready setting up EVCC as a HA Add-on.

But what I noticed is that the CPU usage of this add-on is pretty high (always around 50% - right after start). What could be the cause of this?

I'm running HAOS on a Proxmox cluster. It runs on a NUC with a Core i5-1240P CPU (and 64Gb RAM). That should be more than sufficient.

I use EVCC to control my Tesla Model 3 (2019) via a Tesla Wall Charge (generation 2 - so a dumb one - I control the charging process via the car not the TWC directly).

The interaction between my Tesla and Home Assistant is via a Atom Lite ESP32 device (cfr https://pedroktfc.github.io/esphome-tesla-ble/). My HA entities are updates with the right status on a regular basis.

All grid/PV measurements and charger/vehicle controls are exposed through Home Assistant and accessed by EVCC using the HA API.
Also Grid & PV meters: P1 meter and SolarEdge Modbus values exposed as HA sensors

Below is my cleaned configuration (all tokens removed).

I’d appreciate any feedback on whether this setup looks correct, if there are better ways to structure the custom charger, or if any settings could cause unexpected behavior (e.g., caching, intervals, etc.).

Thanks in advance!

network:
  schema: http
  host: evcc.local
  port: 7070

interval: 120

sponsortoken: "<REDACTED>"

log: info
levels:
  site: info
  lp-1: info
  cache: error
  db: error

modbusproxy: []

meters:
  - name: my_grid
    type: custom
    power:
      source: http
      uri: http://homeassistant:8123/api/states/sensor.p1_meter_diepenbeek_power
      method: GET
      headers:
        - Authorization: Bearer <REDACTED>
      insecure: true
      jq: .state | tonumber
      timeout: 5s
      cache: 0s
    currents:
      - source: http
        uri: http://homeassistant:8123/api/states/sensor.p1_meter_diepenbeek_current_phase_1
        method: GET
        headers:
          - Authorization: Bearer <REDACTED>
        insecure: true
        jq: .state | tonumber
        timeout: 5s
        cache: 0s
      - source: http
        uri: http://homeassistant:8123/api/states/sensor.p1_meter_diepenbeek_current_phase_2
        method: GET
        headers:
          - Authorization: Bearer <REDACTED>
        insecure: true
        jq: .state | tonumber
        timeout: 5s
        cache: 0s
      - source: http
        uri: http://homeassistant:8123/api/states/sensor.p1_meter_diepenbeek_current_phase_3
        method: GET
        headers:
          - Authorization: Bearer <REDACTED>
        insecure: true
        jq: .state | tonumber
        timeout: 5s
        cache: 0s

  - name: my_pv
    type: custom
    power:
      source: http
      uri: http://homeassistant:8123/api/states/sensor.solaredge_i1_ac_power
      method: GET
      headers:
        - Authorization: Bearer <REDACTED>
      insecure: true
      jq: .state | tonumber
      timeout: 5s
      cache: 0s

chargers:
  - name: twc_gen2_ble
    type: custom

    status:
      source: http
      uri: http://homeassistant:8123/api/states/sensor.tesla_evse_status
      method: GET
      headers:
        - Authorization: Bearer <REDACTED>
      jq: .state
      timeout: 5s
      cache: 0s

    enabled:
      source: http
      uri: http://homeassistant:8123/api/states/switch.tesla_ble_charger
      method: GET
      headers:
        - Authorization: Bearer <REDACTED>
      jq: if .state == "on" then 1 else 0 end
      timeout: 5s
      cache: 0s

    enable:
      source: http
      method: POST
      uri: http://homeassistant:8123/api/services/script/tesla_laden_starten_stoppen
      headers:
        - Authorization: Bearer <REDACTED>
        - Content-Type: application/json
      body: |
        {"enable": {{.enable}}}
      timeout: 5s
      cache: 0s

    maxcurrent:
      source: http
      uri: http://homeassistant:8123/api/services/number/set_value
      method: POST
      headers:
        - Authorization: Bearer <REDACTED>
        - Content-Type: application/json
      body: '{"entity_id":"number.tesla_ble_fa6930_charging_amps","value":${maxcurrent}}'
      timeout: 5s
      cache: 0s

    power:
      source: http
      uri: http://homeassistant:8123/api/states/sensor.active_power_laadsnelheid
      method: GET
      headers:
        - Authorization: Bearer <REDACTED>
      jq: .state | tonumber
      timeout: 5s
      cache: 0s

    features:
      - integrateddevice

    icon: ev-icon-tesla

vehicles:
  - name: tesla_m3_ble
    type: template
    template: homeassistant
    title: "Tesla Model 3"
    capacity: 77.8
    uri: http://homeassistant.local:8123
    token: "<REDACTED>"
    soc: sensor.tesla_ble_charge_level
    range: sensor.tesla_ble_range
    status: sensor.tesla_ble_charging_state
    limitSoc: sensor.tesla_ble_charge_limit
    odometer: sensor.tesla_ble_odometer
    climater: binary_sensor.tesla_ble_climate
    finishTime: sensor.tesla_ble_minutes_to_limit
    start_charging: script.tesla_starten_met_laden
    stop_charging: script.tesla_stoppen_met_laden
    wakeup: script.tesla_wakker_maken
    setMaxCurrent: number.tesla_ble_fa6930_charging_amps
    icon: car
    phases: 3
    mode: PV
    minCurrent: 5
    maxCurrent: 16
    streaming: false

circuits:
  - name: main
    title: "main circuit"
    maxPower: 27700
    meter: my_grid

site:
  title: "evcc Oudebaan 44"
  meters:
    grid: my_grid
    pv: my_pv
  residualPower: -2000

loadpoints:
  - title: "Tesla Laadpaal"
    charger: twc_gen2_ble
    mode: pv
    vehicle: tesla_m3_ble
    circuit: main
    priority: 0
    soc:
      poll:
        mode: charging
        interval: 5m
      estimate: true
    enable:
      delay: 1m
      threshold: 0
    disable:
      delay: 3m
      threshold: 0

mqtt:
  broker: localhost:1883
  topic: evcc
  user: mqtt_evcc
  password: "<REDACTED>"

eebus: {}

messaging:
  events:
    start:
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop:
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect:
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect:
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc:
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest:
      title: Unknown vehicle
      msg: Unknown vehicle connected?
  services: []

[DriesA]

Ok,
I have updated my YAML. Where possible I switched to MQTT, assuming it would reduce the overhead.
I also removed the vehicle.

CPU is down from 50% to around 30%. I still think it is high.

network:
  schema: http
  host: evcc.local
  port: 7070

interval: 120

sponsortoken: REPLACE_ME

log: info
levels:
  site: info
  lp-1: info
  cache: error
  db: error

meters:
  - name: my_grid
    type: custom
    power:
      source: mqtt
      topic: homeassistant/sensor/p1_meter_diepenbeek_power/state
      timeout: 1m
    currents:
      - source: mqtt
        topic: homeassistant/sensor/p1_meter_diepenbeek_current_phase_1/state
        timeout: 1m
      - source: mqtt
        topic: homeassistant/sensor/p1_meter_diepenbeek_current_phase_2/state
        timeout: 1m
      - source: mqtt
        topic: homeassistant/sensor/p1_meter_diepenbeek_current_phase_3/state
        timeout: 1m

  - name: my_pv
    type: custom
    power:
      source: mqtt
      topic: homeassistant/sensor/solaredge_i1_ac_power/state
      timeout: 1m

chargers:
  - name: twc_gen2_ble
    type: custom

    status:
      source: mqtt
      topic: homeassistant/sensor/tesla_evse_status/state
      timeout: 1m

    enabled:
      source: mqtt
      topic: homeassistant/sensor/tesla_evse_status_1_0/state
      timeout: 1m

    enable:
      source: http
      method: POST
      uri: http://homeassistant:8123/api/services/script/tesla_laden_starten_stoppen
      headers:
        - Authorization: Bearer REPLACE_ME
        - Content-Type: application/json
      body: |
        {"enable": {{.enable}}}
      timeout: 5s
      cache: 10s

    maxcurrent:
      source: http
      method: POST
      uri: http://homeassistant:8123/api/services/number/set_value
      headers:
        - Authorization: Bearer MY_TOKEN
        - Content-Type: application/json
      body: '{"entity_id":"number.tesla_ble_fa6930_charging_amps","value":${maxcurrent}}'
      timeout: 5s
      cache: 10s

    power:
      source: mqtt
      topic: homeassistant/sensor/active_power_laadsnelheid/state
      timeout: 1m

    features:
      - integrateddevice

    icon: ev-icon-tesla

vehicles: []

circuits:
  - name: main
    title: "main circuit"
    maxPower: 27700
    meter: my_grid

site:
  title: "evcc Oudebaan 44"
  meters:
    grid: my_grid
    pv: my_pv
  residualPower: -2000

loadpoints:
  - title: "Tesla Laadpaal"
    charger: twc_gen2_ble
    mode: "pv"
    circuit: main
    priority: 0

    soc:
      poll:
        mode: charging
        interval: 5m
      estimate: true

    enable:
      delay: 1m
      threshold: 0

    disable:
      delay: 3m
      threshold: 0

mqtt:
  broker: localhost:1883
  topic: evcc
  user: mqtt_evcc
  password: MY_TOKEN

[top-gun]

I can offer you a working solution with the ESP32 project that runs just fine with my EVCC + Home-Assistant, even on a Raspi 4b. The Pi is generally below 5% load in normal operation.

My github project that consists of a HA-blueprint, an EVCC vehicle definition and an EVCC wallbox definition:

https://github.com/top-gun/EVCC-Blueprint

For the TWC2, use the generic wallbox definition: https://github.com/top-gun/EVCC-Blueprint/blob/main/EVCC-generic-wallbox(TWC3).yaml

[DriesA]

Hi,
I have solved the problem. :-)

This was the cause:

interval: 120

It should be this:

interval: 120s

Apparently, if you don't specify a time unit such as minutes/seconds, it defaults to... milliseconds. :-)

@top-gun: thanks for your blueprint! I will take a look into it.