why does my iot central device in provisioned connected status turned disconnected when I update the properties using the IoT Central sdk

Eddie Soong 0

I created my device using IoT Central sdk call:

PUT https://{{AppSubdomain}}.azureiotcentral.com/api/devices/{{deviceId}}?api-version={{dataPlaneGA}}

Body:

{
"displayname" : "12345-PAC",
"template": "dtmi:rnkliqszv:wiipdqd4wj",
"simulated": false.
"enabled": true
}

The device was created and had a status of registered.

Then I have a simulator that sends telemetry data to the device which turns the status of the device to "provisioned".

Then, I called:

PUT https://{{AppSubdomain}}.azureiotcentral.com/api/preview/devices/{{deviceId}}/properties

Body with a list of properties for the device in JSON.

The properties of the device were updated accordingly, however, the devices status turned to disconnected. Why is this?

Note that the device is not connected to a physical sensor. It's like a simulated device but the simulation of the telemetry data is coming from my own python code.

AshokPeddakotla-MSFT 33,756 Reputation points

2023-10-09T10:07:46.6033333+00:00

Eddie Soong Greetings!

It seems that the device status changed to "disconnected" after you updated the properties of the device. This could be because the device is not sending any telemetry data to IoT Central.

Note that the device is not connected to a physical sensor. It's like a simulated device but the simulation of the telemetry data is coming from my own python code.

Since your device is not connected to a physical sensor and the telemetry data is coming from your own Python code, it's possible that the device is not sending any telemetry data to IoT Central.

Did you try sending some telemetry data from your Python code to IoT Central?
Eddie Soong 0 Reputation points

2023-10-09T13:38:12.2166667+00:00

Hi Ashok. Thx for your reply.

Actually, my simulator was sending the telemetry to the device. That's how it changed from registered to provisioned connected. I then stopped the simulator and send the property update call. That when the device turned disconnected.
AshokPeddakotla-MSFT 33,756 Reputation points

2023-10-11T15:54:38.9066667+00:00

Eddie Soong When a device sends telemetry data to IoT Central, it includes a timestamp that indicates when the data was sent. If the device does not send any telemetry data within a certain period of time, its status will change to "disconnected".

Since you stopped the simulator after sending the property update, it's possible that the device did not send any telemetry data to IoT Central and its status changed to "disconnected".

can you try sending some sample telemetry data from your Python code to IoT Central after the property update. This will ensure that the device is sending telemetry data and its connection status remains "provisioned". You can also check the device logs to see if there are any errors or issues with the telemetry data being sent.
Eddie Soong 0 Reputation points

2023-10-13T10:53:43.1566667+00:00

Thanks Ashok. I actually did send telemetry to the disconnected device after updating the properties and it did not revert to provisioned status.
AshokPeddakotla-MSFT 33,756 Reputation points

2023-10-19T06:16:08.7166667+00:00
Eddie Soong Apologies for the delayed response. If you have already sent telemetry data to the disconnected device after updating the properties and it did not revert to the provisioned status, there could be a few reasons for this. I suggest you to try the following steps:

Check the device's last activity time in IoT Central to see when it last sent telemetry data. If it has been a while since the device sent telemetry data, try sending some telemetry data from your Python code to IoT Central.

Check the device's connection to IoT Central. Make sure that the device is able to connect to IoT Central and that there are no issues with the network connection. You can also check the device logs to see if there are any errors related to the connection.

Share via

why does my iot central device in provisioned connected status turned disconnected when I update the properties using the IoT Central sdk

Your answer