2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a 2 ans
0
Possible duplicate - https://repost.aws/questions/QUyWYanxZcSuOMICoY-EX9Pg/aws-io-t-core-and-fleet-indexing-connected-false-response
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un mois
- Réponse acceptéedemandé il y a un an
- demandé il y a 9 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
ok, I just tried this and still getting 0 connect life cycle events, and fleet indexing says it's disconnected