RE: Thread GET response issue

Marjeris Romero — Fri, 26 Apr 2019 12:13:24 GMT

Hi Simon,

Sorry for the very delay response. I am quite new to the Thread SDK and needed some time to dig into it.

Firstly, I don't know if you are aware of but a new version of the Zigbee & Thread SDK has been released (v3.0.0). I strongly recommend switching to the new version.

I found some discrepancies between your code and the way request send and response send functions are implemented in the examples in our SDK.

In your thread_coap_TRYGET_request_send function you are calling otCoapHeaderSetPayloadMarker, this function adds a Payload Marker indicating the beginning of the payload. This is not necessary to do when doing sending a get request, as you are not appending any payload.

From RFC7252, page 16: " The presence of a marker followed by a zero-length payload MUST be processed as a message format error." So this why you are getting OT_ERROR_PARSE when no data was appended.

Then in the request response you want to send a payload, but you haven't set a payload marker before otMessageAppend and otCoapSendRequest. For SDK v3.0.0 you should add:

error = otCoapMessageSetPayloadMarker(p_response);
ASSERT(error == OT_ERROR_NONE);

think this two things should be able to fix your problem. Let me know how it goes.

Best Regards,

Marjeris

RE: Thread GET response issue

Marjeris Romero — Fri, 12 Apr 2019 14:28:45 GMT

Hi Simon,

Unfortunately we have reduce staffing during next week due to Easter holiday. We will try to answer as soon as possible, unless someone in the community are able to help you in the meantime 🙂

Best Regards,

Marjeris