You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
The text was updated successfully, but these errors were encountered:
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
changed the title
Charge heatmap displays charges > 100%
Charge heatmap can be confusing due to auto bucket sizing.
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:
Expected behavior
Charge heatmap doesn't show charges > 100 unless the car actually manages to charge that far :)
Environment
The text was updated successfully, but these errors were encountered: