- Newest
- Most votes
- Most comments
You don't necessarily need to subscribe to updated/accepted
or update/rejected
. But QoS won't help you if the result of the update is that the update was rejected. You wouldn't know.
You can subscribe to more than one topic. Please refer to the SDK's shadow sample: https://github.com/aws/aws-iot-device-sdk-java-v2/blob/main/samples/Shadow/src/main/java/shadow/ShadowSample.java#L242. (I think you mean the AWS IoT Device SDK V2).
Thanks for the response. I was concerned that by not subscribing, a whole bunch of messages would pile up and cause problems. In our situation we have a lot of devices and don't really expect many rejections, so the overhead of subscribing to all those topics isn't worth it.
I do need the update/accepted topic to work for a limited number of devices (basically, ones where my end user actually has our app open at that moment). This used to work, but for some reason it is behaving oddly. I do not receive the expected responses. However if I later unsubscribe and resubscribe, I sometimes get a whole slew of old responses all at once.
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Also, I can't figure out why I'm not getting any responses on /update/accepted or /update/rejected even if I do subscribe to them. Are these responses automatically generated by IoT, or do they depend on the device itself sending a response?