Version 6.6

I currently have A device that upload data to website A and website B. When I was uploading data to website A, both in1 and in2 in the uploaded data were changing. Therefore, the log file of website A can clearly record this, and I can also view the changes through the route menu. However, when I uploaded the same operation to website B, I couldn't see any changes in the data. Website A is version 5.12 and website B is version 6.6. The configuration information in the traccar.xml file is the same for both. I'm wondering if website B has filtered out some data? When B website checked the route, it was found that there was one piece of data per minute, but the correct effect should not be like this. Should I add such a configuration filter.skipLimit

Will the route of version 6.6 only be recorded once every minute? Where should I go to adjust

There's no filtering by default.

In your opinion, where should I start to look for this issue

Will it work if I add filter.skiplimit? Or perhaps add some other configuration

Start with checking logs, as usual.

The data record is not visible in the log. Could it be that some configuration intercepted it before the write date

Are there any changes in location information filtering between version 5.12 and version 6.6

What exactly do you see in the logs?

I uploaded five changes of data within one minute, but only recorded the first one at the beginning and the last one at the end. The data in the middle three times were in1 and in2, which changed, but there was no record in the log and they couldn't be found on the page either. I performed the same operation on another website and found five records of data. I also did not see the filter information like 'Position filtered by Duplicate filters from device'

Logs?

private boolean filterDuplicate(Position position, Position last) {
        if (filterDuplicate && last != null && position.getFixTime().equals(last.getFixTime())) {
            for (String key : position.getAttributes().keySet()) {
                if (!last.hasAttribute(key)) {
                    return false;
                }
            }
            return true;
        }
        return false;
    }

I saw the above part of the code in the code. When we enable <entry key='filter.duplicate'>true</entry>, will we only compare the key at the previous position without comparing the corresponding value?
This is the code I saw in version 6.6

If I upload two location pieces of information where the longitude and latitude are inconsistent, the speeds are not the same, and the values of in1 and in2 are also different, but the number of parameters after parsing the data string is the same, will it be filtered by the system?