feature request : Opening to the world
Most decoded data (latitude, longitude, speed etc) is already available as parameters.
There is a way to send raw command. The type is called "custom" and you need to provide "raw" parameter.
Dear Mr.Tananaev.
I really Appreciate your response.
You right, most decoded data is there.
But some device have more data, i.e : ADC, SOS , etc etc.
- I will take a deeper look on the API part source code.
Sincerely
-bino-
- Those are part of "attributes" field.
Dear Mr.Tananaev.
Thankyou for your help.
But I really don't know what you mean.
No, it's not your fault. It's because I have no Java knowledge.
I'll ask my Java friend here in my area.
Sincerely
-bino-
I mean that "ADC, SOS, etc etc" are part of {attributes} parameter.
Dear Sir.
Could you please give me example on how to use it ?
Sincerely
-bino-
Something like this:
<entry key='forward.enable'>true</entry>
<entry key='forward.url'>http://example.com:8080/?id={uniqueId}&attributes={attributes}</entry>Done !!!
You are the man.
Sincerely
-bino-
Dear Developer.
Hex Data in forward.url
From response at : https://www.traccar.org/forums/topic/are-there-server-hooks/#post-1934
Could you please add :
a. alldata : this is all decoded data, OR
b. hexdata : this is a received hex data, so I can forward --> <entry key='forward.url'>http://example.com:8080/fromtraccar?deviceId={deviceId}&protocol={protocol}&hex={hexData}.
command API :
I thing it'll more flexible if the REST API can receive 'deviceId' and 'encodedCommand'.
traccar only query the database for ip address of deviceId and send encodedCommand
other developer (coming with diferrent programming/scripting language) will then learn his/her device protocol from it's documentation.
ps : I'm a python script-kiddies, I know how to convert from hex to strings and viseversa, but have no knowledge in Java.
Sincerely
-bino-