1 Answer
- Newest
- Most votes
- Most comments
0
Hi. As far as I know, the streaming topics are not published to the broker, and are only published to the device that is downloading from the stream. In other words, only the client that publishes the stream/get message can receive the stream blocks.
Why are you attempting this?
Relevant content
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
I am developing a fleet management solution in my own back-end that interacts with the devices. But I found another solution where I can just fetch the file from s3 and publish the chunks to another non-reserved topic. Now I've run into the same problem with the
$aws/things/thingName/jobs/notifyand$aws/things/thingName/jobs/notify-nextreserved topics. I can only listen for those changes via MQTT on the device side which will prevent me from creating an IoT rule with those reserved topics as well. Any suggestions on what I should do to get around this limitation?I don't understand why your cloud application should need to subscribe to these topics. You must have some requirement that I'm not comprehending. Why would you fleet management solution not just use jobs and/or MQTT file streams as designed? Please elaborate.