No Answers
- Newest
- Most votes
- Most comments
Relevant content
- asked a year ago
- asked 3 years ago
- Accepted Answerasked 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
do you publish the value { "state": { "reported": { "vsr": 70931715605954314 } }} to the shadow update topic: $aws/things/yourdeviceuniqueid/shadow/name/update on the device towards IoT-Core? or are you writing the shadow from IoT-Core to be received by your device
@clogwog Along with the said vsr key there are certain other key value pair that are published by me on the said topic via mqtt protocol to the broker. (-) The value received on the AWS IoT -> Test client is similar (corrupted) to the one shown in device shadow. But the when i see the data in dynamo db the data is intact and is equivalent to the one sent from device. For pushing data to dynamoDb im using rule engine. (-) A unique device publishes only to its own topic. Most likely the issue seems to be large data type because i have seen a similar behaviour when publishing data from aws iot mqtt test client to the device shadow. What i dont know is how to fix this issue. Any suggestion is appreciated Regards, Altamash