- Newest
- Most votes
- Most comments
Subscribe to $aws/things/my_thing/shadow/update/documents
topic to get the full content of the shadow.
- https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-mqtt.html#update-documents-pub-sub-topic
- https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-document.html#device-shadow-example-response-json-documents
As you are using Amazon Timestream to store the values, you can achieve the same outcome without using thing shadows and thus reduce the overall solution cost. Amazon Timestream provides interpolation and binning functions that allows you to only send the data that changes and to reconstruct the other values as needed. For example using the interpolate_locf
function you can obtain the last stored value of a given property. See https://docs.aws.amazon.com/timestream/latest/developerguide/timeseries-specific-constructs.functions.interpolation.html
If the latter option satisfies your requirements, you can further reduce the ingestion costs by using Basic Ingest
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
Awesome thanks! It looks my shadow document has a lot of old unused tags in it that come through with each update even though I'm not pushing them out from my device, is it possible to delete these?
Hi JSap. You can delete the shadow (between updates) or delete the specific properties: https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-data-flow.html#deleting-thing-data. As a side point, if the values don't change very often, it may not be very cost-effective to publish to the shadow every 10s.