|Description||This morning on 8/10/16, I charged to 100% which ended at 5:59 am. A minute later, the site immediately enacted Scheduled Sleep Mode which disabled polling for the next 15 minutes; however, I started a drive around 6:04 or so. When polling resumed, it showed the drive start time at that time (as expected) but Idle 478 between the charge and drive shows 16.53 miles of range loss which is definitely attributed to Drive 345. |
I wasn't sure if you were still working on a way to better capture drives that start when polling is disabled, but it seems safe to assume that any range loss/gain when polling is turned off should be attributed to the drive or charge record following, right? Is it possible to put that into the code so the range loss is more appropriately reflected? Should the odometer reading and range reading be factored into this somehow? Can the GPS location somehow be used, too? Anyway to minimize how incorrectly this is being reported.
|Steps To Reproduce||1. Disable Polling|
2. Start a Drive
Actual Results: A majority, if not all, of the Range Loss in the preceeding Idle session should be attributed to the Drive session.
Expected Results: Range Loss should be more accurate.
Customer support service by UserEcho