Thank you for your comment. I really appreciate the things that your
are trying to do and put together in your project.
There are two mechanisms to integrate legacy devices into OM2M.
Case 1) HTTP or CoAP enabled devices.
Let's suppose that you have a HTTP-enabled plug device with IP
address 192.168.0.4 and listening port 9090.
You can monitor and control this plug using this two specific HTTP
Since, by default OM2M offers the HTTP binding, then you can create
an application resource called MY_DEVICE containing
"http://192.168.0.4:9090" as specific Application Point of Contact
HTTP request example:
That's all. Now when you send a HTTP GET request to the GSCL with
this URI "127.0.0.1:8080/om2m/gscl/applications/MY_DEVICE/state",
the GSCL will automatically translate it to
http://192.168.0.4:9090/state based on the information stored on the
Then, the HTTP request is re-targeted to your plug device, and the
HTTP response is returned to you.
If you send a HTTP POST request with empty body to the GSCL with
this URI "127.0.0.1:8080/om2m/gscl/applications/MY_DEVICE/toggle",
it will be automatically translated to
http://192.168.0.4:9090/toggle and re-targeted to your device to
In addition, you can create an oBIX XML description for the
MY_DEVICE application within a specific container to advertise your
device operations and simplify their discovery.
Let's suppose that the "DESCRIPTOR" container is already created in
this URL: /gscl/applications/MY_DEVICE/containers/DESCRIPTIOR
HTTP request example:
<str name="type" val="xxxx"/>
<str name="location" val="yyyy"/>
<op name="get" href=""
<op name="toggle" href=""
If you check the created contentInstance on the OM2M web interface,
you will find the device attributes and nice buttons that you can
use to monitor and control your device.
You can use also use "create" (is="create") and delete
(is="delete") operations if needed.
Since OM2M implements the CoAP communication binding, CoAP-enabled
devices can be integrated using the same approach explained for
Case 2) Other legacy devices
To integrate IP-enabled devices speaking other protocols like MQTT
or non IP-enabled devices like Zigbee, you need to create a specific
Interworking Proxy Unit (IPU) plugin to make the required mapping.
You can check the following developer guide
https://wiki.eclipse.org/OM2M/Developer to learn how to add a new
plugin to OM2M and implement you own IPU.
Hope this can help,
Le 09/02/2015 22:41, Massimo Vecchio a
first let me take this opportunity to thank the developers team
for this really amazing project!!!
I could build the project from maven flawlessly (and this is
already a personal success for me, not being so smart at pure s/w
side). The merit goes to the crystal clear wiki documentation!
Then the big question mark that is floating in my head...
Imagine that I decide to migrate all my little vertical apps
developed in the last couple of years. Such apps involve sensors
and microcontrollers (mostly arduino-like): in the end little bits
and things which normally are not IP-based but can communicate via
short range communication techs (like bluetooth, nrf, xrf, srf,
etc etc). Normally data reach my gateway (let's be short...a
raspberry pi) which through a dev. framework like node-red can end
up on the internet...
Now, my question is: how can I "port" my current h/w&s/w mix
into om2m? what are the (ideal) sequential steps to follow? is it
worth (apparently yes to me....that's why I started getting
involved in this challenge...)? any advice from anyone that
already tried this out?
om2m-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit