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
For example on reading reqest from /3/0/1 URI the client returns the following payload:
{"bn":"/3/0/1/","e":[{"n":"1","sv":"00000"}]}
The client serialize the payload as multi instance resource while the resource is of type string.
seems that json_serialize function should set rootLevel to URI_DEPTH_RESOURCE_INSTANCE only if tlvP->type==LWM2M_TYPE_MULTIPLE_RESOURCE
The text was updated successfully, but these errors were encountered:
Fix problem serializing resource instance reads.
Fix handling of empty strings and opaque.
Fix JSON serializing single instance resource as multiple. Fixeseclipse-wakaama#378.
Fix JSON parsing of multiple instance resources. Fixeseclipse-wakaama#399.
Signed-off-by: Scott Bertin <sbertin@telular.com>
Fix problem serializing resource instance reads.
Fix handling of empty strings and opaque.
Fix JSON serializing single instance resource as multiple. Fixeseclipse-wakaama#378.
Fix JSON parsing of multiple instance resources. Fixeseclipse-wakaama#399.
Signed-off-by: Scott Bertin <sbertin@telular.com>
For example on reading reqest from /3/0/1 URI the client returns the following payload:
{"bn":"/3/0/1/","e":[{"n":"1","sv":"00000"}]}
The client serialize the payload as multi instance resource while the resource is of type string.
seems that json_serialize function should set rootLevel to URI_DEPTH_RESOURCE_INSTANCE only if tlvP->type==LWM2M_TYPE_MULTIPLE_RESOURCE
The text was updated successfully, but these errors were encountered: