Description:

During this transition form LCM (LOCATOR CONTROL MANAGER) to DMP (Device Management Platform), you may face some issues regarding connectivity to the platform.

On problem is if the Device was created first on LCM and didn't exist in DMP before it.

Right now, all devices created in LCM, are created automatically in DMP. However, when the device does not exist in DMP first, the default protocol will be TCP/DCS

Recreating the problem:

This unit BR_Pro5_Lite was created on Nov. 1st, 2023. The DMP was deleted before that to reproduce the problem.

A 5th Gen Device needs protocol MTTQ/IoT to work, otherwise it will fail to communicate.

Example: FW update

{"commandStatus":"EXECUTING","serviceRequestId":{"requestId":"dmp-dcs-connector-af3ef10c-10e3-4fad-bc59-16ce61e81e4d","serviceName":"firmwareupdate",

Upload has been running for more than 20 minutes with no success (the hour difference is 3h)

The device may answer to sms commands connect and dmpfconnect, but no update will be seen:

The last time connections remains the creation on

Solution

1. Delete the device

2. Recreate it in DMP and take note of the sastoken

3. Send sastoken to the device.

Before sending the sastoken, it will show up as Unspecified, however, the protocol will be the right one:

After sending the sastoken:

The output for sms command dmpfconnect is different as well:

Upgrade is completed then:

Additional information

The following article can assist you on how to add a 5th Gen Device in DMP