Digital Matter devices have historically sent data via the OEM Server to a variety of front end platforms (ie 3rd party servers). Requests for the ability to bypass the OEM Server and go direct to the 3rd party servers have become more frequent. Device firmware has been improved to accommodate this.


Older firmware that was directed straight to a 3rd party platform would send some versioning and downlink messages to the platform. We recommended (in this article) that these messages should be ignored, and given standard canned responses. Newer firmware, with support for direct to 3rd party integration, improves this experience, and enables some convenient features.


With the new "direct to 3rd party" firmware, integrators who wish to bypass OEM will notice the following features:

  • Devices have the concept of a data server and a configuration server. The data server would be the clients server. The configuration server would typically be the OEM Server. The configuration server can be effectively disabled if the client wants no interaction with OEM.
  • The device can be setup to periodically contact the configuration server for updates. This would include firmware, system parameters and admin parameters.
  • The device can be instructed to contact the configuration server on demand by the data server.
  • The device will send all of it's tracking and telemetry data to the data server only. None of this is sent to the OEM Server.
    • This is useful for clients who are sensitive concerned about data leaving their approved network. It can now go straight from the device to to their server.
  • Encryption is optional. If the device is moved to an encrypted channel, care should be taken if it moves back to the unencrypted channel. Either do not trust it, or disallow it.
  • OEM chargers can be avoided if the device is set to "configuration only".
  • "Configuration only" implies:
    • No connector can be set on OEM. If the device does send data to OEM it cannot be forwarded on, and will not be saved.
    • Debugging is not possible on OEM, but the device will send the debug records to the data server.


If you are interested in the direct to 3rd party scheme, please contact your local Digital Matter office. We normally require and NDA and a payment for support to assist with integration.


If you are a new customer, we recommend you get started with the OEM Server and a TCP connector. Once integration is successful, moving the device's data server to your own platform should be straight forward. The benefit of using OEM in the beginning is improved debugging and more effective support from us.


Contact Digital Matter to find out which devices and versions of firmware support this Direct to 3rd Party scheme.