[Fiware-lab-help] OMA LWM2M IoT Agent questions

[Danijel Hodzic]

Greetings,

Hello, and let me first introduce myself.
I'm Danijel Hodzic that has recently become FIWARE Lab user.
My startup team is called Smaczygote and we are invited to present our
proposal and demo application at ICT 2015 from 20 to 22nd October, as part
of the FRACTALS Smart Urban Farming Challenge.

As we have little experience with FIWARE platform usage at the moment, we
would like to get some advise and guidelines for decisions that we have to
make, because we have no much more time.

*The Problem:*
We want to connect some cc2538 contiki motes with Fiware. Up to now we have:
  - instantiate VM based on *orion-psb-image-R4.2* in our project, and
Orion Context Broker is up and running
  - run our CoAP example on devices and tested visibility of our resources
with Firefox Copper CU user-agent.

Now we are interested in simplest way for creating of IoT Agent and
configuration of it northbound and southbound interfaces.
As we understood there is already OMA Lightweighted M2M IoT agent, and it
is functioning as LWM2M Server and it can be easily configured to
communicate with context broker.

*Q1*: Is it good idea to deploy* lightweightedm2m-iotagent* from github to
the same VM where *orion cb* is resided ?
*Q2*: Is there example or concrete exercise where we can see how to
assembly *lightweightedm2m-iotagent *and *orion cb *connection ?
*Q3*: Regarding southbound interface, we have to implement LWM2M Client on
top of CoAP. Is it true that, in order to enable this LWM2M client-server
communication we have firstly to provide ipv6/ipv4 tunneling for our
boarder-router connected to laptop to be able to communicate with our
orion/iotagent VM with IPv4 public address ?
*Q4*: Is there any exercises link about CoAP/OMA LWM2M configuration and
southbound  API usage examples ?

Thank you,
Best regards,
M.S.E.E. Danijel Hodzic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20151012/0355f43a/attachment.html>