There will be a blog post about new features in 3.11. Most H02 problems should be solved.
Can you please share what are optimum settings for HO2 protocol.
Here is how I am using it as of now,
<entry key='database.driver'>com.mysql.jdbc.Driver</entry> <entry key='database.url'>db_con_string</entry> <entry key='database.user'>root</entry> <entry key='database.password'></entry> <entry key='database.positionsHistoryDays'>30</entry> <entry key='coordinates.filter'>true</entry> <entry key='coordinates.error'>2</entry> <entry key='processing.copyAttributes.enable'>true</entry> <entry key='processing.copyAttributes'>power,ignition,battery</entry> <entry key='filter.enable'>true</entry> <entry key='filter.limit'>30</entry> <entry key='filter.invalid'>true</entry> <entry key='filter.zero'>true</entry> <entry key='filter.duplicate'>true</entry> <entry key='filter.distance'>2</entry> <entry key='event.forward.enable'>true</entry> <entry key='event.forward.url'>http://localhost:8083/handleEvents</entry> <entry key='forward.enable'>true</entry> <entry key='forward.url'>http://localhost:8080/?id={uniqueId}</entry> <entry key='h02.messageLength'>45</entry>
The main issue I am facing (in previous versions of Traccar) is random jump in location to equator.
You can find more details about this issue in this thread
https://www.traccar.org/forums/topic/devices-showing-wrong-location-unable-to-read-any-info-of-device-on-selecting/#post-14165
Thanks
There is no such thing as optimal settings. You need to find out what the problem is and then we can see how to fix it.
this particular problem I was talking about.
That's a device problem. It's not possible to fix on the server side.
Hi Anton,
Congrats on the release of new version. You are doing an amazing job.
Wanted to know what are new features in this release and more importantly does it this release addresses the known issues of HO2 protocol which are reported by various users.