Closed einmannlan closed 2 months ago
Hi @einmannlan, I fear that this is nothing I can really fix, the values seem just wrong, they don't even match the current Portal values if you take them as absolute values. Thus I can't even see a heuristic approach here to fix this, unfortunately. What you could do is run a template sensor above the one the integration delivers and build add a fixed offset to compensate. Additionally, you can open a support ticket at E3DC, in my eyes, that has to be fixed by them, whatever's wrong here. Cheers, Torben
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4987 Installed Version | 2.0.0 Stage | running Available Repositories | 1389 Downloaded Repositories | 16Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okDashboards
dashboards | 1 -- | -- resources | 10 views | 1 mode | storageRecorder
oldest_recorder_run | 4. August 2024 um 17:46 -- | -- current_recorder_run | 31. August 2024 um 10:03 estimated_db_size | 800.50 MiB database_engine | sqlite database_version | 3.45.3Checklist
Describe the issue
I've using the integration to monitor a S10E with the following config:
Using this configuration and even newest 3.8.0-beta.5 branch the s10e_additional_consumption_total value is negative but it's increasing.
I've check it using RSCPGUI and it seems it has the same problem: I guess its a bug in the calculation, because L1 is positive and L2+L3 is negative.
Expected total value of the additional power meter according to E3DC Portal is ~5.256 kWh.
Reproduction steps
Should be clear from above issue description, if same configuration is set I guess additional consumption will be wrong in any similar setup.
Debug logs
Diagnostics dump
No response