1 回答
- 最新
- 投票最多
- 评论最多
1
Hi Don. The ThingConnectivity object is returned by the ThingDocument object:
- https://github.com/aws/aws-sdk-net/blob/master/sdk/src/Services/IoT/Generated/Model/ThingDocument.cs#L69
- https://docs.aws.amazon.com/iot/latest/apireference/API_ThingDocument.html
You can get a list of ThingDocument objects by searching the fleet index:
- https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/IoT/MIoTSearchIndexSearchIndexRequest.html
- https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/IoT/TSearchIndexResponse.html
This uses AWS IoT fleet indexing: https://docs.aws.amazon.com/iot/latest/developerguide/managing-fleet-index.html. So fleet indexing will need to be enabled in your account.
Thanks I was able to test this and it works but the delay in status change is too long for our application. We receive the lifecycle events well before the fleet index reports the correct state. This is confirmed in question https://repost.aws/questions/QU5zUQchQ3SWyLWQPeDH7umQ/aws-iot-core-takes-too-long-to-update-the-connectivity-information-of-a-device. We do monitor lifecycle events in a different application and store status in another database, so I will need to tie into that system to get a more reliable result. Thank you for your response.