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
Energy dashboard showing high values after update 5.0 and 5.1 #116762
Comments
Hey there @mletenay, @starkillerOG, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) goodwe documentation |
Which inverter model ? |
Hmmm, it seems I might accidentally break the DT inverter code in this commit marcelblijleven/goodwe@f41674c |
I can confirm the same issue. |
Fix for the above mentioned problem is on the way, but what bothers me a bit is it looks exactly like this ticket #115837 , but that was reported on 2024.4.1 where there was previous version of the goodwe library ... |
Same problem here since 2 may, Goodwe GW8K-DT |
Same Inverter and software, I will wait untill the fix |
Sorry for the troubles caused, but it seems there is a bug/problem with DT inverters that they sometimes report 0xFFFF/-1 as value of the total power/energy registers. To be honest, I have no idea how to fix your energy dashboard data. If my assumptions are correct, the 0 values should be removed and the rest recalculated ? Not sure how to do it or if it is possible at all ... This fix is already implemented and is waiting for review. |
There are 2 ways to fix the dashboard. Another way would be via the development tools, statistics. Then find the correct statistics entry. And there you can adjust incorrect entries. But this is a manual job. It does have a tool to show outliers to find them easy, but you still need to manually calculate the correct value. |
Thanks for the quick support and actions!
…On Sun, May 5, 2024 at 6:39 PM mletenay ***@***.***> wrote:
Sorry for the troubles caused, but it seems there is a bug/problem with DT
inverters that they sometimes report 0xFFFF/-1 as value of the total
power/energy registers.
And recent fix in underlying library which addressed problems with power
values on large inverters changed decoding behavior, which was
(unintentionally) working around this (not known) DT problem.
To be honest, I have no idea how to fix your energy dashboard data. If my
assumptions are correct, the 0 values should be removed and the rest
recalculated ? Not sure how to do it or if it is possible at all ...
This fix is already implemented and is waiting for review.
If you cannot or do not want to wait for next HA release, the fix is
already present in v0.9.9.18 of HACS version of this integration -
https://github.com/mletenay/home-assistant-goodwe-inverter
—
Reply to this email directly, view it on GitHub
<#116762 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWNZAWSA2O3LH5HMRTTS4NLZAZOFPAVCNFSM6AAAAABHGVZAHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUHA3TCNBWG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Met vriendelijke groet,
Jan van Sluisveld
|
For anyone reading this ticket. |
The problem
Since the core update 5.0 (and yesterday 5.1) my energy dashboard values are ruined. It has been working for years but for somehow it reads the values wrong. The biggest misread is the PV side, but the grid side is wrong also if I check the sensor changes in de integration (DSMR).
The dashboard:
The input sensors:
The sensors in the integrations:
What version of Home Assistant Core has the issue?
2024.5.1
What was the last working version of Home Assistant Core?
2024.4.4
What type of installation are you running?
Home Assistant Core
Integration causing the issue
GoodWE and DSMR
Link to integration documentation on our website
https://www.home-assistant.io/integrations/goodwe
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: