Positions are not updated

Hi,
yesterday I updated to Traccar 6.11.1. Now, position changes of the trackers aren't recognised anymore.
Two examples. You can see in the second line that the updated position wasn't recognised by the platform.

Traccar Client, pos. 1:

2026-01-15 12:37:55  INFO: [Tb790849a: osmand < xx.xxx.xx.xxx] POST / HTTP/1.1\r\nContent-Type: application/json; charset=utf-8\r\nContent-Length: 415\r\nHost: traccar.xxx.de:5055\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\nUser-Agent: okhttp/3.12.13\r\n\r\n{"location":{"timestamp":"2026-01-15T11:37:53.938Z","coords":{"latitude":xx.5271631,"longitude":yy.3929698,"accuracy":13.94,"speed":-1,"heading":-1,"altitude":76.5},"is_moving":false,"odometer":xxxxxx,"event":"motionchange","battery":{"level":0.93,"is_charging":false},"activity":{"type":"still"},"extras":{},"_":"&id=xxxxxx&lat=xx.5271631&lon=yy.3929698&timestamp=2026-01-15T11:37:53.938Z&"},"device_id":"xxxxxx"}
2026-01-15 12:37:58  INFO: [Tb790849a] id: xxxxxx, time: 2026-01-15 12:37:53, lat: xx.52744, lon: yy.39119, course: 0.0, accuracy: 13.9

Traccar client position 2:

2026-01-15 12:43:02  INFO: [T4015f5ec: osmand < xx.xxx.xx.xxx] POST / HTTP/1.1\r\nContent-Type: application/json; charset=utf-8\r\nContent-Length: 393\r\nHost: traccar.xxx.de:5055\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\nUser-Agent: okhttp/3.12.13\r\n\r\n{"location":{"timestamp":"2026-01-15T11:43:00.957Z","coords":{"latitude":xx.5263585,"longitude":xx.3931479,"accuracy":16.11,"speed":-1,"heading":-1,"altitude":76.2},"is_moving":true,"odometer":9511568,"battery":{"level":0.93,"is_charging":false},"activity":{"type":"walking"},"extras":{},"_":"&id=641632&lat=xx.5263585&lon=yy.3931479&timestamp=2026-01-15T11:43:00.957Z&"},"device_id":"xxxxxx"}
2026-01-15 12:43:05  INFO: [T4015f5ec] id: xxxxxx, time: 2026-01-15 12:43:00, lat: xx.52744, lon: yy.39119, course: 0.0, accuracy: 16.1

GPS tracker, position 1:

2026-01-15 10:48:23  INFO: [T253f88c9: megastek < xxx.xxx.xxx.xxx] $MGV002,xxxxxxx279,,R,150126,094825,A,xx03.25750,N,0yy17.26168,E,00,12,00,0.79,18.493,270.12,452.1,,228,01,083D,12E7A03,15,,,,,,,,,01,063,Timer,,,0,,;!
2026-01-15 10:48:26  INFO: [T253f88c9] id: xxxxxxxx279, time: 2026-01-15 10:48:25, lat: xx.02565, lon: yy.29485, speed: 18.5, course: 270.1

GPS tracker, position 2:

2026-01-15 12:33:40  INFO: [T8ace1588: megastek < xxx.xxx.xxx.xxx] $MGV002,xxx279,,R,150126,113339,A,4702.32725,N,00810.57782,E,00,06,00,1.36,0.567,346.49,461.7,,228,01,083A,67C4FB,14,,,,,,,,,01,062,Timer,,,0,,;!
2026-01-15 12:33:43  INFO: [T8ace1588] id: xxxxxxxxx279, time: 2026-01-15 12:33:39, lat: xx.02565, lon: yy.29485, speed: 0.6, course: 346.5

What could be the reason for this?

You should probably post your configuration file.

Here is my configuration file:

    <!-- MySQL database -->
    <entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
    <entry key='database.url'>jdbc:mysql://localhost/traccar?zeroDateTimeBehavior=round&amp;serverTimezone=UTC&amp;allowPublicKeyRetrieval=true&amp;useSSL=false&amp;allowMultiQueries=true&amp;autoReconnect=true&amp;useUnicode=yes&amp;characterEncoding=UTF-8&amp;sessionVariables=sql_mode=''</entry>
    <entry key='database.user'>root</entry>
    <entry key='database.password'>root</entry>

    <!-- logging settings 
         available options: off, severe, warning, info, config, fine, finer, finest, all -->
    <entry key='logger.level'>config</entry>

    <!-- notification config --> 
    <entry key='notificator.types'>web,mail,traccar,telegram</entry> 

    <!-- Traccar push notrification config --> 
    <entry key='notificator.traccar.key'>xxxx</entry>

    <!-- E-Mail notification config --> 
    <entry key='mail.smtp.host'>smtp.xxx.de</entry> 
    <entry key='mail.smtp.port'>465</entry>
    <entry key='mail.smtp.ssl.enable'>true</entry> 
    <entry key='mail.smtp.from'>traccar@xxx.de</entry>
    <entry key='mail.smtp.auth'>true</entry>
    <entry key='mail.smtp.username'>traccar@xxx.de</entry>
    <entry key='mail.smtp.fromName'>Control</entry>
    <entry key='mail.smtp.password'>xxx</entry>

    <!-- Telegram config -->
    <entry key='notificator.telegram.key'>xxx</entry> 
    <entry key='notificator.telegram.sendLocation'>true</entry>

    <!-- Geolocation config -->
    <entry key='geolocation.enable'>true</entry>
    <entry key='geolocation.processInvalidPositions'>true</entry>
    <entry key='geolocation.reuse'>true</entry>

    <!-- Google -->
    <entry key='geolocation.type'>google</entry>
    <entry key='geolocation.key'>xxx</entry>

    <!-- filters in use -->
    <entry key='filter.enable'>true</entry>
    <entry key='filter.zero'>true</entry>
    <entry key='filter.accuracy'>100</entry>
    <entry key='filter.maxSpeed'>25000</entry>
    <entry key='filter.relative'>true</entry>
    <entry key='filter.skip.Attributes.enable'>true</entry>
    <entry key='filter.skipAttributes'>PowerOn,Restart,PowerOff,Sos,LowBattery,Error,CallForSms</entry>
    <entry key='coordinates.filter'>true</entry>
    <entry key='coordinates.maxError'>50</entry>
 
    </properties>

This is almost definitely the source of your problem:

<entry key='coordinates.maxError'>50</entry>

This is extremely dangerous option that almost nobody should be using. And if you do use it, it should usually be a large value.

Ok, thanks. I wonder that it caused problems until now. But I'll it and see if it helps.

Wouldn't there be an entry in the logfile if a position was filtered?

I hope you understand what this parameter does. If you do, then it should be fairly clear that it can work fine in some case, but in other cases it will completely block position updates.

I think, I do. ;-) I only wonder that it worked fine until now... I deleted the coordinates.filter and coordinates.max entries now. I'll let you know if it solved the problem.

Imagine the situation where the first position you receive from the device is very inaccurate or outdated. Or imagine if the device didn't have GPS for some time and you moved away from the last position for more than 50 meters. In both of those cases updates will completely stop until you return within 50 meters of the last known location.

I understand. But it never behaved like that. I can send you a screenshot via PM. Maybe, it works now correctly after the with the update to 6.11.1.

(I was using the filter to avoid jumps that occur sometimes even if the tracker isn't moving. I started with a large value and reduced it more an more.)

Thank you, Anton. Problem solved. You were right as always.

But that leads me to another question: Isn't there a log entry if a filter is applied?

Not for coordinates filter.