aws-iot-device-sdk-js | AWS IoT from a device using JavaScript | SDK library

Wasn't able to identify why I couldn't use AwsCredentialsProvider as expected but found a work-around. Instead, I was able to initialize the builder with const config_builder = iot.AwsIotMqttConnectionConfigBuilder.new_with_websockets();. Anyway, didn't figure out why I couldn't utilize AwsCredentialsProvider as expected. Might be something to look into if the dev team has time. 👍

I received an answer in aws-iot-device-sdk-js-v2 repository from jmklix that solved my problem:

Currently, the maintainers of the package don't include the pre-compiled binaries for raspberry pi, but we can do this manually if we want. described in aws-crt-nodejs:

yes you can't able to subscribe dynamic topic you have to change the policy "arn:aws:iot:ap-south-1:453533943651:topic/${iot:Connection.Thing.ThingName}/*" to *..for allow all device.then you can subscribe.topic/${iot:Connection.Thing.ThingName} this denotes the thingname should be come end of the topic. change to allow all you will able to subscribe.

Debugging the Shadow Update

You can subscribe to the reserved topic $aws/things/+/shadow/# to debug the problem.

This shows a 400 error and a message.

Fixing the Update Payload

The error message is:

"message": "Missing required node: state"

This is visible in the stringified update payload. But the stateObject parameter that is passed to thingShadow.update() should be an object and not a string.

So remove the JSON.stringify from: