RE: OpenThread CoAP example

Danny — Sat, 21 Oct 2017 17:45:55 GMT

Thanks Lukasz!, that totally solved it. Time to start adding some new resources!

RE: OpenThread CoAP example

Lukasz Duda — Sat, 21 Oct 2017 11:52:10 GMT

Hello Danny,

Thank you for trying out nRF5 SDK for Thread!

The particular example that you used (simple_coap_server) exposes only two resources:

/light
/provisioning

You received 4.04 responses (Not Found) for /light/light_on or /light/light_off resources since they do not exist.

Simple coap server controls its led using payload of PUT request on /light resource. Accepted payload is:

0 (Turn off the led)
1 (Turn on the led)
2 (Toggle the led)

Note that you can specify payload also in the copper plugin: Payload section -> Outgoing tab. The difficult part is that Cooper plugin allows only to send ASCII string. However the example expects binary 0, 1 or 2, not character '0' which is binary 48. So i believe the easiest solution to use cooper would be to change light_command_t enum in the main.c to:

typedef enum
{
    LIGHT_OFF = '0', // originally was 0, (0 is different than ASCII '0' - which is 48)
    LIGHT_ON,
    LIGHT_TOGGLE
} light_command_t;

Of course it is possible to add a new resources: /light/light_on and /light/light_off by modyfing SDK's example.

We will try to change expected commands value to accept also ASCII characters in upcoming releases to make Cooper plugin easier to use.