Deye SUN SG01HP3-EU-AM2 History values too large by a factor of ten

[froschwilly]

Description

With my Deye SUN SG01HP3-EU-AM2 high-voltage hybrid inverter (HMI C035; MAIN 1066), the values of generation, battery and the counter values of the CT terminals are displayed too large by a factor of ten. How can I fix this myself? Greetings Willy

Steps to Reproduce

In the UI I go to History and look at the values in detail

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

Configuration (YAML)

no yaml configuration

Configuration (UI)

{
  "experimental": true,
  "influx": {"database":"","insecure":false,"org":"","password":"","token":"","url":"","user":""},
  "interval": 30,
  "meter": [
    {"id":16,"name":"db:16","type":"template","config":{"id":1,"template":"eastron","baudrate":9600,"comset":"8N1","delay":"1s","host":"192.168.1.93","modbus":"tcpip","port":502,"timeout":"5s","usage":"pv"},"deviceProduct":"Eastron SDM630-Modbus","deviceTitle":"SofarSolar SOFAR 3.3…12KTLX-G3"},
    {"id":2,"name":"db:2","type":"template","config":{"id":1,"template":"deye-hybrid-3p","batterytype":"hv","baudrate":9600,"comset":"8N1","firmware1098":false,"gridchargecurrent":"0","host":"192.168.1.111","includegenport":true,"maxacpower":"0","maxdischargecurrent":"0","modbus":"tcpip","port":502,"storageunit":"1","usage":"grid"},"deviceIcon":"meter","deviceProduct":"Deye 3p hybrid inverter","deviceTitle":"Deye CT Klemmen"},
    {"id":4,"name":"db:4","type":"template","config":{"id":1,"template":"deye-hybrid-3p","batterytype":"hv","baudrate":9600,"comset":"8N1","firmware1098":false,"gridchargecurrent":"4","host":"192.168.1.111","includegenport":true,"maxacpower":7500,"maxdischargecurrent":"20","modbus":"tcpip","port":502,"storageunit":"1","usage":"pv"},"deviceProduct":"Deye 3p hybrid inverter","deviceTitle":"Deye GEN Port (SMA Tripower 10kWp)"},
    {"id":3,"name":"db:3","type":"template","config":{"id":1,"template":"deye-hybrid-3p","batterytype":"hv","baudrate":9600,"capacity":25.6,"comset":"8N1","delay":5000000000,"firmware1098":false,"gridchargecurrent":"7","host":"192.168.1.111","includegenport":true,"maxacpower":"0","maxchargepower":1500,"maxdischargecurrent":"20","maxdischargepower":11000,"maxsoc":90,"minsoc":10,"modbus":"tcpip","port":502,"storageunit":"1","timeout":10000000000,"usage":"battery"},"deviceProduct":"Deye 3p hybrid inverter","deviceTitle":"Deye Akkuport (Felicity 25,6kWh)"},
    {"id":1,"name":"db:1","type":"template","config":{"template":"discovergy","meter":"1ESY1160865127","password":"***","usage":"grid","user":"***"},"deviceProduct":"Discovergy"}
  ],
  "mqtt": {"broker":"","caCert":"","clientCert":"","clientID":"","clientKey":"","insecure":false,"password":"","topic":"evcc","user":""},
  "residualPower": 40,
  "shm": {"deviceId":"","deviceSerial":"","vendorId":""},
  "site": {"aux":null,"battery":["db:3"],"consumer":null,"ext":["db:2"],"grid":"db:1","pv":["db:4","db:16"],"title":"EVCC HEMS"},
  "tariff": [
    {"id":6,"name":"db:6","type":"template","config":{"template":"fixed","price":0.12},"deviceProduct":"Fester Preis"},
    {"id":5,"name":"db:5","type":"template","config":{"template":"fixed","price":0.31},"deviceProduct":"Fester Preis"},
    {"id":8,"name":"db:8","type":"template","config":{"template":"forecast-solar","az":-30,"dec":35,"interval":"1h","kwp":9.75,"lat":"***","lon":"***"},"deviceProduct":"Forecast.Solar","deviceTitle":"PVPrognose"},
    {"id":7,"name":"db:7","type":"template","config":{"template":"dwd-temperature","interval":"1h","lat":"***","lon":"***"},"deviceProduct":"DWD (Bright Sky) Temperature"}
  ],
  "tariffRefs": {"co2":"","feedIn":"db:6","grid":"db:5","planner":"","solar":["db:8"],"temperature":"db:7"}
}

Logs

[site  ] DEBUG 2026/08/21 22:12:44 pv 1 power: 0W
[site  ] DEBUG 2026/08/21 22:12:49 pv power: 0W
[site  ] DEBUG 2026/08/21 22:12:54 battery 1 soc: 78%
[site  ] DEBUG 2026/08/21 22:12:54 site power: 642W
[site  ] DEBUG 2026/08/21 22:12:54 solar forecast: produced 263.185kWh, forecasted 16.144kWh, scale 16.302
[site  ] DEBUG 2026/08/21 22:13:04 ----
[site  ] DEBUG 2026/08/21 22:13:04 grid power: -10W
[site  ] DEBUG 2026/08/21 22:13:05 pv 2 power: -0W
[site  ] DEBUG 2026/08/21 22:13:09 battery 1 power: 650W
[site  ] DEBUG 2026/08/21 22:13:09 ext 1 power: 4W
[site  ] DEBUG 2026/08/21 22:13:14 pv 1 power: 0W
[site  ] DEBUG 2026/08/21 22:13:19 pv power: 0W
[site  ] DEBUG 2026/08/21 22:13:24 battery 1 soc: 78%
[site  ] DEBUG 2026/08/21 22:13:24 site power: 680W
[site  ] DEBUG 2026/08/21 22:13:24 solar forecast: produced 263.185kWh, forecasted 16.144kWh, scale 16.302
[site  ] DEBUG 2026/08/21 22:13:34 ----
[site  ] DEBUG 2026/08/21 22:13:34 grid power: -16W
[site  ] DEBUG 2026/08/21 22:13:35 pv 2 power: -0W
[site  ] DEBUG 2026/08/21 22:13:39 battery 1 power: 630W
[site  ] DEBUG 2026/08/21 22:13:39 ext 1 power: 3W
[site  ] DEBUG 2026/08/21 22:13:44 pv 1 power: 0W
[site  ] DEBUG 2026/08/21 22:13:49 pv power: 0W
[site  ] DEBUG 2026/08/21 22:13:54 battery 1 soc: 78%
[site  ] DEBUG 2026/08/21 22:13:54 site power: 654W
[site  ] DEBUG 2026/08/21 22:13:54 solar forecast: produced 263.185kWh, forecasted 16.144kWh, scale 16.302

Version

v0.314.2

System

linux/arm64, CEST +02:00

[github-actions]

Thanks for the report. I looked at templates/definition/meter/deye-hybrid-3p.yaml, which is used for your deye-hybrid-3p grid/PV/battery meters.

The energy values (grid Total_GridBuy/GridSell_Power, PV Total_PV_Power/Total_Gen_Power, battery charge/discharge) are scaled with a factor that depends on batterytype and the firmware1098 option:

{{- if or (eq .batterytype "lv") (not .firmware1098) }}
scale: 0.1
{{- end }}

For your config (batterytype: hv, firmware1098: false), a scale: 0.1 is applied. There has been a similar scaling bug fixed before for other Deye firmware/battery combinations (#31543, #30482), so a wrong scale factor for your specific combination (HV, firmware MAIN 1066, i.e. firmware1098 unchecked) is plausible, but I can't confirm it from the report as-is:

• The "Steps to Reproduce" section still contains the template placeholder — no actual History/Config values were pasted.
• The shared debug log only contains power/soc lines, no energy lines, so I can't see the actual computed value or compare it to the raw register data.

Could you provide:

1. The actual values shown on evcc's History/Config pages (numbers or a screenshot), together with the value you'd expect (e.g. from the Deye monitoring app/portal, or your utility meter), so the factor can be verified.
2. A debug log snippet that includes the energy log lines (not just power/soc), e.g. via evcc -l debug while History/Config is open.
3. Confirmation that hv is indeed the correct battery type for your setup, and the exact firmware version (main/HMI) you're running.

With that I can determine whether the scale condition needs adjusting for this firmware/battery combination.

🤖 Generated with Claude Code

[froschwilly]

Excuse me, I answer in German...
Die exakte FW meines Deye SUN SG01HP3-EU-AM2 lautet HMI: 2001-C035 MAIN: 3002-1066-1E08
Der daran über CAN angeschlossene Akku ist ein Hochvoltakku der Fa. Felicity Typ LUX-X-96050HG01.
Alle Werte am Deye Display sind plausibel dargestellt.
Die Konfig der EVCC-UI mit den drei Einsatzbereichen des HV Deye (Netzzähler, PV-Produktion und Batterie) habe ich alle wie im Blogbeitrag angegeben (https://docs.evcc.io/de/meters/deye-3p-hybrid-inverter/) identisch angelegt, mit dem Zusatz bei "weiteren Einstellungen" "GEN-Anschluss als Solar-Eingang verwenden" auf EIN (hier hängt ein Stringinverter mit max. 7500W PV Leistung dran) und "Firmware 1098 oder neuer (nur für HV Versionen)" auf AUS (wg. der 1066).
Ich füge aus der Historie zwei Screenshots bei, in denen die Werte um den Faktor 10 zu hoch dargestellt werden und einen beispielhaft für die drei angelegten Einsatzbereiche (Netzzähler, PV-Produktion und Batterie).

Ich hoffe damit wird mein Problem besser erkennbar.
Danke für den schnellen Support
Gruß Willy

[github-actions]

Thanks for the details, @froschwilly. Confirmed config: batterytype: hv, firmware1098: false (MAIN 3002-1066-1E08, so pre-1098 as expected).

Unfortunately I can't process the screenshots in this automated analysis (no vision access), so I still can't read the actual numbers from them, and the log snippet still only has power/soc lines, not the energy/returnenergy lines that drive the History page (core/site.go persists History from each meter's energy/returnenergy register, not from integrating power).

For your exact combination (hv + firmware1098 unchecked), templates/definition/meter/deye-hybrid-3p.yaml already applies scale: 0.1 to the Total_GridBuy/GridSell_Power, Total_PV_Power, Total_Gen_Power and battery charge/discharge Wh registers — this is the condition the template has used for this specific combination since it was introduced, and the two related fixes (#31543, #30482) only changed behavior for the lv and firmware1098: true cases, not this one. So on paper this case should already be handled, which means either:

• this particular firmware/register still needs a different factor than 0.1 (raw register isn't in the unit the template assumes), or
• the discrepancy you're seeing is actually in the power values (PV1-4 input power / battery power), which get scale: 10 applied whenever batterytype: hv, regardless of firmware1098 — unlike the energy fields, this isn't gated on firmware version, so it's a plausible separate source of a 10x error for older HV firmware.

To pin this down, could you provide as plain text (not screenshots):

1. The exact History values evcc shows (kWh) for grid, PV and battery, together with the true values from the Deye app/portal for the same period.
2. Whether the live Dashboard power values (PV generation power, battery charge/discharge power) are also ~10x too high, or only the History/kWh totals.
3. A debug log snippet (evcc -l debug) that includes the energy/returnenergy lines for grid, pv and battery (they're logged less frequently than power, so let it run a bit longer).

With that I can tell whether the fix belongs in the energy scale condition or the power scale condition (or both).

🤖 Generated with Claude Code

[froschwilly]

Hallo,
zu 1.Mein Deye Inverter ist nicht mit der Deye Cloud verbunden, deshalb kann ich leider nicht mit Vergleichsdaten einer Deye App oder des Deye Portals dienen.
zu 2. Die Werte im Live Dashboard sind alle plausibel. Nur in der Historie werden die Werte zum Deye falsch dargestellt
zu 3. In der Linux Console:
willy@willy-Veriton-M680G:$ ssh admin@192.168.1.94
admin@192.168.1.94's password:
Web console: https://evcc:9090/ or https://192.168.1.94:9090/
Last login: Sat Aug 22 00:29:27 2026 from 192.168.1.11
admin@evcc:$ evcc -l debug
[main ] INFO 2026/08/22 00:40:44 evcc 0.314.2
[main ] INFO 2026/08/22 00:40:44 config file not found, database-only mode
[main ] FATAL 2026/08/22 00:40:44
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.
admin@evcc:$

Wie bekomme ich das von dir gewünschte logfile?

[andig]

Please test the PR

[froschwilly]

andig wrote: "Please test the PR"
Hallo, um den Fix zu testen musste ich von stable auf nightly builds switchen und ja, die Werte in der Konfigurationsansicht kommen nun korrekt rein und auch die Historiewerte passen nun.
Danke für den schnellen Support
Gruß Willy