evcc: vehicleSoc no longer written to InfluxDB since EVCC 0.123

Describe the bug

Even though evcc vehicle still shows the current SOC:

> cschlipf@home:~ $ evcc vehicle
[main  ] INFO 2023/12/28 00:59:24 evcc 0.123.2
[main  ] INFO 2023/12/28 00:59:24 using config file: /home/cschlipf/evcc.yaml
[db    ] INFO 2023/12/28 00:59:24 using sqlite database: /home/cschlipf/.evcc/evcc.db
[mqtt  ] INFO 2023/12/28 00:59:24 connecting evcc-1079426317 at tcp://localhost:1883
Soc:           85%
Capacity:      79.0kWh
Charge status: B
Charged:       12.7kWh
Range:         467km
Odometer:      25970km
Finish time:   2023-12-28 00:59:00 +0100 CET
Position:      0,0
Target Soc:    85%
OnIdentified:  Mode:pv
Features:      [CoarseCurrent]

It is no longer written to the connected InfluxDB:

> select value from vehicleSoc order by desc limit 10
name: vehicleSoc
time                 value
----                 -----
2023-12-27T18:31:42Z 0
2023-12-27T17:58:53Z 0
2023-12-27T17:55:41Z 0
2023-12-23T09:34:22Z 0
2023-12-22T19:33:52Z 0
2023-12-22T14:56:58Z 80.36742608284514
2023-12-22T14:55:58Z 79
2023-12-22T14:55:02Z 77.6010069030602
2023-12-22T14:51:25Z 77.60100572866092
2023-12-22T14:50:17Z 76.3003612438637

The 0’s here are from recent restarts of EVCC. Last updated value is from an EVCC version prior to 0.123. Vehicle was charged after the last time stamp: image

All data that is visualized here is from the EVCC connected InfluxDB.

At the same time the vehicleSoc however is still correctly sent via MQTT. Here logged via Home Assistant: image

Steps to reproduce

  1. Charge vehicle
  2. Using influx run these commands: precision rfc3339 select value from vehicleSoc order by desc limit 10
  3. See that no new values are written for vehicleSoc. All other values are written. …

Configuration details

#General configuration
# open evcc at http://home:7070
network:
  schema: http
  host: home # .local suffix announces the hostname on MDNS
  port: 7070
log: info
levels:
  cache: error
# unique installation id
plant: xxxxxxxxx
# sponsortoken
sponsortoken: xxxxxxxxx
telemetry: true
interval: 10s # control cycle interval



site:
  title: Pirolweg
  meters:
    grid: sofar-grid
    pv: sofar-pv
    battery: 
      - sofar-battery-1


meters:
  - name: sofar-grid
    type: custom
    power:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x0488 # Total PCC active power. Selling electricity is positive, buying electricity is negative
        type: holding
        decode: int16
      scale: -10
    energy:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x068E # Energy_Purchase_Total
        type: holding
        decode: uint32
      scale: 0.1
    currents:
      - source: modbus
        id: 1
        uri: 192.168.158.13:8899
        register:
          address: 0x0492 # R phase PCC current
          type: holding
          decode: uint16
        scale: 0.01
      - source: modbus
        id: 1
        uri: 192.168.158.13:8899
        register:
          address: 0x049D # S phase PCC current
          type: holding
          decode: uint16
        scale: 0.01
      - source: modbus
        id: 1
        uri: 192.168.158.13:8899
        register:
          address: 0x04A8 # T phase PCC current
          type: holding
          decode: uint16
        scale: 0.01
    powers:
      - source: modbus
        id: 1
        uri: 192.168.158.13:8899
        register:
          address: 0x0493 # ActivePower_PCC_R
          type: holding
          decode: int16
        scale: -10
      - source: modbus
        id: 1
        uri: 192.168.158.13:8899
        register:
          address: 0x049E # ActivePower_PCC_S
          type: holding
          decode: int16
        scale: -10
      - source: modbus
        id: 1
        uri: 192.168.158.13:8899
        register:
          address: 0x04A9 # ActivePower_PCC_T
          type: holding
          decode: int16
        scale: -10

  - name: sofar-pv
    type: custom
    power:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x05C4 # Total PV power
        type: holding
        decode: uint16
      scale: 100
    energy:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x0686 # PV_Generation_Total
        type: holding
        decode: uint32
      scale: 0.1
      
  - name: sofar-battery-1
    type: custom
    power:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x0606 # The charging and discharging power of the first battery pack. Charge is positive, discharge is negative
        type: holding
        decode: int16
      scale: -10
    energy:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x069A # Bat_Discharge_Total
        type: holding
        decode: uint32
      scale: 0.1
    soc:
      source: modbus
      id: 1
      uri: 192.168.158.13:8899
      register:
        address: 0x0608 # No. 1 battery pack SOC
        type: holding
        decode: uint16
    capacity: 10


loadpoints:
  - title: Garage
    charger: easee-garage
    # vehicle: tesla-m3-lr
    mode: pv
    phases: 0
    minCurrent: 6
    maxCurrent: 16
  - title: Stellplatz
    charger: easee-stellplatz
    # vehicle: tesla-m3-lr
    mode: pv
    phases: 0
    minCurrent: 6
    maxCurrent: 16



chargers:
  - name: easee-garage
    type: template
    template: easee
    user: xxxxxxxxx # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxxxxxx # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    charger: xxxxxxx
  - name: easee-stellplatz
    type: template
    template: easee
    user: xxxxxx # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxxxxxx # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    charger: xxxxxx



vehicles:
  - name: tesla-m3-lr
    type: template
    template: tesla
    title: Mr White # Wird in der Benutzeroberfläche angezeigt # Optional
    accessToken: xxxxxxx
    refreshToken: xxxxxxx
    mode: pv
    capacity: 79



tariffs:
  currency: EUR
  grid:
    type: fixed
    price: 0.227
  feedin:
    type: fixed
    price: 0.082
  co2:
    type: grünstromindex
    zip: 71126



messaging:
  events:
    # start:
    #   title: Ladestart - ${vehicleTitle}
    #   msg: |
    #     Modus:  ${mode} 
    #     PV Leistung: ${pvPower:%.1fk}kW
    #     Netz: ${gridPower:%.1fk}kW
    #     SOC (Haus): ${batterySoc}%
    # stop:
    #   title: Ladestop - ${vehicleTitle}
    #   msg: |
    #     SOC (${vehicleTitle}): ${vehicleSoc}%
    #     Geladen ${chargedEnergy:%.1fk}kWh in ${chargeDuration}
    #     PV Leistung: ${pvPower:%.1fk}kW
    #     SOC (Haus): ${batterySoc}%
    connect:
      title: Verbunden - ${vehicleTitle}
      msg: |
        Ladepunkt: ${title}
        Modus:  ${mode}
        PV Leistung: ${pvPower:%.1fk}kW
        SOC (Haus): ${batterySoc}%
    disconnect:
      title: Getrennt - ${vehicleTitle}
      msg: |
        SOC (${vehicleTitle}): ${vehicleSoc}%
        Geladen: ${chargedEnergy:%.1fk}kWh
        Verbindungsdauer: ${connectedDuration}
    guest:
      title: Unbekanntes Fahrzeug erkannt
      msg: Verbunden mit Ladepunkt ${title}
  services:
    - type: ntfy
      uri: https://ntfy.sh/schlipf-xxxxxxxxx
      priority: default
      tags: electric_plug,sunny


influx:
  url: http://localhost:8086
  database: evcc
  user: grafana
  password: 


mqtt:
  broker: localhost:1883
  topic: evcc

Log details

x

What type of operating system are you running?

Linux

Version

0.123.2

About this issue

  • Original URL
  • State: open
  • Created 6 months ago
  • Comments: 27 (10 by maintainers)

Most upvoted comments

das ist influx -version? Dann auch 1.8.10

Den Eintrag beim Log-Level ergänzen.

log: info
levels:
  cache: error
  influx: trace

evtl noch soc.poll auf “always” mit 1 Minute ändern (nur testweise) Neustart, evtl Ladung starten und dann nach ein paar Minuten Log abrufen https://docs.evcc.io/docs/guides/setup#wie-kann-ich-ein-logfile-zur-fehleranalyse-erstellen