Job and device/shadow running at same time on the device
See original GitHub issueHello
As we know the device can only run one single connection by same client id, based on that. A physical device opens a connection with the device implementation to subscribe to the AWS IoT Shadow. I was wondering how it that will work based on the jobs implementation seems to create another new MQTT client
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Job and device/shadow running at same time on the device
You use the same connection you already have for your device to use jobs. Jobs are used through publish and subscribe to specific...
Read more >Tutorial: Interacting with Device Shadow using the sample app ...
To interact with the shadow.py sample app, enter a value in the terminal for the desired value. For example, you can specify colors...
Read more >Is IoT Device Shadow Right for You? - Trek10
The AWS IoT Device Shadow service adds shadows to AWS IoT thing objects. ... can make it more time consuming to inspect multiple...
Read more >Understanding Device Shadow Service in AWS IoT Core
The Workshop URL - https://aws-dojo.com/workshoplists/workshoplist6/A device shadow is a JSON document that is used to store and retrieve ...
Read more >Programming with AWS IoT Device Shadow Service - YouTube
Using MQTT to work with Device Shadow Workshop - https://aws-dojo.com/workshoplists/workshoplist6/Free workshops and exercises ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Please open another thread if you still have questions.
That is totally fine although there is an account level throughput limit and other limits as well so you cannot have infinite connect sessions in the end. For your reference. https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html#limits_iot