Softpedia >Mac >Internet Utilities >Traccar >  Changelog

Traccar Changelog

What's new in Traccar 4.0

Aug 6, 2018
  • Update submodule commit.

New in Traccar 3.17 (May 27, 2018)

  • Fix Liquibase driver issue.

New in Traccar 3.16 (Mar 12, 2018)

  • Noteworthy new features and improvements:
  • Access to media files - photos and other media files can now be accessed directly from the web app.
  • POI layer - now it's possible to add custom POI layer to map from a KML file.
  • Disable devices - in addition to disabling user accounts, you can now disable individual devices. Option is available only to admin users in the devices dialog.
  • User actions logging - most of the user actions are now logged in the standard log file. This can be useful for investigating incidents.
  • Limiting notifications to schedule - the new release has an option to link calendar to notification records. It can be used in case user wants notifications to be triggered only during certain period of time.
  • New GPS communication protocols:
  • SPOT - GPS trackers that use satellite connection for reporting data to the server
  • M2C - protocol from M2Cloud
  • GlobeKeeper
  • OpenGTS - standard OpenGTS protocol used by some trackers (e.g. GPSLogger mobile app)
  • Traccar 3.16 also includes multiple smaller improvements and bug fixes. If there is a port conflict with some other process on the system, Traccar will disable the port instead of failing to start. This was a very common issue recently because Microsoft started using port 5040 for one of the system services on Windows. There was also a fix to SMTP user attributes which were broken in the last official release.

New in Traccar 3.15 (Dec 10, 2017)

  • Key modifications and new features:
  • Some attributes (e.g. units) were moved from user and server into corresponding attributes.
  • Filtering was extended to allow some messages to be excluded from filtering. For example, in most cases alarm messages should not be filtered. It is possible now with new release.
  • It is now possible to save commands for later use. It is especially useful for custom commands. For more information refer to commands documentation.
  • There is a significant change to notifications system. Notifications can now be configured per device, not just globally. This feature has been requested many times in the past and now it's available.
  • Traccar now supports flespi service as a protocol. Flespi is an IoT telematics backend and framework platform by Gurtam. It's a proprietary service, but it can improve support for some devices and it has generous free limits. See official website for more information about the service.
  • There are some exciting changes to reverse geocoding module. It's now possible to query address information per user request instead of automatically requesting it for all messages from device. It should help to greatly reduce reverse geocoding costs. If this option is enabled user can request address directly from web app and it will also work for reports like trips.
  • Traccar added support for LDAP user authentication. With LDAP you can integrate Traccar with your directory and share credentials between your website and Traccar. For more information read LDAP documentation.
  • New GPS trackers communication protocols:
  • GEN-X - Sierra Wireless GenX telematics and tracking units
  • flespi - IoT platform by Gurtam (more info above)
  • D-WAY - D-WAY communication protocol
  • Recoda - protocol for M610 and other devices
  • OKO - GPS trackers manufacturer with headquarters in Ukraine
  • IVT401 - Intellinet GPS trackers
  • Sigfox - Digital Matter Oyster Sigfox gateway protocol
  • T57 - protocol for T57 devices

New in Traccar 3.12 (Jul 10, 2017)

  • There is a new feature called “Computed Attributes”. It allows to add a specially-formatted expressions to modify and add new position attributes. For example, it will allow to automatically convert Teltonika “IO” values into meaningful attributes that can then be displayed for the user. Expression language is very flexible and you can implement pretty much anything you want with it. Check official documentation for computed attributes for more information of how to use it.
  • Another major improvement is addition of well-known attributes to the web app. Now instead of English keys, which were sometimes hard to understand, you get localizable attributes with properly formatted values, with units where applicable. You don’t need to remember the keys for commonly used attributes (for example, to set up device speed limit). Now you can select a know attribute from a drop-down menu. This feature is available for all types of attributes (user, device etc). Please don’t use attribute aliases anymore as we plan to remove them in one of the next releases.
  • With well-known attributes we added quite a few string to translate. If you see any missing or wrong translation, please help us to localize Traccar project using Transifex platform. It’s really easy to use and localization won’t take much of your time.
  • And that’s not even all new things related to attributers. We have added all optional well-known attributes to the Route report. You can access them from column header menu. All attribute values are properly formatted in the report as well.
  • There is a new Stops report, a new fuel drop notification and a few new alarm types. For more information about new report check Trips and Stops documentation. Feel free to ask questions on the forum about any of the new features.
  • In the web interface there is now new panel for alerts. It’s located on the right-hand side of the screen on desktop layout, and in a separate window in mobile layout. With this new feature you will never miss any important notifications from your devices.
  • And there are many more smaller modifications and improvements, including support for voice and photos, new statistics options, new icon types, optimizations to distance calculation and geocoding, and seven new GPS communication protocols. As usual, there are also many bug fixes and improvements to existing protocols.

New in Traccar 3.11 (Apr 14, 2017)

  • The biggest new feature in this release is support for SMS communication. This includes SMS notifications, commands and receiving events from devices. To use this feature you need to set up SMPP server details in the configuration file. Check official documentation for more details.
  • Another noticeable change in this release is modification to most dialog windows. There were too many fields in many dialogs (e.g. user), so we decided to split fields into sections. One non-collapsable section contains required parameters and all other sections are split by areas. This change should also help with understanding which fields are optional and which are not.
  • Server-wide device readonly flag allows administrator to disable device modifications for all the users, but still leave all other functionality available. This option is useful in cases when GPS tracking provider does not want to allow users to add arbitrary devices to their accounts.
  • In earlier versions reports and notification that are generated on the server side always included server time because there was no way for user to specify local timezone. Now each user can set up his timezone preference which will be respected for everything generated on the server side.
  • A few new map layers were added to the interface, including Yandex (Russia) road and satellite maps and Baidu (China) road maps. This should help improve quality of maps, especially in some regions like China, and provide more options to choose from.
  • There were number of smaller fixes, improvements and additions. For example, there is a new geolocation provider option and a fix for common issues with H02 protocol.
  • New devices communication protocols in this release:
  • SIWI Protocol
  • StarLink – devices from ERM (Israel)
  • DMT – protocol from Digital Matter Telematics
  • Customizable Xirgo protocol

New in Traccar 3.10 (Feb 11, 2017)

  • New communication protocols in this release:
  • AIS – system usually used for marine tracking
  • GT-30 – protocol for GT-30 GPS tracker
  • TMG – devices from TrackMiGaddi company
  • Pretrace – protocol from Pretrace Technologies
  • Pricol – automotive parts and GPS tracking vendor
  • Among many smaller improvements, this release includes following major features:
  • Calendars
  • Manager Role
  • Each user is able to add one or more calendars to his account. At this point calendars can be used only for limiting geofences to particular schedule, but in future the feature can be extended to work with other modules. For example, maintenance schedule management is a good candidate.
  • Another major improvement is addition of manager user role. Each user now has a limit for users he can create. If the limit is more than zero, it means that user is a manager and he can register and manage his own users. Device limit of the manager applies to the users create by that manager. There is also a flag for disabling device modification, so admin can disallow it for any user account.

New in Traccar 3.9 (Dec 10, 2016)

  • Focus of this release was on improving security and stability of the platform. Last release included a lot of new features and significant modifications, and there were a few issues discovered and fixed since version 3.8. There might still be some minor issues, but it should be safe to update your production environment to the new version.
  • One notable new feature is templates for email notifications. Text-based templates for all notifications are located in the “templates” folder. Format is very simple, so you should be able to easily modify or localize emails sent by Traccar now.
  • Version 3.9 includes support for two new GPS communication protocols:
  • AT2000 – asset tracking device from Teltonika
  • Maestro – protocol for MicroTracker MT-01 from Maestro Wireless

New in Traccar 3.8 (Nov 19, 2016)

  • The biggest new feature of this release is Excel reports. It is a replacement for more primitive CSV reports. Excel exports are based on template system, so report format can be customized to include extra data or modify display format of the current fields.
  • Another key feature is attribute aliases. Now position attributes names can be customized on per-device basis. Currently it affects only display name, but in future aliases can be used to assign sensors to specific functions on the server side as well.
  • There were many changes on the web interface part. Most noticeable one is change of the ExtJS theme to Triton. Default map layer is changed to “Carto”, but OpenStreetMaps layer is still available as an option. Many buttons have been changed from text to icons. It has been done to improve layout on mobile version of the web interface. From now on mobile website has all the same features as the desktop version, including reports. Another important improvement on the web interface part is ability to switch icons. There is a number of options available, including car, truck, boat and airplane. There are many other smaller improvements and modification as well.
  • Extra fields have been added to device and user models. For device you can specify model, phone number, contact details and category. Administrator can now set the expiration date for user account and enable or disable users at any time. There is also a API token associated with every user account now to allow website access without regular login and password.
  • Administrators now have an access to server statistics which includes numbers of active user and devices.
  • On the back-end side there were multiple improvements and fixes as well. A big one is a fix for H02 protocol. As usual with new release Traccar adds more protocols to the supported list. This time it’s almost ten new communication protocols: Arknav CT-X8, AutoGrade, Oigo Telematics, JP-KORJAR, cGuard, FifoTrack, ExtremTrac, TrakMate.

New in Traccar 3.5 (Jul 9, 2016)

  • This version of Traccar server includes one new major feature – device groups. In addition to that there are many bug fixes to existing protocols and features, and some stability improvements.
  • Starting from this release Traccar drops support for old web API. You should be using new REST API. For more information on the new API please see documentation page. There is swagger file available for convenience as it allows to automatically generate clients for many platforms including web, Android and iOS.
  • Main new feature implemented in version 3.5 is device groups. You can now organize devices into groups. It’s also possible to have multi-level hierarchy of groups. Unfortunately because of some technical issues (ExtJS framework bugs), I couldn’t implement a tree view instead of old grid. There is group filtering field at the bottom of devices panel to switch between groups. Tree view option is available in git source code history if someone wants to experiment with it.
  • Version 3.5 brings some other minor new features and improvement for web UI as well. There is now an option to switch to 12-hour time format instead of international 24-hour default preference. New text filtering field at the bottom of devices panel allows to search devices by name in case user has a large number of GPS tracking devices.
  • This release also includes new localization options. If you want to help with translating Traccar web UI or phone apps, please see Traccar project on Transifex website.
  • New devices communication protocols in 3.5:
  • Fox – tracking devices from Serbian company called Geneko
  • GNX – protocol for GNX-2 and GNX-3
  • ARKNAV – Taiwan hardware company
  • Supermate – protocol from Supermate Electronic
  • Appello – Followit Appello 4P model

New in Traccar 3.4 (Jul 9, 2016)

  • There have been some insignificant changes to the REST API to make it easier to integrate new mobile apps. Android version of Traccar Manager app is in alpha testing phase and should be available on Google Play soon. iOS version is still in active development and will be coming some time after Android app.
  • One of the most popular protocols used by various GPS trackers is GL200. Since last version it has been completely re-implemented to allow decoding of all additional data including battery, odometer and other extra attributes. If you encounter any problems after update, please report an issue.
  • With the last update Traccar introduced automatic database migrations using Liquibase library, but there were number of problems because of complexity involved in supporting older versions. So the decision has been made to remove support for upgrade from older versions. You can upgrade from 3.3 to 3.4, but if you want to upgrade from older 3.x version, you would have to upgrade to 3.3 first and then to the latest from there.
  • If you want to add new localization to Traccar or fix any issues in the current translations, please see Traccar project on Transifex platform. New version includes following new languages:
  • Persian
  • Finnish
  • Malayalam
  • Malay
  • Turkish
  • AutoFon45 protocol has been combined with AutoFon protocol. Also, as always this new release includes some new protocols:
  • TT8850 – protocol for all TT88xx devices and possibly some other models
  • NVS – protocol from NVS Technologies AG
  • Kenji – Kenji KJ-8501 device
  • Astra – protocol from Astra Telematics
  • Homtecs – Homtecs H20 device

New in Traccar 3.5 (Apr 17, 2016)

  • This version of Traccar server includes one new major feature – device groups. In addition to that there are many bug fixes to existing protocols and features, and some stability improvements.
  • Starting from this release Traccar drops support for old web API. You should be using new REST API. For more information on the new API please see documentation page. There is swagger file available for convenience as it allows to automatically generate clients for many platforms including web, Android and iOS.
  • Main new feature implemented in version 3.5 is device groups. You can now organize devices into groups. It’s also possible to have multi-level hierarchy of groups. Unfortunately because of some technical issues (ExtJS framework bugs), I couldn’t implement a tree view instead of old grid. There is group filtering field at the bottom of devices panel to switch between groups. Tree view option is available in git source code history if someone wants to experiment with it.
  • Version 3.5 brings some other minor new features and improvement for web UI as well. There is now an option to switch to 12-hour time format instead of international 24-hour default preference. New text filtering field at the bottom of devices panel allows to search devices by name in case user has a large number of GPS tracking devices.
  • This release also includes new localization options. If you want to help with translating Traccar web UI or phone apps, please see Traccar project on Transifex website.
  • New devices communication protocols in 3.5:
  • Fox – tracking devices from Serbian company called Geneko
  • GNX – protocol for GNX-2 and GNX-3
  • ARKNAV – Taiwan hardware company
  • Supermate – protocol from Supermate Electronic
  • Appello – Followit Appello 4P model

New in Traccar 3.3 (Dec 23, 2015)

  • Starting from this release Traccar is switching to new REST API instead of old custom API. It’s not fully REST because it still supports sessions as an authorization option. For live location and status updates service will be using WebSocket instead of long-polling technique used in previous releases. Hopefully this change will simplify integration of third party applications with Traccar. For those who are already using old API, it will be supported as an option for at least this release. Migration to the REST API shouldn’t take a huge effort as the format is almost the same.
  • One of the most user visible features of the new version is addition of device status field. It replaces unique identifier field in the web interface (devices panel). The new column shows time of the last message from device and color indicates connection status. Green means that device is connected, yellow color means that status is unknown and red indicates that device is disconnected from the server.
  • Next big feature is automatic database migration between different versions of Traccar. This means that you no longer need to manually update database schema. Server uses Liquibase library to allow universal migration and database creation process that works on any supported database engine including MySQL, Microsoft SQL Server, PostgreSQL and others. You can automatically update to version 3.3 from any older 3.x version. Note that the process might take a while if you have large amounts of data in your database.
  • Last new feature is support for GSM-based locations (commonly referred as LBS). At the moment Traccar supports OpenCellID and Mozilla Location Service (MLS) providers. The option is disabled by default, but it can be enabled in the config file. Note that you need to provide an API key for the provider that you plan to use. Some protocols don’t include MCC and MNC values in the messages. For those types of protocols you need to manually specify values in the configuration file.
  • This release also includes various small improvements and modifications. There is a new follow button to automatically follow selected device on map. Date and time label has been removed from the tracks.
  • New features:
  • New REST based web API
  • Device connection status indication
  • Automatic database migration
  • Support for GSM-based locations
  • As usual there are a few new protocols:
  • Huabao – popular protocol used in some Chinese GPS trackers
  • U-PRO – protocol for U-Pro mini device
  • AURO – Auro Comfort 1060 protocol
  • Disha – protocol used in DISHA vehicle tracker
  • ThinkRace – another protocol from Chinese manufacturer
  • PathAway – protocol for PathAway mobile app
  • Arnavi – protocol from ArusNavi company

New in Traccar 3.2 (Nov 14, 2015)

  • Added static code analyzing tools to Traccar project. It includes CheckStyle, FindBugs and PMD for Java code and jshint and jscs for JavaScript code. Since then there have been a massive amount effort put into cleaning up all the issues and warnings reported by those tools. There is no visible change to the user and it’s hard to measure, but this improvement in code quality should definitely result in less bugs and better performance especially in long term.
  • In addition to cleaning up code, there have been big changes to unit testing. It should result in better software quality and smaller number of regression issues. There are also two new testing scripts. One simulates specified number of devices and can be used for performance testing. Other one can generate sample data to test user interface.
  • New features:
  • Support for messages without GPS data
  • Sharing devices between users
  • Changes to the map markers
  • Support for custom map layers
  • Responsive web interface
  • Many bug fixes and quite a few new protocols:
  • TRV – protocol for GPS watch like PG88/S88 and PG22/S22
  • GPSMTA – free Android GPS tracking app
  • aQuila – protocol for devices for iTriangle (India)
  • Flextrack – product of Danish company with same name
  • BlackKite – protocol developed by Zilogic Systems
  • ADM – protocol from Neomatica (Russia)
  • Watch – protocol used in many popular Chinese GPS watches
  • T800x – another protocol from Topflytech

New in Traccar 3.1 (Aug 10, 2015)

  • Key new features for this release are:
  • Support for commands (read more info below)
  • Localization support for web interface
  • Compilation and compression of web interface
  • User and server wide preferences
  • In addition to that there are multiple small bug fixes and improvements and a couple of new protocols:
  • TZone – GPS devices from TZone Digital Technology
  • GPSMarker – GPS tracker manufacturer from Russia
  • Cityeasy – Chinese GPS device manufacturer

New in Traccar 2.11 (Jan 19, 2015)

  • Support for four new protocols including Ulbotech and Tramigo. Port 5000 is now special port for identifying communication protocols. In addition to that this version includes number of bug fixes and improvements.

New in Traccar 2.10 (Jan 6, 2015)

  • Support for two new protocols: Orion and Riti. Included universal data source class to improve support for various database engines.