Online Application Simulator Fails to Deliver Commands
- On the Developer Center, choose to view the logs. Check whether the IoT platform finds the corresponding codec plug-in and encodes the command successfully. If there is an encoding error, a codec plug-in error occurs. In this case, use the codec tool to detect the error and rectify the fault based on the error message.
- Check the command delivery mode and device work mode. If the command is delivered immediately, the device must work in DRX mode. To obtain the work mode of the device, contact the carrier.
- Change the command delivery mode to cache delivery (that is, set expiretime to a value other than 0 when calling the Creating Device Commands API). Then, check whether data is successfully delivered after a device reports data.
If a cached command is successfully delivered, the failure is caused by the aging of device links. If the device works in DRX mode and a heartbeat message is reported every 25 hours, but the device link is still aged, the IoT platform service provider must check the parameter configuration of the TUP package.
Calling APIs FAQs
- Authentication API of the IoT Platform Is Successfully Called Locally But Fails to Be Called on Application Servers
- Error Occurs When an NA Calls an API
- Online Application Simulator Fails to Deliver Commands
- Command Is Successfully Delivered Using the Simulator But Fails to Be Delivered by Calling the API
- Application Server Fails to Deliver Commands and Receives Error Code 403
- How Does an Application Server Deliver a Cache Command
- What Does an Expired Command Mean
- Does the IoT Platform Support Command Resending
- What Does a Timeout Command Mean
- Can the IoT Platform Deliver Commands in Batches
- Are the APIs of the IoT Platform Called Only Using Java
- What Are the Command States on the IoT Platform
- Failed to Call the Calling the Registering Directly Connected Devices API
- APIs Fail To Be Called After a Period of Time While Parameters Remain Unchanged
- Commands Fail to Be Sent After a Period of Time While the Previous Commands Are Successfully Sent
- Historical Data Is Not Returned When the Querying Historical Device Data API Is Called
- Devices Registered with the IoT Platform Are Deleted After a Period of Time
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore