Auto duty end on trip end - One Trip One Duty

Problem:

Earlier, even under One Trip One Duty (OTOD) setup, the driver had to manually end the duty after every trip.

This caused:

• Extra manual steps for drivers after each trip
• Occasional missed duty end events on the server
• Incomplete or delayed duty closure logs

Solution:

• When One trip One Duty is enabled and Auto duty end on trip end (Property) is enabled, then on driver app, as soon as the trip ends, the duty end action should also be performed. These commands should also be consumed by the server.
  
  

Dependencies:
Driver app- 6.6.0

ETS- 25.04.33 and 25.06.23

Properties to be enabled:

AUTO_DUTY_END_ON_TRIP_END_OTOD - [T/F]

Notes

• No dead leg will be created by the device or server after trip completion in this mode.
  

• Designed to simplify driver workflow in One Trip One Duty scenarios by automatically closing both trip and duty sessions.