Help Center>
IoT Device Management>
FAQs>
Secondary Development>
FAQs About Product Development>
Device Development>
Command Status Is Not Changed to Successful After a Device Reports the Command Execution Result
Updated on 2022-02-24 GMT+08:00
Command Status Is Not Changed to Successful After a Device Reports the Command Execution Result
On the Developer Center, choose
, and enable the log function. After the device reports the command execution result, check whether logs are recorded.
- If no log is recorded, the message does not reach the IoT platform. In this case, check the network and device.
- If logs are recorded and no error message is displayed, the mid field in the codec may be incorrectly configured. For details on how to use mid, see Codec for Containing Command Execution Results.
Parent topic: Device Development
Device Development FAQs
- Registered Devices Cannot Connect to the IoT Platform
- Message 513 Is Reported When Devices Are Connected to the IoT Platform
- DTLS Encryption Algorithms Supported by the IoT Platform
- What Does CTNB Mean
- How to Select PSM, DRX, and eDRX
- Devices Cannot Receive Commands from the IoT Platform
- IoT Platform Does Not Receive Data Reported by Devices
- Historical Data Does Not Contain Data Reported By Devices While No Error Occurs
- Duration for Devices to Receive Commands
- Devices Fail to Receive Data Reporting Responses
- Data Reporting Is Successful at One Position But Fails at Another Position
- Command Status Is Not Changed to Successful After a Device Reports the Command Execution Result
- Whether the IoT Platform Can Switch Between the Big-Endian and Little-Endian
- Commands Fail to Be Delivered When a Device in DRX Mode Does Not Report Data in One to Two Days
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore