Dear community.
I have Event Forwarding activated and successfully using it to receive Device Online and Device Offline events and others.
We now have setup an event handler on our side that shall handle events that are triggered by Traccar Server in case a Custom Command was successfully executed by the client and a response has been received by Traccar Server. According to the docs, this should result into an event in Traccar Server:
https://www.traccar.org/commands/
It says:
Command results are supported for a limited number of protocols. If it is received and decoded, a command result event will be generated.
I can see in the logs that the command was issues successfully and that the client also responded with the correct response. But I cannot see any event information in the log and also do not receive any new data in our event handler system. Is there anything I am missing to configure?
As the command is received (not sure about decoding and why it should not be decodable - it is manually decodable), I am stuck with where to look at now and would appreciate any help.
Here is the part of the log that is related to one command and its received command result (3rd line).
2026-04-02 13:00:35 INFO: [T1e3c525a] id: 019175848517, command type: custom sent
2026-04-02 13:00:35 INFO: [T1e3c525a: huabao > 47.65.178.183] CXZT
2026-04-02 13:00:35 INFO: [T1e3c525a: huabao < 47.65.178.183] 7e09000095019175848517010c00534d532c43303332283730454c41534344295f4a545f565f312e3020323032352f30332f30340a49443a31393137353834383531370a4950313a747261636361722e63727970746f6e6f64652e646520353031350a4950323a20300a55543a3138302c3630300a4241543a39250a41504e3a7765622e766f6461666f6e652e64650a4750533a432d31342d31300a47534d3a31380e7e
2026-04-02 13:00:35 INFO: [T1e3c525a: huabao > 47.65.178.183] 7e800100050191758485170000010c090000737e
I would expect an event being documented in the log and sent to the event URL.
-- Cheers, Nils
In this case it's probably not decoded yet.
Can you help me to make it decoded and sending the event?
If you're interested in sponsoring the work, feel free to send an email to support. If not, then you can submit a feature request for it.
So, you are confirming that the response is not decoded from Traccar Server? I am asking, because this seems to be a very easy task if it works for other setups... isn't it?
I'm not confirming anything. It's probably relatively easy to implement if it's not decoded yet.
So, what would it be that I am sending to support? I do not want to just send a "it is not working" message. This is why I am using the Forum, to better understand what is the actual issue. Only then, I can understand if I can fix it myself because of a missing setting or if i need professional tech support to enhance the product or protocol handler or anything. Am I right?
If you want to check for sure if it's decoded or not, then you look at the source code.
Sounds fair enough. Can you point me to the part where that happens?
In the HuabaoProtocolDecoder class.
Dear community.
I have Event Forwarding activated and successfully using it to receive Device Online and Device Offline events and others.
We now have setup an event handler on our side that shall handle events that are triggered by Traccar Server in case a Custom Command was successfully executed by the client and a response has been received by Traccar Server. According to the docs, this should result into an event in Traccar Server:
https://www.traccar.org/commands/
It says:
I can see in the logs that the command was issues successfully and that the client also responded with the correct response. But I cannot see any event information in the log and also do not receive any new data in our event handler system. Is there anything I am missing to configure?
As the command is received (not sure about decoding and why it should not be decodable - it is manually decodable), I am stuck with where to look at now and would appreciate any help.
Here is the part of the log that is related to one command and its received command result (3rd line).
I would expect an event being documented in the log and sent to the event URL.
-- Cheers, Nils