0
Not a bug

Combined Record Types Do Not Add Up to 24 Hours for an Individual Day

rfmurphy81 3 years ago updated by James 3 years ago 4

On a whim, I decided to add up the times for sleep, idle, drive, charge, and Supercharge about a week ago. In almost every case, they add up to anywhere from 4 to 15 minutes shy of a full 24 hours.


Shouldn't the data equal 24 hours? Not sure if the missing time is represented by issues with get a response from the API.


Some data:

2/232/222/212/202/192/18
Sleep2:142:4410:0518:4715:5515:22
Idle13:3315:154:265:097:008:12
Drive1:361:174:430:590:20
Charge6:254:350:48
Supercharge1:51
Total23:4823:5121:53* 23:5623:5423:54
Missing0:120:092:070:040:060:06

* Car was in service mode on 2/21 presumably for the amount of time missing from 24 hours.

Not a huge number of data points, but did you notice that the longer the driving time on a given day, the higher the amount of "missing" time? Perhaps a systematic rounding error on the drive logging??

Under review

It's just rounding. I add up the minutes for each drive, idle, sleep and charge in the day. Each state change will have some rounding of the seconds which will mean more "missing" time with the larger amount of state changes in the day.


I'm not sure this is an issue however? The chart displays the days states in % and not time to account for this.


Let me know what you guys think.

Yeah, you're probably right about whether it's worth looking into, especially from how the site handles state changes, as you mentioned. I'd say close this out then.

Commenting disabled