question

RoopakIngole-9169 avatar image
1 Vote"
RoopakIngole-9169 asked SatishBoddu-MSFT commented

IoT Central does not recognise telemetry data of type "Duration"

I have IoT Central application configured to have a telemetry data of type "Duration". My IoT Edge device is sending this data complying to format specified in ISO 8601.
But IoT Central is not able to recognize this datatype and does not parse it.

azure-iot-edgeazure-iot-central
· 13
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @MatthijsvdVeer @RoopakIngole-9169

Thanks for reporting this issue!

We confirm this is an active bug that is being worked upon by our team. We don't have any ETA for the fix release as of now. But we will keep you posted on this thread as soon as possible.

Sorry for the inconvenience caused in this matter!

1 Vote 1 ·

Hey @RoopakIngole-9169, when you're viewing the device in IoT Central, could you go to the Raw Data tab and include a screenshot of it in your question? It will add some context that we can work with. Thanks in advance.


0 Votes 0 ·

@MatthijsvdVeer please see the screenshot as attached. Note that "Uptime" is the data that I am interested in and not able to get processed. In the attached screenshot "Uptime" did not include the microsecond portion. After I add the Microsecond portion, the whole message gets processed but not able to visualize "Uptime" either in Text form or Line Graph form.
57167-image.png
57139-image.png


0 Votes 0 ·
image.png (45.1 KiB)

@MatthijsvdVeer Please find the screenshot of rawdata here as well as Screens. The rawdata shows "Uptime" specified in ISO 8601 format. But not able to process it, as shown in Screens.
57225-image.png

57252-image.png

57174-image.png


0 Votes 0 ·
image.png (37.6 KiB)
image.png (190.7 KiB)
image.png (74 B)

Hello @MatthijsvdVeer @RoopakIngole-9169
, We have escalated this issue to the product team for further investigation and resolution If needed. We will keep you posted!

0 Votes 0 ·

Hello @MatthijsvdVeer @RoopakIngole-9169

Check-point: We are working with the product team to get an update on the fix. Will be providing the ETA soon.

0 Votes 0 ·

Hello @MatthijsvdVeer @RoopakIngole-9169

Check-point: We are working with the product team to get an update on the fix. As of now, there is no ETA, but we will update you soon.

0 Votes 0 ·

1 Answer

SatishBoddu-MSFT avatar image
1 Vote"
SatishBoddu-MSFT answered SatishBoddu-MSFT commented

Hello @MatthijsvdVeer @RoopakIngole-9169

Microsoft Product team has identified this as a bug and is actively working on fixing this. There is no ETA of now to release the fix. but we will keep you posted on this thread.

Please comment in the below section if you have further questions in this matter.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @JosephRoddis-6296 My apologies, I missed your message. Sorry for the delayed response.

Could you please confirm if you are still facing this issue on your side?

0 Votes 0 ·