connectionState property not visible in com.microsoft.azure.sdk.iot.service.devicetwin.DeviceTwinDevice

[pawankaushal]

We are building our application on Azure IOT platform and we need to get connection status for a device but unfortunately the property is not available in POJO DeviceTwinDevice. Please see the feasibility of adding this field.

PS: I can see the JSON document for a device coming from hub response clearly has the property connectionState.

[timtay-microsoft]

You are correct, the SDK should be propagating that field up through the deviceTwinDevice object. I'm working to fix this issue.

[pawankaushal]

Thanks for addressing this. Would be much nicer if we can have a milestone/patch release so that we can incorporate the changes quickly? sorry By mistake I closed this and now reverted this as opened again.

• Regards
  Pawan Kaushal

[az-iot-builder-01]

@pawankaushal, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey

[timtay-microsoft]

This fix has been checked into master, and we are planning to do a release tomorrow (5/31)

[pawankaushal]

This fix has been checked into master, and we are planning to do a release tomorrow (5/31)

Thanks for the update , what would the version number for the build?

[pawankaushal]

ConnectionState coming as null irrespective of state at iot hub as it was not captured in DeviceTwin class. Please see and review the fix.
#535

[pawankaushal]

@timtay-microsoft , do you see the possibility of merging my PR and adding your unit tests on top of it?

[pawankaushal]

@timtay-microsoft , i saw a recent release , but looks like this bug is still not fixed in the current release. We are partners with Azure (lets have a private conversation to discuss this)and our product is based on the IOT platform, would appreciate if you can send us a patch release to work with post merging either PR# 535 or PR # 536.

[pawankaushal]

Hi @timtay-microsoft , @jasmineymlo , @davilu , I believe the code is ready to be merged #535 or #536. Can you please put this into upcoming release? Appreciate a quick reply!

[timtay-microsoft]

As of this release, this bug has been fixed. As such, I am closing this thread. Thanks for providing the code needed to fix this bug, @pawankaushal!