Connectivity issue after converting the IoT hub to DigiCert.

Navya Sri Bondala 10 Reputation points
2023-05-10T04:53:11.2+00:00

Hi,

Recently, we created a new IoT hub and migrated it from Baltimore to DigiCert.

The messages are received from IoT devices to Cloud using Mqtt.

We have followed the procedure for updating certificates in the device too.

The reporting interval is 13min. i.e., the device should report every 13min.

For Ex:

>>For the first D2C messages, the date is successfully published and received after 13min of the device start.

>> The second D2C message is failing to publish from the device side(i.e., checked the logs it is showing mqtt connected but failed to publish the data.

>> This is happening for every alternate reading.

Could you please help me why this is happening? i.e., we are missing a reading every alternate time.

  • Below is the picture, in which the first column is generated message time from the device and 3rd column is the inserted time into the IOT hub and 4th is the count of message. As you there is a difference of approx. 30min from one reading to another.

User's image

Azure IoT Hub
Azure IoT Hub
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
1,157 questions
{count} vote

1 answer

Sort by: Most helpful
  1. Sander van de Velde | MVP 31,211 Reputation points MVP
    2023-08-01T10:18:18.79+00:00

    Hello Navya,

    it's a strange situation to see it sometimes works and sometimes it does not.

    So the client-side code seems to work...

    I suggest submitting a support request ticket. Perhaps the migration had some glitches on some parts of the underlying IoT Hub infrastructure.

    Provide them with the exceptions you see on the device.

    The support team is capable of checking the quality of the service.

    If you use a Device Provisioning Service (a recommended solution), you could migrate your devices to another IoT Hub which does not have these glitches.


    If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

    0 comments No comments