2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta 2 anni fa
0
Possible duplicate - https://repost.aws/questions/QUyWYanxZcSuOMICoY-EX9Pg/aws-io-t-core-and-fleet-indexing-connected-false-response
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
ok, I just tried this and still getting 0 connect life cycle events, and fleet indexing says it's disconnected