Digital Matter Oyster3-4G
Configure it to send to one of the DMT ports and see if it works.
Hello Anton it is configured to Port 5137 and I tryed also the same Ports as for my Android Apps.
And nothing?
Yes there is nothing. I checked the logfiles from Traccar and there is no unknown device. The problem must be somewhere in the configuration from the Oyster3 but the documentaion from the DM devices is terrible. I thought maybe there is someone here in the forum who has had the same problem and knows the solution.
@Cansas: I have exactly the same situation as you have. A Running Traccar System, that works with with my Android phone and the Traccar-Client.
Configured the DM Oyster3-4G via the Provisioning Tool to send data to my traccar endpoint with PORT 5137 with no success.
Have you found a solution?
In case anyone is looking for a solution for these trackers, I made this: https://github.com/Saturn745/digitalmatter-traccar which implements the proprietary protocol that these trackers use and forwards the data to Traccar with the HTTP API. This might be better off in Traccar but I am not sure about the rules on proprietary protocols such as this.
Isn't it already supported in Traccar?
No, not to my knowledge. At least I couldn't get it working natively
If it is that'd be great.
Hmmm maybe it is already supported. Not sure how I missed that. I'll test this soon. Looks like I did all that for nothing lol
I've been experimenting with these recently and have them working directly, and via Device Manager (DM). Note that I've done the configuration via SMS as I don't currently have the DMLink cable (and will be using Device Manager going forward). Adding instructions here as this post came up when I was searching for info.
In Traccar add a device and set the "Identifier" to the Oyster 3's IMEI.
** Warning - don't send the SMS commands below as-is, you need to edit them to fit your environment.
Direct - sent two SMS #*,4GINIT,ApnGoesHere,1 (may not be needed depending upon network) and #*,DSERVER,traccar.server.name.here,5137.
Via DM - may need to send the APN SMS, but in many cases they will just connect to DM when started. In device manager add an "HTTP Connector" with the URL http://server.name.here:5139, then assign the connector to the device.
When testing I needed to restart the Oyster3 multiple times (i.e. take out a battery) to make the initial connection (and it seemed to work best when outside). Once connected they seem pretty reliable in both configurations (have a few deployed now). I did run into some issues sending SMS to the Oyster3; we use private APN's and the system does not support SMS-over-IP which these units appear to jump to (current theory) - have been able to regain contact with most of the units by changing the network config to one that does not offer VoLTE.
can anyone help me out I have the oyster global 3 and we have been trying to connect it to the traccar server with no luck is there anyone that is able to help us with integration support we tried it doing with the raw data but the traccar server is not decoding the data and now we tried doing it with a webhook Json with no luck still
Hello I bought one Oyster3-4G but it's not connect to the Device Manager (OEM Server). Because it is bought from a distributor. I get the "DM Link Wired Provisioning Tool" ( Link: https://support.digitalmatter.com/wired-provisioning-tool ).
I have read here that some has DM devices that are working with Traccar. Does anybody know how I must setup the device to get in conact with my server.
They server work with with my Android phone and the Traccar-Client and GPSLogger.