Azure IoT Hub for Cloud to Device (C2D) and Device to Cloud (D2C) Messaging

[@johnzawodniak8518]

Thank you for taking the time to clearly explain the message routing to the service bus queue. So many of the demos focus on getting the device connected to the IOT hub but give very little insight into what you can do with it once it is in the cloud. For example: if you wanted the MQTT message to trigger a response back to the device with a schedule. Again, thank you.

[@artofaction]

Thank you for the video. Very informative and helpful information. I noticed a small typo in the title, you have C2D twice in the title. Thank you 🙂 Edit: wow, already fixed!

[@atulpathare2775]

Thanks a bunch for your efforts it means a lot. :)

[@nielsdevries9175]

Thanks for the great video. I got one question regarding device firmware updates. Is this also possible using the C2D browser interface you showed? Or how else is this possible? Thanks in advance!

[@1337Ayhr]

Great video. What Ive not understood so far is: If I want to make sure that the devices sending to the IOT hub are really the devices they claim to be, do I need a PKI infrastructure? Or how exactly does it work with the x509 certificates and the device provisioning service?

[@Atmosera-]

PKI infrastructure with TPM attestation is probably the best way to ensure that the device is the one shipped.

[@gayathripochampalli7478]

Hi i'm using azure iot sdk c samples to explore azure iot hub when send messages from c2d always the content type is byte array, even I send string data it's printing bytearray as contenp type, is there any setting to set the content type to string?? Please help me

[@Atmosera-]

Sometimes, you need to do a to strong on the byte array.