Response code when the device make connections
| Response Code | Comment |
|---|---|
| 0 – OK | |
| 1 – DEVICE_NOT_REGISTERED | Change Device from release to acquired |
| 2 – AUTO_REGISTER | |
| 3 – DEVICE_NOT_FOUND | Deleted/Not found in the platform
Verify your uniqueID and Env |
| 4 – DEVICE_INACTIVE | The device is inactive |
| 5 – OBJECT_MOVED | |
| 6 – CPID_NOT_FOUND | Verify your environment and CPID / Check Subscription expiry date |
| 7 – COMPANY_NOT_FOUND | Verify your environment and CPID |
Troubleshooting
BaseUrl not found
Message: { status: false, data: null, message: ‘Invalid URI “sync”‘ }
Reason: CPID and ENV not proper.
Solution:
– Make sure you CPID, uniqueID and ENV are proper on the firmware file if it’s proper then make sure internet connect Lost.
CPID not found or Subscription expired
Message: RC CODE : 6 (CPID_NOT_FOUND)
Reason: The wrong CPID entered or your subscription is expired
Solution:
– CPID should be valid. You can take it from here (How to get CPID)
– Check the combination of CPID and ENV (IoTConnect platform environment)
– Verify your subscription expiry date from dashboard
Device not found
Message: RC CODE : 3 (DEVICE_NOT_FOUND)
Reason: Device not registered on IoTConnect cloud
Solution:
– It should be valid and respective to the entered CPID and ENV
– The device should be registered with entered uniqueId on IoTConnect cloud respective to the selected CPID and ENV
– If your device name is wrong then you need to stop the script and run again after uniqueId correction.
Device not registered
Message: RC CODE : 1 (DEVICE_NOT_REGISTERED)
Reason: Device not registered on cloud
Solution:
– If your uniqueId is right and till you getting the above error then verify below process
– It should be registered on IoTConnect Platform respective to the selected CPID and ENV
– Its status should be “Acquired” (registered on the cloud)
– SDK process is running and rechecking till you follow the above two-point then your device will get connected.
A network connection is not available
Message: { status: false, data: [], message: ‘Network connection error.’ }
Reason: Network connection not available.
Solution: Check the network connection and try again.
X.509 authentication device issue (CA-signed or self-signed)
Message: “SDK options:: Set proper certificate file path and try again.”
Reason:
– CA or Self signed certificate not defined properly
Solution:
– Add your device authenticate certificate in SDK options in the device initialize method.
– Check certificate path proper
Logfile create an issue
Message: “<< Exception error >>”
Reason: In proper file path and permission
Solution:
– Give a proper read and write permission to the device folder
– Check log file path
Send data before device connect or after disconnect
Message: “<< cpid_uniqueid >> :: sendData :: The device is not available on the cloud.”
Reason: Device to cloud connection not available
Solution: Check the device to the cloud connection.