2 個答案
- 最新
- 最多得票
- 最多評論
0
Ok so yea - this seems to be answered by the other post linked in the comment below.
"If your client is using a different client ID from Thing Name when connecting to AWS IoT, the connectivity status of your "thing" will not be indexed by Fleet Indexing"
It seems though that there is some delay between connects and the thing connectivity state updating as per https://repost.aws/questions/QU5zUQchQ3SWyLWQPeDH7umQ/aws-io-t-core-takes-too-long-to-update-the-connectivity-information-of-a-device
已回答 2 年前
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
ok, I just tried this and still getting 0 connect life cycle events, and fleet indexing says it's disconnected