report.trip.useIgnition - What effect does this have on reports?
Ignition is only used for stop detection. Also it seems like you just keep alternating between true and false. It means it won't really have much effect.
Yes, in my tests I switched between true and false to test the effect on the reports.
So can you confirm that this has no effect on the reports?
I know this site https://www.traccar.org/trips-stops/ . Is there a other information to better understand the effect of report.trip.useIgnition ?
There's no other documentation.
I have a customer who needed this setting applied. And yes, I understand your frustration about documentation but read my note about this at the end of my reply.
My best advice to you is to not get caught up in altering individual settings related to trip calculations. They all work together and can result in what you might consider weird behaviour, but if you consider all of the parameters it's possible to work out what is happening.
In my customer's case he was missing a bunch of trips being calculated correctly, and he uses them for business cost purposes. He therefore needed report.trip.useIgnition turned on so it could accurately calculate when a trip stopped. However he also does work on farms and drives short distances that we did not want reported as a Trip, so we needed to make sure we also tweaked his report.trip.minimalTripDuration, report.trip.minimalTripDistance, and report.trip.minimalParkingDuration values.
I have another customer who had different issues, whereby their stops were not being tracked because the "motion" flag was being sent by the GPS tracker. They would perform deliveries, leaving the engine running (which kept the motion flag active), or they would turn the ignition off but be jostling the truck so much that the motion flag stayed active. In their case, we had to use a Custom Attribute in Traccar to nullify the motion flag from the tracker so that Traccar calculated motion based on the distance between GPS tracks.
My overall point here is that this stuff is complex and has many moving parts. It can take quite a while to deal with all the edge cases, and that leads to the issue around Documentation. Anton could spend his life detailing all of the potential edge cases for trip and stop tracking, but really what is being offered here is an extremely flexible platform that relies on your own expertise to make it do what you want it to do.
Dear Kaldek and Anton,
thanks for your massage.
Yes I also noticed before your massage here that I have find the perfect setting by my own to each device.
It is as you write.
Have a good day.
Hello,
I want to know if report.trip.useIgnition have any effect on reports?
I simulate a route with OsmAnd protocol.
One simulation with no ignition values.
The other simulation with ignition values.
In the picture you see Simulator 4 device is sending ignition on or off.
In the other picture you see the Simulator 3 device is not sending ignition on or off.
So this is the test setup!
I set up report.trip.useIgnition in device attributes.
Then I test differnt reports: Trips, Stops.... I dont see any difference.
I did differnt test report.trip.useIgnition true or not.........
Please tell me what is the effect?
