This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 17%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBD%3C/text%3E%3C/svg%3E)
We (client and I) have several (10+) IoT devices that have been sending messages to Azure throughout most of January successfully and some months before as well. Just recently two of the devices have stopped filling out the "Raw Data" view. These devices are definitely still communicating to Azure as there is a custom view set up for Azure and the properties are being accepted on a defined interval on these two devices. Client-side, the program seems to run as expected. I.e. I am seeing the status codes that are expected from the SDK.
Also, these devices had been able to send data to central before. It started showing this behavior a week ago. We have tried deleting the devices from central as well as blocking and unblocking them.
The Azure-iot-sdk-c is being used (with the provisioning client) to provision, assign a model ID, and send data. The SDK version is 1.3.4. The current subscription plan is the basic plan.
My theories are:
* Some new bug with Azure IoT Central
* A limit was hit on the basic plan that I am not aware of
* Issue with outdated SDK (appears to be from July 2019 though)
Hello @Brycen Dhom ,
could the certificate used to secure the communication could have expired?
Either way, this could be the right moment to update the SDK used in your code.
First, there is a new LTS one (and many updates in between).
Plus the readme says:
All Azure IoT SDK users are advised to be aware of upcoming TLS certificate changes for Azure IoT Hub and Device Provisioning Service that will impact the SDK's ability to connect to these services. In October 2022, both services will migrate from the current Baltimore CyberTrust CA Root to the DigiCert Global G2 CA root.
I don't believe that would be the issue as wouldn't that cause most of the devices to not show data on central. One of the devices that is connecting to Azure, but not showing its raw data is a gateway. This gateway does connect to another iot device to pull data and share that with Azure. The one that it is connecting to is showing its raw data in central.
Did have some "expert help" today on this issue, and they are currently creating a ticket to look further into the matter. They believe the issue lies in Azure.
Have you experienced an issue like this before?
Hello @Brycen Dhom ,
without knowing all the details, I guess something is suddenly blocking full communication.
That could be the service itself, but also think about (new) firewall rules, changed WIFI accounts, network providers not letting data trough anymore, time server disconnected (needed to check certificates), etc.
I have not encountered a similar issue (yet) because I have not had any AIC projects running that long (mostly for PoCs and demonstrations only).
The behaviour you see is strange though, the device seems to be connected, only the telemetry does not arrive... perhaps I'm overthinking this too much :-)
Please share your finding here, that is really appreciated, thanks.
MS engineer has confirmed that an internal ticket has been created and is assigned. Will share when updates arrive.
Thanks for the quick replies.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @Brycen Dhom ,thanks for sharing the info.
Could you please provide the channel name by which the issue escalated to MS? was it via Github or Support ticket?
Not sure exactly what the issue was, but it appears that they have resolved it.
It was done through MS support and not through Github.
Hello @Brycen Dhom ,
Sorry for the inconvenience caused in this matter, we see that the issue is now resolved by the Microsoft Product Team.
Please comment in the below section if you need further help in this matter! happy to help!
IoT Central development team fixed the issue.