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
Currently for single resource request, the client can encode the data using TLV if the CoAP GET message content type is application/vnd.oma.lwm2m+tlv. If there is no content type specified, the client uses plain text by default.
On the server-side, the API does not allow to specify the content-type. I'll rework this part.
The recent versions of the spec say now TLV can be used for single resources.
(There is a PR in Leshan which implements this)
The text was updated successfully, but these errors were encountered: