-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Solar production/Home consumption values wrong #119
Comments
I actually think this integration is broken. From one day to the next the values for solar and car are completely wrong now. One day it seems to show the total consumption/production, then some (random?) value. Home consumption is zero now for some reason. It claims we fed more in than what we produced. |
I actually think this integration is fundamentally broken. It hasn't been updated for quite a while unfortunately :/ |
same issue here. I suppose 2024.5 update broke the plugin. |
I saw weird behaviour already before - unfortunately it seems this integration is not updated anymore |
Related to #115 |
Something is wrong with the solar production and home consumption displays.
If I click on the bubble I can see that the underlying sensor was reporting the correct value for yesterday's solar yield (more than 100 kWh):
Yet, the flow chart only shows 37.4 kWh:
Today, we have reached 0.3 kWh but the bubble shows zero (UPDATE: few hours later and the solar production according to the bubble still sits at 0)
For the home consumption bubble it's the same: If I click on the bubble I can see that the sensor reports the correct value. Yet, the bubble shows a different (older?) value.
If I set
energy_date_selection
tofalse
the value for the solar production is correct. The value for home consumption is 0 (wrongly). And the grid import/export suddenly shows Megawatt hours, i.e. does not seem to only show today's values but those from the begin of time.The HomeAssistant energy flow card shows all values correctly (same sensor entities).
The text was updated successfully, but these errors were encountered: