trackermap-server - Patches to the Traccar server for TrackerMap

Age	Commit message (Collapse)	Author
2017-11-25	Remove Starcom gateway support	Anton Tananaev

2017-11-24	Merge pull request #3624 from Shinryuken/payload-as-form-param	Anton Tananaev
	Support for custom params on EventForwarder
2017-11-24	Implement Starcom protocol	Anton Tananaev

2017-11-23	Minor refactoring	Srk

2017-11-24	Decode GoSafe IO status	Anton Tananaev

2017-11-22	Minor refactoring	Srk

2017-11-23	Support GK310 long cell format	Anton Tananaev

2017-11-22	Changing form method	Srk

2017-11-22	Fix JT600 frame decoder	Anton Tananaev

2017-11-22	Implement GK310 protocol extension	Anton Tananaev

2017-11-20	Refactoring: parameters only for one mode of eventForwarder	Srk

2017-11-20	Minor refactoring	Srk

2017-11-20	Minor refactoring	Srk

2017-11-21	Implement Oyster Sigfox protocol	Anton Tananaev

2017-11-19	Merge branch 'master' into payload-as-form-param	Shinryuken

2017-11-19	- Global jsonPrettyPrinting option	Srk
	- Minor refactoring - Config option name changed from "event.forward.prettyPrintedPayload" to "config.mapper.prettyPrintedJson"
2017-11-18	Rollback getting defaults without having an user instance	Srk

2017-11-18	Rollback number as primitive type	Srk

2017-11-18	Removing notification templates references	Srk

2017-11-18	Revert "User defaults when no User is available"	Srk
	This reverts commit 5117b2e64781161c9e06f57cbee217f174d5731e.
2017-11-18	Revert "User defaults when no User is available"	Srk
	This reverts commit ccb2e9e5e0581406963ac63a9d08acb7c2549834.
2017-11-17	Fix IVT 401 coordinates decoding	Anton Tananaev

2017-11-16	Support GP6000F binary protocol	Anton Tananaev

2017-11-15	Implement GV65 CAN message support	Anton Tananaev

2017-11-15	Improve OKO NAVI regex pattern	Anton Tananaev

2017-11-14	Do geocoding for every events related positions	Abyss777

2017-11-14	Merge pull request #3638 from Abyss777/ldap_improve	Anton Tananaev
	Improve LDAP
2017-11-14	Improve LDAP	Abyss777

2017-11-13	removing NotificationFormatter from EventForwarder	Shinryuken

2017-11-14	Fix typo in protocol name	Anton Tananaev

2017-11-13	Fix GV65+ ERI message decoding	Anton Tananaev

2017-11-13	Decode VT900 driver license	Anton Tananaev

2017-11-13	Implement IVT 401 protocol	Anton Tananaev

2017-11-12	Support OKO NAVI protocol (fix #1612)	Anton Tananaev

2017-11-11	Implement LDAP authentication	Anton Tananaev

2017-11-10	- Combine "getAddress" functions	Abyss777
	- Change switches logic
2017-11-08	- Implement synchronous geocoding	Abyss777
	- Implement retry geocoding for trips/stops reports - Implement API for revers geocoding
2017-11-08	Default payload format as json, plaintext available as option	Shinryuken

2017-11-07	User defaults when no User is available	Shinryuken

2017-11-07	User defaults when no User is available	Shinryuken

2017-11-07	User defaults when no User is available - EventForwarder refactoring	Shinryuken

2017-11-07	User defaults when no User is available	Shinryuken

2017-11-08	Fix D-WAY heartbeat response	Anton Tananaev

2017-11-06	Minor refactoring changes	Shinryuken

2017-11-06	Using templates for event forwarded messages	Shinryuken

2017-11-06	ObjectWriter for pretty-printing messaging	Shinryuken

2017-11-07	Handle Sirra GNX-6 serial number	Anton Tananaev

2017-11-06	Remove second to lower case	Anton Tananaev

2017-11-05	More MT-60X alarm types	Anton Tananaev

2017-11-04	Adding support for additional parameters on post body request (pushover support)	Shinryuken
	Hi, i implemented a new modality when sending event messages inside EventForwarder, now you can send requests as a "form-urlencoded", this means that the actual payload will be sent as a form parameter (the parameter name is configurable), this strategy will let you to add another parameters inside the form body message too. You can add new custom form params almost on the same way as the custom headers are inserted (event.forward.header), the only difference is that you will use the equals "=" char instead of ":" as key/value separator. You can enable this mode using the option: "event.forward.payloadAsParamMode", when using this mode you can use the other 2 configuration elements, "event.forward.paramMode.payloadParamName" if you want to change the form name param of the payload (default is "payload") and "event.forward.paramMode.additionalParams" to specify additional key/value form params. I added an option to prettyPrint the payload messages too, you can enable it using "event.forward.prettyPrintedPayload", i decided to add this option only for the EventForwarder behaviour. This is an example (using all the new params) that lets you integrate traccar server with the pushover platform. <entry key='status.timeout'>60</entry> <entry key='event.statusHandler'>true</entry> <entry key="event.forward.enable">true</entry> <entry key='event.forward.url'>https://api.pushover.net/1/messages.json</entry> <entry key='event.forward.prettyPrintedPayload'>true</entry> <entry key='event.forward.payloadAsParamMode'>true</entry> <entry key='event.forward.paramMode.payloadParamName'>message</entry> <entry key='event.forward.paramMode.additionalParams'> token=YOUR_TOKEN_ID user=YOUR_USER_ID </entry> I tested the new options and they work pretty well. Tried to make the change as clean as possible and avoiding code duplications. This mode does not change or affects the actual behabiour of the module. Let me know what do you think.