simple coap sample to send data to the nrf cloud

[Lorenzo Amicucci]

Hi

the UDP sample is a very nice example for testing LTE Cat M and NB IoT power saving features and RAI, however, it does not show data to any cloud and it does not wait for the ACK,

Now that nRF Cloud with coap has been released, is it possible to have a simple coap sample (similar to our upd sample) that send some simple data (similar to the payload we send on the upd sample) and we can see this in the cloud (at least in the terminal interface)? 

It should be easy to optionally enable at least
PSM - and change the timers

eDRX- and change the timers 

RAI

periodic upload: how often it should send data --> timer should be easily configurable (I guess it can be selected on the device?)

push button --> to send data 

CID should be default enabled.

Device should send the data, wait for ack (coap) and then go back to sleep. 

Is there any sample available that implements this?

Thanks

Lorenzo

[Lorenzo Amicucci]

Doing more research:
does this https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/cellular/coap_client/README.html 
or this https://academy.nordicsemi.com/courses/cellular-iot-fundamentals/lessons/lesson-5-cellular-fundamentals/topic/lesson-5-exercise-1/ can be used? Do they support all features above, including CID? 
Californium CoAP server - Eclipse Californium - is very good and support CID , but I would like a more portable GUI, that I can show on smartphone or anywhere else

[Achim Kraus]

If you curious to test CoAP/DTLS 1.2 CID, I prepared a demo for that.

Zephyr coaps client

There is also a CoAP-S3-Proxy , which comes with a JavaScript SPA.

I'm still working on that, but also still hope to include it in Eclipse/Californium until the end of year.

Mid of October is the EclipseCon 2023. Before that I'm a little over busy, After that I will add IoTerop, Golioth and the Nordic Service as destination to that Zephyr Coaps Client. But it will take some time.

[Achim Kraus]

Just as short cut:

If you want to stick to the example in lesson-5, you need just to enable CID:

main.c/client_init:

    int err;
    /* STEP 6.1 - Create a DTLS socket */
    sock = socket(AF_INET, SOCK_DGRAM, IPPROTO_DTLS_1_2);
    if (sock < 0) {
        LOG_ERR("Failed to create CoAP socket: %d.\n", errno);
        return -errno;
    }

//    int cid = NRF_SO_SEC_DTLS_CID_SUPPORTED;
    int cid = NRF_SO_SEC_DTLS_CID_ENABLED;
    err = setsockopt(sock, SOL_TLS, TLS_DTLS_CID, &cid, sizeof(cid));
    if (err) {
        LOG_ERR("Failed to setup socket security DTLS CID supported, errno %d (%s)\n", errno, strerror(errno));
        return -errno;    
    }

NRF_SO_SEC_DTLS_CID_SUPPORTED means, the client doesn't use CID, but supports it, if the server uses it (that's the very common case, where the server doesn't change it's address, but the client maybe.)

NRF_SO_SEC_DTLS_CID_ENABLED means, the client uses CID, and supports also, if the server uses it.

Pretty easy. If that runs for longer is left to your experience. If you want to use e.g. a Thingy:91 to demonstrate, that it sends the "weather data" every hour for a couple of months from battery, I guess my demo may be smoother.

[Lorenzo Amicucci]

Thanks! I will check. I am thinking to something simple where it is easy to change network parameter requests. 
I will study these options

[Amanda Hsieh]

Hi, 

Here is the PR https://github.com/nrfconnect/sdk-nrf/pull/12492

The nrf_cloud_multi_service sample has a new overlay overlay_min_coap.conf that will hopefully meet your request.

Regards,
Amanda H.