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
Statistics and Trip display are inconsistent #3832
Comments
Thanks for reporting. Even if it seems unrelated, please use latest version, which is as of now 1.28.5 |
Additional your second screenshot shows timeframe from 2024-04-09 till 2024-04-10 |
I'm not able to reproduce on teslamate 1.28.5 |
Hmmm, interesting. In the first screenshot of drives, there is an entry as of 2024/09/04 01:... of 35km. Although the range does not include that time. Difficult to track that down, when not in Shangai timezone... |
Thank you for your answer. My default time zone is Shanghai, which has been shown as 8:00 when I first deployed it |
Thank you. Yes, the content shown in the second picture is correct. |
Please note that I also found a problem, this problem may not be important, my server time zone is Shanghai, but the data stored in my database is not saved according to the time of Shanghai, my browser time zone is also Shanghai. I don't know if this is normal. |
@Fred3343 you might want to try the new version in #3857 (comment) |
PR created #3862. Please test and discuss there. |
@Fred3343 could you test latest version https://github.com/DrMichael/teslamate/blob/master/grafana/dashboards/statistics.json? |
I tested the statistics.json and I'm sure it works, thanks |
Is there an existing issue for this?
What happened?
In the statistics display, the Distance displayed on April 9, 2024 is 2km, but when I clicked on the date to enter the interface of that day, my actual Distance was 77.9 km. I had this problem recently
Expected Behavior
I think they're a match. I was fine
Steps To Reproduce
No response
Relevant log output
Screenshots
Additional data
No response
Type of installation
Docker
Version
1.28.3
The text was updated successfully, but these errors were encountered: