I have an IoT device that unfortunately makes it difficult to inspect network traffic inside of a TLS socket that it establishes.
I'm trying to use an MQTT client on this device to PUBLISH an MQTT control packet to IoT Hub, but after I send the control packet, IoT Hub disconnects and the message never arrives in IoT Hub.
I'm only starting out so I don't have any routes and am just relying on the default IoT Hub route.
Using the "az iot hub monitor-events --hub-name ..." Azure CLI command to monitor for the incoming MQTT messages.
If I use the Azure Python IoT Hub SDK, I can see the MQTT messages get delivered just fine.
I just can't seem to get it to work with this other MQTT client on the physical IoT device.
So my question is: How does one debug this MQTT PUBLISH issue, or more generally any other IoT device-to-cloud telemetry issue, when you can't inspect the traffic inside the TLS session?
E.g. Is there an Azure CLI tool that is an equivalent of the actual IoT Hub and can be run locally?
Is there a way to temporarily disable TLS on the IoT Hub end-point?