Eric Wolz
Eric Wolz
**IoTHubDeviceClient_LL_SetDeviceMethodCallback** The _LL_ (low-level) APIs are not multithreaded, so any callback will block the SDK pipeline including MQTT communication. Blocking this for a long time will cause MQTT PUBACK and...
> Regarding multithreaded API. Is the queue handling synchronous, meaning that one blocking direct method would block other? In this case, this would also be a big problem for users...
This usually happens if you have two devices using the same device ID. Only one device with a specified device ID can be connected to a hub. If a new...
Prov_Device_MQTT_Protocol is in prov_transport_mqtt_client.c https://github.com/Azure/azure-iot-sdk-c/blob/32942abb994f6855edc2a4dee8afd80735df4151/provisioning_client/src/prov_transport_mqtt_client.c#L133 You need to build prov_device_client with the cmake -Duse_mqtt:BOOL=ON option https://github.com/Azure/azure-iot-sdk-c/blob/32942abb994f6855edc2a4dee8afd80735df4151/provisioning_client/CMakeLists.txt#L303
@benjaesq the mqtt symbols will be in the prov_mqtt_transport library. libprov_device_client does not call directly into MQTT as it can also support AMQP and HTTP protocols (and websockets). This is...
@benjaesq Thanks, I understand now and will investigate.
There is no current workaround. You would need to build your own .so for this.
connection and messaging reliability is documented [here](https://github.com/Azure/azure-iot-sdk-c/blob/main/doc/connection_and_messaging_reliability.md) > We might have come into a situation where some devices have spotty communication with the cloud and outgoing messages (Device to cloud)...