Open johnwb87 opened 2 months ago
This is because the meaning of the data is a little different, the value represents the actual energy so far + the predicted energy remaining until midnight so its really today's estimate. It excludes any car charging. This means it should match at midnight but before it maybe different.
Describe the bug I've not been especially pleased with how the Predicted and Actual energy had been tracking so I went hunting. I found that the predbat.load_energy_actual entity is not tracking sensor.givtcp_xxxxxxxxxx_load_energy_today_kwh. I understand that predbat pulls from the givtcp sensor so it seems strange. Here's a normal day with no car charging. The start being high seems unusual to begin with and then the jumps seem strange.
Expected behavior The two entities track well so predbat is using good data.
Predbat version
Add-on v8.44
Environment details
G3 Hybrid with GivTCP Load filter threshold 90
Screenshots
Log file The new web interface handily shows no warn errors or unmapped entities in apps.yaml.