Testing OpenThread COAP Server and COAP Client

RE: Testing OpenThread COAP Server and COAP Client

Amanda Hsieh — Thu, 12 Dec 2024 14:09:01 GMT

Hi,

Swathy is out of the office, so I picked up this case.

The mentioned tools is not developed and provided by us, Nordicsemic. Please open an issue in the OTBR/libcoap repository.

Amanda H.

RE: Testing OpenThread COAP Server and COAP Client

gabilm — Thu, 05 Dec 2024 16:39:21 GMT

Hi.

I have tested it form the coap client (another nrf52840dk node) and it works (note that the OpenThread COAP Client example doesn't include the CONFIG_OPENTHREAD_COAP directive in order to allow ot coap in the node, you have to enable it and to run "ot coap start" on the node before the test).

However, I still can not connect from the host. I have ping from the host, but trying the examples:

coap-client-gnutls coap://[fd11:22:0:0:0:0:0:100]/provisioning

coap-client-gnutils -m put -N -e "2" coap://[fd11:22:0:0:0:0:0:100]/light

I get a timeout.

Any idea?

Thanks in advance.

RE: Testing OpenThread COAP Server and COAP Client

SwRa — Thu, 05 Dec 2024 13:37:51 GMT

Hi Gabriel,

You can send GET only to "provisioning" resource when server is in provisioning state (button4). You can also send PUT to "light" resource to trigger LED.
For example after attaching with coap server and other OT CLI device, get IP addres from coap server and press button 4.
when LED3 is blinking, on other device send:

uart:~$ ot coap get fdde:ad00:beef:0:4632:8245:46a9:8af8 provisioning
Done
coap response from fdde:ad00:beef:0:4632:8245:46a9:8af8 with payload:
fddead00beef00004632824546a98af8

And to toggle LED4, from the other device, send:

ot coap put fdde:ad00:beef:0:28cd:59c5:d0a3:66bd light non-con 2

where "2" is toggle command. see: https://github.com/nrfconnect/sdk-nrf/blob/main/samples/openthread/coap_server/interface/coap_server_client_interface.h

Regards,

Swathy