2 Respostas
- Mais recentes
- Mais votos
- Mais comentários
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
respondido há 2 anos
0
Possible duplicate - https://repost.aws/questions/QUyWYanxZcSuOMICoY-EX9Pg/aws-io-t-core-and-fleet-indexing-connected-false-response
respondido há 2 anos
Conteúdo relevante
- AWS OFICIALAtualizada há 3 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há um ano
ok, I just tried this and still getting 0 connect life cycle events, and fleet indexing says it's disconnected