aboutsummaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2019-01-14added message sending to WatchProtocolGavriel Fleischer
2019-01-13Merge pull request #4191 from flocsy/TK-binaryAnton Tananaev
fixed exception when String.format thought the binary data has formt placeholders
2019-01-13fixed removed unnecessary {}Gavriel Fleischer
2019-01-13fixed exception when String.format thought the binary data has format ↵Gavriel Fleischer
placeholders
2019-01-13Fixed output field for F4 formatEvgeny S Maksimov
2019-01-13Fix altitude factorEvgeny S Maksimov
2019-01-13Fix copy/paste errorsEvgeny S Maksimov
2019-01-13Added F6 format support + minor improvements for previous formats.Evgeny S Maksimov
2019-01-12Support H10 cell and wifiAnton Tananaev
2019-01-11Merge pull request #4188 from iEvgeny/logrotateAnton Tananaev
Added logger.rotate configuration parameter for compatibility with logrotate
2019-01-09fixed LOGGER format stringGavriel Fleischer
2019-01-09Merge pull request #4184 from flocsy/fix-log-orderAnton Tananaev
fixed log order
2019-01-09fixed log orderGavriel Fleischer
2019-01-08Add ITS login responseAnton Tananaev
2019-01-08reverted getIntegerGavriel Fleischer
2019-01-08made it possible to customize log order and use any attributeGavriel Fleischer
2019-01-08120 chars line limit...Gavriel Fleischer
2019-01-08use String formatting in loggingGavriel Fleischer
2019-01-08use Java apiGavriel Fleischer
2019-01-08renamed method to parseErrorGavriel Fleischer
2019-01-08added logger.events configurationGavriel Fleischer
2019-01-08log error in GoogleGeocoderGavriel Fleischer
2019-01-08changed log message for port confictGavriel Fleischer
2019-01-07added getInteger that can return nullGavriel Fleischer
2019-01-07log battery level, outdated, invalidGavriel Fleischer
2019-01-07log port in case of conflictGavriel Fleischer
2019-01-07log error in geocoderGavriel Fleischer
2019-01-06Decode Atrack driver idAnton Tananaev
2019-01-05Support Nyitech NT-183W protocolAnton Tananaev
2019-01-04Log original exceptionAnton Tananaev
2019-01-04Fix potential security issueAnton Tananaev
2019-01-03Support alternative Atlanta L100 formatAnton Tananaev
2019-01-02Revert "Improve L100 decoder"Anton Tananaev
This reverts commit 3254dbc
2019-01-02Improve L100 decoderAnton Tananaev
2018-12-31Decode additional Wristband dataAnton Tananaev
2018-12-31Handle Queclink GTSTC messages (fix #4173)Anton Tananaev
2018-12-29Another Wristband updateAnton Tananaev
2018-12-29Another Wristband updateAnton Tananaev
2018-12-29Wristband respond with active modeAnton Tananaev
2018-12-28Fix Wristband responseAnton Tananaev
2018-12-28Fix Wristband protocol responseAnton Tananaev
2018-12-28Wristband protocol response as textAnton Tananaev
2018-12-27Fix Wristband protocol responseAnton Tananaev
2018-12-27Update Wristband decoderAnton Tananaev
2018-12-27SMS client: Changes to support msg91Syed Mujeer Hashmi
The authorization header may require different name:value pair for specifying token by the service provider. Add a config parameter "sms.http.authorizationName" to support this. In case of msg91, the name required is "authkey". The newline at the end of short templates are causing invalid json in request. Get rid of the newline using trim(). The required config to enable msg91 sms notifications are <entry key='notificator.types'>web,mail,sms</entry> <entry key='notificator.sms.manager.class'>org.traccar.sms.HttpSmsClient</entry> <entry key='sms.http.url'>http://api.msg91.com/api/v2/sendsms</entry> <entry key="sms.http.authorizationName">authkey</entry> <entry key='sms.http.authorization'>[YOUR TOKEN]</entry> <entry key='sms.http.template'> { "sender": "SOCKET", "route": "4", "country": "91", "sms": [ { "message": "{message}", "to": ["{phone}"] } ] } </entry> Signed-off-by: Syed Mujeer Hashmi <mujeerhashmi@gmail.com>
2018-12-21Support PT100 protocolAnton Tananaev
2018-12-21Handle long odometer valuesAnton Tananaev
2018-12-20Added logger.rotate configuration parameterEvgeny S Maksimov
2018-12-18Merge pull request #4166 from mujeerhashmi/mapmyindiaAnton Tananaev
Implement MapmyIndia Reverse geocoder
2018-12-18geocoder: Implement MapmyIndia Reverse geocoderSyed Mujeer Hashmi
MapmyIndia reverse geocoding is very helpful for the Indian subcontinent, It's "distance from nearest POI" detail embedded in the formatted_address field of the response is quite impressive for the reports. The Confirgurations required to be added in the config file "traccar.xml" are <entry key='geocoder.enable'>true</entry> <entry key='geocoder.type'>mapmyindia</entry> <entry key="geocoder.url">https://apis.mapmyindia.com/advancedmaps/v1</entry> <entry key="geocoder.key">YOUR_KeY</entry> <entry key="geocoder.format">%f</entry> Signed-off-by: Syed Mujeer Hashmi <mujeerhashmi@gmail.com>