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公式更新しました 1年前
- AWS公式更新しました 1年前
ok, I just tried this and still getting 0 connect life cycle events, and fleet indexing says it's disconnected