-
Notifications
You must be signed in to change notification settings - Fork 879
feat(dashboards): several Improvements for Charging Stats, Statistics and Trip #4791
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
Conversation
…tive charges, better cost per 100km for shorter time periods
✅ Deploy Preview for teslamate ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
JakobLichterfeld
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, ty!
|
Thanks for your work, ideas and great solutions!
#4787 is merged :-) |
|
👍 - @JakobLichterfeld , updated and included cost per 100km in trips dashboard (incl. updated screenshot). |
|
It might result in wrong stats when a Charging process is ongoing at end or start of period. Let me check that later! |
|
ok, aligned cost per 100km/mi calculations across trip, statistics and charging stats dashboards all of them are based on consumption gross, distance and cost per kwh now - that way different soc at beginning and end of period is always considered. ready to be reviewed / merged! :) |
fixes Inconsitant Charging Stats #4788 by aligning query conditions and introducing a min duration filter applied to all panels
come up with a new way to reliably calculate charging costs per 100km for shorter periods -> see here for details feat: add cost per mileage to trips dashboard #4678 (comment)
will be applied to the trip dashboard once fix: align usage of time-range filters to fix consumption gross issues in some edge cases #4787 is merged, than superseding feat: add cost per mileage to trips dashboard #4678
detect consecutive charges and exclude from Charge / Discharge Stats
could be a first step towards Request: Charge tracking merge #673 (beeing a purely query solution that for instance could be toggled on / off in charging dashboards)