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
As an enhancement of #696 for the case that a device could not apply the "desiredProperties" state of a property to its actual state, the device shall send that "unable to apply desired state" information back to Ditto.
sync-state revision number of desired property information is "piggy backed" as part of a normal command as "put-metadata": {"key": "/desiredSyncRevision", "value": 42}
sync-state metadata information is "piggy backed" as part of a normal command as "put-metadata": {"key": "/desiredSyncState", "value": "applied"}
1st option: the desired change could be "applied"
2nd option: it is still trying to apply the desired state: "pending-application"
3rd option: it is impossible as the desired property is not processable "not-applicable"
in addition, e.g. for the 3rd option, a metadata "desiredSyncStateDetails" is optionally provided
As an enhancement of #696 for the case that a device could not apply the "desiredProperties" state of a property to its actual state, the device shall send that "unable to apply desired state" information back to Ditto.
"put-metadata": {"key": "/desiredSyncRevision", "value": 42}
"put-metadata": {"key": "/desiredSyncState", "value": "applied"}
"desiredSyncStateDetails"
is optionally provided_metadata
section introduced in Support for adding arbitrary _metadata for features / properties #680Implementation details
As suggested in #680 this sync-state metadata information is "piggy backed" as part of a normal command, e.g.:
The
_metadata
structure would look like:The text was updated successfully, but these errors were encountered: