Azure-docs: Issue in documentation regarding retrieving Device Twin over HTTP from device.

Created on 17 Jun 2020  Â·  9Comments  Â·  Source: MicrosoftDocs/azure-docs

This page lists the endpoints for devices, one of which is

Retrieve and update device twin properties. A device uses this endpoint to access its device twin's properties.

Below that section, it states the following:

These endpoints are exposed using MQTT v3.1.1, HTTPS 1.1, and AMQP 1.0 protocols. AMQP and MQTT are also available over WebSockets on port 443.

However, retrieving a device twin (from the device itself) is not supported on HTTP, it is supported on AMQP and MQTT.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 assigned-to-author doc-bug iot-husvc triaged

All 9 comments

@MatthijsvdVeer , Thanks for the feedback! We are currently investigating and will update you shortly.

@MatthijsvdVeer ,I have assigned the issue to the content author @robinsh for further review and update the doc as appropriate.

reassign: @JimacoMS3

Hi @MatthijsvdVeer ,

Thanks for your feedback. I'm checking with engineering about this. Have you actually validated that HTPPS is not supported by trying it?

Thanks,
Jimaco

Yes, I tried it and using HTTPS and it comes up with an error message that says it only supports MQTT. But when you run the same code using MQTT or AMQP it works, I was using the C# SDK.
Important to note, I believe this might work with the service endpoint, but from the Device it definitely doesn't work. Let me know if you need more info, I can show you the error over Teams.

Thanks for the info! I think we're OK for the moment. I've asked our engineering team to look into it. I've noticed that in our documentation there are some topics where we say it's MQTT and AMQP only.

I think on the service-side, it should be only AMQP (and AMQP over WebSockets) for device/module twins.

Thanks again for your help. I'll update the thread with what I find out from engineering. It might take a few days for them to respond though.

@MatthijsvdVeer I've heard back from engineering. They've confirmed that reading and writing device twins and reading direct methods are not available over HTTPS from the device. I'll make the appropriate updates in the next couple of days. Thanks for pointing this out!

-Jimaco

Hi @MatthijsvdVeer Thanks again for your help. I've updated the topic to reflect that neither device twin (read/update) nor direct method reads support HTTPS on the device side. I'll leave this open for a day or two for you to comment if you feel that more needs to be done.

-Jimaco

please-close

Was this page helpful?
0 / 5 - 0 ratings

Related issues

behnam89 picture behnam89  Â·  3Comments

jamesgallagher-ie picture jamesgallagher-ie  Â·  3Comments

DeepPuddles picture DeepPuddles  Â·  3Comments

JeffLoo-ong picture JeffLoo-ong  Â·  3Comments

jebeld17 picture jebeld17  Â·  3Comments