You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 15, 2023. It is now read-only.
Currently, client is using /update/delta to sync "reported" and "desired" document.
However, in case, a property of desired document become null, there is no message send to /update/delta.
Could you guide me how the client know a property of desired document become null?
Thanks,
The text was updated successfully, but these errors were encountered:
Thanks for the question. Your understanding is correct. When the desired value is set to null, both the reported and desired fields change to null and the values should appear in the /updated/documents and /updated/accepted topics. Another suggestion to observe these changes would be to subscribe to the topic /update/# in the MQTT client. Using the wildcard would help observe the shadow behavior more clearly as updates to any of these topics would show up in the test client. An example of this use case is described in this document: https://docs.aws.amazon.com/iot/latest/developerguide/interact-lights-device-shadows.html
Hi AWS team,
Currently, client is using /update/delta to sync "reported" and "desired" document.
However, in case, a property of desired document become null, there is no message send to /update/delta.
Could you guide me how the client know a property of desired document become null?
Thanks,
The text was updated successfully, but these errors were encountered: