*Developer guide on Remote light control
http://www.onem2m.org/application-developer-guide/use-case

*Hackster oneM2M project page
https://www.hackster.io/onem2m/onem2m-demo-57022e

*Hardware nodeMCU kit
The device kit that you will use during the event (and that you will get to keep):
https://www.amazon.com/OSOYOO-Programming-Learning-Developmen-Tutorial/dp/B073Z84243/ref=redir_mobile_desktop?_encoding=UTF8&keywords=nodemcu%20kit&pi=AC_SX236_SY340_FMwebp_QL65&qid=1516921167&ref_=mp_s_a_1_2&sr=8-2

*Open Source OM2M implementing oneM2M CSE
**http://www.eclipse.org/om2m/
** https://wiki.eclipse.org/OM2M/one

*onem2mlib by Andreas Kraft
This Python3 module implements a library to access and manage resources on a oneM2M CSE.

https://github.com/ankraft/onem2mlib

Interesting links

2018-03-09T15:10:15Z

Velez:

Interesting links

2018-03-09T15:09:10Z

Velez:

*Developer guide on Remote light control
http://www.onem2m.org/application-developer-guide/use-case

*Hackster oneM2M project page
https://www.hackster.io/onem2m/onem2m-demo-57022e

*Hardware nodeMCU kit
The device kit that you will use during the event (and that you will get to keep):
https://www.amazon.com/OSOYOO-Programming-Learning-Developmen-Tutorial/dp/B073Z84243/ref=redir_mobile_desktop?_encoding=UTF8&keywords=nodemcu%20kit&pi=AC_SX236_SY340_FMwebp_QL65&qid=1516921167&ref_=mp_s_a_1_2&sr=8-2

*Open Source OM2M implementing oneM2M CSE
http://www.eclipse.org/om2m/
https://wiki.eclipse.org/OM2M/one

*onem2mlib by Andreas Kraft
This Python3 module implements a library to access and manage resources on a oneM2M CSE.
https://github.com/ankraft/onem2mlib

Rules of Conduct

2018-03-09T15:01:35Z

Velez:

Hackathon
Code of Conduct: We expect all participants to abide by the below Code of Conduct.

[[MEDIA:OneM2M_Hackathon_-_Code_of_Conduct_6Mar18.pdf ‎| OneM2M_Hackathon_-_Code_of_Conduct_6Mar18.pdf ‎]]

Rules of Conduct

2018-03-09T14:59:08Z

MediaWiki:Sidebar

2018-03-09T14:44:09Z

Velez:

* navigation
** Event Information|Event Information
** Device kit example|Device kit example
#** Support team|Support team
** Interesting links|Interesting links

* SEARCH
* TOOLBOX
* LANGUAGES

2018-03-02T12:28:54Z

Velez: Velez uploaded a new version of File:Map.PNG

Event Information

2018-03-02T12:27:00Z

Velez: /* Venue */

__TOC__

== Venue ==

9-10 March 2018
The University of Texas at Dallas
T1 Auditorium
800 W Campbell Rd
Richardson, TX 75080

[[File:Map.PNG]]

== Abstract ==

The tutorial will present the IoT vision, challenges, and efforts achieved by the standardization bodies to design a globally agreed IoT service platform. The oneM2M standard (www.onem2m.org) will be introduced as a promising solution for IoT cross-domain interoperability. The participants will be asked to follow practical sessions to learn how to quickly integrate heterogeneous IoT devices and develop IoT applications based on the open source project Eclipse OM2M (www.eclipse.org/om2m).

oneM2M standard
Today, sensors, actuators, tags, vehicles, and intelligent things all have the ability to communicate. The number of IoT devices is continuously increasing, and it has been predicted to see billions of connected objects interconnected in the near future. IoT applications provide advantages in various domains from smart cities, factories of the future, connected cars, home automation, e-health to precision agriculture. This fast-growing ecosystem is leading IoT towards a promising future. However, IoT market expansion opportunities are not straightforward. A set of challenges should be overcome to enable IoT mass-scale deployment across various industries including interoperability, complexity, and scalability issues.

Currently, the IoT market is suffering from vertical fragmentation affecting the majority of business sectors. In fact, various vendor-specific IoT solutions have been designed independently for specific applications, which has led to serious interoperability issues. To address this challenge, the eight most important telecom SDOs in the world established a global partnership project called oneM2M. oneM2M provides a common architecture for IoT cross-domain interoperability in terms of communication and semantic data.

== Eclipse OM2M open source project ==
Eclipse OM2M offers a full open source implementation of the oneM2M standard. It supports all types of interfaces and nodes defined in the standard including “Infrastructure Node”, “Middle Node”, “Application Service Node” and “Application Dedicated Node”. Each node may host a set of applications and a Common Service Entity including capabilities for communication protocol bindings, device interworking, management, security, etc. Eclipse OM2M relies on a modular architecture, designed on top of a protocol-independent kernel, running on top of an OSGi layer and is highly extensible via plugins which make a promising candidate for integration and experimentation.
http://www.eclipse.org/om2m/

== Target audience ==
The audience targeted by this tutorial includes software architects and developers as well as academic and industrial researchers, and PhD students who can benefit from the different parts of the tutorial including the theoretical as well as the technical aspects related to IoT standards.

== Outline of the tutorial ==

The tutorial will be structured in two main parts. In the first part, we will develop the foundations and the technical background that will be useful for the attendees for getting started with the oneM2M common architecture’s main concepts, features and interfaces. In the second part, we will conduct the technical learning part. This will consist of interactive training that will address the different issues necessary for developers. This includes understanding and manipulating the oneM2M API for developing applications and integrating devices on top of the Eclipse OM2M platform.

'''The structure of the tutorial is the following:'''

* Technical Presentations
** IoT, Vision and Challenges
** oneM2M Common Architecture for IoT
** Eclipse OM2M, Open Source oneM2M-based Platform

* Demonstrations and API manipulations
** Hands-on oneM2M, development of your IoT Applications
** Interworking with legacy and vendor-specific technologies
** Towards Semantic IoT, oneM2M Base Ontology

== Hackathon Agenda ==

* Day #1 (9 March 2018) - presentations; tutorials; hackathon rules
**Friday morning
***Introductions
***IoT, Vision and Challenges
***Tutorial on oneM2M
****oneM2M Common Architecture for IoT
****Open source (Eclipse OM2M) introduction
****Example of projects using HW provided
**Friday afternoon
***Form teams
***Per team, select one of the challenges to be solved. The solution must use the oneM2M architecture.
***Additional requirements may be specified.
****Each project to use the HW provided.
****Requirement to use the oneM2M service platform.
****Application to be created for PC, web or mobile (IOS, Android).
***The teams develop their projects on Friday evening after dinner until 21:00.

* Day #2 (10 March 2018) - hackathon team work; awards and certificates
**Saturday morning
***The teams develop and finalize their projects.
**Saturday afternoon
***Presentation of each project
***Projects are reviewed by the jury during coffee break
***Awards

Event Information

2018-03-02T12:26:32Z

Velez: /* Venue */

__TOC__

== Venue ==

9-10 March 2018
The University of Texas at Dallas
T1 Auditorium
800 W Campbell Rd
Richardson, TX 75080

[[File:Map.png]]

== Abstract ==

The tutorial will present the IoT vision, challenges, and efforts achieved by the standardization bodies to design a globally agreed IoT service platform. The oneM2M standard (www.onem2m.org) will be introduced as a promising solution for IoT cross-domain interoperability. The participants will be asked to follow practical sessions to learn how to quickly integrate heterogeneous IoT devices and develop IoT applications based on the open source project Eclipse OM2M (www.eclipse.org/om2m).

oneM2M standard
Today, sensors, actuators, tags, vehicles, and intelligent things all have the ability to communicate. The number of IoT devices is continuously increasing, and it has been predicted to see billions of connected objects interconnected in the near future. IoT applications provide advantages in various domains from smart cities, factories of the future, connected cars, home automation, e-health to precision agriculture. This fast-growing ecosystem is leading IoT towards a promising future. However, IoT market expansion opportunities are not straightforward. A set of challenges should be overcome to enable IoT mass-scale deployment across various industries including interoperability, complexity, and scalability issues.

Currently, the IoT market is suffering from vertical fragmentation affecting the majority of business sectors. In fact, various vendor-specific IoT solutions have been designed independently for specific applications, which has led to serious interoperability issues. To address this challenge, the eight most important telecom SDOs in the world established a global partnership project called oneM2M. oneM2M provides a common architecture for IoT cross-domain interoperability in terms of communication and semantic data.

== Eclipse OM2M open source project ==
Eclipse OM2M offers a full open source implementation of the oneM2M standard. It supports all types of interfaces and nodes defined in the standard including “Infrastructure Node”, “Middle Node”, “Application Service Node” and “Application Dedicated Node”. Each node may host a set of applications and a Common Service Entity including capabilities for communication protocol bindings, device interworking, management, security, etc. Eclipse OM2M relies on a modular architecture, designed on top of a protocol-independent kernel, running on top of an OSGi layer and is highly extensible via plugins which make a promising candidate for integration and experimentation.
http://www.eclipse.org/om2m/

== Target audience ==
The audience targeted by this tutorial includes software architects and developers as well as academic and industrial researchers, and PhD students who can benefit from the different parts of the tutorial including the theoretical as well as the technical aspects related to IoT standards.

== Outline of the tutorial ==

The tutorial will be structured in two main parts. In the first part, we will develop the foundations and the technical background that will be useful for the attendees for getting started with the oneM2M common architecture’s main concepts, features and interfaces. In the second part, we will conduct the technical learning part. This will consist of interactive training that will address the different issues necessary for developers. This includes understanding and manipulating the oneM2M API for developing applications and integrating devices on top of the Eclipse OM2M platform.

'''The structure of the tutorial is the following:'''

* Technical Presentations
** IoT, Vision and Challenges
** oneM2M Common Architecture for IoT
** Eclipse OM2M, Open Source oneM2M-based Platform

* Demonstrations and API manipulations
** Hands-on oneM2M, development of your IoT Applications
** Interworking with legacy and vendor-specific technologies
** Towards Semantic IoT, oneM2M Base Ontology

== Hackathon Agenda ==

* Day #1 (9 March 2018) - presentations; tutorials; hackathon rules
**Friday morning
***Introductions
***IoT, Vision and Challenges
***Tutorial on oneM2M
****oneM2M Common Architecture for IoT
****Open source (Eclipse OM2M) introduction
****Example of projects using HW provided
**Friday afternoon
***Form teams
***Per team, select one of the challenges to be solved. The solution must use the oneM2M architecture.
***Additional requirements may be specified.
****Each project to use the HW provided.
****Requirement to use the oneM2M service platform.
****Application to be created for PC, web or mobile (IOS, Android).
***The teams develop their projects on Friday evening after dinner until 21:00.

* Day #2 (10 March 2018) - hackathon team work; awards and certificates
**Saturday morning
***The teams develop and finalize their projects.
**Saturday afternoon
***Presentation of each project
***Projects are reviewed by the jury during coffee break
***Awards

Event Information

2018-03-02T12:26:21Z

Velez: /* Venue */

__TOC__

== Venue ==

9-10 March 2018
The University of Texas at Dallas
T1 Auditorium
800 W Campbell Rd
Richardson, TX 75080

[[File:Map.png

== Abstract ==

The tutorial will present the IoT vision, challenges, and efforts achieved by the standardization bodies to design a globally agreed IoT service platform. The oneM2M standard (www.onem2m.org) will be introduced as a promising solution for IoT cross-domain interoperability. The participants will be asked to follow practical sessions to learn how to quickly integrate heterogeneous IoT devices and develop IoT applications based on the open source project Eclipse OM2M (www.eclipse.org/om2m).

oneM2M standard
Today, sensors, actuators, tags, vehicles, and intelligent things all have the ability to communicate. The number of IoT devices is continuously increasing, and it has been predicted to see billions of connected objects interconnected in the near future. IoT applications provide advantages in various domains from smart cities, factories of the future, connected cars, home automation, e-health to precision agriculture. This fast-growing ecosystem is leading IoT towards a promising future. However, IoT market expansion opportunities are not straightforward. A set of challenges should be overcome to enable IoT mass-scale deployment across various industries including interoperability, complexity, and scalability issues.

Currently, the IoT market is suffering from vertical fragmentation affecting the majority of business sectors. In fact, various vendor-specific IoT solutions have been designed independently for specific applications, which has led to serious interoperability issues. To address this challenge, the eight most important telecom SDOs in the world established a global partnership project called oneM2M. oneM2M provides a common architecture for IoT cross-domain interoperability in terms of communication and semantic data.

== Eclipse OM2M open source project ==
Eclipse OM2M offers a full open source implementation of the oneM2M standard. It supports all types of interfaces and nodes defined in the standard including “Infrastructure Node”, “Middle Node”, “Application Service Node” and “Application Dedicated Node”. Each node may host a set of applications and a Common Service Entity including capabilities for communication protocol bindings, device interworking, management, security, etc. Eclipse OM2M relies on a modular architecture, designed on top of a protocol-independent kernel, running on top of an OSGi layer and is highly extensible via plugins which make a promising candidate for integration and experimentation.
http://www.eclipse.org/om2m/

== Target audience ==
The audience targeted by this tutorial includes software architects and developers as well as academic and industrial researchers, and PhD students who can benefit from the different parts of the tutorial including the theoretical as well as the technical aspects related to IoT standards.

== Outline of the tutorial ==

The tutorial will be structured in two main parts. In the first part, we will develop the foundations and the technical background that will be useful for the attendees for getting started with the oneM2M common architecture’s main concepts, features and interfaces. In the second part, we will conduct the technical learning part. This will consist of interactive training that will address the different issues necessary for developers. This includes understanding and manipulating the oneM2M API for developing applications and integrating devices on top of the Eclipse OM2M platform.

'''The structure of the tutorial is the following:'''

* Technical Presentations
** IoT, Vision and Challenges
** oneM2M Common Architecture for IoT
** Eclipse OM2M, Open Source oneM2M-based Platform

* Demonstrations and API manipulations
** Hands-on oneM2M, development of your IoT Applications
** Interworking with legacy and vendor-specific technologies
** Towards Semantic IoT, oneM2M Base Ontology

== Hackathon Agenda ==

* Day #1 (9 March 2018) - presentations; tutorials; hackathon rules
**Friday morning
***Introductions
***IoT, Vision and Challenges
***Tutorial on oneM2M
****oneM2M Common Architecture for IoT
****Open source (Eclipse OM2M) introduction
****Example of projects using HW provided
**Friday afternoon
***Form teams
***Per team, select one of the challenges to be solved. The solution must use the oneM2M architecture.
***Additional requirements may be specified.
****Each project to use the HW provided.
****Requirement to use the oneM2M service platform.
****Application to be created for PC, web or mobile (IOS, Android).
***The teams develop their projects on Friday evening after dinner until 21:00.

* Day #2 (10 March 2018) - hackathon team work; awards and certificates
**Saturday morning
***The teams develop and finalize their projects.
**Saturday afternoon
***Presentation of each project
***Projects are reviewed by the jury during coffee break
***Awards

File:Map.PNG

2018-03-02T12:25:34Z

Velez:

Main Page

2018-03-02T12:03:53Z

Velez:

Device Kit example

2018-03-02T12:03:17Z

2018-03-02T11:56:21Z

Velez:

<div class="noautonum">__TOC__</div>

== Demonstration high level architecture ==

[[File:Diagram.png]]

== 1.Prerequisites ==
The following tools are required to run this demonstration.
*JAVA 1.8
*Arduino IDE 1.8.5
*NodeJS

== Download the project ==

Download the oneM2M demo project from Github from the following link:

https://github.com/mbenalaya

The project contains the following folders:
*onem2m-platform
*onem2m-device
*onem2m-app

== Start oneM2M platform instance==
__TOC__
The oneM2M platform is available on folder “oneM2M Platform”

===Configure the platform===
You can keep the default configuration for a local demonstration. The platform will listen on ports 8080 and 8443. The database is reset after each restart.

If needed, you can change the configuration of the platform by editing the file “configuration/config.ini”.

===Start the platform===
Start the platform by executing the "start.bat" script on Windows or "start.sh" on Linux and Mac OS.

[[File:Console.png]]

===Login to oneM2M web interface===
Open the following URL in your browser to access the oneM2M platform web interface:
https://127.0.0.1:8080/webpage

[[File:Login.png]]

Enter "Cae-admin" as originator then click on “connect”.

[[File:Resource-tree.png]]

==Connect your IoT Device==
The arduino source code and required libraries are available on the folder onem2m-device.

===Schematics===
*Breadboard
*Nodemcu board
*LED
*Luminosity Sensor
*1Kohm resistance

Connect the LED and luminosity sensor to the Nodemcu board using:

[[File:Board-plan.png]]

Real wiring:

[[File:Real-wiring.jpg]]

===Download and install arduino IDE===
Download and install the Arduino IDE v1.8.5 from the following link:
https://www.arduino.cc/en/Main/Software

NB: We don’t recommend to use the Arduino Web Editor for this demonstration because the nodemcu board is not supported.

===Add Nodemcu board to Arduino IDE===

Firstly open the Arduino IDE
Go to files and click on the preference in the Arduino IDE

[[File:Arduino-ide.png]]

copy the below code in the Additional boards Manager

http://arduino.esp8266.com/stable/package_esp8266com_index.json

click OK to close the preference Tab.

After completing the above steps , go to Tools and board, and then select board Manager

[[File:Arduino-ide2.png]]

Navigate to esp8266 by esp8266 community and install the software for Arduino.

[[File:Arduino-ide3.png]]

Once all the above process been completed you are ready to program the nodemcu board with Arduino IDE.

===Add Arduino “Timer.h” library===

The “Timer.h” library is available on the zip folder “Timer-master.zip”.

Go to Sketch, and then select “include library”.
Chose the “Add .ZIP library” option

[[File:Arduino-ide4.png]]

Select the zip folder “Timer-master.zip” then confirm.
NB: You don’t have to extract the zip content.

===Configure the oneM2M sketch===
Open the sketch “onem2m-adn.ino” in your Arduino IDE.

Set your WIFI parameters
*const char* ssid = "XXXXXXXX";
*const char* password = "XXXXXXXX";

Set the IP address of the oneM2M platform
*const char* host = "XXXXXXXX";

===Compile the oneM2M sketch===

Click on verify button [[File:Button1.png]] to compile the sketch.

Compilation output:

[[File:Compiliation.png]]

===Upload the oneM2M sketch to Nodemcu board.===

Click on upload button [[File:Button2.png]] to upload the sketch to the nodemcu board .

Upload output:

[[File:Compiliation2.png]]

===Debug the code execution using serial monitor===

Cick on [[File:Button3.png]] button to open the Arduino Serial Monitor to display the Nodemcu console.

Then after opening the Serial Monitor select 115200 from the drop-down list.

[[File:Monitor.png]]

===Check IoT device resources on oneM2M web interface===
You should see “mydevice1” Application Entity resource with “luminosity” an “led” containers created on the oneM2M resource tree.

[[File:Resource-tree2.png]]

==Connect your IoT application==
The luminosity monitoring application source code is available on the folder onem2m-app

===Configure application===
Open the file onem2m-monitor.js with a text editor.

Set the IP address of the oneM2M platform. You can keep localhost if you are running the oneM2M platform and the application in the same machine.

===Start the application===

Start the nodejs oneM2M application using the following command:
> node onem2m-monitor.js

[[File:Console2.png]]

===Check IoT application resource on oneM2M web interface===

You should see “mymonitor1” Application Entity resource created on the oneM2M resource tree.

[[File:Resource-tree3.png]]

==Demonstration==

If you hide the luminosity sensor with your hand for few seconds, you should see the led switched ON by the monitoring application and vice versa.

[[File:Final-result.png]]

2018-03-02T11:49:09Z

Velez: Velez uploaded a new version of File:Real-wiring.jpg

API specification

2018-03-02T11:46:46Z

Velez:

<div class="noautonum">__TOC__</div>

== Demonstration high level architecture ==

[[File:Diagram.png]]

== Prerequisites ==
The following tools are required to run this demonstration.
*JAVA 1.8
*Arduino IDE 1.8.5
*NodeJS

== Download the project ==

Download the oneM2M demo project from Github from the following link:

https://github.com/mbenalaya

The project contains the following folders:
*onem2m-platform
*onem2m-device
*onem2m-app

== Start oneM2M platform instance==
__TOC__
The oneM2M platform is available on folder “oneM2M Platform”

===Configure the platform===
You can keep the default configuration for a local demonstration. The platform will listen on ports 8080 and 8443. The database is reset after each restart.

If needed, you can change the configuration of the platform by editing the file “configuration/config.ini”.

===Start the platform===
Start the platform by executing the "start.bat" script on Windows or "start.sh" on Linux and Mac OS.

[[File:Console.png]]

===Login to oneM2M web interface===
Open the following URL in your browser to access the oneM2M platform web interface:
https://127.0.0.1:8080/webpage
[[File:Login.png]]

Enter "Cae-admin" as originator then click on “connect”.
[[File:Resource-tree.png]]

==Connect your IoT Device==
The arduino source code and required libraries are available on the folder onem2m-device.

===Schematics===
*Breadboard
*Nodemcu board
*LED
*Luminosity Sensor
*1Kohm resistance

Connect the LED and luminosity sensor to the Nodemcu board using:

[[File:Board-plan.png]]

Real wiring:
[[File:Real-wiring.jpg]]

===Download and install arduino IDE===
Download and install the Arduino IDE v1.8.5 from the following link:
https://www.arduino.cc/en/Main/Software

NB: We don’t recommend to use the Arduino Web Editor for this demonstration because the nodemcu board is not supported.

===Add Nodemcu board to Arduino IDE===

Firstly open the Arduino IDE
Go to files and click on the preference in the Arduino IDE

[[File:Arduino-ide.png]]

copy the below code in the Additional boards Manager
http://arduino.esp8266.com/stable/package_esp8266com_index.json
click OK to close the preference Tab.
After completing the above steps , go to Tools and board, and then select board Manager
[[File:Arduino-ide2.png]]

Navigate to esp8266 by esp8266 community and install the software for Arduino.

[[File:Arduino-ide3.png]]

Once all the above process been completed you are ready to program the nodemcu board with Arduino IDE.

===Add Arduino “Timer.h” library===

The “Timer.h” library is available on the zip folder “Timer-master.zip”.

Go to Sketch, and then select “include library”.
Chose the “Add .ZIP library” option

[[File:Arduino-ide4.png]]

Select the zip folder “Timer-master.zip” then confirm.
NB: You don’t have to extract the zip content.

===Configure the oneM2M sketch===
Open the sketch “onem2m-adn.ino” in your Arduino IDE.

Set your WIFI parameters
*const char* ssid = "XXXXXXXX";
*const char* password = "XXXXXXXX";

Set the IP address of the oneM2M platform
*const char* host = "XXXXXXXX";

===Compile the oneM2M sketch===

Click on verify button [[File:Button1.png]] to compile the sketch.

Compilation output:

[[File:Compiliation.png]]

===Upload the oneM2M sketch to Nodemcu board.===

Click on upload button [[File:Button2.png]] to upload the sketch to the nodemcu board .

Upload output:

[[File:Compiliation2.jpg]]

===Debug the code execution using serial monitor===

Cick on [[File:Button3.png]] button to open the Arduino Serial Monitor to display the Nodemcu console.

Then after opening the Serial Monitor select 115200 from the drop-down list.
[[File:Monitor.png]]

===Check IoT device resources on oneM2M web interface===
You should see “mydevice1” Application Entity resource with “luminosity” an “led” containers created on the oneM2M resource tree.

[[File:Resource-tree2.png]]

==Connect your IoT application==
The luminosity monitoring application source code is available on the folder onem2m-app

===Configure application===
Open the file onem2m-monitor.js with a text editor.

Set the IP address of the oneM2M platform. You can keep localhost if you are running the oneM2M platform and the application in the same machine.

===Start the application===

Start the nodejs oneM2M application using the following command:
> node onem2m-monitor.js

[[File:Console2.png]]

===Check IoT application resource on oneM2M web interface===

You should see “mymonitor1” Application Entity resource created on the oneM2M resource tree.

[[File:Resource-tree3.png]]

==Demonstration==
If you hide the luminosity sensor with your hand for few seconds, you should see the led switched ON by the monitoring application and vice versa.
[[File:Final-result.png]]

API specification

2018-03-02T11:45:58Z

Velez:

<div class="noautonum">__TOC__</div>

== Demonstration high level architecture ==

[[File:Diagram.png]]

== Prerequisites ==
The following tools are required to run this demonstration.
*JAVA 1.8
*Arduino IDE 1.8.5
*NodeJS

== Download the project ==

Download the oneM2M demo project from Github from the following link:

https://github.com/mbenalaya

The project contains the following folders:
*onem2m-platform
*onem2m-device
*onem2m-app

== Start oneM2M platform instance==
<div class="noautonum">__TOC__</div>
The oneM2M platform is available on folder “oneM2M Platform”

===Configure the platform===
You can keep the default configuration for a local demonstration. The platform will listen on ports 8080 and 8443. The database is reset after each restart.

If needed, you can change the configuration of the platform by editing the file “configuration/config.ini”.

===Start the platform===
Start the platform by executing the "start.bat" script on Windows or "start.sh" on Linux and Mac OS.

[[File:Console.png]]

===Login to oneM2M web interface===
Open the following URL in your browser to access the oneM2M platform web interface:
https://127.0.0.1:8080/webpage
[[File:Login.png]]

Enter "Cae-admin" as originator then click on “connect”.
[[File:Resource-tree.png]]

==Connect your IoT Device==
The arduino source code and required libraries are available on the folder onem2m-device.

===Schematics===
*Breadboard
*Nodemcu board
*LED
*Luminosity Sensor
*1Kohm resistance

Connect the LED and luminosity sensor to the Nodemcu board using:

[[File:Board-plan.png]]

Real wiring:
[[File:Real-wiring.jpg]]

===Download and install arduino IDE===
Download and install the Arduino IDE v1.8.5 from the following link:
https://www.arduino.cc/en/Main/Software

NB: We don’t recommend to use the Arduino Web Editor for this demonstration because the nodemcu board is not supported.

===Add Nodemcu board to Arduino IDE===

Firstly open the Arduino IDE
Go to files and click on the preference in the Arduino IDE

[[File:Arduino-ide.png]]

copy the below code in the Additional boards Manager
http://arduino.esp8266.com/stable/package_esp8266com_index.json
click OK to close the preference Tab.
After completing the above steps , go to Tools and board, and then select board Manager
[[File:Arduino-ide2.png]]

Navigate to esp8266 by esp8266 community and install the software for Arduino.

[[File:Arduino-ide3.png]]

Once all the above process been completed you are ready to program the nodemcu board with Arduino IDE.

===Add Arduino “Timer.h” library===

The “Timer.h” library is available on the zip folder “Timer-master.zip”.

Go to Sketch, and then select “include library”.
Chose the “Add .ZIP library” option

[[File:Arduino-ide4.png]]

Select the zip folder “Timer-master.zip” then confirm.
NB: You don’t have to extract the zip content.

===Configure the oneM2M sketch===
Open the sketch “onem2m-adn.ino” in your Arduino IDE.

Set your WIFI parameters
*const char* ssid = "XXXXXXXX";
*const char* password = "XXXXXXXX";

Set the IP address of the oneM2M platform
*const char* host = "XXXXXXXX";

===Compile the oneM2M sketch===

Click on verify button [[File:Button1.png]] to compile the sketch.

Compilation output:

[[File:Compiliation.png]]

===Upload the oneM2M sketch to Nodemcu board.===

Click on upload button [[File:Button2.png]] to upload the sketch to the nodemcu board .

Upload output:

[[File:Compiliation2.jpg]]

===Debug the code execution using serial monitor===

Cick on [[File:Button3.png]] button to open the Arduino Serial Monitor to display the Nodemcu console.

Then after opening the Serial Monitor select 115200 from the drop-down list.
[[File:Monitor.png]]

===Check IoT device resources on oneM2M web interface===
You should see “mydevice1” Application Entity resource with “luminosity” an “led” containers created on the oneM2M resource tree.

[[File:Resource-tree2.png]]

==Connect your IoT application==
The luminosity monitoring application source code is available on the folder onem2m-app

===Configure application===
Open the file onem2m-monitor.js with a text editor.

Set the IP address of the oneM2M platform. You can keep localhost if you are running the oneM2M platform and the application in the same machine.

===Start the application===

Start the nodejs oneM2M application using the following command:
> node onem2m-monitor.js

[[File:Console2.png]]

===Check IoT application resource on oneM2M web interface===

You should see “mymonitor1” Application Entity resource created on the oneM2M resource tree.

[[File:Resource-tree3.png]]

==Demonstration==
If you hide the luminosity sensor with your hand for few seconds, you should see the led switched ON by the monitoring application and vice versa.
[[File:Final-result.png]]