IoT Central Rest Api Add/Update Device w/deviceTemplate returning 400 Bad Request

Question

IoT Central Rest Api Add/Update Device w/deviceTemplate returning 400 Bad Request

waiiki 20

I'm going to go ahead and link the github issue I created. I closed the issue there and am moving it here because I'm not sure if its specific to me, or if the docs are incorrect. Please see this link:

https://github.com/MicrosoftDocs/azure-docs/issues/110004

Basically I am following the CreateDevice api request with a given device template id and am receiving this error:

"The model definition for this device was not found. You can contact support at https://aka.ms/iotcentral-support. Please include the following information. Request ID: ba7ybknx, Time: Thu, 25 May 2023 16:50:15 GMT."

Support for technical questions is $30/month which I'm hoping not to have to pay.

VasimTamboli 5,550 Reputation points MVP

2023-05-25T17:34:52.4066667+00:00

general guidance to help troubleshoot the issue:

Review the error message: The error message suggests that the model definition for the device template specified in your API request was not found. This could indicate a problem with the device template ID or a mismatch between the ID and the templates available in your IoT Central application.

Verify the device template ID: Double-check that the device template ID you are using in your API request is correct and corresponds to a valid template in your IoT Central application. Make sure there are no typos or errors in the ID.

Check template availability: Ensure that the device template you are referencing is available and published in your IoT Central application. If it's not published, you may encounter issues when trying to create or update devices based on that template.

Validate the API request payload: Review the structure and content of your API request payload to ensure it aligns with the expected format for creating or updating devices in IoT Central. Ensure that you are providing all the necessary properties and values as required by the device template.

Seek assistance from Azure support: If the issue persists and you are unable to resolve it, you may consider reaching out to Azure support for further assistance. They can help investigate the problem and provide guidance specific to your scenario.

While support for technical questions may have associated costs, it's best to refer to the official Azure support documentation or contact Azure support directly to understand the available options and any potential fees.

2 answers

Your answer

VasimTamboli 5,550 Reputation points MVP

2023-05-25T17:34:52.4066667+00:00

general guidance to help troubleshoot the issue:

Review the error message: The error message suggests that the model definition for the device template specified in your API request was not found. This could indicate a problem with the device template ID or a mismatch between the ID and the templates available in your IoT Central application.

Verify the device template ID: Double-check that the device template ID you are using in your API request is correct and corresponds to a valid template in your IoT Central application. Make sure there are no typos or errors in the ID.

Check template availability: Ensure that the device template you are referencing is available and published in your IoT Central application. If it's not published, you may encounter issues when trying to create or update devices based on that template.

Validate the API request payload: Review the structure and content of your API request payload to ensure it aligns with the expected format for creating or updating devices in IoT Central. Ensure that you are providing all the necessary properties and values as required by the device template.

Seek assistance from Azure support: If the issue persists and you are unable to resolve it, you may consider reaching out to Azure support for further assistance. They can help investigate the problem and provide guidance specific to your scenario.

While support for technical questions may have associated costs, it's best to refer to the official Azure support documentation or contact Azure support directly to understand the available options and any potential fees.

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 deleted comment

Comments have been turned off. Learn more

Answer 2

Dominic 1,631 Microsoft Employee

The docs include some more detailed examples and link to a Postman file that you can use to experiment with the API:

LeelaRajeshSayana-MSFT 17,421 Reputation points Moderator

2023-05-26T13:40:43.15+00:00

Hi @Dominic Thank you for sharing these resources. I have tested the Device Template List API and the model ID returned through that API is as expected. However, if we test the Device List API, the template ID returned is different. This templated ID which is returned from this API is needed to create a device through Add Device API. We have no means to track this ID on the portal and it is not reported in documentation that ID would be different. I will investigate this further and provide more feedback on this.