Getting Thread+CoAP Google Cloud IoT Example working with Californium

[thread_yoda]

Didrik Rokhaug Continuing the discussion that was documented here: 

https://devzone.nordicsemi.com/f/nordic-q-a/64691/how-to-use-the-latest-version-of-californium

1) I modified the resources a bit to better reflect our use case. However, can you give some pointers on what's the proper use of the arguments for the nRF5 console java client? What I received from the cf-secure output is the following

19:45:32.504 INFO [MessageTracer]: DTLS([fe80:0:0:0:d832:d8c5:ecf5:6a8a%10]:5694,ID:A5AA854700) ==> req CON-PUT MID=29594, Token=3436423F656D00B0, OptionSet={"Uri-Path":["tempsensor","temp,"], "Content-Format":"text/plain"}, "30"
19:45:32.511 INFO [ServerMessageDeliverer]: did not find resource /tempsensor/temp, requested by /fe80:0:0:0:d832:d8c5:ecf5:6a8a%10:5694
19:45:32.516 INFO [MessageTracer]: DTLS([fe80:0:0:0:d832:d8c5:ecf5:6a8a%10]:5694,ID:A5AA854700) <== res ACK-4.04 MID=29594, Token=3436423F656D00B0, OptionSet={}, no payload

How do I use PUT and GET using Nrf5xConsoleClient?

PUT coaps://[fe80::d832:d8c5:ecf5:6a8a]:5684/tempsensor/temp, 30

Is this correct for PUT?

2) Can you give some pointers to get the Thread+CoAP Cloud IoT example in the nRF5 SDK for Thread working with Californium? Is it better to start with the github repo for the CoAP Proxy demo? But I think this was using an old version of Californium. Not sure how to reconcile the two.

Thanks!

[Didrik Rokhaug]

Hi,

 

How do I use PUT and GET using Nrf5xConsoleClient?

 You can run  the client without any arguments to get some documentation and examples on how it can be used.

Your suggestion is almost right, but the arguments are separated by a space, not a comma. So unless you try to put something to 'temp,', you should remove the comma.

 

2) Can you give some pointers to get the Thread+CoAP Cloud IoT example in the nRF5 SDK for Thread working with Californium?

 I haven't used Thread much myself, so I will need some time set this up and test myself.

Best regards,

Didrik

[thread_yoda]

Thanks for the pointers! I'll play with that and see how far I get and will keep you posted. 

I have another ticket describing my experience with the Thread+CoAP Cloud IoT example here if you're interested in getting some additional context: https://devzone.nordicsemi.com/f/nordic-q-a/62893/losing-connection-with-thread-coap-google-cloud-example

The CoAP proxy demo repo I was referring to that is leveraged by GCP is here: https://github.com/GoogleCloudPlatform/community/tree/master/tutorials/cloud-iot-coap-proxy

We are interested in the Californium technology but want to see how to deploy that in an Azure (or other public cloud) environment which is the genesis for this exercise.

[thread_yoda]

Ok thanks for the tips. After removing the comma PUT works like a champ and i was also able to verify GET works as well. Cool!

Now if we can figure out how to tie this in with the Thread+CoAP example this will be great.

[Marjeris Romero]

Hi thread_yoda,

Perhaps it would be easier to start with the Simple CoAP Client example: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v4.1.0%2Fthread_client_server_example.html&cp=7_3_2_10_4_2_2&anchor=thread_client_server_example_coap-server

You will then need to implement a similar functionality the as thread_coap_utils_unicast_light_request_send function, but entering the correct address and URI paths for your Colifornium server.

BR,

Marjeris

[thread_yoda]

Hi Marjeris, thanks for your reply but I am not sure this is the correct place to start since it is a different paradigm from the simple coap client + server model. I want to POST updates which is going to cause a resource to be created on the Californium side I believe. This is how it is supposed to work with the Thread+CoAP Google IoT example. Please advise.