Possible Bug in Energy Dashboard with -0 Value

[MrCaspan]

Hey guys I hope this is the right place to post this, if not can you please let me know the correct please to post this bug?

https://community.home-assistant.io/t/issue-with-corrected-energy-readings-and-0-bug/867917

If you look at that Post it explains with screenshots that if I use the developer tools and correct a bad reading from one of my energy sensors that if I correct that value form a negative value to 0 and there are no more readings for that hour the total kWh for that device for that hour will report as -0 and causes a visual issue with the energy consumption graph. Not a huge deal but it starts to show the negative scale of the graph because your code perceives a negative number will need to be displayed (because it sees -0 and then accordingly set the high and low for the y axis of the graph. it looks liek you add about a 0.3 as a buffer to the y axis so that there is a bit of a padding before the end of the graph at the bottom.. Again to me this is an issue that it should never evaluate to -0 but maybe want to make sure the code for the front end shows as proper also if this ever happens.. maybe instead test for a if values is < 0 then testing for is value is negative

Again it's not a bad issue but it also shows this 0 value in the hourly graph and really it should not show at all because it has 0 value. Not sure where the problem should be fixed but jsut want to let someone know so they can address it or point me in the right direction!

[karwosts]

I'm wondering if there's some tiny value that's less than 0 but it's just getting rounded to zero in the display, which I think has limited decimal points.

What does adjust sum look like for this sensor for that hour?

[MrCaspan]

Great Point! didn't think bout that. When I looked using the Developer tools for that hour they all said 0 but I never looked at the database which I thought about after in the long term stats table. Kicking myself for not doing that now. To fix it I just set one of the reading for the hour to 0.01 . This corrected the value and all the issues in my database AND I fixed all my filters that allowed these bad reading. So the problem is I am not sure if it will happen with me again to recreate it or check the DB again.. but you are right it might be a rounding issues also!