How to use aws-iot-device-client to read/write to the Classic Shadow #345
Replies: 2 comments 4 replies
-
|
We have a sample of using a classic shadow in the v1 to v2 migration guide: # Update Shadow
def customShadowCallback_Update(payload, responseStatus, token):
return
JSONPayload = '{"state":{"desired":{"property":' + str(3) + '}}}'
deviceShadowHandler.shadowUpdate(
JSONPayload,
customShadowCallback_Update,
5) |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, but can we use the classic shadow with the aws-iot-device-client? |
Beta Was this translation helpful? Give feedback.
-
|
We've been able to write to the classic shadow using the v1 Python SDK, but we'd like to do it using aws-iot-device-client instead |
Beta Was this translation helpful? Give feedback.
-
|
Does @bretambrose answer work for you? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately we lack the ability to compile the source code right now for our embedded linux platform, so we're limited to just using the aws-iot-device-client binary. |
Beta Was this translation helpful? Give feedback.
-
|
The device client is in C++ and uses the v2 C++ SDK. So you should be able to put something together using https://github.com/aws/aws-iot-device-sdk-cpp-v2/tree/main/samples/shadow/shadow_sync |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there!
Does anyone know if its possible to read/write to the Classic Shadow (Default one) using aws-iot-device-client?
I've been able to connect to other named shadows, but for some reason I can't use the Classic Shadow.
I tried setting the shadow-name parameter to "Classic Shadow", but that didn't seem to work. I also left it blank, but then the client would error and say that I needed to provide a value.
Beta Was this translation helpful? Give feedback.
All reactions