Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update 0.2.2 causes energy dashboard to break #37

Closed
N3rdix opened this issue May 10, 2024 · 6 comments
Closed

Update 0.2.2 causes energy dashboard to break #37

N3rdix opened this issue May 10, 2024 · 6 comments

Comments

@N3rdix
Copy link
Contributor

N3rdix commented May 10, 2024

Describe the bug
Although it is mentioned in the code that the new workaround for #32 should handle zero values correctly it seems to break something.
I have updated to 0.2.2 yesterday and now the total energy sensors jump to zero at night and jump back to the original value when the DTU starts at morning. This of course leads to incorrect solar production values as in my example.

To Reproduce
Steps to reproduce the behavior:

  1. Update to 0.2.2
  2. Add the total energy sensors to the energy dashboard
  3. See error

Expected behavior
The total energy sensors should not reset to zero at all.

Screenshots
image
image
image

Additional context
Temporary workaround can be to delete the outlier values every day, so at least nothing will break hard 😄

@suaveolent
Copy link
Owner

Thanks, you are right. Will provide a fix later today.

@suaveolent
Copy link
Owner

One more comment: you should not use total energy for the energy dashboard.

If you restart your home assistant instance and the inverter is not available it might return 0 anyway.

Instead use daily energy. It works just as intented even if the sensor is set to 0.

@N3rdix
Copy link
Contributor Author

N3rdix commented May 10, 2024

One more comment: you should not use total energy for the energy dashboard.

If you restart your home assistant instance and the inverter is not available it might return 0 anyway.

Instead use daily energy. It works just as intented even if the sensor is set to 0.

Thanks for that hint, will look into this although I did not have any trouble yet (luckily). Historically I've added total (total_increasing) sensors the past years, but according to the HA docs your advice might be the best choice 👍

@suaveolent
Copy link
Owner

v0.2.3 should fix the problem.

@N3rdix
Copy link
Contributor Author

N3rdix commented May 10, 2024

Thanks for the quick resolution, awesome work 👏

@suaveolent
Copy link
Owner

You‘re welcome. With the fix you should be able to keep using the total sensor.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants