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
Incorrect report in bars vs history-graph #1054
Comments
On the next step of testing try with "line" graph & increase |
I am not following, do you mean that this The actual sensor is a ever growing counter of a flipping bucker flips, 1 flip == 0.5mm. Then there is a template sensor to make it millimetres. On top of that there are daily and hourly utility meters. Hopefully this makes sense.
Ok, trying this. But I suspect I just expect something what the card is not designed to do. The sensor I am using is utility meter per day. A couple of days ago it was raining, 25.5mm and this card was showing exactly that at the left top corner. But next day the bar for the day before is 14.48mm.
"Line" is even more confusing :) It is one dot per day, the numbers are same as with bars when hovering over the dots . |
Any issue related to
Note: MGC may be same as HG with it's simplest config (step 1) and may be not same with a desired config, it's ok, at least we'll localize the issue. step 1:
As for In the beginning of the graph I see many readings within an hour.
The
For the 1st step of our "investigation" a nature of this sensor is not important. |
@aik try adding |
I also think, this should help. The default aggregation function is 'mean', I think. |
2 cards reporting the same data differently. The cards are below, the amount of rain is >80mm but the second card says 55.
The rain sensor is an utility meter integrating from a rain gauge, daily. Interestingly, these cards work fine with another utility meter sensor which reports the rain data hourly, there I see the correct bars. What is missing in the second card?
The text was updated successfully, but these errors were encountered: