Users may wish to bypass the OEM Server. The devices can be set to send data directly to a 3rd party server. The support for "direct to 3rd party" devices has changed over time:

  • Before 2018: integration via OEM is the preferred method. If you wish to bypass OEM, there is limited support in the firmware. Devices can be directed to a third party server either with Admin Parameter in OEM, or with an SMS. The devices will send 2 messages to the 3rd party server that are normally filtered out by OEM. They require two "canned responses". These are described below.
  • In 2018: support for direct to 3rd party server setup has been improved. Device with newer firmware will no longer require the two canned responses below. Settings on devices can be changed with periodic connections to OEM (no data, just settings) or directly from the 3rd party server.
___________________________________________________________________________

As discussed above, pre-2018 and older firmware operated in a "direct to 3rd party" setup require these 2 canned responses. All other unknown messages can simply be ignored.

1. Message Type 0x14: Canned response 1

Multiple messages with ID = 0x14 may be received. Respond to each with the canned response below.

 

Request:

Offset

Length

Data Type

Description

0

2

BYTE[ ]

Sync characters = 0x02, 0x55

2

1

BYTE

Message type = 0x14

3

2

UINT16

Payload length is variable = X

5

X

BYTE[X]

Payload with variable contents

 

Canned Response:

Offset

Length

Data Type

Description

0

2

BYTE[ ]

Sync characters = 0x02, 0x55

2

1

BYTE

Message type = 0x15

3

2

UINT16

Payload length = 0x0C or [ 0x0C, 0x00]

5

12

BYTE[12]

Body = [ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 ]

 

The full response, including the sync chars, message type and length will look like this: 

0x02, 0x55,  Sync Chars

0x15,           Message Type

0x0C, 0x00,  Length of 12

0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00           Canned response

 

2  Message Type 0x22: Canned response 2

Multiple messages with ID = 0x22 may be received. Respond to each with the canned response below.

 

Request:

Offset

Length

Data Type

Description

0

2

BYTE[ ]

Sync characters = 0x02, 0x55

2

1

BYTE

Message type = 0x22

3

2

UINT16

Payload length = [0x00, 0x00]

 

Canned Response:

Offset

Length

Data Type

Description

0

2

BYTE[ ]

Sync characters = 0x02, 0x55

2

1

BYTE

Message type = 0x23

3

2

UINT16

Payload length = [ 0x00, 0x00]

 

The full response, including the sync chars, message type and length will look like this: 

0x02, 0x55,  Sync Chars

0x23,  Message Type

0x00, 0x00  Length of zero