Open ArturMalyszewicz opened 9 years ago
Similar to Argus 20635
This issue is related to #30
In my opinion it is not a bug as due to this long driving check interval an event of long driving may be caught even 60 later than maxDrivingTime and that is why totalDrivingTime is approximated one minute above expected value.
In LongDriving message there is wrong value of totalDrivingTime field - it is always one minute above the correct level/ Steps to reproduce: