Issue sending commands to Real Tracker J4 device (port 5056)

Junior_Man7 days ago

Hello everyone,

I’m using a Real Tracker J4 device that is successfully communicating with the Traccar platform via port 5056. Location data is being received correctly, and everything seems to work fine in that regard.

However, I’m having trouble sending commands through the platform. When I send commands via SMS, they work normally (for example: relay,123456,1 to cut off the engine).

I’ve tried several formats using the Custom Command feature on the Traccar interface, but none of them are accepted by the device — it doesn’t execute the command or respond in any way.

Could someone please share a working example of a relay (engine cut-off) command for this device, using the custom command type in Traccar? I want to better understand how to properly format commands for this model.

Below are the logs from the server after I tried sending a custom command and also the built-in “Block” command from the platform:
I tried to send the custom commands below:

*ET,IMEI,KS,relay*123456*1#
*ET,IMEI,KS,relay*123456*1
ET,IMEI,KS,relay*123456*1
ET,IMEI,KS,relay*123456*1#

I also tried the command that is already on traccar, that is "enginestop" but it also won't work.

The command for blocking using SMS is: relay,123456,1

I don't know how to make it block by gprs on traccar, someone can help me?
I just need an example.

Logs:

log j4.jpg

This is the protocol document:
https://smallpdf.com/share-document#r=result&t=917e945cb032d9b3961d83848ea9fe53&i=share

Thanks in advance

Anton Tananaev7 days ago

As you can clearly see from your log, Traccar adds heading and ending automatically. So instead of sending *ET,IMEI,KS,relay*123456*1#, you should be sending just relay*123456*1.

Junior_Man6 days ago

I tried it but it won’t work too

Anton Tananaev6 days ago

Logs?

Junior_Man6 days ago

Logs:

The last picture is about the sms I sent before and worked well.

LOGSSSS.png

Imagem do WhatsApp de 2025-07-26 à(s) 20.13.51_a18895da.jpg

Anton Tananaev6 days ago

From what I can tell, the format matches the documentation. So either the documentation is incorrect or there's some issue with the device itself.

Junior_Man6 days ago

Alright, I’ll try to talk to the company who sold them and ask for informations about it.
Thanks a lot.

Junior_Man6 days ago

Hello, I did some more testing and noticed that sometimes the command works on the device and sometimes it doesn’t. And yes, the command format is exactly as you explained. Thank you.

Junior_Man6 days ago

I also set the device password to 123456 in the device parameters, although I’m not sure if that makes a difference.