Help Center>
IoT Device Management>
FAQs>
Secondary Development>
FAQs About Application Development>
Calling APIs>
Failed to Call the Calling the Registering Directly Connected Devices API
Updated on 2022-02-24 GMT+08:00
Failed to Call the Calling the Registering Directly Connected Devices API
Rectify the fault based on the error information returned when the API is called. For details, see the Registering Directly Connected Devices API in the API reference.
- If a message is displayed indicating that the device has been bound, check whether the device with the same verification code (IMEI or MAC address) exists under your account.
NOTE:
If no device with the same verification code (IMEI or MAC address) is found under your account, contact the IoT platform service provider to check whether the verification code (IMEI or MAC address) has been used on the IoT platform.
- If a message is displayed indicating that the number of devices reaches the upper limit, contact the IoT platform service provider to increase the maximum number of devices supported by the IoT platform.
Parent topic: Calling APIs
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore