Bug description
The Energy Mix shown in the evaluation/statistics appears to be calculated incorrectly.
Grid consumption is either missing completely or reported as 0, although the grid meter data clearly shows actual energy imported from the grid.
This causes the Energy Mix to assign almost/all consumed energy to PV, although part of the energy was demonstrably supplied by the grid.
Expected behavior
The Energy Mix should correctly distribute consumed energy between the available energy sources, especially:
- Grid
- PV
- Battery
- Charging points, where applicable
Whenever the grid meter reports positive imported energy, the corresponding grid share must also be reflected in the Energy Mix and in fields such as energy_imported_grid.
Actual behavior
In the attached monthly JSON export for August 2026, counter0.energy_imported contains positive grid import values, while the calculated Energy Mix reports the grid share as 0.0.
Example for 2026-08-01:
"counter": {
"counter0": {
"grid": true,
"energy_imported": 0.583,
"energy_exported": 8.145
}
}
At the same time, the charging point aggregation contains:
"cp": {
"all": {
"energy_imported": 19.164,
"energy_imported_grid": 0,
"energy_imported_pv": 19.164,
"energy_imported_bat": 0
}
}
The home consumption aggregation shows the same behavior:
"hc": {
"all": {
"energy_imported": 9.559,
"energy_imported_grid": 0,
"energy_imported_pv": 9.559,
"energy_imported_bat": 0
}
}
And the resulting Energy Mix is:
"energy_source": {
"grid": 0.0,
"pv": 1.0,
"bat": 0.0,
"cp": 0.0
}
This cannot be correct because the same daily record contains a measured grid import of 0.583 kWh.
Reproducibility / additional findings
The problem is not limited to a single day.
The attached file openwb_monthly_202608.json contains 17 daily entries from 2026-08-01 to 2026-08-17.
For all 17 entries:
counter0.energy_imported is greater than 0
- the summed measured grid import is approximately 5.769 kWh
energy_source.grid is nevertheless 0.0
cp.all.energy_imported_grid is 0
hc.all.energy_imported_grid is 0
For comparison, the JSON contains approximately:
- total charging point consumption: 126.962 kWh
- assigned charging point grid energy: 0 kWh
- total home consumption: 132.510 kWh
- assigned home grid energy: 0 kWh
Therefore it looks as if grid energy is not included in the source allocation at all and consumption is instead attributed almost completely to PV.
Possible area to investigate
The raw grid meter data itself appears to be available because counter0.energy_imported contains plausible non-zero values.
The issue therefore seems more likely to be located in the subsequent calculation/allocation of the energy sources used for:
energy_imported_grid
energy_imported_pv
energy_imported_bat
energy_source
- Energy Mix visualization/statistics
Please check whether grid import is currently omitted or incorrectly assigned during the calculation of the Energy Mix.
System information
- openWB version: 2.2.2
- openWB variant: series2 Standard+
- Browser cache cleared: yes
- PV module / inverter: SMA Tripower 6.0 and Sunnyboy 3.0
- EVU / grid meter module: SMA HomeManager 2.0
- Battery module: Solakon
Attachments
openwb_monthly_202608.json
Summary
The grid meter records real grid import, but this energy is not reflected in the calculated Energy Mix.
The monthly JSON clearly shows positive counter0.energy_imported values while energy_imported_grid and energy_source.grid remain 0.
As a result, the Energy Mix displayed in the evaluations does not match the actual measured energy flows.
openwb_monthly_202608.json
Bug description
The Energy Mix shown in the evaluation/statistics appears to be calculated incorrectly.
Grid consumption is either missing completely or reported as
0, although the grid meter data clearly shows actual energy imported from the grid.This causes the Energy Mix to assign almost/all consumed energy to PV, although part of the energy was demonstrably supplied by the grid.
Expected behavior
The Energy Mix should correctly distribute consumed energy between the available energy sources, especially:
Whenever the grid meter reports positive imported energy, the corresponding grid share must also be reflected in the Energy Mix and in fields such as
energy_imported_grid.Actual behavior
In the attached monthly JSON export for August 2026,
counter0.energy_importedcontains positive grid import values, while the calculated Energy Mix reports the grid share as0.0.Example for 2026-08-01:
At the same time, the charging point aggregation contains:
The home consumption aggregation shows the same behavior:
And the resulting Energy Mix is:
This cannot be correct because the same daily record contains a measured grid import of
0.583 kWh.Reproducibility / additional findings
The problem is not limited to a single day.
The attached file
openwb_monthly_202608.jsoncontains 17 daily entries from 2026-08-01 to 2026-08-17.For all 17 entries:
counter0.energy_importedis greater than0energy_source.gridis nevertheless0.0cp.all.energy_imported_gridis0hc.all.energy_imported_gridis0For comparison, the JSON contains approximately:
Therefore it looks as if grid energy is not included in the source allocation at all and consumption is instead attributed almost completely to PV.
Possible area to investigate
The raw grid meter data itself appears to be available because
counter0.energy_importedcontains plausible non-zero values.The issue therefore seems more likely to be located in the subsequent calculation/allocation of the energy sources used for:
energy_imported_gridenergy_imported_pvenergy_imported_batenergy_sourcePlease check whether grid import is currently omitted or incorrectly assigned during the calculation of the Energy Mix.
System information
Attachments
openwb_monthly_202608.jsonSummary
The grid meter records real grid import, but this energy is not reflected in the calculated Energy Mix.
The monthly JSON clearly shows positive
counter0.energy_importedvalues whileenergy_imported_gridandenergy_source.gridremain0.As a result, the Energy Mix displayed in the evaluations does not match the actual measured energy flows.
openwb_monthly_202608.json