I encountered an issue where the client SEND operation does not use the existing fragmentation logic implemented for server WRITE operation. This results in the creation of oversized CoAP packet when large payloads are sent, which the server then rejects due to exceeding the maximum packet size limit.
Steps to Reproduce
Start the server and example client.
Add a new resource that exceeds the 2048 byte limit.
Attempt to send the resource from the client using the SEND method (lwm2m_send).
Observe that the payload is not fragmented and is sent in a single large CoAP packet.
Expected Behavior
The client SEND operation should fragment large payloads into multiple CoAP packets, similar to how the server-side WRITE operation handles them.
Possible Fix
The issue can be resolved by utilizing the _transaction_setpayload method in the _lwm2msend method, similar to its usage in the server WRITE operation, instead of the currently used _coap_setpayload.
Description
I encountered an issue where the client SEND operation does not use the existing fragmentation logic implemented for server WRITE operation. This results in the creation of oversized CoAP packet when large payloads are sent, which the server then rejects due to exceeding the maximum packet size limit.
Steps to Reproduce
Expected Behavior
The client SEND operation should fragment large payloads into multiple CoAP packets, similar to how the server-side WRITE operation handles them.
Possible Fix
The issue can be resolved by utilizing the _transaction_setpayload method in the _lwm2msend method, similar to its usage in the server WRITE operation, instead of the currently used _coap_setpayload.