Ignition ON/OFF Delay Issue with filter.static in Traccar – Looking for a Workaround
This is my entire filteration parameters:-
<entry key='filter.enable'>true</entry>
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.future'>600</entry>
<entry key='filter.minPeriod'>10</entry>
<entry key='filter.duplicate'>true</entry>
<entry key='filter.static'>true</entry>
<entry key="filter.stationaryPeriod">300</entry>
<entry key="filter.stationaryDistance">3</entry>
<entry key='filter.distance'>0</entry>
<entry key='filter.skipLimit'>300</entry>
<entry key='filter.skipAttributes.enable'>false</entry>
<entry key='filter.maxSpeed'>200</entry>
<entry key="filter.past">300</entry>
<entry key="filter.angle">10</entry>
<entry key="filter.accuracy">40</entry>
<entry key='filter.skipOld'>false</entry>
<entry key='filter.period'>0</entry>
<entry key="coordinates.filter">true</entry>
<entry key="event.motion">true</entry>
<entry key='event.motion.start'>true</entry>
<entry key='event.motion.stop'>true</entry>
<entry key='motion.inactive.timeout'>600</entry>
<entry key='event.ignition.on'>true</entry>
<entry key='event.ignition.off'>true</entry>
<entry key='event.motion.speedThreshold'>2</entry>
It's Resolved. Thank you!
Do you want to share what the problem was?
Sure. When I was applying:-
<entry key="filter.static">true</entry>
<entry key="filter.stationaryPeriod">300</entry>
Ignition ON/OFF was getting delayed by 5 min so, I was not sure how to resolve that so, I applied.
<entry key='filter.skipAttributes.enable'>true</entry>
<entry key="filter.skipAttributes">ignition,alarm,event</entry>
And it got resolved.
I’m facing an issue while tuning ignition behavior in Traccar and would appreciate guidance from the community.
When I use:
<entry key="filter.static">true</entry> <entry key="filter.stationaryPeriod">300</entry>the device is correctly treated as stationary, and database flooding is controlled. However, in this setup, Ignition ON and Ignition OFF events are delayed by up to 5 minutes when the vehicle is not moving.
If I change the configuration to:
<entry key="filter.static">false</entry>then Ignition ON/OFF events are triggered instantly, but the downside is that stationary devices start generating excessive position records, causing heavy database growth.
I’m looking for a clean and reliable workaround that allows me to:
Keep filter.static = true to control stationary data flooding
Still receive instant (or near-instant) Ignition ON/OFF events
Any insights or best practices would be greatly appreciated.