Looks like it's still the case. You can see here what message types are supported:
Hello Anton,
Is there any way to solve this issue?
We really need to start receving this kind of message to our data base. I found an example of this messages between the ones sent by our calamp device:
2020-10-30 13:05:13 INFO: [53f664d3: calamp < 179.28.88.198] HEX: 830547643586340101010400105f9c39ba5f9c302eeb36d5bddf39df700000000000000000003400040321ff9f4f0087080200001c30783330304544383946333335303139303030303030343637450d0a
I'm using a calamp LMU2720 and connected to it I have a serial device that sends data to the LMU. I've talked to Calamp support and they told me that the message sent to the server in this case is a type 5 message and that the device is sending it, but I can't visualize it in the data base. I saw a thread from two years ago in this forum that said that traccar didn't support user serial messaging. Is this still the case? Is there any solution?
Thanks in advance