Position filtering and filter.skipAttributes
If you disable filtering do you see "result" attribute in the position?
Yes, without filtering, I see the results of commands as well as information about the ignition, etc.
Screenshot please.
Without distance filtering: https://www.dropbox.com/s/r68ls6jk09rhdkm/Zrzut%20ekranu%202018-09-23%20o%2002.29.00.png?dl=0
You need to set filter.skipAttributes.enable to true.
Yesterday I tried to add this entry and it did not help but I checked by switching on the ignition. Today I've set filter.skipAttributes.enable to true again. In fact, responses to commands are no longer filtered. Unfortunately, it does not work to turn on the ignition.
Is the switching on of the ignition for the Teltonika protocol not interpreted as an alarm in this case ?
In my case, with the records containing information about switching on the ignition or other events from the tracker, the Event attribute always has a value other than zero. Is it possible to somehow set that if the event attribute has any value then the record will not be filtered ?
That's exactly what skip attributes is for.
Exactly, but what should I enter in filter.skipAttributes if, for example, I want the information about switching on the ignition not to be filtered.
The setting like <entry key="filter.skipAttributes">alarm</entry> does not work for the teltonika protocol. Ignition information is sent in each AVL package and the ignition switch status is sent as event 239
Settings <entry key="filter.skipAttributes">event</entry> causes that nothing is filtered, because the event is probably also sent in every avl package, but it just equals 0. and (if I understand correctly) this setting only works if any new io appears in the package
You can only use attribute presence as a condition, not a value.
Ok, thank you for help. Therefore, the only solution will be to add an additional attribute event on the tracker side, which will be sent only at the moment of the event.
I am asking for help in understanding the operation of "filter.skipAttributes". Despite the exclusion of result commands, entries containing command results and alarms are still filtered out ... or did I forget something?
my config:
<entry key="filter.enable">true</entry> <entry key="filter.future">86400</entry> <entry key="filter.distance">10</entry> <entry key="filter.skipAttributes">alarm,result</entry>log example: