
My provider keeps telling me the same thing and sent me this screenshot.
You're asking for help, but then completely ignoring what I'm saying.
Why do you think that? I answer every question and look for a solution to the case.
I told you exactly what you should be using in Traccar. But you're going back to the protocol documentation.
again it doesn't work
Have you checked logs?
2026-05-10 17:19:57 INFO: [Ta5b8b04f] id: 869595061374194, time: 2026-05-10 17:18:27, lat: 43.24816, lon: 27.97801, course: 0.0
2026-05-10 17:19:57 INFO: Position filtered by Zero filters from device: 869595061374194
2026-05-10 17:20:53 INFO: [Ta5b8b04f: iotm < 95.42.86.116] 325400054243452f44000202020800f24cbb60e4160300013b004294006a0500306b2f0508301c010e00d0f5fd2c42f7d2df410000100900000a01006d00011300040320030405203d000200010b0001940000120018
2026-05-10 17:20:53 INFO: [Ta5b8b04f: iotm > 95.42.86.116] 40020002
2026-05-10 17:20:56 WARN: Attribute computation error - org.traccar.handler.ComputedAttributesHandler.computeAttribute:146@1:2 variable 'battery' is undefined - Variable (ComputedAttributesHandler:147 < *:159 < BasePositionHandler:34 < ProcessingHandler:171 < *:180 < MotionHandler:41 < ...)
2026-05-10 17:20:56 INFO: [Ta5b8b04f] id: 869595061374194, time: 2026-05-10 17:20:50, lat: 43.24800, lon: 27.97801, course: 0.0
2026-05-10 17:21:25 INFO: [Ta5b8b04f] id: 869595061374194, command type: outputControl sent
2026-05-10 17:21:25 INFO: [Ta5b8b04f: iotm > 95.42.86.116] 323200143836393539353036313337343139342f4f555443000002020800f24cbb60e4160300040a00ffffff7f00000300b0b150
2026-05-10 17:21:26 INFO: [Ta5b8b04f: iotm < 95.42.86.116] 40020000
2026-05-10 17:21:53 INFO: [Ta5b8b04f: iotm < 95.42.86.116] 325400054243452f44000202020800f24cbb60e4160300013b007e94006a0500307b2f0508301c010e00d0f5fd2c42f7d2df4100000c0b00000a01006d00011300040320030405203b000200010b000094000012005f
2026-05-10 17:22:23 INFO: [Ta5b8b04f: iotm < 95.42.86.116] 325400054243452f44000202020800f24cbb60e4160300013b007e94006a0500307b2f0508301c010e00d0f5fd2c42f7d2df4100000c0b00000a01006d00011300040320030405203b000200010b000094000012005f
2026-05-10 17:22:53 INFO: [Ta5b8b04f: iotm < 95.42.86.116] 32920100054243452f44000202020800f24cbb60e4160300013b007e94006a0500307b2f0508301c010e00d0f5fd2c42f7d2df4100000c0b00000a01006d00011300040320030405203b000200010b00009400001200013b00ba94006a0500306b2f0508301c010e00d0f5fd2c42f7d2df410000100b00000a01006d00011300040320030405203d000200010b000194000012008f
...
Looks like the command was sent successfully. Have you verified the HEX?
I don't actually know which code and what I should check. The command is apparently being sent, but the device output is not responding.
You should check the command from logs against your documentation.
I already know it by heart, but it doesn't help me with success.
You know what by heart? The statement doesn't make absolutely any sense. You have to check what is sent against the documentation.
I'm trying both options. I want to be able to start and stop it with a command.