aboutsummaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2017-11-20T580W: review comments fixesValerii Vyshniak
2017-11-19Merge branch 'master' into payload-as-form-paramShinryuken
2017-11-19- Global jsonPrettyPrinting optionSrk
- Minor refactoring - Config option name changed from "event.forward.prettyPrintedPayload" to "config.mapper.prettyPrintedJson"
2017-11-18Rollback getting defaults without having an user instanceSrk
2017-11-18Rollback number as primitive typeSrk
2017-11-18Removing notification templates referencesSrk
2017-11-18Revert "User defaults when no User is available"Srk
This reverts commit 5117b2e64781161c9e06f57cbee217f174d5731e.
2017-11-18Revert "User defaults when no User is available"Srk
This reverts commit ccb2e9e5e0581406963ac63a9d08acb7c2549834.
2017-11-18T580W: add battery level to all eventsValerii Vyshniak
It is possible to use "processing.copyAttributes" configuration to have battery level in all events, but this will not work if battery events will be filtered somehow and dropped from DB, so it will be no event in DB with latest battery level. So, ensure all our events have latest battery level.
2017-11-18T580W: CommandsValerii Vyshniak
2017-11-18T580W: Alarms parsingValerii Vyshniak
2017-11-18T580W: parse LBS and WiFi data packetValerii Vyshniak
2017-11-18T580W: parse battery levelValerii Vyshniak
2017-11-18T580W: parse altitude and satellites num in GPS data packetValerii Vyshniak
2017-11-17Fix IVT 401 coordinates decodingAnton Tananaev
2017-11-16Support GP6000F binary protocolAnton Tananaev
2017-11-15Implement GV65 CAN message supportAnton Tananaev
2017-11-15Improve OKO NAVI regex patternAnton Tananaev
2017-11-14Do geocoding for every events related positionsAbyss777
2017-11-14Merge pull request #3638 from Abyss777/ldap_improveAnton Tananaev
Improve LDAP
2017-11-14Improve LDAPAbyss777
2017-11-13removing NotificationFormatter from EventForwarderShinryuken
2017-11-14Fix typo in protocol nameAnton Tananaev
2017-11-13Fix GV65+ ERI message decodingAnton Tananaev
2017-11-13Decode VT900 driver licenseAnton Tananaev
2017-11-13Implement IVT 401 protocolAnton Tananaev
2017-11-12Support OKO NAVI protocol (fix #1612)Anton Tananaev
2017-11-11Implement LDAP authenticationAnton Tananaev
2017-11-10- Combine "getAddress" functionsAbyss777
- Change switches logic
2017-11-08- Implement synchronous geocodingAbyss777
- Implement retry geocoding for trips/stops reports - Implement API for revers geocoding
2017-11-08Default payload format as json, plaintext available as optionShinryuken
2017-11-07User defaults when no User is availableShinryuken
2017-11-07User defaults when no User is availableShinryuken
2017-11-07User defaults when no User is available - EventForwarder refactoringShinryuken
2017-11-07User defaults when no User is availableShinryuken
2017-11-08Fix D-WAY heartbeat responseAnton Tananaev
2017-11-06Minor refactoring changesShinryuken
2017-11-06Using templates for event forwarded messagesShinryuken
2017-11-06ObjectWriter for pretty-printing messagingShinryuken
2017-11-07Handle Sirra GNX-6 serial numberAnton Tananaev
2017-11-06Remove second to lower caseAnton Tananaev
2017-11-05More MT-60X alarm typesAnton Tananaev
2017-11-04Adding 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.
2017-11-01Support iStartrek VT900 protocolAnton Tananaev
2017-10-31Handle Bofan PT600 long framesAnton Tananaev
2017-10-30Merge pull request #3617 from Abyss777/math_jexlAnton Tananaev
Map "Math" to Computed Attributes context
2017-10-30Support Oner OCT retransmissionAnton Tananaev
2017-10-30Map "Math" to Computed Attributes contextAbyss777
2017-10-30Support Topin D3 micro messagesAnton Tananaev
2017-10-28Extend Bofan PT600 supportAnton Tananaev
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-05 20:45:48 +0000