Curves wrong in Optimize

[marco050969]

Description

Curves are wrong in Optimize Tab.

Steps to Reproduce

See Scrennshots

⚠️ RETURN TO EVCC TAB → COPY STEP 2 → PASTE HERE

Configuration (YAML)

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070
log: debug
levels:
  cache: error
# unique installation id
plant: *****
interval: 30s # control cycle interval
sponsortoken: *****
# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: true
site:
  title: Mein Zuhause
  meters:
    grid: grid1

Configuration (UI)

{
  "charger": [
    {"id":23,"name":"db:23","type":"template","config":{"connector":"1","connecttimeout":"5m","meter":"true","metervalues":"Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage","stationid":"***","template":"ocpp-evbox-elvi"},"deviceProduct":"EVBox Elvi"}
  ],
  "experimental": true,
  "influx": {"url":"","database":"","token":"","org":"","user":"","password":"","insecure":false},
  "interval": 15,
  "loadpoints": [
    {"id":24,"name":"db:24","batteryBoostLimit":80,"charger":"db:23","defaultMode":"pv","limitEnergy":0,"limitSoc":0,"maxCurrent":16,"minCurrent":6,"phasesConfigured":3,"planEnergy":0,"planPrecondition":0,"planStrategy":{"continuous":false,"precondition":0},"planTime":"0001-01-01T00:00:00Z","priority":0,"smartCostLimit":null,"smartFeedInPriorityLimit":null,"soc":{"poll":{"mode":"charging","interval":3600000000000},"estimate":true},"thresholds":{"enable":{"delay":60000000000,"threshold":0},"disable":{"delay":180000000000,"threshold":0}},"title":"Carport"}
  ],
  "meter": [
    {"id":18,"name":"db:18","type":"template","config":{"host":"192.168.178.83","id":"0","template":"hoymiles-ahoydtu","usage":"pv"},"deviceProduct":"Hoymiles HM & HMS Series (via AhoyDTU)","deviceTitle":"BKW 600 Watt"},
    {"id":29,"name":"db:29","type":"template","config":{"baudrate":9600,"capacity":15,"comset":"8N1","host":"192.168.178.113","id":1,"maxchargepower":5000,"maxdischargepower":5000,"maxsoc":100,"minsoc":0,"modbus":"tcpip","port":502,"template":"huawei-emma","usage":"battery"},"deviceProduct":"Huawei EMMA","deviceTitle":"Huawei Luna"},
    {"id":27,"name":"db:27","type":"template","config":{"baudrate":9600,"comset":"8N1","host":"192.168.178.113","id":1,"modbus":"tcpip","port":502,"template":"huawei-emma","usage":"pv"},"deviceProduct":"Huawei EMMA","deviceTitle":"Huawei Sun 2000"},
    {"id":28,"name":"db:28","type":"template","config":{"baudrate":9600,"comset":"8N1","host":"192.168.178.113","id":0,"modbus":"tcpip","port":502,"template":"huawei-emma","usage":"grid"},"deviceProduct":"Huawei EMMA"}
  ],
  "mqtt": {"broker":"","user":"","password":"","clientID":"","insecure":false,"caCert":"","clientCert":"","clientKey":"","topic":"evcc"},
  "residualPower": 0,
  "shm": {"vendorId":"","deviceId":"","deviceSerial":""},
  "site": {"title":"Mein Zuhause","grid":"db:28","pv":["db:18","db:27"],"battery":["db:29"],"aux":null,"ext":null,"consumers":null},
  "tariff": [
    {"id":20,"name":"db:20","type":"template","config":{"price":0.00082,"template":"fixed"},"deviceProduct":"Fester Preis"},
    {"id":19,"name":"db:19","type":"template","config":{"price":0.003406,"template":"fixed"},"deviceProduct":"Fester Preis"},
    {"id":21,"name":"db:21","type":"template","config":{"template":"grünstromindex","token":"***","zip":"***"},"deviceProduct":"Grünstromindex"},
    {"id":22,"name":"db:22","type":"template","config":{"ac":"1000","alphatemp":"-0.004","az":45,"de":"0","dec":40,"dm":"0","efficiency":"100","interval":"1h","kwp":10.44,"lat":"***","lon":"***","rossmodel":"0.0342","template":"open-meteo"},"deviceProduct":"Open-Meteo","deviceTitle":"PV Vorhersage"}
  ],
  "tariffRefs": {"grid":"db:19","feedIn":"db:20","co2":"db:21","planner":"","solar":["db:22"]},
  "vehicle": [
    {"id":30,"name":"db:30","type":"template","config":{"cache":"15m","capacity":36,"climaterdisabled":false,"icon":"rocket","maxCurrent":16,"minCurrent":6,"mode":"pv","password":"***","phases":"2","priority":0,"template":"skoda","title":"Froggy","user":"***","vin":"***"},"deviceProduct":"Škoda MyŠkoda"}
  ]
}

Logs

[lp-1  ] DEBUG 2026/08/08 14:42:28 charge power: 3285W
[lp-1  ] DEBUG 2026/08/08 14:42:28 charge currents: [14.9 0 0]A
[site  ] DEBUG 2026/08/08 14:42:28 pv 1 power: 544W
[site  ] DEBUG 2026/08/08 14:42:28 grid power: -2295W
[site  ] DEBUG 2026/08/08 14:42:28 pv 2 power: 8324W
[site  ] DEBUG 2026/08/08 14:42:28 battery 1 power: -2454W
[site  ] DEBUG 2026/08/08 14:42:28 pv power: 8868W
[site  ] DEBUG 2026/08/08 14:42:28 grid powers: [-1483 -2394 1582]W
[site  ] DEBUG 2026/08/08 14:42:29 battery 1 soc: 84%
[site  ] DEBUG 2026/08/08 14:42:29 grid currents: [-6.8 -10.4 7]A
[site  ] DEBUG 2026/08/08 14:42:29 battery has priority at soc 84% (< 90%)
[site  ] DEBUG 2026/08/08 14:42:29 site power: -2195W
[lp-1  ] DEBUG 2026/08/08 14:42:29 charge voltages: [219 3 13]V
[lp-1  ] DEBUG 2026/08/08 14:42:29 detected connected phases: 1p
[lp-1  ] DEBUG 2026/08/08 14:42:29 detected active phases: 1p
[lp-1  ] DEBUG 2026/08/08 14:42:29 session energy: 8.470kWh
[lp-1  ] DEBUG 2026/08/08 14:42:29 charge total import: 4139.620kWh
[lp-1  ] DEBUG 2026/08/08 14:42:29 charger status: C
[lp-1  ] DEBUG 2026/08/08 14:42:29 vehicle soc: 85%
[lp-1  ] DEBUG 2026/08/08 14:42:29 vehicle range: 210km
[lp-1  ] DEBUG 2026/08/08 14:42:29 soc estimated: 86.89% (vehicle: 85.00%)
[lp-1  ] DEBUG 2026/08/08 14:42:29 vehicle soc (estimator): 87%
[lp-1  ] DEBUG 2026/08/08 14:42:29 !! plan: plan time zero
[lp-1  ] DEBUG 2026/08/08 14:42:29 pv charge current: 25.5A = 16A + 9.54A (-2195W @ 1p)
[site  ] DEBUG 2026/08/08 14:42:29 solar forecast: produced 25.388kWh, forecasted 31.366kWh, scale 0.809

Version

v0.309.2

System

linux/arm64, CEST +02:00

[iseeberg79]

Looks like an enormous jump within your recorded (historic) household metrics. Forecast is getting adjusted accordingly. 1800kW isn't right?

[iseeberg79]

Or specifically:

evcc metrics data db:28 --from 2026-08-02 --to 2026-08-02 --aggregate 15m --csv

[marco050969]

I´m not so fit in Linux so i don´t know what i do ...my english is more bad... :)

Do you have a command to fix that immediately?

pi@evcc:~ $ evcc metrics data db:28 --from 2026-08-02 --to 2026-08-02 --aggregate 15m --csv
[main ] INFO 2026/08/08 18:25:56 using config file: /etc/evcc.yaml
[main ] FATAL 2026/08/08 18:25:56
Found systemd service database at "/var/lib/evcc/evcc.db", evcc has been invoked with no explicit database path.
Running the same config with multiple databases can lead to expiring vehicle tokens.

If you want to use the existing service database run the following command:

sudo evcc --database /var/lib/evcc/evcc.db

If you want to create a new user-space database run the following command:

evcc --database ~/.evcc/evcc.db

If you know what you're doing, you can skip the database check with the --ignore-db flag.

[iseeberg79]

So the bug seems to be known, has been described multiple times (#29286, #30555), and has been patched twice—but not released. Version 0.309.2 still has this vulnerability.

db:28 is your grid meter — that matches what homePower is derived from (grid + pv − battery), so the spike traces back there.

Your evcc log around that timestamp (once you have it from step 1), e.g.:

journalctl -u evcc --since "2026-08-02 HH:MM" --until "2026-08-02 HH:MM"

Looking for anything like a Modbus timeout/reconnect to the EMMA device at that time.

---

Once you have the timestamp, here's the fix. The data lives in the meters table (one row per 15-min slot: meter = entity id, ts = unix timestamp of slot start, energy/return_energy in kWh):

sudo systemctl stop evcc
cp /var/lib/evcc/evcc.db /var/lib/evcc/evcc.db.bak

-- find it (gives you the exact ts)
sqlite3 /var/lib/evcc/evcc.db "
  SELECT ts, datetime(ts,'unixepoch','localtime') AS slot, energy, return_energy
  FROM meters WHERE meter=28
    AND ts >= strftime('%s','2026-08-02 00:00:00')
    AND ts <  strftime('%s','2026-08-03 00:00:00')
  ORDER BY energy DESC LIMIT 10;"

-- then delete just that row (safest, since the real value is unknown)
sqlite3 /var/lib/evcc/evcc.db "DELETE FROM meters WHERE meter=28 AND ts=<BAD_TS>;"

Then sudo systemctl start evcc.

Worth also checking entities.energy_meter for id 28 — if the bad cumulative reading is still stored there as the baseline, the next real reading could produce another anomaly on recovery:

sqlite3 /var/lib/evcc/evcc.db "SELECT id, name, energy_meter, return_energy_meter FROM entities WHERE id=28;"

I've assumed a database in /var/lib/evcc.

There is a bugfix prepared that might adress the error.

[mfuchs1984]

Version 0.309.2 still has this vulnerability.

This version is quite outdated. The current one is 0.313.2

[iseeberg79]

Version 0.309.2 still has this vulnerability.

This version is quite outdated. The current one

is 0.313.0/2

[marco050969]

Alle genannten Lösungsvorschläge werden mit Fehlern quittiert, ich bin leider nicht in der Lage, das alles umzusetzen. Das Update habe ich mittlerweile aufgespielt, es kommen aber nur mehr noch mehr Fehler dazu.

vor 2 Minuten

[db:18-BKW 600 Watt] WARN 2026/08/08 21:17:59 uncached request repeated within 1s, please report at https://github.com/evcc-io/evcc/issues: http://192.168.178.83/api/inverter/id/0
vor 5 Minuten

optimizer: meter profile incomplete
vor 5 Minuten

[db:18-BKW 600 Watt] WARN 2026/08/08 21:14:38 uncached request repeated within 1s, please report at https://github.com/evcc-io/evcc/issues: http://192.168.178.83/api/inverter/id/0

Mag mir wer über Teams oder Pi Connect helfen?? Ich schaffe das nicht...Ich wollte die Datenbank über ein Windowstool ändern, selbst das funktioniert nicht.

[mfuchs1984]

Ich wollte die Datenbank über ein Windowstool ändern, selbst das funktioniert nicht.

Welches Tool? Was bedeutet "funktioniert nicht" genau?

[marco050969]

db Browser for SQLite. Die Datenbank kann ich öffen, ist aber leer, bzw. nichts zum editieren da. Auf dem PI selbst klappt das auch nicht nach >>>>Fix wrong data in history after #30950 #31129
Ich bin da definitiv zu blöde für...sorry.

[mfuchs1984]

Eventuell hast du einfach die falsche erwischt. Starte evcc neu und schau ins log. Dort wird der Pfad zur DB geloggt.

[iseeberg79]

Das kriegen wir schon hin, erstmal DB finden

[marco050969]

Mit Hilfe von ChatGPT hat es schlussendlich geklappt. Sonst hätte ich die Wallbox und das Laptop leider vernichtet. Ich hab gerade eine ganz kurze Zündschnur, es klappt einfach nichts und das Wetter setzt mir sowas von zu als Lungenkranker, der eigentlich auf die Spenderliste soll, aber dafür gehts mir ja noch zu gut. Trotzdem besten Dank an @mfuchs1984 und @iseeberg79 für die schnelle Hilfe.

[iseeberg79]

Ab heute gibt es zusätzlich zu:

curl "http://evcc-host:7070/api/history/energy?from=2026-08-02T02:00:00Z&to=2026-08-02T02:59:59Z&name=db:28"

Um eine Teilmenge, oder ganzen verdächtigen Zeitraum zu entfernen:

curl -X DELETE
-H "X-Admin-Password: "
"http://evcc-host:7070/api/db/metrics/energy?from=2026-08-02T02:00:00Z&to=2026-08-02T02:59:59Z&name=db:28"

Damit wäre es deutlich einfacher gewesen.

[marco050969]

Schade Schokolade 🍫 einen Tag zu spät und ChatGpt hat noch einen Fehler gefunden im Juni nach installieren des Emma und Rückbau Dongle. Jetzt ist alles in Ordnung soweit. Hab zwar noch andere Unstimmige Problemchen, gehören hier aber nicht hin.