4G (or possibly 5G) tracker recommandation?
I'm pretty sure you can get SinoTrack ST-906GL to work. It probably requires some configuration.
Do you have any advice where I could start doing this? In the logs, HEX is not followed by Lat, Long, etc... but decoding it manually shows all that info. h02 is enabled, the device is registered in traccar, port 5013 is forwarded (I also tried all the other ports, this was the one that worked). If I get location by SMS it all works fine. I went through the troubleshooting about 7 times so far and haven't gotten anywhere. What else could I try to get it to work? Tracker is on version 1.0.8
When you say configuration, is that tracker side or server side?
The common issue with H02 devices is different length of binary messages. You have to configure your server to match length of binary message from your specific device model. There are some threads on the forum about it, but basically you need to set h02.messageLength configuration parameter.
I'll give that a shot. Thank you.
You can try to send the CXZT or RCONF text command to check the config and make sure all the config are correct.
I did that several times. CXZT doesn't even get a reply. RCONF shows all the settings and I redid them so many times I learned them by heart. Installed new traccar server - latest version (my original one is not up to date) but still the same exact problem. I'm getting HEX messages in the log but that's it. Setting the length of the message to 45 didn't help either.
If so you can try to test our device on demo server (https://demo.traccar.org) first to make sure the server without issue.
I did notice something weird though in the messages sent by the tracker. The Fix is A but the coordinates are wrong. For example, if the coordinates are 50.856843291439475, 0.5779072270744523 then the HEX decoder will show 5085.6843291439475, 57.79072270744523 (it moves the decimal 2 places). Could this be the problem since the place it decodes doesn't exist? Getting text messages with google link work just fine though.
EDIT: won't allow me to edit previous reply.
I tried demo2 server but it's the same result. It's always offline. I don't have access to the server logs but I'm assuming it's the same thing.
2 days and 3 servers (on different OS) later and still in the same situation. All servers work just fine with other devices (none on h02 protocol, thank God), SinoTrack just won't show as online at all.
I tried all the cloned ports, every single port except 5001 and 5093 don't show any errors in log (just HEX code which decoded shows Lat, Long, device ID, etc).
HEX message is 188 characters long so I set h02.messageLength to 94 (is this correct?) but still no success. I also tried messageLength 45 and 47 but still not working.
Logs?
Every 5 minutes it reconnects and sends this (device id and location changed):
2024-07-20 10:33:50 INFO: [T6cf19671] connected
2024-07-20 10:33:51 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:34:21 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:34:51 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:35:21 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:35:51 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:36:20 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:36:50 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:37:21 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:37:51 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:38:21 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:38:39 INFO: [T6cf19671: h02 < 93.41.225.115] 2a48512c313233343536373839302c56312c3038343532362c412c353231302e383535332c4e2c3131372e3935332c452c2020302e33362c3030302c3230303732342c46374646464446462c3233342c33322c313231362c313939373523
2024-07-20 10:38:59 INFO: [T928faab1] connectedThe samples from your log work for me.
I know they work. That's what I've been saying. Decoding them manually I can see the info that the server is meant to use but the device is always offline. I don't see the second INFO row where the HEX is decoded. If I decode them manually, I can see that info but the server won't do it automatically for some reason and as a result the device always shows as offline.
When you say "they work for you" did you add them to a server somehow and it shows on the map or that they can be decoded manually?
Setting the messageLength to 94 is correct?
Hi, can anyone recommend any 4G (or 5G) tracker that is proven to work with traccar? I've been trying to get a SinoTrack ST-906GL to work with traccar but I can confirm that IT WILL NOT WORK even though you might find other posts that say ST90x devices settings etc. I managed to get the tracker to send info to traccar server, I can see HEX received by the server and can confirm it shows protocol h02 and when I decode it using https://www.traccar.org/hex-decoder/ I can see the coordinates just fine, however, in the frontend it always shows the device as offline. After a few hours of fiddling with it I decided it to look for something else that is guaranteed to work with traccar.
Because 2G and 3G are being fazed out, I'm being forced to look at devices using at least 4G (if not 5G). My old devices still work just fine with traccar but at the end of 2024 3G will be turned off effectively killing my devices.
Since I am planning on replacing at least 6-7 devices, obviously the cheaper the better but functionality trumps price at this point. Also, devices should have relays (to disable/enable engine) so if anyone is using anything that matches these requirements I would very much appreciate a recommendation.
Thank you.