Skip to content
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

Charge heatmap can be confusing due to auto bucket sizing. #1354

Closed
leewillis77 opened this issue Feb 16, 2021 · 1 comment
Closed

Charge heatmap can be confusing due to auto bucket sizing. #1354

leewillis77 opened this issue Feb 16, 2021 · 1 comment

Comments

@leewillis77
Copy link
Contributor

leewillis77 commented Feb 16, 2021

Describe the bug

The Charge Heatmap (on the Charging Stats dashboard) shows charges > 100% even if no such data exists in the charging_processes table.

At first I assumed this was just down to the bucket size (which is set to auto - might be better set to bucket size 10?), but changing that doesn't make any difference.

See screenshot, and data extract below:
Screenshot 2021-02-16 at 17 43 11
Screenshot 2021-02-16 at 17 46 38

Expected behavior

Charge heatmap doesn't show charges > 100 unless the car actually manages to charge that far :)

Environment

  • TeslaMate version: 1.21.2
  • Type of installation: Docker
  • OS TeslaMate is installed on: RaspberryPi
  • User OS & Browser: Chrome / MacOSX
@leewillis77
Copy link
Contributor Author

Actually, I ignore most of the above report - I was confused by Teslamate showing a heatmap for one car, and comparing against data that I'd failed to filter down to just one car - my bad!

However, I do think that having auto bucket sizes causes confusion, so perhaps setting a bucket size of 10.00001 would be better. That ensures that 100% charges show in a "90-100" bucket rather than causing an additional 100-110 bucket.

Essentially though it will cause other common values to "drop down", so 90 will show in 80-90 rather than 90-100.

@leewillis77 leewillis77 changed the title Charge heatmap displays charges > 100% Charge heatmap can be confusing due to auto bucket sizing. Feb 16, 2021
adriankumpf pushed a commit that referenced this issue Feb 21, 2021

Verified

This commit was signed with the committer’s verified signature. The key has expired.
adriankumpf Adrian Kumpf
Co-authored-by: Lee Willis <lee@ademti-software.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant