Hello, I would like to ask to enrich swagger documentation by all the possible values that can be set for the entity types, resp. it's properties. E.g. when creating Sensor there is need to specify SensorDataType, while swagger provides following documentation for SensorDataType field:
"SensorDataType : defined as category of data the sensor collects, i.e. "Motion", "Temperature", "Humidity", "Sound", "Light", etc." When trying to use custom value, I get error, because apparently SensorDataType value must be from the set of predefined values, but the whole list is not available. So my ask is to change the "etc." word in swagger documentation for the actual full list of possible values, while this relates to many other fields and properties, for which the whole list of possible values is missing. Thank you.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
Hi @MarekLani - Thanks for the great suggestion! Existing reference and tutorial documentation is in the process of being improved.
Please call the API endpoint below to bring back a complete list of available Types:
https://<YOUR_DIGITAL_TWINS_RESOURCE>.azuresmartspaces.net/management/api/v1.0/typesTo submit a custom Type:
YOUR_MANAGEMENT_API_URL/types.{
"id": 307,
"category": "SensorDataUnitType",
"name": "PercentPerHzCommand",
"disabled": true,
"logicalOrder": 0,
"friendlyName": "%/Hz"
}
Two resources that describe the existing Swagger spec (and where you can find more info) include:
Please let me know if there's anything else I can clarify further. Thanks!
I have overlooked this API. It is great to have possibility to define custom types. Thank you very much for the guidance @KingdomOfEnds .
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
@MarekLani - Glad to help! Your suggestions and recommendations have been relayed to other team members. We're reviewing ways to improve the API and documentation going forward. Thanks again!